Here's the call. Here's what Mallin noticed. Here's what Marcus asked next, and the deck he walked into the follow-up with. No slide of it was written by him.
The call
Pulled from a 45-minute discovery call. Real cadence — speakers cut each other off, timeline questions get vague answers, the load-bearing fact arrives sideways.
12:43Cara …yeah, so we're on QuickBooks plus Shopify Plus, and, um, the wholesale chargebacks from Target — Diana and I are spending like two days a week on this. Between us. It's bad. We've, you know, we've outgrown the stack.
13:08Marcus Two days a week — wow, okay. Is this — sorry, is this a project Heritage Brands IT is leading, or are you guys, like, running this independently from the parent?
13:14Cara We're running it. I mean —
13:15Marcus — sorry, yeah —
13:15Cara no, no, you're good. We're running it. We'll loop them in eventually, but right now it's me and Diana figuring out what's right for us specifically.
13:22Marcus Got it. And — sorry, just to make sure I understand — Heritage Brands IT, when you say "loop them in," that's after you've picked something? Or like —
13:27Cara After. Yeah. They'll have to bless it but they're not in the room right now. the Heritage CFO — he'll want to see whatever we land on.
13:35Marcus Okay. What's the timeline looking like?
13:37Cara We'd love to be on something by end of year. Has to be running before holiday 2026 — the Ulta launch is January and Diana's been killing herself on the SKU isolation piece, which is — actually let me come back to that. Where were we?
13:51Marcus Timeline.
13:52Cara Right. End of year, ideally. The Heritage CFO's been hands-off so far. But he'll want to see it.
…38 more minutes. Pricing range stays vague; demo timing gets a "we'll get back to you."
What changed the read
Mallin connects two facts Marcus can't hold in his head mid-call: who Cara was 9 weeks ago, and what her end-of-2026 deadline really means.
What she said
“We're running it. We'll loop them in eventually.”
Sounds reasonable. It's misleading.
What Mallin already knew
Cara joined Maven Beauty 9 weeks ago from Lumen Botanicals — another Heritage Brands portfolio brand.
She came from another Heritage brand — so she already knows how Heritage operates. Her end-of-2026 deadline matches when Heritage plans to fold Maven Beauty in. Heritage is already shaping this deal, even if its IT team isn't in the room yet.
The one decision that matters most
Find out who you're really up against — before you talk price. Walk out with one answer: has Heritage IT formally engaged on system selection, or is Maven Beauty running this independently? Everything else depends on the answer.
What the rep asks next
Not a methodology checklist. The questions are written for THIS deal — Cara's lateral move, the holiday timeline, the Heritage CFO mention. Each line ties to what the answer actually tells the rep.
“How are you scoping this with Heritage IT — joint decision, or running independently?”
Why → The single fact that tells you whether you're closing a deal or just doing their homework for them.
“What systems are you running today — Maven Beauty side AND any shared with the parent?”
Why → Surfaces the silent Corveon competitor without naming it first.
“Where's the most painful manual work right now — month-end close, EDI compliance, or inventory visibility?”
Why → Anchors discovery on pain. Forces a specific answer instead of “lots of things.”
“What does the integration roadmap with Heritage look like over the next 12 months?”
Why → Tells you whether the FY26 integration mandate is hands-on or arms-length.
“Who else should be in the next conversation — Diana? Heritage IT? An implementation partner?”
Why → The honest answer reveals who really decides — not who the org chart says.
“If we got to commercial terms, does sign-off stay inside Maven Beauty or escalate to Heritage?”
Why → Surfaces the budget threshold. Above it, you're selling to two companies.
The deck
Four slides from the deck Mallin built for Marcus's follow-up. Specific to the call, specific to where the deal is. No slide of it was written from a template.
“I didn't write a slide of this.” — Marcus, looking at the deck four minutes after his discovery call ended. The product mapping — which Meridian modules address which Maven Beauty pain — comes from what Mallin already knows about the deal. The rep doesn't research it again.
The move, executed
The read told Marcus what matters. Then Mallin does the work: it drafts the CRM update and the deck to the room, and executes each only when he approves — from his own systems. Nothing touches a prospect or the record on autopilot.
One approval queue. One audit trail. Nothing on autopilot.
What changes operationally
Not “features.” Not “workflows.” What the rep's calendar actually loses.
When a call lands, Mallin re-reads the deal and re-renders the brief. The next prep is already done before you sit down for it.
Not a methodology playbook. The questions, the warnings, the framing — all reference your account by name. Generic MEDDPICC becomes specific decision math.
Stop rebuilding slides every Monday. The follow-up deck is generated from what Mallin already knows about this deal — recent events, stakeholders, the decision frame, the questions you got real answers to.
What this gives back
Fewer hours rebuilding prep.
45 minutes scanning a transcript becomes 4 minutes reading a brief that already named the load-bearing fact.
Fewer repeated deck edits.
The next deck starts from what was actually said on the last call, not from a generic template.
Fewer forecast reviews on stale reads.
Pipeline reads stay current between meetings. Reviews triage what changed, not what happened weeks ago.
Directionally consistent with sales-productivity research from Salesforce State of Sales, McKinsey, Gartner CSO, and Forrester field studies on rep time allocation.
What does your Tuesday morning look like
when every brief is already this specific?