Fifteen years building software that is still running.
Hospitals, universities, retailers and development banks. The work usually starts before the build, on what is worth building at all.
What we do, in the order it usually happens
Most engagements start at one of these and move forward. Few start at the first one, and that is usually the problem.
Product strategy & discovery
Testing what the product should be before anyone commits budget
Design
Research, interface and design work written straight into the repository
Engineering
New products, and the systems that already carry the business
Artificial intelligence
Assistants and automation that run inside the systems already in place
Data
Warehouses, pipelines, and the screens someone acts on
Legacy modernization
Changing what runs the business without the business stopping
How we can work together
How a project gets delivered is the first decision. Four shapes; which one fits depends on how defined the scope is and how long the product has to live.
AI Pods
Small teams working alongside AI agents, billed on delivered outcomes rather than hours. Each one has a single person accountable for everything that ships.
Best when the scope is clear and the date is not negotiable.
Dedicated team
A standalone team that owns a product end to end, with its own lead, reporting to you.
Best when the product will live for years and needs a team that stays with it.
Staff augmentation
Senior people who join your team, your rituals and your repo, working your way and your hours.
Best when you have the direction and need depth in a specific area.
End-to-end delivery
A defined scope, delivered in releases, with a fixed price and milestones you can verify.
Best when you want the whole thing priced up front and delivered as one project.
Numbers that come with what they were measured against
- 4x
- lower recruitment cost
- On the Stanford Medicine research apps, app downloads cost four times less through social networks than through conventional ABS outreach. Recruitment tripled and participation doubled against the same comparison.
- Stanford Medicine. Read the case →
- 3.5%
- conversion, up from 1.2%
- Immediately after the new Lentesplus site went live, the ecommerce conversion rate increased from 1.2% to 3.5%, following the migration to Adobe Commerce Cloud and the stabilization of the platform.
- Lentesplus. Read the case →
- 35%
- better treatment adherence
- Healthcare organizations running outreach programs on the EmpowerHealth platform report 35% better patient adherence and 20% fewer avoidable emergency visits.
- EmpowerHealth. Read the case →
Bring us the project you’re weighing.
Leave with a first opinion. In a 45-minute working session we’ll go through what you’re considering, what it would take, and whether it is the thing worth doing first.