Where to start
Tell us what's happening.
We'll tell you what it needs.
Most agencies make you guess which service you need. Pick the sentence that sounds like you. We'll tell you how long it takes to start and how we bill.
Hire engineers / Dedicated engineers
Senior engineers working as part of your team
Hiring a senior engineer locally takes around eleven weeks. This takes two. They work in your repo, join your stand-ups, and a second senior engineer of ours reviews every pull request before it reaches you. We start with a paid two-week trial on real tickets. If it isn't working, you stop. No notice period, no fee.
- Who you get
- 1 to 3 senior engineers
- Time to start
- 2 weeks
- Billing
- Monthly, per engineer
- Notice
- 30 days
What we do
Three families.
Nine services.
You need people, you need something built, or you need a business system sorted. That's the whole list.
Hire engineers
When you know what to build, but don't have enough senior people.
- Dedicated engineers, full time on your backlog
- Engineering pods: a team with its own lead
- Fractional leadership, for direction not extra hands
Build software
When you'd rather buy the result than manage a team.
- Web & product engineering
- AI & machine learning
- Data & cloud infrastructure
- Assessment & stabilisation
Business platforms
When the systems your revenue runs on have drifted.
- Salesforce & enterprise platforms
- Marketing & growth engineering
The people you meet on the first call are the people who write the code.
Twelve senior engineers. No junior bench.
Proof
Three numbers
that moved.
Each one is written up in full on the work page: the problem, what we did, and what we'd change next time.
An overnight job that had started overlapping the working day. We profiled it, rebuilt it, and added a test that fails the build if it ever slows down again.
Logistics platform, Netherlands
Accuracy against a question set written and approved by underwriters beforeany retrieval code existed. Nothing left the client's own cloud.
Insurance group, United Kingdom
Test coverage on the core paths of a codebase whose every original author had left, reached without a rewrite and with customers live throughout.
Health technology, United States
What you can hold us to
Five things we
put in the contract.
These go in the contract. Most of our work comes from people who already hired us once.
The people you meet are the people who work
No substitution after an engagement is awarded without your written approval, in advance.
You own everything, from the first commit
Work happens in your repository, under your accounts. Code and IP are yours throughout, not on completion.
A working demonstration every week
Software you can use, not a status report. If there is nothing to show, we tell you that instead.
Rates and terms are published
You don't need two discovery calls to learn how billing works. It is written on the contact page.
You can stop
Thirty days' notice on monthly work, none during the trial. You're not locked in.
How we work
Four stages,
in one line each.
What each stage delivers, what we need from you and the standards we hold are set out in full on how we work.
Days 1 to 3
Understand
A call with the engineer who'd lead it. Free, and we'll say if we're wrong for the work.
Week 1
Scope & quote
Milestones, named people, a written rate. Nothing starts until you approve it.
Week 2 on
Build
Short sprints, a working demonstration every Friday, written updates daily.
Final week
Hand over
Runbooks, documentation and a walkthrough with whoever takes it on.