SAMPLE OUTPUT
Before you answer anything, look at what you'd get.
This is a redacted page from a real Architecture Audit, the five-dimension scoring, the findings underneath it, and the connector roadmap that comes out the other side. Client details are changed; the structure and the bluntness are not.
PAGE 1 OF THE AUDIT
Five dimensions, scored 0–5, with the evidence attached.
Scores are not a grade. They tell you which dimension is the binding constraint, so the roadmap starts where it actually matters.
Signal coverage
Conversation happens in three places; only one is captured anywhere durable. Two years of product truth lives in a chat history nobody can query.
Identity resolution
No stable person key across community handles, billing accounts, and support tickets. 41% of active members could not be matched to a customer record by any deterministic rule.
Data quality
CRM fields are populated and mostly trusted, but ownership is stale, 18% of accounts point at a former rep.
Routing and ownership
Escalation is a human noticing. No SLA, no queue, no record of what was routed and what was dropped.
Measurement
Engagement is reported weekly; nothing ties a community signal to a renewal, expansion, or churn event after the fact.
Illustrative composite. Numbers are drawn from real engagements but changed so no client is identifiable.
PAGE 2 OF THE AUDIT
The connector roadmap that follows from those scores.
Sequenced by dependency, not by ambition. Each phase names what it unlocks so you can stop after any one of them.
Phase 1 · Weeks 1–3
Identity spine
One person key joining community handles, billing accounts, and support identities, with a confidence score and a manual review queue for the ambiguous tail.
Phase 2 · Weeks 3–6
Community-to-CRM connector
Production connector writing resolved activity, intent scores, and thread links onto the account record, with retries, dead-letter handling, and alerting.
Phase 3 · Weeks 6–9
Routing with owners and SLAs
Scored signals routed to a named owner with a clock. Every route is logged; every drop is visible.
Phase 4 · Ongoing
Outcome measurement
Signal-to-outcome attribution against renewals and expansions, reviewed monthly against the metrics agreed at Define.
Tooling-agnostic by design.
Named tools are hardened examples of what we have already run in production, not the only systems we support. We select per-engagement, typically the tools you already own.
WHAT THE REAL ONE ADDS
The delivered Architecture Audit ($3,500 fixed) runs on your systems: your signal inventory, your identity gaps measured rather than estimated, effort and cost per phase, and a plain statement of what we would not build. It ends with a recommendation you can take to another vendor if you prefer.
NEXT STEP
Seen enough to test your own setup?
Four questions, no email required. Or bring your systems to a 20-minute call and we'll tell you plainly whether this applies.