Build the essential path
An authorised customer submits a request, staff review it and update its status, and the customer can see the result. Agree access and acceptance checks.
Product Engineering
Startup Lab
Develop the first version of your product around a complete customer task. We define the scope, design the workflow and build a release you can test with users, with operating costs planned before launch.
FROM IDEA TO FIRST RELEASE
Move from an idea to a product people can use
We turn the product idea into decisions about users, the first workflow and the work worth funding. You review the scope and assumptions before development begins.
01
A product idea still needs a defined user, task and reason to change an existing habit.
02
The first release should test the most important assumption, not attempt every feature at once.
03
Data, integrations and operating costs can change what is practical to build first.
04
Early user feedback helps decide what to improve before a larger investment.
What each stage produces
The exact deliverables and order are agreed for the product.
First-release scope
Target users, their task, important assumptions and a first-release boundary.
Design and prototype
Key journeys, information structure and a prototype where it helps validate decisions.
Working product
Agreed workflows, data model, integrations and quality checks in a usable release.
Documentation and handover
Architecture, deployment and operating information needed by the responsible team.
Post-launch insights
Usage events, operational issues and customer feedback collected under the agreed data and access rules.
Next priorities
A review of what users did, what failed and which change deserves investment next.
Example first release / B2B service portal
Choose what the first paying customer actually needs.
A service business launches a customer portal with a small operations console. Start with a complete request-to-delivery workflow and keep later automation out of the first release.
Keep a deliberate manual step
In this example, staff schedule the work and issue invoices through existing tools. Automated dispatch, advanced billing and AI can follow when demand supports them.
Plan life after launch
Identify required support, hosting, licences and paid APIs alongside the build. Review usage, problems and customer feedback before expanding the scope.
The first release, technical lead, ongoing costs and deferred work are agreed around your budget and product.
How we work
How the first release takes shape
We organise product analysis, design, engineering, testing and release. You bring the market knowledge and make the business decisions at agreed review points.
Define the first release
Break down the business hypothesis, users, data and constraints. Identify what the first release needs to test and what remains unknown.
Design the user workflow
Design the key journeys, system boundaries and an interactive model where it helps validate decisions.
Build and review
Build and test the agreed release in stages. Review working software against the scenarios and acceptance criteria.
Prepare the launch
Prepare the environment, data, release checks, user onboarding and the documentation needed for handover.
Engineering stack
Technology chosen for the product
We choose the stack after reviewing target devices, existing systems and the team that will operate the product. Each choice affects integration work, release planning and ongoing costs.
Web
Choose a browser interface when customers and staff need access without installing an application.
React
Next.js
TypeScript
Mobile
Assess mobile features such as camera access, notifications and offline work before choosing shared or native code.
React Native
.NET MAUI
Swift
Kotlin
Desktop
Consider a desktop application when work depends on local files, connected equipment or operating-system features.
Avalonia
Electron
C++
Qt
Backend
Define where business rules run, how integrations fail and who maintains the services after launch.
Node.js
.NET
Python
Data
Choose storage around records, transactions and reporting, with an agreed migration and recovery plan.
PostgreSQL
MSSQL
Redis
Infrastructure
Agree deployment access, monitoring and backups, then separate hosting charges from development and paid support.
AWS
Azure
Docker
AI / ML
Add AI where a defined task and review set can establish whether it helps. Include source access and usage costs in the scope.
OpenAI
Claude AI
RAG
Partnership
Choose what to build first
Discuss a separate assessment, a defined module or a phased team engagement. Full custom software projects start at USD 50,000. For a smaller scope, describe the intended result and available budget; we first confirm fit, then agree deliverables, price and schedule.
Product assessment
- One user workflow and the assumption to test
- Inputs, retained tools and integration questions
- First-release scope and explicit exclusions
- Acceptance scenarios and unresolved risks
- Cost assumptions and a next-stage decision
First working module
- Core functionality
- Interface design
- System integrations
- Deployment and analytics
- Agreed deliverables and acceptance criteria
From idea to launch
- Cross-platform solution
- Server infrastructure and administration
- Monitoring and analytics system
- Load testing
- Support scope agreed separately
The proposal sets deliverables, exclusions and payment terms. Paid support is required during operation; its coverage and price, hosting and third-party services are budgeted separately.
Common questions
Questions about your first release
How is project cost determined?
We estimate the first customer workflow, including design, integrations, testing and launch. The proposal states assumptions and exclusions, with development and operating costs separated. Full projects start at USD 50,000; a smaller assessment or module needs its own agreed scope.
Can you adapt to non-standard requirements?
Yes. We examine unusual business rules, integrations and device requirements, then test the uncertain parts before committing to implementation. You review the options and their effect on scope, cost and delivery.
Should we start with a discovery phase?
Start with an assessment when unresolved workflows, data or technical constraints prevent a useful estimate. We agree its price and outputs first, then document the findings, first-release scope and questions that still need answers.
Who owns the code after project completion?
The agreement defines ownership, repository access and third-party licences before development starts. Handover includes the agreed source code, deployment materials and operating documentation. We plan any technical walkthrough and continuing support with the receiving team.
How do you handle changes during development?
We assess the affected work and show the change in cost and schedule. You decide whether to include it now, replace another item or defer it. The agreed scope and acceptance checks are updated before implementation.
Can we sign an NDA before sharing details?
Yes. We can agree an NDA before confidential details are shared. An initial conversation can cover the business goal and constraints while the terms are being settled.
Do you work with international clients?
Yes, in Europe, the USA, Canada and Australia. We agree overlapping working hours, demonstrations and review dates, with written decisions so delivery can continue between calls.
How can you help after the MVP launches?
Paid support is required while the product operates. Before launch, we agree coverage, response responsibilities and price. We use operational issues and customer feedback to plan subsequent releases, with new features estimated separately.
Plan the first release
Turn the idea into a first release worth testing
Tell us who the product serves and what they need to do. We will help define a scope, budget and delivery plan.
Start a project