Senior hands only
The person in the first call writes the code. Nothing is offshored, nothing is handed to a junior to learn on, and nobody is 'assigned' to you by a resourcing spreadsheet.
The studio
A small senior studio. We take on two builds at a time, we stay long enough to live with what we ship, and we have opinions we can defend about almost all of it.
Position
We are not the cheapest, the biggest, or the fastest to start. We are the studio you call when the last attempt didn’t work, or when it matters too much to find out the hard way.
Principles
The person in the first call writes the code. Nothing is offshored, nothing is handed to a junior to learn on, and nobody is 'assigned' to you by a resourcing spreadsheet.
We choose technology by how well it will be understood in five years, not by what shipped last month. Novelty is reserved for the places it actually buys something.
Budgets are enforced in CI from the first commit. A site that scores 100 at launch and 61 a year later was never really fast — it was briefly fast.
Your repository, your accounts, your infrastructure, from day one. No proprietary platform to be locked into, and no leverage held over you at renewal time.
We turn down more work than we take, because two projects at a time is the only way to keep the standard. If we're not right for it, you'll know within a day.
Decisions, trade-offs and the reasoning behind them live in the repository. When we hand over, your team inherits the thinking and not just the code.
We use AI throughout, because refusing to would mean charging you more for slower work. But it drafts, it does not decide — a senior reviews every line, tests pin the behaviour, and security-sensitive code gets read by a human who knows what to look for. Speed that costs you correctness isn't speed, it's debt with a deadline.
Track record
The studio is new. The people in it are not — this is where the seventeen years were spent.
Nine years of self-directed projects before the first professional role. Sites and applications built because they were interesting, then maintained long after the interesting part was over — which is where the actual lessons are. Nobody teaches you what a bad schema decision costs; you find out two months later, on your own time.
Consultancy years at Elastycloud and Ecomatics. Magento 2, SEO tooling, integrations and infrastructure — and Click Shop, an internal product that took demo-store setup from most of a day to under ninety seconds. The first taste of deleting a cost everyone had stopped noticing.
Nearly three years leading Acordo, a cloud-native microservices CRM for major telecom operators, from the very first commit through to production. Architecture, cloud infrastructure, observability, and then living with all of it long enough to learn which decisions were right.
Front-end for Backify's cashback platform and CRM integrations for the Lynes telephony system — while founding and shipping Idolify, an iOS and Android social app, alongside full-time work. Founding a company while employed is a reasonable proxy for how much someone likes this job.
Backend on Meta's Workplace platform, building GDPR-compliant data workflows in PHP and Hack. Then a year at Ingka IKEA on a transaction management layer handling every payment method at global scale, with Terraform and CI/CD from the first commit. Two organisations where review, testing and performance budgets are the cost of entry.
Leading a CRM build at Aidoni Group with real-time Pipedrive automation — and starting Swoo. The newest thing here, deliberately: the same senior engineering, working directly for clients instead of through an employer, with no layer of account management in between.
Tooling
Front-end
Back-end & data
Cloud & delivery
Certifications
We keep the roster short on purpose. If your timeline is real, get in early.