A new version - V2 or V3
The roadmap exists. The budget is roughly there. The team is being assembled. And the decisions about how the product should actually work are still being made informally — in meetings, in someone's head, in a spec that leaves the hard parts vague.
Then developers interpret the vague parts, build, and some of that work gets thrown away.
What usually turns out not to be decided
- What the product's core number actually means. On one platform the entire commercial value was a compliance percentage. The dashboards were designed. No formula for it existed.
- Who this version is for. Not the segment — the role, named.
- What's in this version and what waits.
- What happens to each object when it changes, expires, is deleted, or is linked to something else.
Developers can't un-know the architecture - they've lived inside it for years.
Domain experts can't see the product through a stranger's eyes.
And nobody with a stake in the outcome can ask the CEO and the CTO the same question and then publish that the answers differ.
Book a fit call
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.
