Project outsourcing where we deliver your scope and you accept each milestone

Project outsourcing with us means you hand over the delivery and keep the decisions. Every two weeks, a demo shows you what the team built.

Abstract 3D illustration of a scoped stack of blocks moving past milestone markers to a finished releaseAbstract 3D illustration of a scoped stack of blocks moving past milestone markers to a finished release

Project delivery

What do you hand over when you outsource a project?

You hand over an agreed scope, and a team delivers it end to end. We plan the work, staff the team, test it and release it. You decide what the product does and sign off each milestone. Nobody on our team reports to you day to day, so there is no project manager or engineer for you to direct.

Project delivery is one of the five ways we work with clients, and they differ in who runs the day-to-day work. With a tech lead and a working process of your own, you would be better off adding engineers to your own team instead. If you own the backlog and want to reorder it as you learn, a dedicated team we manage fits better.

Abstract 3D illustration of a defined block of work handed to a delivery team and returned as a finished productAbstract 3D illustration of a defined block of work handed to a delivery team and returned as a finished product

Fit check

Is this the right model for your project?

The result can be described

You can say what the product does, who it is for and what has to work on day one, well enough to plan it. If that is still fuzzy, run discovery first.

No tech lead on your side

That's fine. We direct the engineers and run the delivery, so that job never lands on your desk.

One party answering for delivery

We are responsible for the delivery, and we commit as a company to the scope and the timeline.

Not a fit: your priorities keep moving

On an agreed scope, each shift in priorities becomes a change request, and when the order of work changes every sprint, those pile up. A team that works to your current order suits that better.

Not a fit: you need one missing skill

If your team runs well and lacks one skill, say a mobile engineer, buying a whole delivery is more than the problem needs.

Abstract 3D illustration of shaped recesses and matching pieces: checking a delivery model against your needsAbstract 3D illustration of shaped recesses and matching pieces: checking a delivery model against your needs

Price types

Fixed price or time and materials?

Neither price type is the safe one. What decides it is how well you can describe the outcome today, before a line of code. The price itself follows the size of the project, since a bigger project takes more time, and we quote it once discovery has produced the scope and the estimate.

Fixed price per milestone

Each milestone is priced from what discovery produced. It suits an outcome you can describe well enough to plan in detail.

It asks you to settle the scope up front and keep to it. The price covers what was agreed.

Time and materials pricing

Best for a scope you expect to learn about as you build, when your first users will show you what matters next.

You pay for the time the work takes and see it at each bi-weekly demo. If it will pass the discovery estimate, we say so there, and you approve a revised estimate before we go on.

Send us the result you want built

Write a few lines about the product and who it is for, and we will tell you whether discovery should come first.

Delivery process

How a project runs from discovery to handover

The build starts from discovery that sets the scope and estimate, then runs milestone by milestone with bi-weekly demos. Discovery is where the risky parts get found, so it normally comes before the build is priced.

  1. STEP 1

    Discovery

    An architect, a business analyst and a delivery manager write the backlog, architecture, estimate, plan and risks, and a designer adds a prototype when a flow needs one.

    Usually 2–4 weeks

  2. STEP 2

    Milestones and a price type

    The milestones come from the backlog discovery produced, and we agree the price type with you.

  3. STEP 3

    Sprints with demos

    The team works in Agile sprints and shows the work at bi-weekly demos. Tasks and progress live in Jira, daily questions in Slack.

  4. STEP 4

    QA and release

    Testing is part of the delivery, with QA built into each milestone, and we take the product through release.

  5. STEP 5

    Handover or support

    The product moves to your own team, or into support after the release with us, as you prefer.

How we work

Engagement models and terms

Project delivery

We deliver an agreed scope end to end: plan, team, milestones, QA and release. You make the product decisions and accept each milestone.

Fixed price per milestone after discovery, or time and materials against an estimate.

  • Scope changes go through change requests.
  • On fixed-price projects, a warranty period agreed in the contract, usually 30–60 days.

Managed team

An agreed team capacity that we manage. We coordinate delivery and handle the team's make-up. You set the priorities and own the backlog.

Per-engineer rates, or a fixed monthly fee for the agreed capacity.

  • We handle replacements ourselves, and the team keeps its agreed capacity and pace.
  • Engineers work full-time for your team only.

Staff augmentation

Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.

Hourly rate per engineer by role and seniority, invoiced monthly.

  • If an engineer isn't the right fit, we replace them within 14 days at no extra cost.
  • Knowledge transfer to the replacement engineer isn't billed.
  • There is no free trial period.
  • 30 days' notice to take an engineer off or end the engagement, with no minimum term beyond it.
  • Out-of-hours on-call only if agreed with you; we set its hours and billing together.
  • After two years, moving an engineer onto your own staff is something we can discuss.

Whichever model you choose

  • We reply to an inquiry from the contact form within 24 hours.
  • We sign an NDA before work starts, and IP passes to you on payment.

Case studies

Projects we took from brief to release

The briefs had little in common: a fintech startup with its scoring rules already written, a retirement date a missing feature had to beat, a service management platform customized until every upgrade was a risk. Each time the client set the result and we answered for reaching it.

Behind each project sits a design call of ours. On the training module we used a proven engine to play SCORM courses rather than write our own. On the warehouse, the transformation logic lives in Python and Airflow, outside Vertica, so a later move means repointing pipelines.

Healthcare

From an idea to a white-label eHealth platform

Developer portal of the eHealth platform shown on a laptop: FHIR R4 Observation docs with query parameters and a sandbox request returning a blood glucose reading

Agree what done means, then the price

"A fixed price is only as good as the description it prices, so we write that description with you before anyone quotes the build."

Dzmitry Kuchynski, Chief Operating Officer, Octalance

FAQ

Questions to ask before you hand over a project

What do we commit to before we know the full price?

Only discovery. It is a fixed-price phase of its own, usually 2–4 weeks, and the build is priced from the estimate it produces. Its outputs stay with you whether or not the build continues with us, so the requirements, architecture and plan are yours to take to any team.

What if the project runs over the estimate?

On time and materials, every bi-weekly demo shows where the work stands against the discovery estimate. If it looks like passing that estimate, we tell you at the demo, with the reason and a revised estimate, and you decide whether to continue, cut scope or stop. We don't carry on past the estimate without your approval. On a fixed price, the agreed price covers the agreed scope, and anything you add or change becomes a change request.

Can we stop the project partway through?

Yes. You can stop a fixed-price project at the end of any milestone, and a time-and-materials one at the end of any bi-weekly demo. You pay for the work done up to that point, and with that payment we hand over the code, the documentation and the discovery outputs.

Who will work on our project, and can we meet them?

We select and vet the team ourselves, because we answer for the delivery, and you can interview the people in the key roles. Each candidate goes through a technical skills assessment, a soft-skills evaluation and a review of their job history. Some roles add a live coding interview. Across the company, 80%+ of our engineers are senior-level or above, with 7 years' average experience.

What do we have to do on our side if we have no tech lead?

You make the product decisions. Our product manager co-owns the roadmap and backlog with you and turns your priorities into work for the engineers. Keep the demos in your calendar: that is where you see progress and raise questions while they are still cheap to answer. The fair lending platform in our case studies shows this product-management work.

Who owns the code, and what happens when the project ends?

You do. IP passes to you on payment, and the code usually lives in your repositories, sometimes in ours. Systems we control are hosted in the EU, and we sign a data processing agreement where we handle your data. When the project ends, transition-out is routine, whether the product moves to your team or stays with us for support.

How do working hours line up with a US team?

We match your hours by choosing where the team sits and shifting its schedule. For a US client we can arrange 4+ hours of daily overlap with the West Coast, and more with the East Coast. CET/CEST business hours are the default, and we don't run round-the-clock shifts.