Work Area
Digital Products
We shape, build, launch, and improve digital products: software people use as the thing you offer. We start with the smallest version that proves the idea, put it in front of real users early, and grow it from what they do.
- 1,200+ clients helped
- Building since 2010
- 15 services, one team
- 50+ technologies
At a glance
What we build
We build digital products: software your customers use as the thing you offer, such as an app, a platform, or an online service, and we keep improving it with you.
Problems we solve
Teams build too much before learning what people want, or launch and then have no plan to improve.
Who we serve
Founders and teams creating a software offering, and organizations turning an internal tool into a product.
How to choose
Build the smallest version that tests your biggest assumption, learn from real use, and grow what people value.
In practice
Software that you offer, and keep improving
We build software you offer to customers as a product. Unlike a one-off project, it has users, a roadmap, and an owner, and we design it to keep changing as people use it.
Products fail less often from poor engineering than from solving the wrong problem. The early work is therefore about learning: who the users are, what they struggle with, and what they will pay for.
We shape the product with design and engineering together, so ideas are tested as real, usable screens before large amounts are built.
From many ideas to a growing product
Stages that narrow: Many ideas: Everything the product could do.; A few that matter: The ones that solve a real problem.; One first version: The smallest set that tests the idea.; Real users: A small group using it for real.; A growing product: Features added because people asked..
- Many ideasEverything the product could do.
- A few that matterThe ones that solve a real problem.
- One first versionThe smallest set that tests the idea.
- Real usersA small group using it for real.
- A growing productFeatures added because people asked.
What we do
Working on a product
Shape
- Research with users.
- A clear statement of the problem.
- A ranked list of what to build first.
Build
- Design and engineering as one team.
- Working software every few weeks.
- Tests that protect what already works.
Launch
- A small, watched release.
- Measures of use, not only of sign-ups.
Improve
- A regular rhythm of changes.
- Support for users.
The cycle
Learn, build, measure, repeat
Products improve through short cycles, not through one big release.
Learn, build, measure, repeat
A sequence of 5 steps. Understand the problem: Talk to users and study how they cope today.; Design a test: Sketch and prototype the smallest useful answer.; Build the first version: Only what the test needs.; Launch to a few users: Watch what they do, not just what they say.; Learn and decide: Grow it, change it, or stop..
- Understand the problemTalk to users and study how they cope today.
- Design a testSketch and prototype the smallest useful answer.
- Build the first versionOnly what the test needs.
- Launch to a few usersWatch what they do, not just what they say.
- Learn and decideGrow it, change it, or stop.
First version
What should the first version be?
There is more than one way to test an idea. Choose by what you most need to learn.
What is your biggest uncertainty?
Choose this when
You are not sure the problem is real or common.
- What you get
- A clickable prototype shown to real people, before any code.
- Keep in mind
- Interest is not payment. Ask what they would give up or pay.
Choose this when
People like the idea, but you need to know about price and value.
- What you get
- A narrow working product, offered to a small group.
- Keep in mind
- Keep it small, but make the core job work well.
Choose this when
The idea works, and you need it to serve more people reliably.
- What you get
- Stronger foundations: performance, security, and support.
- Keep in mind
- Do not do this before you have evidence the idea works.
A typical example
An internal tool becoming a product
A typical case is a firm that built an internal tool for scheduling inspections, and finds that other firms ask to use it. Turning it into a product means adding accounts, billing, help for new users, and a way to handle many customers safely.
A first step could be a small group of outside firms using a cleaned-up version, while the team learns what they need. Features would follow actual use.
Tell us about the product idea
Describe the idea and who it is for. We will suggest a first version that tests it before you invest further.