---
title: "How we work"
updated: "2026-11-16"
url: "https://www.etheon.com/company/how-we-work"
---

# How we work

How we work. Six steps from the first conversation to the next release: formulate, design, create, test, launch and improve.

## How we work. Six steps from the first conversation to the next release: formulate, design, create, test, launch and improve.

- Formulate: The problem, the users, the data and how success is measured.
- Design: The product and its architecture, agreed before we build.
- Create: The software and the models, built in short cycles.
- Test: Every change tested and every model evaluated before release.
- Launch: Released to your users in stages, each with a rollback.
- Improve: Real use measured, and the next release planned with you.

### Formulate.

What happens

- The problem and its users, named
- How success is measured, agreed
- The data and the risks, listed

Who leads: Etheon, with you

You receive: Scope document, Success measures, Risk list, Build plan

Ends when: you approve the scope

### Design.

What happens

- The flows and screens, drawn
- The architecture and the models, chosen
- The build plan, agreed with you

Who leads: Together

You receive: Product design, Architecture document, Release plan

Ends when: you approve the design

### Create.

What happens

- Built in short cycles
- Working software shown at each cycle's end
- Your feedback in the next cycle

Who leads: Etheon, with you

You receive: Working software, The code in your repository

Ends when: the agreed scope is built

### Test.

What happens

- Every change tested in the pipeline
- Every model evaluated against the success measures
- Security and performance checked

Who leads: Etheon, with you

You receive: Test results, Evaluation report

Ends when: the release meets the success measures

### Launch.

What happens

- Released to your users in stages
- A rollback ready at each stage
- Your team shown how to run it

Who leads: Together

You receive: Release notes, Runbook, Handover docs

Ends when: every user has the release

### Improve.

What happens

- Real use measured against the success measures
- Issues fixed and models evaluated again
- The next release planned with you

Who leads: You, with us

You receive: Usage report, Next release plan

Ends when: you approve the next scope

[Contact Us](https://www.etheon.com/company/how-we-work?start=1)

## Three ways to work with us. Who leads, from us to you.

### Dedicated team

Dedicated team. A team that works only on your product. You set the priorities; we run the delivery.

What you get

- A product team sized to the work
- One accountable lead
- Weekly demos of working software

[Dedicated team](https://www.etheon.com/company/how-we-work/dedicated-team)

### Fixed-scope projects

Fixed-scope projects. An agreed scope and timeline, fixed before anything starts.

What you get

- A scope written before we start
- A price fixed per milestone
- Your sign-off at each milestone

[Fixed-scope projects](https://www.etheon.com/company/how-we-work/fixed-scope-projects)

### Team extension

Team extension. Our engineers inside your team, in your process and your tools.

What you get

- Engineers in your stand-ups
- Your process and your tools
- The code stays yours

[Team extension](https://www.etheon.com/company/how-we-work/team-extension)

|  | Dedicated team | Fixed-scope projects | Team extension |
| --- | --- | --- | --- |
| Team shape | A whole product team | A team sized to the scope | Engineers who join your team |
| Who leads | Etheon, with you | Together | You, with us |
| How it is priced | by team | by scope | by team |
| Best for | A product with a long roadmap | A clear scope and a fixed budget | More engineers for a team you already run |

## What you can count on. Ownership, quality and security on every engagement.

### Ownership.

The code, the models and the accounts are yours.

### Quality.

Every change tested and every model evaluated before release.

### Security.

How we protect your data and code.

[Trust](https://www.etheon.com/company/trust#security)

### You own what we build. The code, the models and the accounts, in your name.

#### What it is

Ownership is who holds the code, the models and the accounts a project creates. With Etheon it is you: the repository, the cloud accounts and the trained models are in your company's name from the start.

#### What we do

- The code in your name
- The models in your name
- The accounts in your name

#### How we do it

1. Your accounts first: The repository and the cloud accounts are opened in your company's name, or we work in yours.
2. Your repository from the first commit: Every change lands where you can see it.
3. Models in your name: Trained models and their data stay in your accounts.
4. Hand over the keys: Access, docs and runbooks, with nothing left only in our hands.

#### Questions

**What about open-source parts?**

Open-source parts keep their own licences. We list each one in the docs, so your lawyers can check them.

**Can the Lab's own code end up in our product?**

Where it fits, under the licence its repository states. It is listed in the docs like any other open-source part.

**Can another team take over?**

Yes. Everything is in your name, so another team can pick it up from the repository and the docs.

#### What you get

- The repository
- The accounts
- The docs

#### Related

- [Who owns the code](https://www.etheon.com/company/faq#who-owns-the-code)
- [The first release](https://www.etheon.com/solutions/startups?detail=first-release#first-release)

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

### Quality you can check. Every change tested and every model evaluated before release.

#### What it is

Quality is how you know the software does what it should before your users find out it does not. We test every change, evaluate every model before release and release in stages, so a problem stays small.

#### What we do

- Tests in the pipeline
- Every model evaluated before release
- Releases in stages, each with a rollback

#### How we do it

1. Agree what good means: The success measures, and the cases a model must get right, written down first.
2. Test every change automatically: The tests run before a person reviews the change, and a failing test stops the merge.
3. Review every change: A second engineer reads the code before it merges.
4. Compare every model with the last: A new version runs against the same evaluation set as the one before it.
5. Release behind a rollback: In stages, watched, with the previous version one step away.

#### What you get

- Test results for every change
- An evaluation set and its scores
- Release notes
- A rollback plan

#### Stack and tools

- Test frameworks
- Continuous integration
- Code review
- Evaluation sets
- Error monitoring

#### Related

- [Evaluation](https://www.etheon.com/services/ai?detail=evaluation#evaluation)
- [Quality assurance](https://www.etheon.com/services/software?detail=qa#qa)

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

How it starts. Three moves before the first line of code.

- A call.: Tell us your use case and timeline. We reply within one business day.
- A written proposal.: The scope, the team and the plan, in writing.
- [A first sprint.](https://www.etheon.com/company/how-we-work?start=1): Working software at its end, reviewed with you.

- [FAQ](https://www.etheon.com/company/faq): Answers on cost, ownership and timelines.
- [Trust](https://www.etheon.com/company/trust): How we protect your data and code.