Purchase price is not total cost
The real cost includes team time, subscriptions, changes, fixing errors, migration and revenue lost when people cannot understand the offer or complete an action. These costs are scattered and rarely shown in the initial proposal, but they can quickly exceed the difference between suppliers.
Find out where the saving comes from
- Design starts immediately, without objectives or architecture.
- Content is left entirely to the client, without structure or review.
- A visually similar theme is bought even though it does not fit the needs.
- Mobile, accessibility and error states are handled at the end.
- There is no testing, documentation or meaningful account handover.
- Every later change is billed as a separate intervention.
Some compromises can be right for a first version. What matters is that they are explicit. A three-page website with a simple form and no administration may be a good choice. It becomes a poor choice when sold as a flexible platform that will support years of growth.
Debt is not only technical
Fragile code causes errors, but improvised content creates debt too. Pages without a purpose, inconsistently described services and images without rules slow down every campaign. Repair later requires analysis, rewriting, redesign and sometimes migration — precisely the stages omitted at the start.
Dependency on one supplier has a price
If you do not control the domain, hosting, code, design and accounts, changing partners may mean rebuilding. The same happens when the system relies on obscure extensions or has no documentation. Handover should not only be convenient for the supplier; it must be possible for the owner.
Compare scenarios, not only proposals
- What is excluded, and who will do that work?
- What can you update without technical intervention?
- How much does a routine change cost after launch?
- Who owns the assets and how does handover work?
- Which checks are included before launch?
- Can the system support the likely direction of the next two years?
The cheap option is good when it reduces project scope, not when it hides necessary work.