Know who owns the work before it starts

• Primary model

  Own the work

  You bring a product goal or an engineering scope. We take it from plan to production, and keep developing it after launch.

  FitsMigrations, rebuilds, integrations, takeovers and new products.

• Secondary model

  Strengthen your team

  You lead the team and the roadmap. We add senior engineers who work inside it, with our engineering leadership behind them.

  FitsA team short of senior capacity, or of one specific skill.

An engagement can start with one engineer in your team and grow into us owning a migration, an integration or a module.

Agreed at kickoff, before the first line of code. The difference between the two models is who answers for the result.

Technical direction

Own the work Amplire: the architecture and the technical decisions, with the reasoning shared as they are made.

Strengthen your team Your tech lead. Our senior leadership is on hand for the hard calls.

Backlog and scope

Own the work You set the priorities. Amplire turns them into the costed roadmap and keeps it current.

Strengthen your team Your backlog. Our engineers work in your sprints, your tools and your process.

What stays with you

Own the work Product decisions and priorities, and every repository, environment and account.

Strengthen your team Team leadership, process and roadmap, and every repository, environment and account.

Accountability for the result

Own the work Amplire, for the agreed scope: delivery, code quality and production readiness.

Strengthen your team You, for the product. Amplire, for the engineers we add and the quality of their work.

Who you talk to day to day

Own the work The senior engineers doing the work and making the technical decisions.

Strengthen your team Our engineers, in your stand-ups and channels, like the rest of your team.

• The skills the work needs. Backend, frontend, DevOps or an architecture review, rather than one generalist stretched across all of them.
• Composed around the scope. A core engineer from the start; other skills join as needed, in the proportion the work requires.
• Senior leadership stays close. The mix changes with the product’s stage. The people who own the technical decisions stay on it.
• Knowledge is shared. Code, decisions and context are shared, so the product does not depend on one person.

• Core

  Retainer / dedicated capacity

  You reserve an agreed level of engineering capacity each month, and the priorities move as the product does.

  FitsOngoing development and the product’s life after launch.

• Core

  Time & materials

  You pay for the engineering time actually used, on work whose scope cannot honestly be fixed in advance.

  FitsMigrations, legacy systems, complex integrations and takeovers.

• Exception

  Fixed-scope MVP

  A fixed price for a new product’s first version, when its scope can be defined clearly. Retainer or T&M can follow.

  FitsA new product meant to outlive its first release.

Rates and terms come with the estimate, once we have seen your scope.

• Ongoing ownership. The team that built the platform keeps developing it. One has been in production with us since 2018.
• Maintenance and evolution. Upgrades, fixes and new features continue as one stream of work, not a new project each time.
• Handover. Your team can take the platform over.
• Repositories, infrastructure and accounts stay yours. Throughout, under either model. We work with the access you grant.
• No artificial lock-in. Standard, open stacks and nothing held back: if you move on, the whole platform goes with you.