Cross-platform development can share significant logic, but release and device requirements still matter.
Some ideas need
a product, not a page.
Apps are treated separately from website packages because a repeat-use product introduces product strategy, authentication, data, release, device and operational decisions that can change the scope dramatically.
Book. Pay.
Track.
A repeat-use customer product can keep service, payment and status in one branded experience.
Customer operations
Welcome back.
Price follows the
product decisions.
That is why apps use discovery and a custom quote rather than being forced into the £599 website tier.
Customer-only, staff-only and multi-role products have different security and data requirements.
External services and business-critical workflows increase implementation and testing scope.
Admin tools, APIs, databases, reporting and automation are part of the product even when customers never see them.
Build the smallest
useful product first.
A good MVP is not the cheapest possible collection of screens. It is the smallest version that can test the real user and business assumptions.
User, problem, business model and product constraints.
Core journeys, roles, screens and backend responsibilities.
Interaction and usability before expensive implementation decisions.
Core product, data, authentication, integration and quality testing.
Web deployment or store release, analytics and roadmap evidence.
Scoped around the product.
Never forced into £599.
Dedicated mobile work sits outside the website tiers. The estimator narrows a realistic custom range from the actual users, workflows and platforms selected.