Skip to content

Guides · · 4 min read

Dedicated team, team extension or a fixed scope: which fits?

A dedicated team fits a long roadmap, team extension a team you already run, and a fixed-scope project a clear scope, a fixed budget and a date to meet.

By Etheon

On this page

A dedicated team fits a product with a long roadmap. Team extension fits a team you already run that needs more engineers. A fixed-scope project fits a clear scope, a fixed budget and a date to meet. Those are our three ways to work with you, with one process behind them.

How do the three compare?

Engagement model

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 is a dedicated team?

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

  • The team: a tech lead, software engineers, AI engineers, a product designer and a QA engineer, all working to your product owner.
  • What you get: a product team sized to the work, one accountable lead, and weekly demos of working software.
  • When it fits: a product with a long roadmap, no in-house team yet, or a team needed faster than hiring allows.

More on Dedicated team.

What is team extension?

Team extension, also called staff augmentation, puts Etheon engineers inside your own team, working in your process, your tools and your stand-ups.

  • What stays yours: the code (everything our engineers write for you is yours), the process (your way of working, kept as it is) and the roadmap (your priorities, set by you).
  • The terms: a minimum term agreed with you before the engineers start; notice the same for both sides, set in the contract; billing by team, for the engineers on your team; working hours that overlap with yours.

More on Team extension.

What is a fixed-scope project?

A fixed-scope project agrees the scope and the timeline before anything starts, then Etheon builds to that scope.

  • What is fixed: the scope, written before we start; the timeline, agreed per milestone; the price, fixed per milestone; acceptance, by your sign-off.
  • What you receive: a written scope with its milestones before the work; working software at each milestone during it; the code, the docs and the accounts, in your name, at the end.
  • When it fits: a clear scope, a fixed budget and a date to meet. When it does not: a product still finding its shape, whose scope will change as you learn.

More on Fixed-scope projects.

How is each one priced?

By engagement model: a dedicated team and team extension by team, a fixed-scope project by scope. We do not publish prices. We take on projects of every size, from a first release to a long roadmap: share your budget in the brief, and we tell you plainly which engagement model it fits.

How long does a project take?

It depends on the scope. We agree the timeline in writing before work starts, and on a fixed-scope project it is fixed milestone by milestone.

Can we start with one model and move to another?

Yes. With a startup we start with a fixed scope for the first release (scope, design, build, first release), then continue with team extension or a dedicated team. Where we start depends on the stage:

Stage

What you want

We start with

Startups

A first release

A fixed scope

Scale-ups

A product that keeps up

Engineers in your team

Enterprises

AI in the systems you run

A security review

The stages are compared on Solutions.

What stays the same in all three?

Ownership, quality and security on every engagement. The code, the models and the accounts are yours. Every change is tested and every model evaluated before release. And one process sits behind all three: six steps from the first conversation to the next release, formulate, design, create, test, launch and improve.

How does it start?

With three moves before the first line of code:

  1. A call. Tell us your use case and timeline. We reply within one business day.
  2. A written proposal. The scope, the team and the plan, in writing.
  3. A first sprint. Working software at its end, reviewed with you.

The models side by side, with the six steps, are on How we work.

Published
Category
Guides
Reading time
4 min read

More news. What else Etheon has shipped.

Get started with Etheon

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

Services

Six services, one firm.

All services

Research index

Every paper, milestone and release from our Lab.

Browse all research