Portfolio copy. Partner and company names have been changed; all figures are illustrative. This is a working enablement framework produced for a payments referral engagement — including the interactive note-taking layer used to run revision cycles with the client.
One home where a rep signs on, gets profiled, adds contacts, and the machine builds the rest — research, game plan, training, objection practice, debrief, handoff, and a live view of the pipeline and their money. The rep's whole job stays tiny: make the warm intro, book the meeting with Marcus.
If copy is blocked in this viewer, select all below and copy manually.
This is the spine of the tool — the rep rides the rail left to right. Stations 0–1 happen once; stations 2–6 repeat per contact; station 7 runs forever.
Two inputs the rep taps in seconds — relationship × comfort — decide the intro path and talk track for every contact. No ML required: a rules engine over clean inputs, with AI writing the prose on top. Tap a cell.
START HERE — the auto-sorted first deal. Casual, personal intro; likely close; builds the confidence every later rep runs on.
Once "Loop Marcus in" is hit, Marcus owns the path to close — and the portal keeps the rep in the loop with stage notifications, check-in prompts, and a residual ledger that accrues as their friends' businesses process. This is the retention engine.
Stage changes push a notification to the rep. Manager drags stages in MVP; automated feeds later.
Residuals per merchant, accruing as volume is processed.
Gated: requires the processor’s per-merchant residual reporting (API or monthly file) + the 1099 sub-agent vs. direct-pay decision. Figures illustrative.
No ML, no raw call recording, no CRM-grade complexity until the loop is proven with Devon and one or two more reps.
Each one blocks a specific feature — settle them in this order.