Once Stages 1 and 2 produce a qualified opportunity, Stage 3 is where strategic selling earns its keep — the meetings, the discovery, the proposal, the navigation of multiple stakeholders, the Miller-Heiman discipline that turns a qualified lead into a closeable deal.
This page is the optional extension that sits between the signal engine and the human closing skill. It's how every conversation builds the Gold Sheet, how the pipeline stays alive across reps and timezones, and how Colliers' institutional memory survives turnover. The closing stays human (that's stages 4–6). Everything else here is what makes that human moment more effective.
A live operator UX where signals, accounts, opportunities, and conversations live in one place — not seven tabs across Salesforce + CoStar + LinkedIn + email + Excel. This is what we use for our own commercial ops at BC, what CARR Biosystems uses for theirs, and what the Colliers OSBA team would use for theirs.
One canonical view per account — signals stack chronologically, relationships visible at a glance, prior conversations one click away, ICP score live, status taxonomy (Cold · Warm · Active · Closed-Won · Closed-Lost · Past-Customer) visible.
Each Stage 2–4 opportunity has its own record: trigger that spawned it, persona it routed to, Gold Sheet attached, meetings logged, action items live, contract artifacts (when Stage 4 starts) anchored.
Every broker logs in and sees: their top 3–5 actions for today (matcher output), their open opportunities sorted by next-touch-due, their quiet accounts that need attention, their signals from overnight. No "where do I start" problem.
What's at each stage. Where it's slipping. Which reps are over/under capacity. Which accounts have gone quiet. The view Kareem and Scott would use in their Monday morning pipeline review.
This very page you're reading is an instance of the same pattern: a per-prospect / per-opportunity working page that auto-updates from Hub DB after every conversation. For Colliers' actual deals, we could spin up the same kind of deal-room page per qualified opportunity — signal context, account history, Gold Sheet preview, next-meeting prep all in one URL. Brokers stop preparing for meetings from scratch.
Same engine running BC's book runs CARR's book. Now imagine it running Colliers OSBA's.
We're naming it explicitly: Miller-Heiman. We hear in your conversations that the discipline is already part of how you think about selling — we'd operationalize it as a living, signal-fed system on top of the pipeline command-view. Not a template you fill out once; a living working sheet that updates after every conversation and persists for the life of the account.
Org chart, buying influences, win/loss patterns. Persistent across deals.
Per-deal strategy: position, plan, gaps. Spawned from Gold Sheet context.
Tactical pre-meeting brief. Stakeholders, objectives, action items.
Gold Sheet enriched with deal outcome. Ready for next cycle.
Org chart · Economic/User/Technical/Coach buying influences · red flags · prior-deal history · persona profiles. Auto-drafted from Hub DB + MI research. Updated after every conversation. This is the document that survives reps moving on, accounts going quiet, and deal cycles spanning years.
New signal at a known account triggers green-sheet creation: trigger · ICP fit · recommended persona · suggested first message · expected deal contour. Routes automatically to the right broker. Gold Sheet attached on day one. No "starting from scratch."
Pre-meeting prep brief (your day-of-meeting cheat sheet, in plain English). In-meeting Fireflies capture. Post-meeting action items extracted by speaker. Recap draft for follow-up. Each Blue Sheet binds to the opportunity record, then enriches the Gold Sheet automatically.
The Gold/Green/Blue system is continuously fed by the same signal feeds, transcript ingest, and account graph powering Stages 1+2. Past deals + past relationships become institutional memory automatically. The sheets aren't a layer of admin work for brokers — they're a layer that does admin work for the broker. Most importantly: the Gold Sheet is what loops Stage 7 back to Stage 1. See the closed loop.
The loop we use internally: meeting requested → pre-brief drafted → meeting recorded (Fireflies / Fathom) → transcript ingested → action items extracted → CRM updated → recap drafted → next-meeting prep auto-generated. No manual data entry. No "I'll get to that recap later." No context loss between meetings.
For every booked meeting, agent auto-drafts a Blue Sheet: who's in the room, persona profiles, last conversation summary, open questions, recommended angle. Broker reads this in 60 seconds before joining.
Fireflies / Fathom → Hub DB conversation graph. Speaker-segmented. Chunked. Embedded. Intent-flagged (task, pricing, metric, question, commitment). Searchable forever.
By speaker. With timestamps. Auto-routed to the right system (CRM update, calendar invite, contract draft request, follow-up email). Already running for the Colliers 5/22 + 5/28 transcripts — 13 action items live.
Draft follow-up email sent to broker for review. Gold Sheet auto-updated with new context. Next-meeting prep already starting before the current meeting is fully cold.
Same loop we run for BC's own client meetings. Same loop we ran for the Colliers 5/28 demo — that's how this page got built so quickly.
For Stage 3 (and feeding back into Stages 1–2), here's the data stack we'd build, separated by what Colliers likely already licenses vs. what we'd add. Q-01 on June 5 ("does Colliers already license CoStar / Reonomy / CompStak?") drives the architecture of this whole layer.
If Colliers already licenses CoStar at full tier, the lease-data layer is essentially zero marginal cost. If not, we add ~$1.5K–4K/mo for the BC-purchased equivalent (LoopNet API + Crexi + county recorders + REIT pulls). That's the single biggest pricing variable for the whole engagement.
This is one of the questions we need answered before June 5 turns into scope. Three honest options — not a leading question.
BC engineer works directly alongside Kareem's BI lead, day-in / day-out. Your team learns the system as we build it. Highest knowledge transfer. Slowest to ship initial features (we're teaching as we ship).
BC ships in 2-track parallel sprints; Colliers reviews at defined gates (every 2–3 weeks). Your team owns acceptance and feedback; we own delivery. Balanced. The default we'd recommend.
BC ships to spec, hands off at milestones. Lowest involvement from your team during the build. Fastest to initial features. Risk: knowledge stays with us until handoff — harder to operate post-handoff without ongoing BC support.
No wrong answer. Different right answers for different teams. We've run all three with different clients — some teams want to learn the platform deeply, some want a deliverable. The choice shapes pricing, timeline, and what Tier (A/B/C) post-handoff support looks like.
