A named developer, with a profile
Stack, seniority, years, how they work with AI. You read it before they start, and you can say no.
Embedded developers
Add a senior developer to your team this month.
Staff augmentation done properly: senior developers in your team two days a week or full time, working in your repo, your tickets and your stand-ups, on a fixed monthly plan you can pause or change with notice. No recruitment fees, no six-month search.
What you get
Everything a hire gives you, minus the hiring
A plan is a person plus the things that make a person productive on day one.
Your handler
One person who runs the weekly call, knows your roadmap, and sorts things out when they need sorting.
A weekly worklog
What shipped, what is next, what is blocked. Written by the developer, visible in your portal, every week.
AI tooling included
Our developers arrive with their tooling and their process. It is a flat subscription per person, covered by the plan, never a line on your invoice.
Code review on everything
A second senior developer reviews what ships, even on a one-person engagement. It is not optional.
Cover when life happens
Holidays and sick days are ours to manage, not yours. The wider team knows your codebase enough to step in.
How it runs
From first call to first pull request
We keep the start deliberately unfussy. A half-hour call to understand the work. A profile or two to choose from. The agreements, signed in the portal. Then a start date, usually within a couple of weeks.
From there your developer works the way your team works: your repo, your tickets, your stand-ups, your Slack. Your handler checks in weekly and you get a worklog every Friday. The invoice arrives monthly and says exactly what it is for.
- Week 0: call, profiles, agreements, plan
- Week 1: access, onboarding, first tickets
- Every week: worklog and handler call
- Every month: one itemised invoice
usually two weeks to start
The protections
The paperwork, in plain English
Bigger clients rightly ask about this before anything else, so here it is up front.
- Non-solicitation. You agree not to hire our developers directly during the engagement and for a period afterwards. It is proportionate, it has a buy-out figure rather than a blanket ban, and it protects the thing that makes the plan work.
- Intellectual property. Everything built for you is yours, transferred on payment. No licences, no lock-in.
- Data protection. A proper data processing agreement under UK GDPR, with a named list of sub-processors, including any AI providers used on your work.
- Notice. Three months minimum, then 30 days' notice. Pause, change capacity or stop, and it is handled through your handler, not an argument.
All of it is versioned and signed in the client portal, so both sides can always find the exact wording that applies.
boring on purpose
Good questions
Things people ask before adding a developer
Straight answers, no small print.
Capacity without the hiring
Add a senior developer to your team this month.
Also from Ikigai
Other ways we can help
AI-first development
Senior developers building with AI in the loop, reviewed and tested by people who know what good looks like.
Laravel development
Laravel applications, Filament admin, APIs, migrations and Laravel developers for hire, from a UK agency that built its own CMS in Laravel.
Bespoke software development
Bespoke software for UK businesses: portals, operations systems, billing and integrations, built in Laravel and Nuxt at a fixed price you own outright.
Web application development
Custom web applications: customer portals, dashboards, SaaS and internal tools built in Laravel and Nuxt, with Stripe, integrations and AI features done properly.