How much does a custom website or automation cost?
There is no package price that fits every brief. Make website, system, and automation proposals comparable by scope and responsibility.
AT A GLANCE
The cost of a custom website, business system, or automation depends on the job to be solved, available content and data, system connections, exceptions, verification, and operation after handover. After a short discovery, I provide an estimate that separates deliverables, assumptions, exclusions, and third-party fees. Without a verified rate card that applies to every brief, I do not publish invented price ranges.
- Compare the same outcome and quality level across proposals.
- List third-party fees, client responsibilities, and exclusions separately.
- Define one complete, real workflow before estimating the work.
Why is there no single package price for every project?
“A five-page website” or “AI automation” does not yet describe the actual work. Scope changes when approved copy and imagery already exist versus when the offer, information structure, content, and measurement plan still need design. The same applies to automation: one reliable rule differs from a workflow spanning systems, roles, exceptions, and human approvals.
A fixed package can be useful when inputs, deliverables, revision rounds, and handover conditions are genuinely consistent. For custom work, an early confident package price often hides assumptions. A useful estimate shows what is known, what is assumed, and which pending decision would change the cost.
What changes the cost of a website or web system?
Research, writing, imagery, page types, multiple languages, forms, search, accessibility, performance, SEO migration, and measurement may all be separate website tasks. A web system can add roles, permissions, case states, migration, administration, notifications, reports, and recovery procedures.
Page count is therefore a weak pricing measure. One complex customer journey may require more design and verification than several simple information pages. Compare delivered page types, functions, states, content ownership, and acceptance criteria instead.
What changes the cost of automation or integration?
The trigger, source-data quality, connected APIs, run frequency, failure handling, duplicate protection, and exception rate all affect the work. A validated field transfer is smaller than interpreting documents, synchronising several systems, or adding approval with financial consequences. AI also requires a test set, quality measurement, human review, and a plan for usage cost.
Keep external subscriptions, transaction fees, and model usage separate from implementation cost. The proposal should show which fees are one-off or recurring, who contracts with the provider, and what happens after a price change or outage.
What belongs in a comparable proposal?
State the objective, deliverables, exclusions, required access and client inputs, decision points, acceptance criteria, schedule, and handover. External licences, hosting, domain, messaging, payment, AI, and other provider fees should appear separately.
“SEO”, “security”, or “testing” alone is not a verifiable promise. Name the output: for example a URL and redirect map, permission tests, invalid-input cases, performance measurements, backup procedure, or operator documentation. This lets you compare responsibility for the same result, not only the final number.
What information supports a useful first estimate?
Describe one concrete situation: who is trying to do what, how it works today, where it stalls, which systems are involved, what counts as done, and which exceptions occur. For a website, include the audience, offer, intended next step, and available content. For automation, show the trigger, input, owner, and output.
Do not send passwords, API keys, or real sensitive customer data for estimation. Synthetic or appropriately anonymised examples are sufficient for initial scope. The first outcome may be an implementation proposal, a narrow paid discovery, or a recommendation to configure an existing product instead. The aim is to clarify the necessary solution, not inflate the project.
A PRACTICAL TEMPLATE
Development proposal comparison checklist
Compare two proposals using the same fields: deliverables, exclusions, acceptance criteria, one-off and recurring fees, handover, and support. The template contains no invented prices.
- Deliverables
- Exclusions and assumptions
- External and recurring fees
- Handover and support
Sources and further reading
- Choose the right tools and technologyGOV.UK Service Manual · Checked: 2026-10-31
- Secure Software Development Framework (SSDF) Version 1.1NIST · Checked: 2026-10-31
Borbély Kristóf
The developer behind Kriside, writing practical guides about web systems, automation, and AI solutions.