Analysis
MVP launch check
Your prototype works in the demo. We review one user journey and identify what is missing before your next launch.
Implementation / Backend development & data architecture
VAT-exempt under section 19 of the German VAT Act
Build an MVP
We turn a clearly scoped product idea into a first usable web application, with one core journey, an interface and a backend.
US$11,199.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- Define and develop one core flow with up to six views and three data objects
- Integrate up to two roles and a suitable authentication method
- Connect up to one documented external API with two endpoints
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- A limited first web application for the agreed core flow
- Documented feature status, test evidence and clear next steps
Included
- Define and develop one core flow with up to six views and three data objects
- Integrate up to two roles and a suitable authentication method
- Connect up to one documented external API with two endpoints
- Core-flow and access tests plus deployment to a test environment
- Hand over source code, operating requirements and prioritised open extensions
Excluded
- Unlimited feature catalogue, native apps and complex marketplace logic
- Guaranteed product-market fit, revenue or investment readiness
- Custom AI model training, a payment platform or ongoing operation
Which projects does this service suit?
Suitable if …
- A product idea should be tested through a usable first version
- Initial scope can be consistently limited to one core flow
Not suitable if …
- A complete platform product should be created at an entry price
- Audience and basic benefit remain entirely unresolved
Possible overlaps with: Build a web application interface, Integrate accounts and permissions, Build a backend feature. If you enquire about these services for the same project, we check for duplicated work before commissioning. Your selection also shows a notice.
What this covers
How does a product idea become a first version people can actually use?
An MVP is a deliberately limited initial product version. It makes one specific core flow usable so you can test an important assumption. The package combines interface, storage and required backend logic within clear limits. It is more than a clickable design but not a complete platform.
Before development, we select the core flow and necessary functions. Up to six views, three data objects and two roles define the framework. If the flow does not fit, we redefine the first version together.
The smallest useful flow is the key product decision
An MVP can be small, but its core flow must work end to end. A user should complete the relevant task and reach a clear outcome. Loading and error states, storage and access control therefore belong even in a first version.
The product assumption being tested must be identified beforehand. Technical completion does not prove customers need the offer or will pay. Handover separates implemented functions, open assumptions and possible later extensions.
Does this sound familiar?
An idea needs a usable test
A prototype shows interaction but not real data flow. A limited first application can make the core process testable in its intended context.
The wish list exceeds the first step
Prioritisation is part of preparation. We narrow scope to one testable task rather than creating every function superficially.
An existing design needs implementation
An established audience and flow can provide the basis. Missing backend rules and operating needs are still addressed explicitly.
How we approach it.
Define the core assumption and scope
We describe the first usable flow and acceptance criteria. Views, objects, roles and any integration are clearly limited.
Develop a connected version
Frontend and backend are implemented as a complete core flow. Relevant errors, storage and access belong to the first version.
Hand over test status and next work
The application is tested and deployed in a test environment. Documentation separates existing functions, operating needs and open product assumptions.
After handover
A finished MVP is a technical and business work state, not confirmation of economic success. Actual usage must still test its underlying assumptions.
Interface, authentication and backend logic included in the project do not need separate packages for the same core flow. Extensions outside the boundary are decided separately.
Describe the intended function and an example of a successful process. Name existing systems and the roles involved without sharing real customer data or credentials.
After your enquiry, we clarify which data the function processes, which rules it must follow and which systems it must contact. Required documents and test access are agreed separately.
Terms used in this service
What does that mean?
- MVP / first product version
- An initial usable version with deliberately limited scope. It enables testing of a specific product assumption and is not shorthand for a complete product.
- Core flow
- The connected task the first version should support reliably. It links entry, processing and a clear completion.
- Product assumption
- A statement about need or usage still requiring verification. Technical implementation can enable testing but does not automatically validate it.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Is design included?
Practical design of agreed views within an existing or agreed simple visual framework is included. Complete brand development is excluded.
Can the MVP be developed further?
Yes. Source code and technical documentation are handed over. Later requirements may still require changes to the initial data model or integrations.
Is an AI function possible?
A clearly limited integration can be assessed as the agreed external API. Custom model training and uncontrolled autonomous flows are outside this package.
Is the product launched publicly?
The package includes test deployment. Public launch requires approved content, legal and operational prerequisites and a separately agreed publication commission.
Is an MVP launch check also necessary?
Development includes its own relevant tests. A separate check may serve a different purpose; identical checks are reviewed for overlap before commissioning.
When does work begin?
We confirm the start and delivery deadline in writing after reviewing your documents. The agreed scope and complete source data determine the schedule.
Which access is needed?
A specific audience, testable product assumption and prioritised core flow Responsible decisions about functions, content and required provider access Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
Planning a customer portal: who may see which process?
From repair status to document links: define which data customers may see, who maintains it and how to test access boundaries.
Read the guide ↗Related services
These may fit too.
Ongoing support
Develop an existing application
Continue developing your existing application across frontend and backend within a prioritised development block.