SoulGait / calculators
Website scope planning calculator
Assess website scope across pages, integrations, bookings and content migration. See a weighted breakdown, worked examples and planning guidance.
The working tool
Build a scenario.
A page count alone is a poor measure of effort. This planning tool gives separate weight to the content footprint, external connections, transactional journeys and migration work. It helps you compare two versions of your own brief before seeking a proper estimate.
Know the inputs
What the calculator measures.
Use the result to identify questions for discovery. A 10-page practice site with a complex booking and payment journey may take more work than a 30-page information site. The weights make that difference visible, but they cannot predict implementation hours without a feature specification.
Read the inputs before changing them.
Start with a measured value where one exists. Where it does not, run a low, expected and high scenario rather than treating one guess as a forecast.
| Input | Meaning and practical check |
|---|---|
| Approximate page count | Count planned public URLs, including service, profile and resource pages. Do not count a reusable template as a single page if every URL needs distinct content. |
| Integration complexity (1–5) | Choose 1 for a simple form or email connection. Choose higher levels when several APIs, data mappings, permissions or recovery flows are needed. |
| Commerce / booking complexity (0–5) | Use 0 if no transaction occurs. A high level fits multi-provider availability, deposits, subscriptions, payouts and cancellation rules. |
| Content migration complexity (0–5) | Use 0 for a new site. Increase it for existing URLs, media libraries, redirects, taxonomy changes and structured content to preserve. |
Transparent method
Formula and worked examples.
The calculation is transparent and uses only the fields above. It does not import market benchmarks, current prices or external account data.
A worked example
With 12 pages, integration level 2, booking level 1 and migration level 2, the contributions are 24 + 36 + 22 + 20 = 102 points. The components are more useful than the total: integration and booking account for 58 of those points.
Compare three versions of the same decision
These figures are examples with illustrative inputs, not expected results for your business. Change the form above to use your own numbers.
| Scenario | Assumptions | Modeled output |
|---|---|---|
| Lean brochure site | 8 pages · level 1 integrations · no booking or migration | 34 points |
| Illustrative practice site | 12 pages · level 2 integrations · level 1 booking · level 2 migration | 102 points |
| Complex practitioner platform | 25 pages · level 4 integrations · level 4 booking · level 3 migration | 240 points |
Put it to work
How to use the estimate.
A calculator helps when its assumptions lead to a specific next action. Use this three-step check before committing budget or building a product.
Map journeys
List what a visitor, practitioner and admin must do, including exceptional states such as failed payments or cancelled sessions.
Separate versions
Score a minimum viable scope and a later-phase scope with the same assumptions. Note what each extra feature contributes.
Request estimates
Provide the journey map, content inventory and integration list to a developer. Ask for discovery, build, migration and QA estimates separately.
Where the number can mislead
The numerical weights are SoulGait editorial assumptions for comparison; they are not market benchmarks. Reusable components, content quality, regulatory review, accessibility, multilingual content and the condition of existing systems can materially change effort. There is no defensible conversion from score to price or weeks.
Straight answers
Frequently asked questions.
Does a higher score mean the site will cost proportionally more?
No. The score has no monetary unit. Two projects with the same score can differ because of design originality, integrations, security requirements and existing assets.
Should every industry or city get its own page?
Only when that page answers a genuinely different user need with substantial distinct information. A large count of near-identical URLs is not useful scope.
How do I choose an integration level?
Write down the systems, data exchanged, authentication, failure handling and who owns the connection. Simple one-way notification is lower complexity than two-way synchronisation.
What is included in migration?
Typical migration work includes content mapping, media, URLs and redirects, metadata checks, QA and ownership of old-to-new page decisions.
Can I use this as an agency quotation?
No. Use it to prepare a clearer brief and compare alternatives within one project, then obtain an estimate against written requirements.