Building a productized web design service on a fixed scope
A productised website offer sells one defined thing at one price: these pages, this many revisions, delivered in this window. It works only if the scope is genuinely fixed and the delivery is repeatable. The trick is to design the package around what your tools do reliably, then say no, kindly, to everything else or price it as an add-on.
Design the package from the tool outwards
A productized web design service is profitable when the same steps produce the same quality every time. So start from what Anticode's design engine builds dependably and turn that into the menu, rather than promising features you'd then have to improvise.
| Part | In the package | Add-on or not offered |
|---|---|---|
| Pages | Home plus up to four of: Services, About, Pricing, FAQ, Work, Contact | Extra pages as an add-on |
| Look | One of the seven design systems, one action colour, light, dark or the system's own theme | Custom brand design isn't offered |
| Forms | Contact form, emailed to the client | Booking calendar, newsletter, connectors as add-ons |
| Content | Client supplies copy and photos; you edit | Copywriting as an add-on |
| Revisions | One consolidated round | Further rounds at a fixed fee |
| Launch | Published to the client's domain on a paid plan | Domain purchase and email setup stay with the client |
| Selling | Buy buttons that open the client's payment link | Not offered: a shop with stock, member logins, booking deposits |
The selling row matters. Anticode's stores take payment through payment links, published sites have no visitor accounts, and bookings have no deposits or calendar sync. Name these on the sales page so the wrong clients don't buy.
One design system, chosen in the kickoff
Offer the seven design systems as a choice, not a blank canvas: Editorial, Technical, Luxury, Playful, Brutalist, Organic and Swiss, each with one font family and one action colour from a set of eight. Show the client an example of each at kickoff and ask them to pick one. That one decision replaces most of the open-ended design back-and-forth that sinks fixed-price work. The build is then held to that system, and the Critic's nineteen design checks run on every page.
The delivery sequence
- Day 1: kickoff. A short call: business facts, pages from the menu, design system, action colour. Send the content list with a deadline.
- Content deadline. Late content moves the delivery date; say so in the terms.
- Build. Describe the business to Anticode with the chosen pages and look. Review the Architect's plan against the package before saying "Build it". Paste in the client's copy, and add their photos as hosted addresses in a CMS collection (work or products) (or upload them if the build is an app).
- Your own check. Run the release checklist, which runs every publish check without publishing, and read every page on a phone.
- The revision round. One client review link, comments tied to sections, one consolidated list back. Each item becomes a sentence-sized change request or a direct edit.
- Launch. Connect the client's domain on a paid plan, test the contact form on the live site, and send the handover note.
Pricing and plans
Your package price is yours to set; Anticode's own plans are on the pricing page. Two decisions to make before you publish a price: whose account the site runs on (yours on a Team or Agency workspace, or the client's own), and whether ongoing hosting is part of the package or a separate monthly fee. Agency plans add white-label client sites with no Anticode branding.
Saying no without losing the client
- "Can we add a blog?"
- Offer CMS collections for posts as an add-on, and be clear there are no comments, RSS or scheduling.
- "Can it be in Welsh too?"
- Not offered: pages are in English.
- "Can customers log in?"
- Not on a published site. Point to a specialist tool or a custom build.
- "Just one more round"
- At the add-on price, quoted before you start.
What goes wrong
- The package is too broad. If every project needs a custom conversation, it isn't productised. Narrow the menu.
- Content arrives late and the window slips. Hold the line in the terms; delivery dates run from complete content.
- Add-ons are priced by feel. Write them down with fixed prices so every client hears the same answer.
How you know the package works
Most projects finish inside the delivery window with one round, add-ons are sold at their listed price, and your hours per project are roughly the same each time. Track hours for the first ten; if they vary widely, find the step that does and fix it in the package.
Limits
Anticode supplies the builder, design systems, review links, change requests and publishing. It doesn't sell your package, take payment from your clients, write their copy or manage the delivery calendar. For outreach, see selling websites to local businesses; for the paperwork, the website proposal; for running sites afterwards, a maintenance retainer.
Questions people ask
What should a fixed price website package include?
A defined page list, one design choice, a set number of revision rounds, a delivery window that starts from complete content, and a clear list of what isn't included.
Can I sell Anticode sites under my own brand?
Agency plans make client sites white-label, with no Anticode branding. Paid plans already drop the free badge.
How fast can a productised site be delivered?
The build is quick; the content and the revision round set the pace. Most packages promise a window that starts when content is complete.