Digital Product Engineering
One team, from first prototype to steady release
Designers, engineers and a product lead who stay together from the first idea to the hundredth release, so nothing is lost in a handover.
Talk to us
Our view
Products fail in the gaps: between the people who imagine them and the people who build them, between launch and the year after. We put one small, senior team on a product and keep it there, shipping in short cycles and learning from real users every week.
A typical team is six to nine people: a product lead, a designer, engineers and a quality engineer, with your product owner sitting with us.
We release small changes often. It is safer, it is calmer, and it means users see progress every fortnight rather than once a year.
By the numbers
How our product teams work
- 90 days
- from the first workshop to a first release in real users' hands, on average.
- 2 weeks
- between releases, or less, for every product we build and run.
- 6 to 9
- people in a typical product team, including your own product owner.
- 4.7
- average app store rating across the client apps we have built since 2023.
KIASA product engagements, 2023 to 2026.
What we do
Everything a product needs to reach its users
Product discovery
Interviews, data and quick experiments to find the problem worth solving before a line of production code is written.
Prototypes that test the idea
Clickable or coded prototypes put in front of real users within weeks, so the riskiest assumption is tested first.
Web and mobile applications
Fast, accessible applications on the web, iOS and Android, built to be maintained by the team that inherits them.
Product platforms and APIs
The services behind the screens, designed so the next product can reuse them instead of starting again.
Release engineering
Pipelines, feature flags and staged rollouts that make releasing on a Friday afternoon unremarkable.
Product analytics
Measures agreed at the start and tracked in the product, so decisions are made on behavior rather than opinion.
Client work
Our work in action

Healthcare
Tessera Health's patients book across 38 clinics in one app
Released to one clinic first, then rolled out over four months as each clinic joined the shared record.
Read the case study
Retail and consumer
Northmere Grocers rebuilt its ordering app in five months
Checkout time halved, and the team now releases every week instead of every quarter.
Explore retail
Education
Ashby Vale University put enrollment on students' phones
Eleven paper forms became one guided flow, used by 14,000 students in its first term.
Explore education
What we think
Thinking on building products
Research report
Platform pulse: what engineering leaders will fund in 2027
Product teams are being asked to ship more with flat budgets. Where 320 leaders are finding the room.
Perspective
Green software is mostly just good software
Lighter pages and fewer calls make faster products. They also use less energy.
Research report
AI in the back office: where the first real savings are showing up
The first useful AI features are often behind the scenes. What 60 teams learned building them.
Research report
The maintenance dividend
Every feature shipped is a feature to maintain. How the best product teams keep that cost down.

“The same people who sketched the first screen were still there at the hundredth release. That continuity is why the app works the way our customers expect.”
How we work with you
From an idea to a steady rhythm
Discover
Two to four weeks with your users and your data. We leave with a problem worth solving and a way to measure it.
Prototype
The riskiest idea is built first, roughly, and tested with real users within a month.
Release
A first version reaches a small group of users, then everyone, behind flags that let us roll back in minutes.
Settle the rhythm
Releases every fortnight, measured against the goals we set together, with your team taking on more each cycle.
Our leaders
Talk to the people who lead this work
Camila Restrepo
Practice Lead, Digital Product Engineering
Has led product teams in retail, health and education. Measures success by the hundredth release, not the first.
Oskar Lindgren
Principal Engineer, Mobile
Built Tessera Health's patient app and the release pipeline behind it.
Fatima Zahra Benali
Head of Product Management
Coaches product owners on both sides of the table. Ran discovery for Ashby Vale University's enrollment app.

Have a product to build?
Tell us who it is for and what it should change for them. We will propose a first ninety days.
