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.
- Decision forcing sessions. 6-10 sessions over 4-6 weeks with your founder, product lead, operations lead, and technical lead. Each session surfaces structural questions your team believes are already settled but aren't. Every decision gets named, dated, approved, with 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, workflows — the contract between your domain thinking and your engineering. When a developer asks "what happens when X?" the model answers before a meeting is scheduled.
- Working prototype. Every decision made visible and interactive in Figma. Your developers see what to build, not just read about it. Scenario-tested across user roles so the logic holds before a line of code is written.
Why this order matters?
Most teams start with screens and work backward. We start with decisions and work forward.
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's where rework comes from.
Decisions first. Model second. Prototype third.
Each layer builds on the one before it. Nothing is designed until it's decided. Nothing is decided until it's been stress-tested against the hardest counter-evidence we can find.
We actively try to break every conclusion before we lock 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 authority to make decisions. No middlemen. No presentations to committees.
Senior team. Engagements are led by people who combine product management, UX design, and neuroscience background. 10 years in vertical B2B software.
- Defines what the product should do and why, grounded in how people actually think and behave.
- Finds every unanswered question and every gap in the logic before your developers do. Translates what was decided into how it should work - the structure, the states, the flows, the edge cases nobody raised yet.
- Translates how it should work into how users should see it. Manages attention, hierarchy, and perception - so the logic holds when a real person is looking at the screen under pressure.
Start with a conversation
What happens next:
- Fit call - we learn about your product, your situation, and whether we can help. If it's not a fit, we'll tell you.
- Pilot assessment - 2 weeks, fixed price. We go in, surface 3-5 structural decisions your team hasn't made, and deliver them locked and documented. You see exactly how we work before committing further.
- Full engagement — fixed-price packages by scope. If there's more to do, we scope it into fixed-price work streams: decision log, product model, prototype. You know what you're paying before each stage starts.
