What was said
What this says
Current to 11 Oct 26Jennifer Holloway, Director of Operations at Ledgerwood Freight, described hours of manual reconciliation across Salesforce, a dispatch system, Xero and Gong. Jordan Pike sized it as Growth and promised a proposal and a follow-up call.
What happened: On 20 Jul 2026 Jordan ran a discovery call with Jennifer. She named Salesforce, a separate dispatch database, Xero, Gong recordings and support tickets as the scattered sources.
Customer view: Reconciling customer history takes hours and pulls sales time away from selling. She estimated thirty to forty users across sales, operations and customer support.
Commercial: Jordan positioned Growth with four or five connectors against the eight included. Price was asked about but no figure was given; a proposal was promised for the next day.
Watch: The dispatch system is unnamed and unconfirmed as a connector. Jordan said data-freshness issues are owned by BB-Demo, but standard Growth terms credit availability only, so the order form wording matters.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Jordan Pike to send the Growth proposal, as promised on the call.
- Jennifer Holloway to send the dispatch system name so connector fit can be checked.
- Jordan Pike to hold the follow-up conversation two weeks after the call.
Risks
Current to 9 Oct 26- The dispatch system is not named, so the connector count and whether it can be connected are unconfirmed.
- Jordan said data-freshness issues are owned by BB-Demo, but standard Growth terms credit availability only.
- Price was asked about and no figure was given on the call.
Opportunities
Current to 9 Oct 26- Growth subscription with implementation for thirty to forty users across sales, operations and support.
- Four or five connectors fit within the eight included in Growth, leaving headroom.
Transcript
- Jordan Pike NoneHi Jennifer, thanks for taking the call. Quick agenda: I want to understand your current data challenges and see if we can help. Sound good?
- Jennifer Holloway NoneSounds good. Yeah, we're definitely looking at how we can consolidate some of our data.
- Jordan Pike NoneGreat. So Ledgerwood Freight, less-than-truckload operator in the Southeast. Tell me about your current systems and where the pain is.
- Jennifer Holloway NoneWe use Salesforce for customer relationship management, but we've also got a dispatch system that's basically a separate database. Our accounting is handled by another platform. And then we've got call recordings, customer support tickets. It's kind of all over the place.
- Jordan Pike NoneYeah, that's common in logistics. So if you wanted to know, say, all the freight we've moved for a customer this year and whether they've paid, you're pulling from different systems?
- Jennifer Holloway NoneExactly. Salesforce, the dispatch system, accounting, takes hours to manually reconcile. And our sales team wastes time figuring out customer history when they could be selling.
- Jordan Pike NoneOK. How many people would need access to something like this? Just sales, or wider?
- Jennifer Holloway NoneSales, operations, customer support. Maybe thirty to forty people across those teams.
- Jordan Pike NoneThat's solidly in Growth range for us. So let me ask about your systems. Salesforce for CRM, obviously. What's the accounting platform?
- Jennifer Holloway NoneWe use Xero.
- Jordan Pike NoneGood, we connect with that. The dispatch system, is that a third-party product or something you've built?
- Jennifer Holloway NoneThird-party. Pretty standard logistics software.
- Jordan Pike NoneI'll need to check on that one. Do you have the name handy?
- Jennifer Holloway NoneI can send it to you after this call.
- Jordan Pike NonePerfect. And calls, do you record them?
- Jennifer Holloway NoneWe do, yeah. We use Gong.
- Jordan Pike NoneGreat, that's no problem. So we're looking at four, maybe five connectors depending on the dispatch system. Growth comes with eight, so you'd be in good shape.
- Jennifer Holloway NoneWhat does implementation look like?
- Jordan Pike NoneGrowth implementation is eight weeks. We'll work with your team on connectors, data governance, and then training. During that time we're pretty hands-on, anything that gets stuck, you reach us directly.
- Jennifer Holloway NoneAnd after we're live, how does support work?
- Jordan Pike NoneOne-hour response time if something breaks. You get quarterly business reviews with our team so we're tracking whether you're getting value. And any data-freshness issues, we own those.
- Jennifer Holloway NoneHow much is this going to cost?
- Jordan Pike NoneGrowth is an annual subscription plus a one-time implementation fee. I'll put together a detailed proposal and send it over, probably tomorrow. Then we can have a follow-up conversation about whether it makes sense for you.
- Jennifer Holloway NoneFair. When would you want to follow up?
- Jordan Pike NoneHow about two weeks from now? That gives you time to review, talk with your team internally, and we can dig into any questions.
- Jennifer Holloway NoneTwo weeks works.
- Jordan Pike NonePerfect. I'll get that proposal over tomorrow and we'll touch base in two weeks. Thanks, Jennifer.