Skip to content
AwakastLet's talk

From an idea to a first version people use, in weeks

We shape the product with you, design the key screens, build it on a solid base and launch it with real users, typically in six to eight weeks.

First step
Idea to first version
Timeline
Typically 6–8 weeks
What you get
Fixed scope agreed before we start

Who it's for

  • Founders with an idea and a budget.

    You know the problem and the people who have it. You need a first version they can use, without hiring a team first.

  • Companies launching something new.

    A new product, a customer portal or an internal tool that has to work properly from day one.

  • Teams who prototyped with AI and want to start properly.

    You've proven the idea with a quick prototype. Now you want a version you can build a business on.

What you get in "Idea to first version"

A fixed scope agreed before we start, delivered in weekly releases you can try yourself.

  • A shaped product.

    The one problem the first version solves, who it's for, and what's in and out. Written down, agreed, and kept small on purpose.

  • Designed key screens.

    The flows people use most, designed with our design partners before we build them.

  • A working product on a solid base.

    Accounts and permissions, data stored safely, payments if you need them, and the integrations the first version can't live without.

  • A launch with real users.

    Analytics in place, so you see what people actually do.

  • Hosting in the EU.

    On our infrastructure or in your own cloud account, with monitoring and backups from day one.

  • A plan for the next three months.

    What to build next, based on what real users did.

How six to eight weeks usually look

  1. Shape (week 1).

    We work through the idea with you, agree the first version's scope and the screens that matter most.

  2. Design and foundations (weeks 2–3).

    Key screens designed, architecture and data model set, accounts and hosting in place.

  3. Build in weekly releases (weeks 3–7).

    Every week you get something you can click through and comment on.

  4. Launch and plan (last week).

    We launch with real users, measure what happens and agree what comes next.

Why it's faster with us

Our engineers work with their own AI agents. Agents write the first drafts of code and tests, keep documentation current and check every release. Engineers decide what to build, review every change and stay accountable for it. You get the speed of AI tools with the care of an experienced team.

After launch

Most first versions keep growing. When they do, a growth team takes the roadmap forward month by month, and hosting and care keeps everything running underneath. If you'd rather take it in-house, we hand over code, data, accounts and documentation.

From an idea to a market-ready product

4.1×

more candidates reviewed per recruiter per day

Recruitment platform, candidate screening

Screening, interview questions and billing for a recruitment product, from concept to a market-ready version in three months.

Questions people ask us

How much does a first version cost?

It depends on what the first version has to do. Every "Idea to first version" has a fixed scope and price agreed before we start, so you know the total in advance.

Do I need designs or a specification?

No. A clear idea of the problem and the people who have it is enough. We shape the rest with you in the first week.

Will I own the code?

Yes. Code, data and accounts are yours from day one.

I already have a prototype built with AI. Do we start from scratch?

Rarely. We look at what you have first; often the right move is our launch readiness review rather than a new build. See From AI-built app to production.

Can you build AI into the first version?

Yes, when it's part of the core problem. We'd rather ship one AI feature that works than five that impress in a demo.

What happens after launch?

You choose: a growth team to keep building with you, hosting and care only, or a full handover to your own team.

Is there any reason not to find out how we'd do it?