Hamza Work

Custom MVP or template website: which does your idea need?

Compare a template business website, a prototype and a custom MVP by user needs, ownership, data, integrations and recurring costs.

Guide details

By Hamza ยท Published 2026-10-22

A brochure website and a working software product solve different problems.

Compare ownership, recurring costs and export rules as well as the initial price.

A concept preview is not a finished customer project or an active subscription.

Start with the customer's next action

If a salon needs customers to read opening hours, view services and make an inquiry, a small website may be sufficient. If staff must manage appointments, permissions, reminders and changing availability, that is an operational workflow. The visual design can look similar while the software and maintenance requirements differ substantially.

When a template is a sensible fit

A predefined template is useful when its sections and editing limits already match the business. Ask which content you can change, what hosting is included, what happens to a custom domain, and how to export your content. A low monthly price cannot reasonably include unlimited manual design work or custom integrations.

When to commission a prototype

A clickable or functional concept can help you test navigation and explain an idea. Confirm whether it uses sample data and whether authentication, payments and integrations are simulated. A prototype should be labeled clearly so a customer cannot mistake an example confirmation for a real order or booking.

When a custom MVP is justified

Discuss custom development when the value depends on specific roles, rules or data that existing tools cannot support well. Examples include a proposal workflow, a customer portal or a specialized internal tool. Start with one complete job, document its boundaries and test the experience with intended users before expanding it.

Compare the whole operating arrangement

Ask about source-code ownership, data portability, hosting accounts, backups, supported devices, third-party subscriptions and post-launch changes. Treat e-commerce, payment processing and personal-data handling as explicit requirements. They should not be implied by a template screenshot or a vague promise of an admin dashboard.

Options at Hamza Work

The website rental page describes a standardized Micro offer and its limits. New rental signups and recurring payments are currently paused. Custom website and SaaS scopes start with a conversation with Hamza. Portfolio records show existing work; the Concept Demos section shows separate examples and prototypes.

Choose by the work the user must complete

  • Option: Template website. Best fit: Present a business and help visitors make contact. Check before committing: Editing limits, hosting, cancellation and export
  • Option: Concept prototype. Best fit: Explore a flow and gather feedback. Check before committing: Sample data and unsupported integrations
  • Option: Custom MVP. Best fit: Test a specific real software workflow. Check before committing: Scope, access control, operating costs and handover

Can a rented website become a custom application later?

Potentially, but the agreement must explain content export, domain ownership and which parts can be reused. Custom software should be scoped and quoted separately; it is not an automatic entitlement of a low-cost template plan.

Is the $2 website rental a custom MVP?

No. It is a limited template offer described on the rental page, with signups currently paused. Bespoke workflows, e-commerce checkout and advanced integrations are outside that Micro scope.