Most strategy engagements end with a document nobody opens again. We built the Innovation Blueprint to end with decisions instead.
This post explains what it is, how it runs, and what you have when it's finished — written for the brokerage, MLS, title company or proptech leader trying to work out whether it's the right starting point.
Leadership teams are rarely short on ideas. They're short on agreement.
Priorities differ by department. Technology decisions get made in isolation, usually by whoever felt the pain most recently. The operating model drifts out of step with the market, and nobody can point to the moment it happened. The result is a company working hard in several directions at once.
You can't buy your way out of that. More tools applied to an unclear operating model produce a more expensive unclear operating model.
The Blueprint runs in three phases.
Listen. Conversations with leadership, department heads, and often the people doing the work. Structured interviews across operations. A review of the current technology stack, vendors and contracts. Positioning, pricing, and who the business actually serves best. Where handoffs break down and the same work gets done twice.
The question behind all of it: what prompted you to look at this now?
Map. The business on paper. How work, decisions and information actually move through the organization. Which systems earn their cost, which overlap, and which are quietly in the way. The gap between what the company says it does and what it does. The handful of constraints that genuinely govern what's possible next year.
Decide. Findings become sequenced decisions in working sessions with your leadership team. This is where alignment gets built, because the people who have to live with the plan are the ones who shape it.
Three things.
A current-state picture — how the business operates today, written plainly enough to hand to a new executive.
A set of decisions — what to keep, replace, retire or leave alone, each with the reasoning behind it, so the choices hold up when someone asks why six months from now.
A 12–24 month roadmap — sequenced, owned and realistic. Built to survive contact with the calendar rather than to look ambitious in a slide deck.
Late, and deliberately so.
We start with how decisions and information move through your organization, not with software. Technology enters the conversation once the operating model is clear, because the same tool produces different results in different companies, and the difference is usually the operating model rather than the tool.
This occasionally means the recommendation is to remove software rather than add it.
Organizations at a decision point. Independent, regional and multi-market brokerages rethinking their operating model. MLSs, title and transaction companies whose value depends on trust, data and process. Proptech firms deciding what to build next and who to build it for.
It's most useful when there's a real decision in front of you — a platform change, a merger, a repositioning, a year that has to go differently from the last one.
It's least useful when the answer is already known internally and what's wanted is external validation. That's a legitimate need, but it isn't this.
Some organizations take the roadmap and run with it internally. That's a normal and good outcome.
Others continue with Advisory or Managed Services, where the same people who helped shape the plan help put it into practice. Neither is assumed at the start, and the Blueprint is built to be useful on its own either way.
If you're weighing strategic direction, technology decisions or how your organization should be designed, a short conversation is the fastest way to find out whether this is the right place to start. Learn more about the Innovation Blueprint.