Native or cross-platform? Three questions decide it
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
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.
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.
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 |
A team that works only on your product. You set the priorities; we run the delivery.
More on Dedicated team.
Team extension, also called staff augmentation, puts Etheon engineers inside your own team, working in your process, your tools and your stand-ups.
More on Team extension.
A fixed-scope project agrees the scope and the timeline before anything starts, then Etheon builds to that scope.
More on Fixed-scope projects.
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.
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.
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.
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.
With three moves before the first line of code:
The models side by side, with the six steps, are on How we work.
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
Migration moves your systems off your own servers to the cloud you choose, in planned waves, each workload with a rollback point.
The business keeps running: we audit the old system, wrap it in tests, replace it one module at a time with a rollback at each step, then switch it off.