Two founders. One shared inbox, and no one in between.
Kellosolutions is deliberately small. We take on a handful of projects at a time so the person who scopes your product is the person who writes it — and the person who answers when something breaks at 2am.
96+
Projects shipped
18y
Combined experience
12h
Average reply time
98%
Client retention
You get both of us, on every project
One of us owns the engineering, the other owns the commercials and the schedule. You deal with both directly — there is nobody else to route a question through.
Runs the business side of the studio: commercial terms, budgets, scheduling and delivery oversight. Your first conversation about scope, price or timeline is with him, and he stays accountable for the engagement from the contract through to handover.
Ten years building consumer and fintech mobile apps, from solo App Store releases to teams shipping to millions of devices. Owns the technical direction end to end — the apps, the services behind them, and everything that touches a store review.
How we got here
No funding rounds, no headcount targets. Just a decade of shipping, and a decision not to grow into something slower.
- 2019
The studio starts
We had met working on the same product from opposite ends — one building it, one running the commercials behind it. Our first project as a pair was a React Native app for a logistics startup, delivered in nine weeks. We never got around to hiring anyone else.
- 2021
SaaS becomes the core
Clients stopped asking for apps and started asking for products — billing, dashboards, multi-tenancy. We built the playbook we still use for MVPs.
- 2023
Long-term partnerships
Most work now comes from clients we have shipped for before. We introduced retained support so products keep improving after launch.
- 2025
AI features, done carefully
Added LLM-backed features to client products — search, summarisation, assistants — with evaluation harnesses so quality is measured, not assumed.
- 2026
Still two people
96+ projects shipped and no plans to grow into an agency. Small stays fast, and fast is the only reason clients pick us.
Six rules we actually follow
Not a poster in an office we do not have. These are the decisions we make when a project gets difficult.
Radical clarity
Weekly demos, written scopes, visible progress. You always know what is done, what is next and what it costs.
Cut before you build
The cheapest feature is the one we talk you out of. We push for the smallest version that proves the idea.
Boring technology
We pick tools with long support horizons and large hiring pools. Novelty is reserved for your product, not your stack.
Own the outcome
Scope is a shared agreement, not a shield. If something we built breaks, we fix it — the invoice conversation comes later.
Leave it readable
Documented, tested, conventional code. Every project is written for the engineer who inherits it, whoever that turns out to be.
Play the long game
Most of our work is repeat business. That only happens if we are honest about timelines, trade-offs and our own mistakes.
What the two of us cover between us
Depth in a narrow stack beats shallow familiarity with everything. This is the list we will happily be judged on.
Languages
Mobile
Frontend
Backend
Data
Cloud & DevOps
Three ways to engage us
Pick the one that matches how defined your problem is. Switching later is normal and costs nothing.
Fixed-scope project
Written scope, fixed price range, defined delivery date. Change requests are quoted before they are built.
Best for: MVPs and well-defined launches
Monthly retainer
A predictable block of engineering hours each month for continuous product work, support and improvements.
Best for: Live products that keep evolving
Technical partner
We act as your engineering team: architecture, hiring input, code review and hands-on delivery alongside your staff.
Best for: Funded startups without a CTO
The questions we get asked first
Because there is no coordination overhead. One of us owns the engineering end to end, the other owns the commercial and delivery side, so nothing waits on a handover meeting. We take on a limited number of projects at a time so each one gets real focus, and we scope tightly enough that a project is measured in weeks rather than quarters.