How we work
We run structured working sessions with your executive team to surface the product decisions that nobody has explicitly made - then lock them in artifacts your developers build from directly.
The process.
- Working sessions with your executive team. We ask each executive the same structural questions separately - separately is the mechanism, because in a group people converge on whoever speaks first. Then one session with everyone in the room, answers side by side. Every decision gets named, dated, approved, with the alternatives killed and documented. When someone re-opens a settled question in month three, the log closes the conversation in 90 seconds.
- Product model. Entities, relationships, states, lifecycle rules, dependency order - the contract between your domain thinking and your engineering. What happens to each object when it changes, expires, is deleted, or is linked to something else. What must exist before what. When a developer asks "what happens when X?", the model answers before a meeting is scheduled.
- Working prototype. The target state, built to be used - real states, real flows, not a slide of screens. Your developers see what to build instead of interpreting a description. It is not a design artifact. It is the instrument that makes the decisions testable before they are locked.
Why this order matters?
Most teams start with screens and work backward. We start with what has to be decided.
A screen without a decision underneath it is a guess dressed up as a deliverable. When your developer builds from it, they fill in the missing logic themselves — and their version won't match yours. That is where rework comes from.
But the three don't happen in sequence. The decisions, the model and the prototype get built together, because each one tests the others. A decision that reads correctly in a document comes apart when someone runs a real scenario through a working screen. The prototype is where that happens — while it is still cheap to change.
Nothing is designed until it is decided. And nothing is locked until we have tried to break it. Most consultants converge and present. We converge, contradict, then conclude. What survives is what your team can stop debating.
Our team.
We work directly with founders, CTOs and executive teams - the people who own the product and have the authority to decide. No middlemen. No presentations to committees.
A senior team, not one person's calendar. Ten years in vertical B2B software, combining product management, UX design and a research background in how people make decisions under pressure.
One of us defines what the product should do and why. One finds every unanswered question and every gap in the logic before your developers do. One translates what was decided into how it should work - the structure, the states, the flows, the edge cases nobody raised yet - and how a real person should see it on the screen.
Start with a conversation
What happens next:
- Fit call - We learn about your product and your situation. If it's not a fit, we'll tell you.
- Pilot - 2 weeks, $10,000 fixed. The question it answers: what have we not decided yet? We close the two or three most expensive gaps - named, dated, approved by your people. You see exactly how we work before committing to anything larger.
- Full engagement - scoped by product area. Every structural decision closed, the model they rest on - entities, relationships, states, lifecycle rules, dependency order - and a prototype of the target state.
