Initiative 01 — Productised packages: a website you can buy without a long negotiation
Why CodeXon is turning its most requested work into three fixed-scope packages, what each one will contain, what it deliberately leaves out, and how a published price will be arrived at rather than invented.
01The problem with quoting from a blank page
A bespoke quote is honest but slow. The client has to explain everything, we have to infer the rest, and the number that comes back is a guess dressed as a price. Fixed scope fixes the conversation before it starts: the client reads what is included, decides, and we begin with the agreement already made.
A package is not a cheaper version of the work. It is the same work with the edges drawn in advance.
02The three packages being designed
Each one maps to something people already ask us for. They are described here as designed scopes; none is on sale yet, and the wording below is what we are working towards.
- Website Launch — a new multi-page business website: structure, design, build, copy placement, analytics, and a launch day with the domain and mailboxes confirmed.
- Redesign Sprint — a fixed window spent on an existing site: an audit of what is broken or slow, a revised layout for the pages that matter, and the fixes shipped rather than handed over as a document.
- Care Plan — a monthly slot after launch: updates, monitoring, small changes, and a short written summary of what was touched.
03What a fixed scope will always include
The parts of the work clients cannot see in a screenshot are the parts most often cut when a scope is vague. They will be written into every package so they cannot be quietly dropped under time pressure.
- Responsive layouts checked on phone, tablet and desktop before launch.
- Accessibility basics: keyboard focus, readable contrast, labelled forms.
- Page-speed budget agreed before the first component is built.
- Search metadata, social preview cards and structured company data.
- A handover that a different developer can follow without a phone call.
04What a package deliberately leaves out
Exclusions are the honest half of a package. Anything below moves a project to custom scoping, where the estimate is written from scratch and the client approves it before work starts.
Out of scope for a package: payment flows and checkout, bookings with inventory, user accounts and permissions, native mobile apps, data migrations from a legacy system, and content writing we cannot fact-check.
05How the price will be set, not invented
We will not print a number we cannot defend. Each package price comes from an hourly rate the studio owns, multiplied by the hours a scope actually takes — measured on real work, not guessed from a competitor's page. Until that rate is configured, anything we quote to a client is expressed as estimated hours and an agreed scope, and we say so plainly.
06How the first year will be validated
The design is only good if a stranger can read the page and understand it. The validation plan is deliberately small — three enquiries, then a rewrite.
- Weeks 1–3
Draft
Write the scope, exclusions and delivery list for all three packages. Nothing published.
- Weeks 4–8
Test
Quote three real enquiries from the draft alone and record every question the page failed to answer.
- Weeks 9–12
Revise
Rewrite the pages, publish the price for the package that survived testing, and keep the other two in draft.