Built like an enterprise.
Certified like one.
- You own the code
- NDA signed before work starts
- Profiles in 48 hours to 1 week, depending on project type
Trusted ISO Certified Company
Choose how you want to work with us
Every project is different, so we offer five engagement models. Tell us your goal, your stack and your team, and we will recommend one. If another model fits better than ours, we will say so.
DEDICATED DEVELOPER
One senior engineer, full time on your product
- Works only for you
- Reports to your tech lead and joins your standups
- Follows your sprint cadence
- Minimum 3 months
Best for ongoing work
DEDICATED TEAM
A self-managed team for a longer roadmap
- Engineers, a tech lead
- a project manager and QA
- Usually three to six people
- Owns delivery against your roadmap
- Minimum 6 months
STAFF AUGMENTATION
Vetted engineers added to your team
- One to ten engineers
- Billed hourly or monthly
- Scale up or down as needs change
- No long-term commitment
PROJECT-BASED BUILD
A defined outcome, planned and delivered by us
- Scope, plan and milestones agreed up front
- We manage delivery
- Handover and documentation at the end
- Quoted after we review your requirements
SUPPORT RETAINER
Monthly capacity to keep a live system healthy
- Fixes, updates and small changes
- A team that already knows your system
- Move up to a larger team later
Compare the models
Pricing is quoted per engagement. Contact us for a quote.
Each models in detail
Dedicated developer
How it works: One senior engineer works full time on your product. They report to your tech lead, attend your standups and ship in your sprints.
Best for: Ongoing feature work, a product with an established roadmap, or a role you would otherwise hire in-house.
Not right if: You need a whole team, or you have nobody who can set priorities and review code.
You get: A named engineer, your tools and processes, and a minimum 3-month engagement.
Dedicated team
How it works: A cross-functional team of engineers, a tech lead, a project manager and QA works on your roadmap. The team is self-managed: it plans, builds and tests, and you set direction and priorities.
Best for: Products that will run for many months, or work where continuity and shared knowledge matter.
Not right if: The roadmap changes every week with no owner, or the work is a single defined deliverable (see project-based build).
You get: A stable team, a lead who is your point of contact, and a minimum 6-month engagement. Team size depends on the technology and scope.
Staff augmentation
How it works: We add one to ten vetted engineers to your existing team. They work in your tools, report to your engineering manager and follow your priorities.
Best for: Filling a specific skill gap, adding capacity for a release, or sprint-based work.
Not right if: You do not have a lead who can direct and review the work.
You get: Engineers billed hourly or monthly, the freedom to scale up or down, and no long-term commitment. Profiles in 48 hours to 1 week, depending on project type.
Project-based build
How it works: We agree the scope, plan and milestones, then plan and deliver the work. You review progress at each milestone, and we hand over code and documentation at the end.
Best for: A defined outcome, such as a new application, an integration, a migration or a redesign.
Not right if: Requirements are still unclear. We recommend a short discovery first, or a dedicated team.
You get: A written scope, milestone reviews and a handover. Pricing is quoted after we review your requirements.
Support retainer
How it works: You reserve monthly capacity for a team that knows your system. We use it for fixes, updates and small changes.
Best for: Live websites, applications and integrations that need reliable care after launch.
Not right if: You need large new features. Move to a dedicated team or a project-based build for those.
You get: A team that already knows your system, and the option to scale up later.
Mixing and switching
Start small, change as you grow Most clients do not stay on one model. A common path is a project-based build to launch a product, then a support retainer to keep it healthy, then a dedicated team when the roadmap grows. Others start with staff augmentation for a skill gap and move to a dedicated team. Each piece has one clear owner, and we agree changes in writing. Link: Not sure how to choose? Read our guide: dedicated team vs staff augmentation vs project model (/dedicated-team-vs-staff-augmentation-vs-project-model/)
Work under NDA
Most of our client work is confidential Most of our work is under NDA, so we cannot publish client names or project details. On a call we can describe relevant examples for your technology and model, within what each client has approved.
Engagement models FAQ
What is an engagement model, and how is it different from a pricing model?
An engagement model decides who does the work and who manages it. A pricing model decides how you pay. We explain both, then quote after reviewing your requirements.
Which model should we choose?
Choose staff augmentation to fill a gap under your own lead, a dedicated developer or team for ongoing work, a project-based build for a defined outcome, and a support retainer for a live system. Tell us your goal and we will recommend one.
Who owns the code?
Your company, under the signed contract. We recommend keeping repositories and cloud accounts in your organisation.
Can we switch or combine models?
Yes. Many clients start with one model and move to another as the work changes. We agree changes in writing.
How is pricing decided?
Pricing depends on the model, the technology and the seniority you need. Every project is different, so we quote after reviewing your requirements.
Not sure which model fits?
Tell us what you are building, your stack and your team. We will recommend a model and send a quote. If another model suits you better than ours, we will say so.
- Free, no-obligation AI audit
- Reply within 1 business day
- NDA on request