Services/Discovery phase

Discovery Phase

Before the budget goes into code, we find out what exactly has to be built, on which technologies, in what order and for how much. You get requirements, an architecture, a plan and an estimate you can act on.

Where discovery starts

Three starting points. The result, however, is the same: a plan you can build from.

You have an idea

You know the problem and the people who have it. What the product should do on day one is still open.

What you get
  • A list of features with priorities
  • Requirements written down and agreed with you
  • A first estimate of time and budget

You have a specification

The document exists, but nobody has checked whether it can be built for the money you have.

What you get
  • Gaps and contradictions found before development
  • A technical approach and a stack, with the reasons
  • An estimate for each part

You need an MVP

The full product is too big to start with. The question is what to leave out.

What you get
  • The smallest version that is still useful to a user
  • A list of what waits for the second release
  • An architecture the full product can grow from

What we do during discovery

Six kinds of work, usually in this order. Discovery is analysis and planning, so no screens are drawn and no code is written yet.

Market analysis

Before anything is planned, we look at what already exists. In particular, we study the competing products and the ready-made solutions, and see what they do well and where they fall short. As a result, you know which features users already expect and where your product can be different. Sometimes it also shows that a part of the product can be bought instead of built.

Documentation review

If you already have a specification, a presentation or notes, we read them first. Engineers check whether each requirement can be built and whether the requirements agree with each other. Therefore gaps and contradictions are found on paper, before they turn into code. If the product replaces an existing system, we also study how that system works.

Requirements gathering

We ask questions until it is clear what the product must do, for whom and in what order. Then we write the answers down as requirements that can be checked. Each one gets a priority, so it is clear what goes into the first version and what waits. You approve the list before we move on.

Technology stack

The stack is chosen for the task, not the other way round. Therefore we look at the load you expect, the platforms you need, the systems the product has to work with and the stack you already have. Then we propose the languages, the frameworks and the cloud, and explain the reasons for each choice. Because the reasons are written down, another team can understand them later.

Architecture

The architecture shows which parts the system consists of and how they talk to each other. We plan it for the first version, but also check that the full product can grow from it. In addition, we name the risks: what can go wrong, how likely it is and what we do about it. As a result, expensive decisions are made before the code is written.

Time and budget planning

When the requirements and the architecture are agreed, we break the work into stages. Each stage has dates and also a result you can check. Then we estimate every stage and send you the estimate in writing. You approve the plan and the budget before development starts.

What you get at the end

Six documents. They are yours, and any team can build from them.

Market overviewWhat existsThe competing products and ready-made solutions, with what they do well and where they fall short.
RequirementsWhat is builtWhat goes into the product and, just as important, what does not.
ArchitectureParts and stackThe parts of the system, how they talk to each other and which technologies they are built on, with the reasons.
RisksNamed up frontWhat can go wrong, how likely it is and what we do about it.
PlanStagesStages with dates, so you can check the result at the end of each.
EstimateIn writingA written estimate for every stage. You approve it before development starts.

Have an idea or a specification?Send it to us. We will then tell you how long the discovery phase takes and what you get at the end.

Start a discovery
Client's testimonial
We turned to the 24Gen team when the project was in a critical stage. Deadlines were looming, and the product was far from ready. From the very beginning, we were impressed by the team's professionalism and accountability. In a short time, they assembled an MVP, set up scrum processes, and introduced an AI-based solution for moderation. Despite tight deadlines, all key modules were delivered on time and with solid quality. We are very satisfied with the collaboration and confidently recommend 24Gen as a reliable partner for large-scale projects.
Max AdamsInvestor
Watch the video

Engagement models

Three ways to work with us. We help you pick one on the first call.

Dedicated TeamLong projects, open scope

Our engineers work as an extension of your team, under your lead or ours.

orFixed BidClear scope, fixed budget

We agree on the scope, the price and the deadline before the work starts.

orTime & MaterialsScope that changes

You pay for the hours worked and change priorities whenever you need.

Questions about the discovery phase

Did not find yours? Ask us directly.

Ask a question

Do we need a discovery phase at all?

+

If the scope is clear and written down, no: we estimate it and start. Discovery pays off when the idea is still open, when the specification has never been checked by engineers, or when the budget does not cover everything you want.

How long does it take?

+

It depends on the size of the product, so we name the time and the price of the discovery phase itself after the first call.

Who takes part from your side?

+

A project manager and a team lead. Discovery is analysis and planning, so there is no design work in it.

Can we take the result to another team?

+

Yes. The documents are yours, and they are written so that any team can build from them.

What if discovery shows the idea is too expensive?

+

Then you learn it before the development budget is spent. We show what a smaller first version would cost and what it would leave out.

How do you estimate the cost?

+

After the first call we break the task into parts and send you a written estimate. When the scope is clear, we fix the price and the deadline. When it is open or likely to change, we work on time and materials or as a dedicated team.

Do you sign an NDA?

+

Yes, whenever you need one, before you tell us about the product.

Tell us about your product

Describe the task in a few lines. We will get back to you to set up a call.

info@24gen.space
 






    PDF, DOC, DOCX, JPG, GIF, PNG — up to 20 MB