Fact
Arc ecosystem listing anchors the real partner names used in the demo.
Interview control
Erika / Matt Demo Scorecard
A route-by-route walkthrough that ties the demo to partner management at scale, day-one readiness, Salesforce-compatible review, and Product feedback loops.
demo route order
What To Show First
| / | Thesis and role-criteria coverage | I treated this as an operating-system problem, not a partnership deck. |
| /partners | Seven real Arc-listed partner anchors | This shape scales from public anchors to hundreds of launch and post-launch partners. |
| /partners/p-003 | Dossier with blockers, dependencies, source candidates, and growth path | A useful dossier tells the owner what evidence to gather and what action comes next. |
| /sources | Source registry, signals, and adapter simulation | Public sources become evidence candidates; claims stay review-gated. |
| /review | Human review and Salesforce Sync Preview | Salesforce remains source of truth; this layer proposes sourced writes. |
| /feedback | P0/P1 triage, SLA aging, and state machine | Partner asks stop disappearing into Slack. |
| /digest | Friday macro/micro operating cadence | This creates the weekly reliability loop for partners and internal teams. |
scale and client obsession
Erika Fit
| Partner management at scale | Registry and lifecycle model | Category-driven operating layer for wallet, RPC, bridge, DeFi, RWA, payments, and custody partners. |
| Salesforce limits | Salesforce Sync Preview | Keep Salesforce authoritative; add orchestration and review around it. |
| Two-way Product bridge | Feedback and Review routes | Product updates become partner obligations; partner feedback becomes typed Product signal. |
| Specific growth opportunities | Partner dossiers | Each dossier carries a commercial opportunity and next action. |
| Client obsession at scale | Digest and SLA triage | Client obsession becomes cadence, owner, SLA, and next update discipline. |
GTM and technical-business bridge
Matt Fit
| GTM onboarding | Mock Salesforce records | Plug into existing systems before asking for new tooling. |
| Day-one readiness | Readiness gates | Readiness is a gate with evidence, not a subjective status. |
| Integration matrices | Sources and adapters | Monitor source, cadence, trust, downstream field, and review requirement. |
| StableFX / global wallet GTM | Ramp Network and MetaMask dossiers | Treat wallets and payments as program lanes with corridors and funding paths. |
| Agency | Demo flow | Technical signals become business actions without leader memory as the bottleneck. |
fact / assumption / recommendation
Defensible Caveats
Assumption
Operational readiness, SLAs, and launch commitments remain needs-review until Circle confirms.
Recommendation
Use local/mock ingestion first, then add live read-only fetches after compliance and source permissions.
Guardrail
No low-confidence signal writes to Salesforce or partner-facing language without human review.