Jordan Pike

Pemaquid Analytics / BB-Demo – Proposal

Callcompleted

Pemaquid Analytics: documents logo Pemaquid Analytics: documents · 2026-07-27 16:45

On the 27 Jul 2026 proposal call, Raymond Tsai, the CFO, questioned payback and seat use on a £4,011 expansion. He will decide only after seeing a usage page, wants one year only and will not pay early.

What was said

What this says

Current to 11 Oct 26

On the 27 Jul 2026 proposal call, Raymond Tsai, the CFO, questioned payback and seat use on a £4,011 expansion. He will decide only after seeing a usage page, wants one year only and will not pay early.

What happened: Jordan Pike presented a £4,011 expansion on its own order form, with the Growth subscription staying at £50,000 a year. Raymond pressed for payback and seat use.

Customer view: Raymond said the benefits were nice but not a number. Jordan accepted that the active group is well below the 40 licensed users, and Caitlin Mercer named a key-person risk around Tyrell.

Commercial: Raymond will sign only if the usage is moving, wants one year with no multi-year term and will not pay early. Records point to a close around 29 Sep 2026; this call does not show whether that happened.

Watch: Raymond sees the Growth seats as partly unused, so the value case for the 1 Apr 2027 renewal is still open.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Expansion proposal, payback doubts
Importance
upsell
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hollie Grieve is to deliver the usage page before the order form is sent.
  • Jordan Pike is to send the recap and then the order form once the usage page has been seen.
  • Caitlin Mercer is to gather the team names so the usage view makes sense.

Risks

Current to 9 Oct 26
  • The CFO sees paid seats going unused and wants a number for payback before committing to the expansion.
  • Questions are concentrated in one or two people, a key-person risk the VP Customer Success raised herself.
  • The CFO will not pay early and wants one year only, so the expansion adds no multi-year commitment.

Opportunities

Current to 9 Oct 26
  • A separate expansion order form for the Growth account, aimed at account managers and support leads.
  • A monthly one-page usage view by person and by team could give the CFO the value case he asked for.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Hi Caitlin, hi Ray. Thanks for joining. One line agenda: I want to walk you through the expansion proposal and get to a clear next step. We have 30 minutes, so I'll keep an eye on the clock.
  2. Caitlin Mercer
    Caitlin Mercer None
    Great. Quick one before we start, because it's how I begin every week: renewals. We had a good week, nothing slipped, two that I was nervous about both came through. So I'm in a good mood.
  3. Raymond Tsai
    Raymond Tsai None
    Good afternoon. Jordan, what's the number?
  4. Jordan Pike
    Jordan Pike None
    Ha, straight in. Okay, Ray, here's where we are. The expansion is £4,011. That's the total value of this piece of work, not an annual price for your whole subscription. Your Growth subscription stays as it is, at £50,000 a year.
  5. Raymond Tsai
    Raymond Tsai None
    Understood. £4,011 in total. What's the payback?
  6. Jordan Pike
    Jordan Pike None
    To be transparent, I can't give you a payback number that I'd stand behind without Caitlin's view of where the team's time goes. So Caitlin, maybe you can say what you've seen since you've been live.
  7. Caitlin Mercer
    Caitlin Mercer None
    Sure. So, three things. One, renewal prep used to take my team most of a morning per distributor and now it's a page they open. Two, Tyrell built a dashboard that I actually use in the Monday meeting. Three, more of the team are asking the brain questions, not just Tyrell. What's the signal? The signal is that people stopped asking me where to find things.
  8. Raymond Tsai
    Raymond Tsai None
    That's nice, but it's not a number. How many seats are we using?
  9. Jordan Pike
    Jordan Pike None
    Fair question. You have 40 licensed users. The active group is a lot smaller than that today, but it has grown quickly since the spring. So you have headroom, and that's actually part of why I'd say this expansion is about reach and not about seats.
  10. Raymond Tsai
    Raymond Tsai None
    So we're paying for seats we're not using.
  11. Jordan Pike
    Jordan Pike None
    Right, and I'd rather say that to you plainly. You're not at the limit, and I'm not going to tell you that you need more users. What I'd say is the question is how to get more of the team onto what you already have, and the expansion is aimed at that.
  12. Caitlin Mercer
    Caitlin Mercer None
    And Ray, that's what I want to say to you as well. I'd rather we fill what we have. The expansion is what lets the account managers and the support leads see the same view, so that when a distributor calls, nobody's surprised.
  13. Raymond Tsai
    Raymond Tsai None
    Okay. What happens if we don't do it?
  14. Jordan Pike
    Jordan Pike None
    Nothing breaks, to be transparent. Your subscription runs as it does today. You'd keep working with the group that's on it now. The expansion just widens who benefits.
  15. Caitlin Mercer
    Caitlin Mercer None
    Can I add, though, the thing I'm worried about is that if it stays with a few people, I become the person who explains it to everyone else. That's a key person problem, honestly. Tyrell is great but I don't want it all sitting with him.
  16. Jordan Pike
    Jordan Pike None
    That's a good point, and it's one I see a lot. When one or two people ask most of the questions, you carry a risk if they move on. Spreading it is the protection.
  17. Raymond Tsai
    Raymond Tsai None
    Fine. I don't need product detail. Is it a separate order form?
  18. Jordan Pike
    Jordan Pike None
    Yes. It would be its own order form, and your renewal date stays where it is. I'd send it over once we've agreed the scope, and what we have in our records is that you'd be looking to close around Tuesday 29 September 2026. Does that timing work?
  19. Raymond Tsai
    Raymond Tsai None
    That works. I'd want it before then, so I can review it. And it's one year only. No multi-year.
  20. Jordan Pike
    Jordan Pike None
    Understood, nothing multi-year. Your current term runs to 31 Mar 2027 and renews on 1 Apr 2027, and we'd keep it simple.
  21. Caitlin Mercer
    Caitlin Mercer None
    Can I ask about the dashboard side? Can we get that on a dashboard, I mean the adoption numbers? Who's using what, by team, so I can show Ray.
  22. Jordan Pike
    Jordan Pike None
    Yes, usage by person and by team is something we can set up with Hollie and the team. I'll make sure that's part of the follow up. Then Ray gets an answer to how many seats are we using, every month, without asking.
  23. Raymond Tsai
    Raymond Tsai None
    I'd like that. Monthly. One page.
  24. Caitlin Mercer
    Caitlin Mercer None
    One page, got it.
  25. Jordan Pike
    Jordan Pike None
    So here's where we are. What would make this a yes for you, Ray? Let me ask it straight.
  26. Raymond Tsai
    Raymond Tsai None
    Show me the usage page first. Then the order form. If the usage is moving, I'll sign. I'm not paying early, though. Normal terms.
  27. Jordan Pike
    Jordan Pike None
    Normal terms, understood. So the order is: the usage page from Hollie, then the order form from me, then you decide.
  28. Caitlin Mercer
    Caitlin Mercer None
    That works for me. I'll get the team names together so the usage view makes sense, and I'll tell Tyrell. Let's operationalise it.
  29. Jordan Pike
    Jordan Pike None
    Perfect. I'll send a short recap this afternoon, with the order form to follow. Anything else from either of you?
  30. Raymond Tsai
    Raymond Tsai None
    No. Thank you.
  31. Caitlin Mercer
    Caitlin Mercer None
    Nothing from me. Thanks Jordan. Best, Caitlin. Talk soon.
  32. Jordan Pike
    Jordan Pike None
    Thanks, both. Have a good rest of your day.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only