Services
Six things we take on.
The same engineers who run our own products run client engagements. Every one of these has software behind it you can go and read about.
Product engineering
Taking something from nothing to a running product, then keeping it running.
Something that does not exist yet, taken to a running product with real users on it. Architecture, build, release, and then staying on it, because a first version is where the work starts rather than where it finishes.
This is the shape of engagement where we are making the calls: what to build first, what to leave out, and which decisions are expensive to reverse later.
Read the workPickleShirt Designer
Taking over existing software
Inheriting a codebase somebody else wrote and making it maintainable again.
Usually it has been in production for years, the people who wrote it have moved on, and the framework is several major versions behind. Nobody wants to touch it, so nothing ships.
The first job is always the same. Get it building, get it understood, then move. Where’s My Concrete arrived on Ember 2.x and now runs on 7.2, migrated while the application stayed in production.
Read the workWhere’s My ConcreteBookCorner
AI and agents
LLM integration, RAG, and agents that act inside systems you already run. Wired into your data, not bolted on beside it.
LLM integration, retrieval over your own data, and agents that act inside systems already running rather than sitting beside them in a separate chat window.
On Testable we built the interface for AI-generated test scenarios and AI-written run summaries. That problem is harder than it reads: a summary is only useful if the reader can get from it back to the raw numbers underneath, so the dashboard has to hold both without either one burying the other. We run the same work in our own products, aala.land and LILA.
ERP and internal platforms
The systems a business runs on rather than the ones it sells.
The software nobody outside the company ever sees, which is usually the software the company cannot operate without. Orders, stock, production, logistics, accounting, and the joins between them.
Lapchi is a handwoven rug studio whose whole operation ran on an ERP and CRM we built over nine years. Off-the-shelf inventory software assumes interchangeable units, and every piece Lapchi makes is one of a kind, so the system holds the fibre blend, the dye formula and the weaving specification on the order itself.
Read the workLapchi
Web and mobile applications
Interfaces built to be used every day, not demonstrated once.
Applications people sit in front of for hours rather than click through once in a demo. That changes what matters: how fast it is on the tenth screen, what happens when the data is messy, and whether the thing is still usable at the volume the business hits in year three.
React, Next.js, Ember.js, Laravel, Flutter, React Native and native iOS and Android. Chosen per project, not by habit.
Read the workConsumer BreakEvoFitsFox
Embedded engineers
Our engineers working inside your team, on your board, to your process.
Our engineers inside your team, on your board, working to your process and reviewed by us. You get the people, not a resourcing layer standing between you and them.
This is the one that gets confused with staffing, so to be plain about it: we do not fill seats. Engineering responsibility stays with us, which is why these engagements run in years. Testable has had our team for six, BookCorner for eight.
Read the workTestableBookCorner
How it starts
A two-week pilot.
Every engagement opens with a two-week pilot. A real piece of the work, scoped narrowly enough to finish, delivered as running software rather than as a document.
Both sides then decide on evidence instead of on a proposal. You see how we write, how we estimate, and how we behave when something turns out to be harder than it looked.
After that, engagements run monthly. What we will not do is staffing by the seat with no engineering involvement from us. If nobody from here is responsible for the work, we are the wrong shop.
What we build with
Chosen per project.
Everything listed here is in something we have delivered. We pick per project, and the case studies say which stack went where.
- Frontend
- ReactNext.jsEmber.jsGlimmerJavaScriptViteThree.jsWebGL
- Mobile
- FlutterReact NativeiOSAndroid
- Backend
- LaravelNode.jsScalaGraphQLREST
- Data
- PostgreSQLMySQLDynamoDBFirebase
- Cloud
- AWS LambdaAWS AmplifyAWS AppSyncAPI GatewayDigital Ocean
- Testing
- PlaywrightPuppeteerSeleniumQUnit
What next
Tell us what you have.
We will tell you plainly whether it is work we should take, and if it is not, who we think should.