Estimated reading time : 4 min · Published
Use the same scope for each proposal
List the pages, languages, journeys and content before comparing amounts. Identify who writes copy, prepares photography, enters products, produces translations and approves facts. A proposal excluding content migration cannot be directly compared with one that includes it. Ask which tests, training and handover documents are included in the quoted fee.
Separate launch requirements from future options. Booking, commerce and membership features each require implementation and ongoing operation. A feature nobody can administer is not a saving.
- Pages and languages.
- Features people will use.
- Provided content and migration work.
- Deliverables, acceptance and support.
Collect recurring and one-off costs
Separate recurring, one-off and variable items, with frequency and scope. Fictional example, not a quote: a €120 annual license costs €360 over three years if its price stays unchanged; do not count it again when a package already includes it. Record renewals, limits, users and consumption assumptions rather than only the promotional price.
Include future changes: a new section, another language, original photography or data migration. Their cost cannot be reliably inferred from page count alone. Obtain a quote for a concrete example and keep the assumptions explaining the figure.
- Amounts on a consistent tax basis.
- Renewals and commitment periods.
- Included usage and variable charges.
- Internal work identified separately.
Compare time horizons without inventing prices
With constant annual amounts, a three-year total equals launch spending plus three years of operation plus planned one-off changes. Where rates differ by year, calculate each year separately. An annual payment does not automatically include all desired interventions.
Fictional arithmetic exercise, not a quotation or market price: launch costs €3 000, hosting €120 per year and maintenance €360 per year. A €300 translation is planned in year 2 and €200 exit assistance in year 3. Each of the three years includes a full operating year. With unchanged amounts on one calculation basis, the total is 3 000 + 3 × 480 + 500 = 4 940 €. A licence already included in maintenance is not added again.
The table explains an addition, not every project’s full cost. Internal time, excess usage or a rate change still need recording where relevant. An unknown expense is not zero: retain it as an item to price and state that the total is partial. When comparing proposals, also check the period’s start, covered durations and deliverables recoverable on exit. Methodological references explain cost categories; they do not supply this exercise’s invented amounts.
- First-year and multi-year totals.
- Confirmed amounts separated from estimates.
- The same usage scenario for each proposal.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Fictional period | Launch | Recurring | One-off | Total |
|---|---|---|---|---|
| Year 1 | 3 000 | 480 | 0 | 3 480 |
| Year 2 | 0 | 480 | 300 | 780 |
| Year 3 | 0 | 480 | 200 | 680 |
| Three-year total | 3 000 | 1 440 | 500 | 4 940 |
Plan exit and keep a decision record
Examine domain, content, files, media, data and support needed for exit separately. Fictional example: two offers show the same three-year total, but only one includes media handover and migration assistance; the comparison remains incomplete until that gap is costed. Check recoverable formats and responsibilities before concluding that one proposal is cheaper.
Keep the selected scope, justified amounts, total, limits and an owner for each item in a short decision document. The agency’s indicative budgets, domain and hosting guide and handover guide help prepare questions. The final written proposal defines the commitments.
Reference documents
- DGCCRF : Information sur les prix (France) · Source consulted
- Cabinet Office : Architecture Principles, Total Cost of Ownership · Source consulted
- Government Digital Service : Managing technical lock-in · Source consulted
Content updated on
Documented reference points for this topic
| Reference | Value or syntax | Scope |
|---|---|---|
| WordPress · Tools Export | WXR / XML | A WordPress content export can include posts, pages, post types, comments, custom fields and taxonomies. Its scope depends on selected filters. Check media files, theme, plugins and configuration separately before treating it as a complete migration. |
| Shopify · Exporting products | CSV UTF-8 · Image Src | Product images are not embedded in the CSV. During import into another store, their URLs must still be accessible. Retain the original store until product, variant and image associations have been checked; inventory has a separate export. |
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
