Make the offers comparable first
Collect pages, functionality, content, editing and support in one requirements list. Two proposals cannot be compared fairly if one includes writing and ongoing edits while the other covers development only. Mark those differences before comparing amounts.
Separate ownership and access from payment too. Identify delivered files, controlled accounts and exit conditions. Do not assume all subscriptions impose identical restrictions or every project purchase grants identical rights.
Create a calculation without guessed items
Choose a common comparison period and list development, continuing services and expected changes. Use actual proposal figures. An unknown cost is unknown, not zero. Do not include future growth or sales as if guaranteed.
A simple structure is project cost plus recurring costs over the period plus separately commissioned changes. For an ongoing fee, establish what the fee actually covers. The worksheet supports comparison but does not replace contractual conditions.
| Comparison | Ask both alternatives |
|---|---|
| First delivery | Are scope and quality equivalent? |
| Recurring costs | Which services and dependencies are covered? |
| Changes | Which work is commissioned separately? |
| Exit | What happens to files, content, accounts and operation? |
Try two usage scenarios
A small company with a stable offer may need few design changes but still require hosting and factual updates. A team publishing monthly campaigns may need regular production regardless of how the original site was paid for.
Record the tasks your team handles and those needing external help. A low starting cost may omit work from the comparison. A large first delivery might also include things you do not need. Choose around actual tasks rather than the model’s name.
Record the decision and unresolved questions
Before commissioning, ask owners to confirm delivery, access, support and changes. Keep unresolved items explicit. A reasonable choice should be justified through needs, responsibility and reviewed conditions. There is no general rule that one model is always cheaper or better. Use the cost guide for the wider project budget and the handover guide for what the receiving team needs. This comparison focuses on payment and service scope, making it easier to identify which remaining questions belong elsewhere.