About
A small studio that builds software businesses depend on.
Treblesys was founded in 2014 to build software that has to keep running long after launch, whether that's an internal platform or a product your customers log into. We've stayed small on purpose, and we judge ourselves on how our clients' operations are running twelve months on.
Treblesys started with two engineers and a shared frustration. Too much business software was built to win the pitch and then struggled to run the operation. It was sold by the experienced people and built by a junior team, and it became expensive to change the moment the launch team moved on.
So we set out to run the studio the way we'd want a supplier to run it if it were our own money. That meant scoping before we estimated, and something running in the client's own accounts every two weeks, built by people who would still be around to answer for it a year later. 12 years on, most of our work comes from clients we've known for years, and a typical engagement lasts a lot longer than the project it started with.
We're based in London, with engineers across the UK and Europe. Clients range from funded startups building a first product to established SMEs replacing spreadsheets and ageing systems nobody wants to touch. We also work with enterprise teams that need an outside partner to own one specific platform.
Sample figures.
What we believe
Four rules we work to.
- 01
Say the hard thing early
If the scope is too big or the deadline can't be hit, we'll say so in the first conversation, while there's still time to do something about it. Same if a feature won't move the metric.
- 02
Tests and documentation pay for themselves
Tests, documentation and a tidy architecture cost something up front. They're also why year three of a system costs less to run than year one.
- 03
Optimise for the long relationship
Most of our work comes from clients we've been working with for years, which only happens if each project leaves them better off than the last.
- 04
Small teams, nobody in between
There's no account layer between you and the engineers writing the code, so when something goes wrong you know exactly who to ask.
Leadership
The people you'll work with.
Everyone here has shipped production systems and run them afterwards. The leadership team still does client work day to day.
- DO
Daniel Okafor
Co-founder · Head of Engineering
Fifteen years building and running production systems for logistics and financial services companies. Still reviews code every week.
- PN
Priya Natarajan
Co-founder · Principal Consultant
Runs discovery and architecture. Ran platform teams at two scale-ups before Treblesys, and will draw you a sequence diagram whether you asked for one or not.
- TA
Tom Ashworth
Product Director
Takes a vague business problem and turns it into a scoped plan with things you can test. Spent the years before Treblesys in B2B SaaS and on complicated internal tools.
- EV
Elena Vasquez
Head of Design
Designs screens full of data that people can use without a training day. Looks after our design system and the accessibility work.
- ML
Marcus Lindqvist
Head of Cloud & DevOps
Infrastructure as code, and monitoring someone will look at. Keeps the cloud bill from being a shock at month end. Was an SRE at a payments company before this.
- AR
Aisha Rahman
Delivery Director
Keeps every engagement straight on scope, risk and dates. When one of them is slipping, it goes to the steering meeting the same week.
Placeholder team profiles. Replace names, roles, bios and add photographs in src/content/team.ts.
How we're organised
Small teams with an engineer in charge and no account managers.
Each engagement has a lead engineer, a designer where the work needs one, and a delivery lead who owns scope and risk and does most of the reporting. When you phone, the person who picks up is on your project.
Photography · Alesia Kazantceva, Alexandre Debiève, Alvaro Reyes, Annie Spratt, Austin Distel, Bench Accounting, Blake Wisz, Campaign Creators, Christopher Gower, Franck, Ilya Pavlov, Jordan Harrison, Lenny Kuhne, Luca Bravo, Marcin Jozwiak, Marvin Meyer, Nastuh Abootalebi, National Cancer Institute, Scott Graham, Sean Pollock, Sergey Zolkin, Taylor Vick, ThisisEngineering RAEng, via Unsplash.