From idea to finished platform: how a platform project works
Key takeaways
- A platform project runs in phases: sharpening the idea, defining the core workflow and roles, a clickable prototype, the MVP, a test phase with real users, launch and further development. Each phase ends with a decision that the next one builds on.
- As the client, you contribute your knowledge of your customers and processes and make the product decisions. The Scrum Guide assigns this to a single person, not a committee.
- You can recognize a project on track by working software that you try out yourself at regular intervals. In the Scrum Guide, a work cycle lasts one month or less, and in a joint review the team and stakeholders inspect the results.
- Before the open launch, a limited group of real users works with the platform. The UK government's Service Manual calls this stage private beta.
As of September 2026
Suppose you have been placing installers with construction companies for years, so far by phone, email and spreadsheet. Now you want to turn this into a platform: construction companies post jobs, installers accept them, and billing runs automatically. You have never commissioned anything like this and wonder what happens between the first conversation and the first real job on the platform. This roadmap shows the phases, your contribution in each of them and how to tell that your project is going well.
It starts with the problem, not the feature list
In the first phase, the idea becomes a clear goal. A good start is one sentence that describes who uses the platform and what problem it solves. The UK government's Service Manual, a guide to building digital services with the phases discovery, alpha, beta and live, advises reframing a predefined solution as a problem. Instead of planning an interactive map of contact points, you ask how people can find the nearest contact point more easily.
Your contribution: you explain how things work today, where they get stuck and what your customers want. Also clarify how the platform should earn money. Our article on revenue models for platforms offers ideas.
The phase ends with the decision on who the first version is built for and what result it should deliver. In the example, that could be: construction companies in one region find a suitable installer within a day.
A core workflow and clear roles give the project direction
In the second step, you define the core workflow together: the path a user takes from the first visit to the desired result. In the example, that is five steps: a construction company posts a job, suitable installers see it, one accepts, the job is confirmed, and then it is billed. Our article on paying out partners explains how the money reaches the installers automatically. Then come the roles, meaning who sees and may do what: construction companies, installers and your own team in the back office.
What is left out for now matters just as much, for example ratings, a dedicated app or the connection to accounting. Your contribution is real cases from everyday business, especially the special cases, such as an installer who cancels at short notice.
Also name one person who makes product decisions. The Scrum Guide, the rulebook of the widely used Scrum framework, calls this role the Product Owner and states: one person, not a committee.
A clickable prototype makes the idea tangible
A clickable prototype looks like the future platform but has no real technology behind it yet. You click through the most important screens, from posting a job to accepting it. For the alpha phase, the Service Manual recommends prototypes that are just complex enough to test ideas. The focus is on the most challenging areas and the riskiest assumptions.
Your contribution: show the prototype to a few real customers and watch where they hesitate. It also works well for conversations with partners or investors. At the end, you decide which version will be built.
The MVP gets the core workflow fully running
The minimum viable product, or MVP, is the first version from which you learn the most about your customers. Founder and author Eric Ries stresses that it is not about creating minimal products. For your platform, this means the core workflow works completely and with real data, from posting a job to billing.
Development happens in short cycles: the principles behind the Agile Manifesto recommend delivering working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale. In the Scrum Guide, such a work cycle (sprint) lasts one month or less. Towards the end, the team and stakeholders review the results together in the Sprint Review and work out what to do next. To close the sprint, the team looks at its own way of working in the Sprint Retrospective.
Your contribution: take part in the demos, try out interim versions yourself and give feedback promptly. Provide texts, prices, images and access to existing systems. What the MVP costs and which running costs follow is covered in our article What does your own platform cost?
In the test phase, real users work with the platform
Before the platform opens to everyone, a small group of real users works with it in their daily business. The Service Manual calls this stage private beta: you invite a limited number of people to use the service so you can get feedback and make improvements.
Your contribution: choose test users who give honest feedback, in the example long-standing customers and installers. At the end of this phase, you decide what still needs to be done before launch and what moves to a later stage.
The launch opens the platform to everyone
At launch, the platform opens to everyone who wants to use it. The Service Manual advises making sure beforehand that your support team can also help users who do not get along with the service right away. On the technical side, the Service Manual lists secured availability and regular quality testing, and once the service is live, monitoring as well.
Your main contribution now is sales: winning partners, inviting existing customers and announcing the launch.
After launch, the platform grows in stages
According to the Service Manual, the live phase is about supporting the service in a sustainable way and continuing to improve it, based on user research and carefully tested. For your platform, this means collecting user requests, ranking them by value and implementing them in stages.
In the example, that could be ratings, an app or the connection to accounting. Your contribution is a fixed framework for further development, in terms of both time and budget.
How to recognize a project that is on track
The best sign of a good project is software you can try out yourself. The principles behind the Agile Manifesto call working software "the primary measure of progress". Good signs are:
- Regular demos: at fixed intervals, you see what is new. The Scrum Guide describes the Sprint Review as a working session, not just a presentation.
- Early test version: you get early access to a test environment and can run through the core workflow yourself.
- Visible priorities: there is an ordered list of open items, and you know what comes next.
- Verified interim versions: according to the Scrum Guide, every interim version is thoroughly verified and usable.
How we work at njudev
Our process starts with concept and architecture: before the AI begins, we have thought through architecture, logic, data model (which data the platform stores and how it is connected) and the technologies used. Then follows AI-powered development, where humans and AI work together. Finally comes review and testing: every output is reviewed by senior developers, tested and approved.
AI handles the routine work. We bring 20 years of experience to the decisions, the details and the delivery. For founders, we also build prototypes for investor meetings, real demos instead of slide decks.
In practice
The booking platform we developed for Wasserplasma Experience shows what a clearly defined core workflow looks like. The brief fit into one sentence: one platform that takes the booking, collects the payment, controls the device and settles accounts, without extra work for the studio team. The real-world test was just as important: the full chain, from booking through device control to payout, has been tested end to end on a real device.
Our own product byclaw.io started with a question rather than a feature list: what does a shop look like when the customer is an AI agent? The answer is an AI shopping agent that is live today, with five agent personalities, a watchlist with price alerts and hallucination protection that only lets real products through. We are looking for partners who want to take byclaw further with us.
Frequently asked questions
How much time should I plan for as the client?
The most at the beginning, when the goal, core workflow and roles take shape, and during the test phase. During development, it is mainly the demos and quick answers to questions. Short lines of communication help: the principles behind the Agile Manifesto state that business people and developers must work together daily throughout the project.
Do I need a complete requirements specification before the project starts?
No. The authors of the Agile Manifesto value "working software over comprehensive documentation". What helps is a clear goal, a description of the core workflow and the user groups, and a first list of what must be there at launch and what can come later. The details take shape together during the project, on the prototype and the interim versions.
What happens if something changes along the way?
That is part of the plan. The principles behind the Agile Manifesto explicitly welcome changing requirements, even late in development. In short cycles, new insights flow straight into the next step.
Conclusion
A platform is best built in phases, from a sharpened goal to further development after launch. In each phase, you contribute your knowledge and make a clear decision. Regular demos and an early test version show you where your project stands. Step by step, your idea becomes a platform that grows with your business.
Do you have an idea for a platform?
Describe it in our AI project estimator. You will receive a free estimate by email, and we will get back to you within 24 hours.
Learn more about our services for platforms and marketplaces and SaaS products. Or simply write to us at our email address.
Sources
- Kent Beck et al.: "Manifesto for Agile Software Development", 2001. https://agilemanifesto.org/
- Kent Beck et al.: "Principles behind the Agile Manifesto", 2001. https://agilemanifesto.org/principles.html
- Ken Schwaber, Jeff Sutherland: "The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game", November 2020. https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf
- GOV.UK Service Manual: "How the discovery phase works", last updated June 21, 2021. https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works
- GOV.UK Service Manual: "How the alpha phase works", last updated May 8, 2019. https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works
- GOV.UK Service Manual: "How the beta phase works", last updated February 19, 2021. https://www.gov.uk/service-manual/agile-delivery/how-the-beta-phase-works
- GOV.UK Service Manual: "How the live phase works", last updated May 8, 2019. https://www.gov.uk/service-manual/agile-delivery/how-the-live-phase-works
- Eric Ries: "Minimum Viable Product: a guide", Startup Lessons Learned, August 3, 2009. https://www.startuplessonslearned.com/2009/08/minimum-viable-product-guide.html