Sprint
Two fixed weeks to answer one hard question, with a prototype and a written plan at the end.
Pl. I — Services
Three crafts, one team.
We take on a few products a year. The people who ask the first questions are the ones who ship the release.
01
Product design
Research, flows and interfaces that feel obvious the first time.
We start with the people who will use it and the job they are trying to get done. Then flows, then screens, every state and not only the happy path, tested with real users before anything is built.
Typical shape, in weeks
Illustrative. We scope every project on its own.
What you get
- Research and interviews
- Flows and information architecture
- Interface design, every state
- Prototypes tested with users
02
Engineering
Web and mobile products built to last, by the people who designed them.
The same team carries the design into code: typed, tested, accessible and fast. We ship in small releases you can see every week.
Typical shape, in weeks
Illustrative. We scope every project on its own.
What you get
- Web apps and platforms
- Native and cross-platform mobile
- APIs, data and infrastructure
- Performance and accessibility audits
03
Applied AI
Language models put to work inside real products, measured like any other feature.
We treat a model as one more component: scoped to one job, evaluated against actual cases, and designed so people can see and correct what it does.
Typical shape, in weeks
Illustrative. We scope every project on its own.
What you get
- Use-case discovery and feasibility
- Retrieval, tools and agents
- Evaluation sets and guardrails
- Interfaces for review and correction
How we engage
Three ways to start.
Build
A product from the first question to release, usually ten to sixteen weeks.
Stay
A standing arrangement after launch: fixes, measurements and the next version.
Have something worth making well?
Tell us about the product. We'll start with questions, not a pitch deck.
