Digital product development
Digital Product MVP
A focused first version of a platform, portal, directory or internal tool—built properly, deployed, and ready to be tested with real users.
Best for: Entrepreneurs and organisations validating a focused digital platform, portal, directory or internal business tool.
- Pattni community price
- From £1,999
- Standard price
- From £3,500
Scoped per project
Community pricing is available to members of the Pattni community and is confirmed during the project application process. Standard pricing applies to everyone else, with the same delivery standard either way.
The approach
What an MVP actually is
An MVP is a deliberately focused first version containing the smallest useful set of features needed to test the idea and deliver the principal user outcome.
Focused does not mean unfinished. Everything in the agreed scope is designed, built, tested and deployed to the same standard as any other Pattni Digital project. The discipline is in what the first version deliberately leaves out, so you learn from real usage before committing budget to features nobody has asked for yet.
Best for
Examples
The kind of products this suits
Each of these can be reduced to one principal user type and one core workflow, which is what makes a focused MVP possible.
- Supplier directory
- Member directory
- Customer portal
- Event-registration system
- Internal business tool
- Basic booking platform
- Simple marketplace
- Business dashboard
Scope
What the starting scope may include
The final scope is agreed in the proposal. This is the shape of a tightly defined MVP engagement.
- Initial discovery session
- Requirements and agreed MVP scope
- Basic wireframes
- Responsive interface
- User registration and login where required
- One principal user type
- Database setup
- One core user workflow
- Basic dashboard
- Basic administration
- Transactional email foundations
- Testing
- Deployment
- Handover
- 30 days of bug support
How the price is set
Delivery
How the project runs
The same five stages apply, with discovery and requirements carrying more weight than they do on a website build.
Understand
We discuss the business, audience, goals and required outcome.
Define
We agree the scope, deliverables, timescale and price.
Design
We establish the structure, content hierarchy and visual direction.
Build
The website or product is developed, reviewed and tested.
Launch
The final product is deployed, handed over and supported.
Delivery guidance
Typically six to ten weeks for a focused MVP after scope approval, but the exact schedule will be included in the proposal. Treat the range as an indication of shape rather than a commitment: the proposal is the document that sets the dates.
Boundaries
Explicitly outside the starting scope
Naming these up front is more useful than discovering them mid-project. Any of them can be quoted as part of a larger engagement.
- Native iOS application
- Native Android application
- Multiple complex user roles
- Live chat
- Advanced subscription billing
- Marketplace split payments
- Large data migration
- Complex reporting
- Extensive external integrations
- Unlimited features
- Unlimited revisions
- A full Shaadi Source-scale platform
Sizing
Two products, two very different quotations
A worked comparison, because the difference between an MVP and a platform is easier to see with an example.
Focused directory MVP
One user type, a searchable listing, a single core workflow and basic administration. This kind of product may fit the starting scope, and the proposal confirms it.
Multi-sided marketplace
Claiming, subscriptions, favourites, comparison tools and advanced administration involve several user types and many interacting workflows. That is a larger bespoke project with its own scope, schedule and price.
Questions
Digital Product MVP questions
Why is the price a starting figure rather than fixed?
Because the honest cost of a product depends on what it has to do. Two directories can differ by a factor of three once roles, permissions, payments and administration are considered. The starting price reflects a tightly defined MVP, and your written proposal sets out the actual scope and price before anything is committed.What happens to the MVP after launch?
You own it. The 30-day bug-support period covers defects in the delivered scope, and further development — new features, additional user types, integrations — is scoped and quoted as the next phase once you have real usage to learn from.Can the MVP grow into a full platform?
That is the intention. An MVP is built on production-grade foundations, so the second phase extends the same product rather than replacing it. What the second phase should contain is a decision best made after real users have used the first.Do I need my requirements written before I enquire?
No. A description of the problem, who it is for and what a successful outcome looks like is enough to begin. Turning that into requirements and an agreed MVP scope is part of the discovery work.Will there be a mobile app?
Not within this scope. The MVP is a responsive web application that works properly on a phone. Native iOS and Android applications are outside the starting scope and would be quoted separately.
Next step
Have a product idea worth testing?
Describe the problem, who it is for and what a successful first version would do. We will come back with the most sensible MVP scope and a proposal.