The calculation, in order
- Add the website-type base and each selected feature allowance, counting each feature once.
- Multiply by the design factor and technology factor to get the unrounded base scenario.
- Apply the freelancer, studio or agency delivery factor. For an agency, also apply the relevant Neaptide minimum where one is recorded.
- Convert from USD with the fixed currency assumption, then round each final amount once to a whole currency unit.
Freelancer = base scenario
Studio = base scenario × 2.2
Agency = max(base scenario × 5, applicable Neaptide minimum)
Feature allowances are added before the multipliers. A $400 technical SEO allowance therefore changes the final total by more than $400 when the combined factors exceed one.
Website base amounts
| Website type | Model base |
|---|---|
| Landing page | $1,000 |
| Business website | $2,500 |
| Online store | $4,500 |
| Web app / SaaS | $7,500 |
| Content website | $1,500 |
A category is not a fixed page count or a complete product specification. Large catalogs, custom workflows and substantial migrations require separate discovery.
Design and technology factors
| Design choice | Factor |
|---|---|
| Adapted template | ×1 |
| Custom design | ×1.4 |
| Advanced visual design | ×2 |
| Technology choice | Factor |
|---|---|
| No-code | ×0.8 |
| CMS | ×1 |
| React / Next.js | ×1.3 |
| Custom backend architecture | ×1.8 |
The factors express the model’s assumed effort. They do not measure performance, accessibility, security or suitability. A simpler platform can be the right choice when it supports the required workflow.
Feature allowances
| Feature | Allowance before multipliers |
|---|---|
| Accounts & login | $600 |
| Payments | $800 |
| Multiple languages | $400 |
| CRM integration | $700 |
| Admin panel | $800 |
| Blog | $300 |
| Support chat | $200 |
| Search & filtering | $500 |
| Technical SEO setup | $400 |
A checkbox cannot describe every version of a feature. “Payments” may mean a supported checkout connection; subscriptions, refunds, invoicing and unusual tax rules require explicit scoping. The same applies to permissions, migrations and integration failure handling.
A calculation you can reproduce
For a business website with custom CMS design and technical SEO, the model adds $2,500 for the website base and $400 for the selected feature. The formula is:
Studio: $8,932 · Agency: $20,300
The model’s $8,200 agency minimum is below the calculated agency amount, so it does not change this example. Open this exact calculation →
Compare more clearly defined briefs in the worked examples.
Where the inputs come from
Base amounts, feature allowances and multipliers are SiteCost’s internal assumptions inherited from the calculator. No sample of client transactions has been used to validate them. Publishing the arithmetic makes the estimate inspectable; it does not turn the inputs into market evidence.
The model records indicative Neaptide starting prices supplied on September 9, 2026: $2,900 for landing pages, $8,200 for business websites and $14,000 for web apps. These act as floors for the matching agency scenarios. Confirm current terms with Neaptide before relying on them. No Neaptide minimum is recorded for ecommerce or content websites.
The broad delivery categories are useful discussion prompts. Actual proposals can overlap; compare the responsibilities and deliverables, not only the label.
Currency does not adjust for a local market
The model uses fixed conversions: 1 USD = 0.92 EUR, 93 RUB or 7.24 CNY. These are not live exchange rates, and their market date is unknown. Language and currency changes do not alter the underlying scope or model local supplier prices.
Use a current exchange rate and the provider’s agreed currency for an actual proposal. Taxes and local commercial terms are not calculated.
What the estimate leaves out
- Content: writing, translation, photography, product entry and editorial research.
- Migration: auditing an existing website, moving records, content cleanup and URL mapping.
- Operations: domains, hosting, licenses, subscriptions, payment fees, usage charges and ongoing support.
- Complex requirements: AI inference, regulated data, multi-tenant isolation and bespoke backend workflows.
- Commercial terms: taxes, provider availability, rush delivery and contract-specific commitments.
Put these into the brief and first-year budget as appropriate. A blank or excluded item is not a zero cost.
Timeline labels and cost allocations are illustrative planning assumptions. They are not staffing commitments, delivery promises or measured failure probabilities. The model does not calculate a reliability score.
How to cite or challenge an estimate
Include the model version, date accessed, website type, design, technology, selected features, currency and delivery scenario. Keep “model estimate” and the main exclusions next to the amount, so a reader can understand it outside this page.
For example: “SiteCost model 2026-09-09: business website, custom design, CMS, technical SEO; freelancer scenario $4,060 USD for development, excluding content, migration, operating costs and tax.”
Report unclear assumptions or calculation errors to hello@neaptide.ai. Model revisions should change the version and explain their effect on the example results. This editorial review clarifies the existing model; it does not replace its pricing inputs.
Neaptide maintains SiteCost and benefits from inquiries through the tool. See ownership, editorial standards and measurement.