Copperwick Logistics / BB-Demo – Kickoff
Callcompleted
Copperwick Logistics: documents · 2026-06-08 17:30
Kickoff for Copperwick's Growth brain. Salesforce first, then the TMS, then support. Several owners are still unnamed, Salesforce duplicates will be flagged after load, and margin fields stay out of the first load.
What was said
What this says
Current to 11 Oct 26Kickoff for Copperwick's Growth brain. Salesforce first, then the TMS, then support. Several owners are still unnamed, Salesforce duplicates will be flagged after load, and margin fields stay out of the first load.
What happened: Hollie Grieve confirmed the 1 Jun 2026 signing, the term to 31 May 2027 and forty licensed users. Laura Penhaligon agreed the connector order and Salesforce prerequisites with Lauren Pacheco and Tyler Nguyen.
Customer view: Lauren wants one view per shipper and wants to hear the moment a connector goes live. She accepts a thinner first version and a small pilot group of reps.
Commercial: Only a handful of reps will use it at first, so forty licences leave plenty of headroom. Early value depends on a good first Salesforce load and the pilot reps' experience.
Watch: The TMS owner and Snowflake admin are not yet named. Tyler flagged patchy lane data and duplicates, and he chose a sandbox first, which adds a few days.
Themes
Current to 9 Oct 26Theme
Growth implementation kickoff
Importance
neutral
Sentiment
positive
Voice
decision-maker
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Tyler Nguyen to complete the Salesforce prerequisites and start merging duplicates from Laura Penhaligon's list.
- Lauren Pacheco to name the TMS owner and the Snowflake admin and add them to the next session.
- Hollie Grieve to send the action email with owners and time options, then connector go-live notes.
Risks
Current to 9 Oct 26- Salesforce lane data is patchy with duplicate shippers, which could undermine the one-view-per-shipper use case.
- Owners for the TMS and the Snowflake admin are not yet named, which could delay the second and third connectors.
- Lauren Pacheco wants instant visibility of connector go-lives and a quick time to value, so slippage would show.
Opportunities
Current to 9 Oct 26- A small pilot group of reps is expected to prompt requests for wider access across the forty licences.
- Margin fields are deferred, so a later access decision could widen use of the brain.
Transcript
Hollie Grieve NoneHi, hello. Can everyone hear me? Lauren, Tyler, good to see you both. Laura's just coming in from the other room.
Lauren Pacheco NoneHi Hollie! Yep, got you loud and clear. Hi Tyler. Sorry it's the evening for you, I know it's late over there.- Hollie Grieve NoneNo, that's fine, honestly. It's a good time for us to catch you before your day wraps up. Tyler, can you hear us all right?
Tyler Nguyen NoneHey, yeah, I'm good. Give me one second, my mic keeps switching to the laptop. There. Better?
Laura Penhaligon NoneEvening, all. Laura Penhaligon, I'm the implementation consultant, so I'll be the one in your Snowflake and your Salesforce over the next few weeks. Sorry, I was dialling in on the wrong link.- Lauren Pacheco NoneNo problem! Quick agenda from me, if that's okay: who owns what, which connectors go first, and what I need to tell my reps and when. And I have a hard stop at the end of the hour.
- Hollie Grieve NonePerfect, that's basically my list as well. Just so we're level before we start, you signed on 1 Jun 2026, so you're a week in. The term runs to 31 May 2027, and renewal falls on 1 Jun 2027. You're on Growth, with forty licensed users.
- Lauren Pacheco NoneForty users. We only have a handful of reps who'll live in it day to day at first, so we're fine on that for now. What's the time to value?
- Laura Penhaligon NoneGrowth implementation takes about two months end to end. But I'd expect your reps to see Salesforce data in the brain a lot sooner than that. The connector order matters, so let's agree that today.
- Lauren Pacheco NoneOkay. Salesforce first, obviously. Then the TMS. Then support. That was the idea when we bought.
- Laura Penhaligon NoneThat's how I've got it written down too. Tyler, this is where you come in. For Salesforce, I need a dedicated integration user, read access to the objects Lauren cares about, and to know if there's anything custom we should be aware of. Accounts, contacts, opportunities, cases?
- Tyler Nguyen NoneYeah. So, we have accounts and contacts, standard. Opportunities, yes. And then we have a pile of custom objects for loads and lanes. I'd have to check which of those are actually clean. Some of them are, uh, let's say a work in progress.
- Lauren Pacheco NoneTyler, be honest, how bad is it?
- Tyler Nguyen NoneNot bad. The load object is good because everyone uses it. The lane one is patchy. Reps have been creating duplicates for a couple of years, and I keep meaning to merge them.
- Laura Penhaligon NoneThat's useful to know up front, thank you. Duplicates won't stop us connecting, but they'll show up in the brain as the same shipper appearing twice, and Lauren's whole use case is one view of each shipper. Can we decide whether to clean first or load first?
- Lauren Pacheco NoneOh, I don't love the idea of reps seeing doubles. But I also don't want to wait on a clean-up project. Can we load and flag them?
- Laura Penhaligon NoneWe can. My suggestion is we load, I give Tyler a list of likely duplicate shippers from what the brain sees, and he merges from the top of that list. Then you're not guessing which ones matter.
- Tyler Nguyen NoneOkay, I like that better than doing it blind. Send me the list and I'll set aside time for it.
- Hollie Grieve NoneI'll note that as an action for Tyler, with Laura sending the list once Salesforce is live. Lauren, you'd want to know the moment that happens, right?
- Lauren Pacheco NoneYes, please. I never want to wait for a monthly report to find out something's happening.
- Hollie Grieve NoneUnderstood. For the first few weeks I'll send you a short note whenever a connector goes live, and we can set the regular rhythm afterwards.
- Lauren Pacheco NoneLove it. Who's the owner on your side if something breaks?
- Hollie Grieve NoneDuring implementation, Laura. After go-live, it's me for adoption and the relationship, and support tickets go through the normal route. Jordan Pike remains your account owner for anything commercial.
- Lauren Pacheco NoneGood. And on our side, I'm the business owner. Tyler is technical owner for Salesforce. I need an owner for the TMS and for support too. I don't tolerate vague owners, so let me sort that out this week.
- Laura Penhaligon NoneThat'd be great, because the next piece is the transport management system. I'll need to know what it exposes: an API, database access, or flat file exports. That decides how we connect it.
- Tyler Nguyen NoneI think it has an API, but I'm not the one who looks after it. That's the operations systems team. Honestly I've never seen their documentation.
- Lauren Pacheco NoneI'll find out who that is and get them on the next call. Is that fine?
- Laura Penhaligon NoneThat'd be ideal. If they can join for fifteen minutes with the documentation, we can settle the method in one sitting rather than going back and forth by email.
- Hollie Grieve NoneQuick question on Snowflake while we're on infrastructure. Tyler, who has admin there? Laura will need an account set up inside your environment.
- Tyler Nguyen NoneThat's our data engineer, not me. I'm in Snowflake as a user but I can't create roles. I'll ask him to join as well.
- Lauren Pacheco NoneSo that's two more people. TMS owner and the Snowflake admin. I'll put them on the invite. Can we do the next session early next week?
- Laura Penhaligon NoneEarly next week works for me. I'd like to leave this call with the Salesforce prerequisites agreed and the other two sorted out. Shall I walk through what I need for Salesforce, step by step? It takes five minutes.
- Tyler Nguyen NoneYeah, go for it. I'll write it down.
- Laura Penhaligon NoneSo, first, the integration user with read-only access to the objects we listed. Second, a connected app or whichever authentication method you prefer. Third, a list of the custom objects you want in and the ones to leave out. Fourth, confirmation of any fields containing sensitive data that we should mask or skip.
- Tyler Nguyen NoneSensitive data. Hm. Probably some driver details on the load object. I'll check what's actually in there.
- Lauren Pacheco NoneAnd pricing fields. Reps can see their own margin on loads, but I don't want that visible to everyone through the brain. Can the brain respect that?
- Laura Penhaligon NoneThat's exactly the kind of thing we settle at this stage. The simplest approach is to leave those fields out of the first load and decide on access afterwards. I'd rather be careful than have to pull something back.
- Lauren Pacheco NoneYes. Leave margin out for now. We can add it once I've talked to Mike about who should see it.
- Hollie Grieve NoneGood call. Let me ask about users. You've got forty licences. Lauren, who do you want in the first group? Because the early experience shapes how everyone else sees it.
- Lauren Pacheco NoneA small pilot group. A few reps on the biggest shippers, plus me and Tyler. If the reps like it, the rest of the team will ask for access, they always do.
- Hollie Grieve NoneThat's the pattern we like to see. I'll plan a short training session for the pilot reps once Salesforce is live, so they're asking real questions about their own shippers on day one.
- Lauren Pacheco NoneYes! Can we see it by shipper? That's what I'll ask them to try first.
- Laura Penhaligon NoneThat should work once the Salesforce accounts are in, and it improves as the TMS and support data arrive. The shipper view gets richer with each connector, so the first version will be thinner than the third.
- Lauren Pacheco NoneFine. I'd rather set that expectation with the reps than have them think it's broken.
- Hollie Grieve NoneAgreed. I can give you a couple of lines for the team announcement, if that helps.
- Lauren Pacheco NoneThat would help a lot, thanks.
- Tyler Nguyen NoneOne more thing from my side. Do you need a sandbox of ours, or are you going straight to production Salesforce?
- Laura Penhaligon NoneRead-only into production is normal and low risk, since we're not writing anything back. But if you'd feel safer starting in a sandbox, we can test the connection there first and then repeat it in production.
- Tyler Nguyen NoneI'd prefer that. Just so I can see what it does before it touches real data.
- Laura Penhaligon NoneSensible. Then sandbox first, production after you're comfortable.
- Lauren Pacheco NoneHow does that affect the timeline?
- Laura Penhaligon NoneMarginally. A few days at most, and it saves problems later. The Salesforce piece should still be well ahead of the other connectors.
- Lauren Pacheco NoneOkay. Let's do that. Hollie, can you put these actions in an email so I can forward them to the team?
- Hollie Grieve NoneOf course. I'll send it tonight, with owners against each action: Tyler for the Salesforce prerequisites and the duplicate merges, Lauren for the TMS owner and the Snowflake admin, and Laura for the connection and the duplicate list.
- Lauren Pacheco NonePerfect. And the next session early next week, with the other two people on it.
- Hollie Grieve NoneYes. I'll send a couple of time options with the email. Thanks, everyone, that was a really useful kickoff.
- Lauren Pacheco NoneThanks! Lauren. Talk soon.
- Tyler Nguyen NoneThanks, everyone. Speak next week.
- Laura Penhaligon NoneBye for now.
Callsmade from