What a custom business platform costs to build
Most quotes for a custom platform arrive without arithmetic behind them. This page shows the arithmetic. It sets out the conventional cost of building a connected business platform — site, commerce, CRM, automation, dashboards, search infrastructure — the engineering hours behind each range, and where an AI-accelerated delivery model changes the number and where it does not.
- Small system
- $40k–$120k conventional
- Mid platform
- $150k–$400k conventional
- Full operating system
- $700k–$1.5M conventional
- Basis
- Hours × blended rate, shown
How software is normally priced
Agency and in-house pricing both reduce to the same formula: estimated engineering hours multiplied by a blended rate, plus project management, design, QA, content and a risk margin. In the United States a blended agency rate of $120–$220 per hour is typical for senior work; a small in-house team lands lower per hour but carries recruiting time, benefits and management overhead. Every range below states the hours it assumes so you can substitute your own rate.
- Marketing site with real structure, capture and tracking — 250–600 hours
- Commerce or quote-to-order flow with accounts and order states — 500–1,200 hours
- CRM, lead routing, notifications and attribution — 400–900 hours
- Search infrastructure: metadata, schema, sitemaps, content system — 300–800 hours
- Automation, scheduled jobs and approval governance — 400–1,000 hours
- Executive dashboards and measurement — 300–700 hours
Three honest bands
These are ranges, not quotes. Scope, integrations and data quality move them more than anything else. A quote for your business follows a written assessment, not a phone call.
- A focused system — site, capture, CRM, tracking: roughly 350–900 hours, about $40,000–$120,000 conventionally
- A mid-sized platform — commerce or quoting, accounts, automation, reporting: roughly 1,200–2,500 hours, about $150,000–$400,000
- A full operating system — multi-brand, content engine, governed automation, intelligence layer: roughly 4,000–6,500 hours, about $700,000–$1,500,000 including design, content, QA and delivery management
Where the number comes down, and where it does not
AI-accelerated delivery compresses implementation: scaffolding, migrations, repetitive interface work, tests and content structure. It does not compress the parts that decide whether a platform works. Architecture, data modelling, security review, editorial standards, integration negotiation with third parties, and the judgement of what to build first still take human time — and those are the hours that protect the investment.
- Compressible: implementation, boilerplate, migrations, test coverage, documentation
- Not compressible: architecture, security and privacy review, integrations, editorial accuracy, decisions about sequence
- Result: a shorter calendar and a smaller team, with the same discipline — not a discount on thinking
Proof of concept: our own platform
We did not model this on someone else's project. The platform running this website is our own build, and its measured scope is public on our case study page: roughly 174,000 lines of application code, 180-plus public routes, about 100 database migrations, a governed automation layer and an approval-first content system. Rebuilt conventionally, that scope maps to roughly 4,150–6,400 engineering hours — about $350,000–$960,000 in engineering alone, or $720,000–$1,500,000 with design, content, QA and delivery management included.
- Scope figures are counted from the repository, not estimated
- Cost figures are hours × published rate ranges, shown so you can check them
- A working platform proves capability; it does not predict your results
How an engagement actually runs
Every engagement follows the same four steps, in the same order. We do not start building before the architecture is agreed, and we do not agree architecture before we have seen the evidence.
- Diagnose — a Business X-Ray of what is publicly observable, plus your own numbers where you have them
- Architect — a written current-state and target-state map, with the sequence and effort behind each step
- Build — implemented in priority order, with each phase usable before the next begins
- Measure — tracking, dashboards and a review rhythm so decisions come from evidence
What we will not tell you
We will not promise a ranking, a lead volume, a conversion rate or a revenue figure. Anyone who does is guessing. What we will do is show you the arithmetic behind any projection, label what is measured versus estimated, and tell you plainly when something is unknown.
Common questions
- Why do quotes for the same project differ by 5x?
- Usually because they assume different scope, or because one includes design, content, QA, tracking and handover and the other does not. Ask for the hours and the assumptions behind any number, including ours.
- Is a cheaper AI-assisted build lower quality?
- It can be, when nobody reviews the architecture, security or accuracy. We treat AI as delivery leverage under human review, and we keep the same non-negotiables: tests, security policies, accessibility, measurement and documented ownership.
- What does an assessment cost before any build?
- A free Business X-Ray covers what is publicly observable. A paid written architecture assessment follows, priced to scope, and it is yours to keep whether or not you build with us.
- Who owns the code?
- You do, along with the accounts and data. Nothing important should live only with your vendor.