---
title: "From an idea to a first release: how a startup project starts"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/from-an-idea-to-a-first-release"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# From an idea to a first release: how a startup project starts

We scope, build and launch the first version of your AI product in stages, in your accounts, and then the next one.

We scope, build and launch the first version of your AI product, and the next one: a fixed scope first, then your team, or ours.

## What do you hold after each stage?

Each stage leaves you holding something, from a problem to a backlog for the next release:

| Stage | You hold |
| --- | --- |
| Idea | A problem |
| Scope | A scope and a plan |
| Prototype | A prototype users have tried |
| First release | An app in your accounts |
| Next release | A backlog for the next one |

The journey is drawn on our [Startups page](https://www.etheon.com/solutions/startups#journey).

## What goes into a scope?

A scope is the written agreement on a first release: the problem it solves, the users it serves, what it includes and leaves out, and the measures that say it works. We write it in five steps:

1. Hear the idea: who it is for, the problem it solves and what you already know.
2. Talk to users: short interviews, or a look at the data you hold, to test the problem.
3. Cut the scope: what the first release must do, and what waits for the next.
4. Check feasibility: the data, the models and the risks, tried on a small prototype.
5. Write it down: the scope document, its success measures and the build plan, for your approval.

You receive a scope document, success measures, a risk list and a build plan. [A scope you can hold](https://www.etheon.com/solutions/startups#scope) is on our Startups page.

## What if we only have an idea?

That is where most scopes start. We work from the problem and the people who have it, and a prototype tests the idea before anything is built for real.

## What if the scope shows the idea will not work?

You learn it before the build, not after. We say so plainly and suggest what would work instead.

## Can we build it ourselves after the scope?

Yes. The scope document and the build plan are yours, written so any team can build from them.

## How does the first release reach users?

In stages, each with a rollback, the code and the accounts in your name. A release in stages puts the first version in front of a few users, then more, so a problem is found while it is small and the version before is one step away.

1. Set up your accounts: the cloud, the repository and the app stores, in your company's name.
2. Build in short cycles: working software at the end of each cycle, reviewed with you.
3. Release to a few: the first users get it first, with a rollback ready.
4. Widen the release: more users at each stage, once the last one holds.
5. Hand over: the repository, the docs and the accounts, with your team shown how to run them.

You receive an app in your accounts, the repository and the docs. More on [a first release in stages](https://www.etheon.com/solutions/startups#first-release).

## What risks do founders bring, and how is each answered?

| The risk | How it is answered |
| --- | --- |
| Building the wrong thing. | A prototype real users try before we build. |
| Running out of runway. | A fixed scope for the first release. |
| Hiring takes too long. | A team from the first week. |
| A code base you cannot take over. | Your repository, your accounts, docs from day one. |

The risks are answered on our [Startups page](https://www.etheon.com/solutions/startups#risks).

## What comes after the first release?

Phase two: your team, or ours. Phase one is a fixed scope (scope, design, build, first release); then we continue with [team extension](https://www.etheon.com/company/how-we-work/team-extension), which puts Etheon engineers inside your own team, or [a dedicated team](https://www.etheon.com/company/how-we-work/dedicated-team), a team that works only on your product. [How we start](https://www.etheon.com/solutions/startups#how-we-start) is set out on our Startups page.

## Which startups have we built for?

Jeriko and Kuest AI are client work Etheon built for startups, each named with the client's permission: Jeriko, a team of personal AI agents, and Kuest AI, an AI tutor that teaches step by step. Their stories are on [Work](https://www.etheon.com/work).

Tell us your use case and timeline. We reply within one business day.