Web design terms

Before you hire a web designer: how I work, in plain words

Before you hire a web designer, you should know everything that usually hides in the fine print: who owns what, what you pay for and to whom, how the work goes, and what happens if something goes wrong. I'm a small business web designer, and I'd rather you know all of this before we start.

This is general information about how I work, not legal advice.

In short

Five things to know

Your domain, hosting, email and the site itself are in your name. I work in your account as an invited member, and you can remove me at any time.

You know the price before work begins, and it doesn't change unless the job does.

One third up front, the rest when the site is ready. Once you've paid in full, the site, the code and all rights to them are yours.

Every month you pay me only for what you chose yourself (support, or a mailbox with my support), and you can cancel with one message.

I don't promise what nobody can guarantee: first place on Google, a legal guarantee of accessibility, perfect security.

Hosting

What your site runs on

Free hosting in your own account, with its honest limits.

Your site runs on Cloudflare Workers, on the free plan, in your own Cloudflare account. The limits are 100,000 requests a day and 10 ms of processing per request. The database (Cloudflare D1) holds up to 500 MB and handles 5 million row reads and 100,000 row writes a day. For a small business website, that is plenty.

If your site ever grows past the daily limit, Cloudflare answers with an error until the end of the day. The paid plan costs $5 a month, paid by you directly to Cloudflare, and I never turn it on without your consent.

Backups: the database keeps its own history for 7 days on the free plan and 30 days on the paid one, so it can be rolled back to any minute.

The honest risk: this is someone else's free plan, and Cloudflare can change its terms. If that happens, I'll tell you and offer options. The code isn't tied to Cloudflare forever and can move to another host.

Your domain is bought in your account through Cloudflare Registrar, at cost with no markup: about $10 to $15 a year for a .com. Your contact details are hidden from public WHOIS by default. If a renewal fails, ICANN rules give you a grace period and then another 30 days to restore the domain.

The contact form is protected from bots by Cloudflare Turnstile, for free. No WordPress, no plugins, no analytics, no tracking cookies and no cookie banner. Email comes in four options, from free to team email with Google or Microsoft.

Sources: Cloudflare Workers limits · Cloudflare Workers pricing · Cloudflare D1 limits · D1 Time Travel · Cloudflare Registrar · WHOIS redaction · ICANN: expired domains

Email options →

Ownership

Own your website, from the domain to the code

What is yours, what is mine, and when it changes hands.

The domain is yours from day one: you are its registrant, and ICANN describes your rights and duties as its owner. It can move to another registrar no sooner than 60 days after registration; that is ICANN's rule, not mine.

The Cloudflare account is yours, on your email, and you are its Super Administrator. I get the Administrator role: I can see everything the site needs, but not your billing details, and I can't manage members. The role technically allows turning on paid services; I never do that without your written consent. You can remove me at any time: Members, then Revoke.

The site and the code: under US law, a website built by a contractor is not a work made for hire, so I remain its author until the rights are transferred in writing. Our agreement says exactly that: all rights to the code and design I make for you pass to you once you've paid in full. Until then, the site lives on my account, and you see it through a preview link.

Open-source libraries I use stay under their own licenses (MIT, for example), and you get them on the same terms.

Your texts, photos and logo stay yours. You confirm you have the right to use them: photos taken from the internet without a license can't go on your site.

Portfolio: before I show your site in my portfolio, I'll ask your permission.

Sources: ICANN: registrant rights · ICANN Transfer Policy · Cloudflare account roles · 17 U.S.C. 101 · 17 U.S.C. 201 · 17 U.S.C. 204

Process

Step by step: what you do and what I do

1. You tell me in the form what you need, in your own words. I reply within one business day and ask a couple of questions.
2. Together we agree on what is included, the price and the timeline. I send a one-page agreement, and you accept it by replying “I agree.”
3. You create a Cloudflare account on your email, buy the domain with your card (about $10 to $15 a year, paid directly to Cloudflare) and invite me as a member. I walk you through every click.
4. You pay one third.
5. You send everything that should be on the site: texts, photos, details and access. Access is given by invitation; nobody passes passwords to anybody.
6. I build the site on my account and show it to you through a preview link that search engines can't see. You can look at it at any time. Three rounds of changes after the preview are included.
7. You pay the rest when the site is ready.
8. I move the site to your account, connect the domain, set up email if you chose it, and hand over the admin panel (you set your own password), a short guide and the code: as a repository on your GitHub or as an archive.
9. You remove my access, or keep it for support.

Payment

Prices and payment

The prices on the web design page are complete: they include everything I charge for the work described there, with no hidden fees. Third parties you pay directly and separately: the registrar for the domain and, if you choose it, Google or Microsoft for team email.

Starting prices are valid until December 31, 2026. The support price holds for a year from your site's launch.

Anything beyond what we agreed, I price before starting and do only after your yes.

You can pay by card (through Stripe; I pay the card fee of about 2.9% plus 30 cents, so you pay exactly the listed amount) or by Zelle, at the same price. To be honest about protection: a credit card payment has an official dispute process, while Zelle has no buyer protection. Choose whichever you're more comfortable with.

Taxes: in California a custom website is a service, and no sales tax applies to it. If you're a business paying me $2,000 or more by Zelle in 2026, you may need Form 1099-NEC, and I'll give you a Form W-9 for it. When you pay by card, the payment processor reports it, and you don't need to do anything. Individuals paying for a personal site need no forms. This is general information, not tax advice.

Sources: California: hidden fees · CFPB: card disputes · Zelle terms · CDTFA: websites · CDTFA Regulation 1502 · IRS: Form W-9 · IRS: paying contractors · IRS: 1099 instructions

See prices →

Timelines

Timelines and rounds of changes

As a small business web designer, I name a timeline for every package. It holds if, within that time, you send me everything the site needs: texts, photos, access and details. I start working right away, without waiting for all of it.

Three rounds of changes after the preview are included in the price. One round is one list of changes you send me at once for the version I showed: texts, photos, colors, the order of blocks. A new design, new pages or new features aren't a round of changes; I price them separately before starting. If something doesn't work the way we agreed, that's my mistake, and fixing it doesn't use up a round.

Cancelling

If you change your mind

You can cancel the order at any time, with one message.

Before work begins, I refund the upfront third in full.

After work has begun, I refund the upfront third minus the reasonable value of the work already done, and I send you the calculation in writing.

Unpaid work stays on my account and isn't handed over. The domain and the Cloudflare account stay yours either way.

Sources: California Civil Code 1671

Monthly

Monthly support and email, with no traps

Support is $19 a month: small changes up to three hours a month, I keep an eye on the site so it always works, and I answer within one business day. A mailbox with my support is $6 a month per mailbox.

I turn them on only after you clearly agree, and I email you the terms and how to cancel.

Every month you get an invoice with a link to pay it. There is no automatic charge to your card.

You can cancel at any time with one message. I confirm the cancellation in writing, and no more invoices come; I finish the month you've paid for.

The support price holds for a year from your site's launch. If it changes after that, I'll tell you at least 30 days ahead.

A mailbox with my support can move to your own account at any time, with all your mail.

Sources: California B&P Code 17602 · 15 U.S.C. 8403 (ROSCA)

Promises

What I do and what I don't promise

Accessibility, privacy, search and security.

Accessibility: I build to WCAG 2.2 level AA and check it. The US Department of Justice says business websites must be accessible, but there is no single binding technical standard for private websites, and in California the Unruh Act gives at least $4,000 per violation. So I give no legal guarantee: compliance also depends on what you add to the site later.

Privacy: every site I build has a privacy policy page. California law (CalOPPA) requires one on any commercial website where Californians leave a name or an email. My sites have no analytics and no tracking cookies; if you add them later, the policy needs an update. The CCPA applies to businesses with at least $26,625,000 in yearly revenue or data on 100,000 people or more, so a small business is usually outside it.

Search: as a small business web designer, I set up everything that depends on the site: titles, descriptions, speed, a sitemap and connection to Google and Bing. I don't guarantee a place in the results: nobody can, as Google itself says, and the FTC has gone after companies that promised first place. I don't do paid advertising.

Security: I follow best practices (https, a protected form, security headers, no plugins), but my sites haven't had an independent security audit.

Sources: DOJ: web accessibility · California Civil Code 51 · Civil Code 52 · CalOPPA · CCPA · CCPA threshold · Google: Do you need an SEO? · FTC

Independence

I'm an independent contractor

I run my own business as a small business web designer: my own tools and accounts, my own schedule, several clients at a time. Our agreement is a contract for services, not employment.

California's freelance worker law asks a California business that hires a freelancer for $250 or more to put it in writing: the services, the amount and the payment date; with no date, payment is due within 30 days of completion. I send such an agreement to every client, whatever the amount or the state.

Sources: California Labor Code 2775 · Labor Code 2776 · California SB 988

Agreement

The agreement

One page in plain words: what I'll do, the price, the payment schedule, the timeline and what I need from you, three rounds of changes, the transfer of rights after full payment, what happens if you cancel, and whether I may show the site in my portfolio.

You accept it by replying “I agree” to my email. Under the federal E-SIGN Act and California's electronic transactions law, that counts as a signature, including for transferring copyright.

My liability under the agreement is limited to what you've paid me, except where the law doesn't allow limiting it: fraud, willful misconduct or breaking the law.

The agreement follows California law.

Sources: 15 U.S.C. 7001 (E-SIGN) · California Civil Code 1633.7 · MRIS v. AHRN (4th Cir. 2013) · California Civil Code 1668

Disputes

If something goes wrong

First we write to each other: most things get settled in a message or two.

If we can't settle it, California has a small claims court, with no lawyers needed: claims up to $12,500 for individuals and $6,250 for businesses.

I never hold your site hostage: the domain and the account are yours no matter what, and a dispute about money doesn't touch them.

Sources: California CCP 116.221 · CCP 116.220 · California Courts: small claims

After launch

After launch

Your site works without me.

You can move to another developer at any time: the code and the data are yours, and the database exports with one command.

Your materials left with me after the move, I delete, and I keep the copy made for the move no longer than a week.

If you're ready to hire a web designer who works by these rules, tell me what you need.

Tell me what you need →