Translate package names into observable work
For each item, ask who supplies the content, who enters it and how completion is checked. “SEO included” could refer to basic metadata or a broader programme; “contact form” does not explain delivery testing. A page allowance also says little about the number of distinct layouts. Put these differences into a written comparison rather than filling the gaps with assumptions.
Include operation and the next change
Separate one-off production from hosting, support, paid services and future changes. Establish which costs continue, which can vary and what happens when the package limit is reached. A transparent smaller package may be preferable to an apparently comprehensive one whose essential tasks appear later as extras. Compare the same intended release in every proposal.
A practical check before you buy
Send each supplier the same sample service page, editing task and enquiry flow. Ask them to mark each as included, optional or outside scope, with the evidence they will provide at handover.
| Decision | What to consider | What to check |
|---|---|---|
| Content | Writing or insertion? | Name the responsible party |
| SEO | Which specific tasks? | List actual deliverables |
| After launch | Which recurring work? | Separate charges and limits |
An illustrative business scenario
A UK business comparing proposals should ask whether quoted totals and recurring charges use the same tax assumptions, without treating this guide as tax advice.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.