Copperlane Payroll / BB-Demo – Kickoff
Callcompleted
Copperlane Payroll: documents · 2025-06-05 11:30
Kickoff for a four-week build. Hamza Akhtar set out the plan and Marcus Bell the post-go-live support. Rebecca Nuttall and Ian Brearley asked practical questions about validation and issues after go-live, with no concerns about value or price.
What was said
What this says
Current to 11 Oct 26Kickoff for a four-week build. Hamza Akhtar set out the plan and Marcus Bell the post-go-live support. Rebecca Nuttall and Ian Brearley asked practical questions about validation and issues after go-live, with no concerns about value or price.
What happened: Hamza Akhtar walked Rebecca Nuttall and Ian Brearley through a four-week plan: requirements, connector build with weekly sample pulls, final testing, then a Friday go-live.
Customer view: Ian asked what a normal validation cycle looks like and what happens if data issues appear after go-live. Rebecca checked who owns what, with Ian validating and Marcus Bell running training and adoption.
Commercial: Nothing on price, rivals or renewal was said. The call sets up the adoption path Marcus owns: training after go-live, a check-in two weeks later, then quarterly.
Watch: Delivery depends on Copperlane giving admin access to the payroll system, billing system, CRM and call recorder, and on Ian turning samples around each week.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Hamza to send the access requirements checklist and set weekly Monday calls for the four build weeks.
- Marcus to schedule training after go-live and a check-in two weeks later.
Risks
Current to 9 Oct 26- Go-live depends on timely admin access to four source systems and weekly sample validation by Ian.
Opportunities
Current to 9 Oct 26- A smooth go-live and training session starts the adoption record that supports the first renewal.
Transcript
Hamza Akhtar NoneRebecca, Ian, great to have you both. I'm Hamza, the implementation consultant, and this is Marcus, your customer success manager. We're going to plan out the next four weeks.
Marcus Bell NoneI'll be your main point of contact once you go live. Questions, feedback, adoption, that's me. Hamza's going to run the technical build.- Hamza Akhtar NoneSo here's the timeline. Week one, that's starting next Monday, I'm gathering requirements. I'll need admin access to your payroll system, billing system, CRM, and call recorder. I'll also need a test user account in Snowflake. From that, I'll build a data map, shows how each system's tables connect together.
Ian Brearley NoneWhat do you need from us in week one?- Hamza Akhtar NoneMainly access and a bit of your time. I'll ask you questions about your data: how you structure payroll records, whether there are any quirks in your billing system, that sort of thing. A couple of hours probably.
Rebecca Nuttall NoneAnd weeks two and three?- Hamza Akhtar NoneI'm building the connectors. Payroll connector pulls from your payroll system, normalises the data, loads it into Snowflake. Same for billing, CRM, call recordings. I'll do a sample data pull each week and send it to you, you validate it, tell me if anything looks wrong.
- Ian Brearley NoneWhat's a normal validation cycle?
- Hamza Akhtar NoneYou get the sample on, say, Tuesday. You look through it, spot any oddities. We have a review call Wednesday. I take feedback, make adjustments, send a new sample Thursday. Most connectors are good to sign off after one or two cycles.
- Rebecca Nuttall NoneAnd week four is go-live?
- Hamza Akhtar NoneYeah. Week four is final testing, we run queries, you validate the results. Once you're confident the data is clean, we go live. That's typically midday on a Friday, gives us the weekend to monitor if anything goes wrong.
- Marcus Bell NoneOnce you go live, I'll schedule a training session: walk you through search, chat and dashboards. That's usually a couple of hours. Then we'll do a check-in two weeks later, see how adoption's going.
- Ian Brearley NoneWhat happens if we find data issues after go-live?
- Hamza Akhtar NoneYou message the helpdesk, we investigate. If it's a data mapping thing, I fix it in the connector and it's right on the next refresh. If it's something in your source system, we work with you to fix it there. Nightly refresh complete by seven every morning.
- Rebecca Nuttall NoneSo I've got Ian validating the connectors week by week, and then Marcus is running training and adoption after go-live?
- Marcus Bell NoneThat's right. Hamza's the build lead; I'm adoption and ongoing support. We'll do a check-in in two weeks, then quarterly after that.
- Hamza Akhtar NoneI'll send the access requirements checklist today. Systems, Snowflake user, that sort of thing. Once I've got that, I'll build out the data map and we'll schedule weekly calls, Mondays work?
- Ian Brearley NoneMondays are fine.
- Hamza Akhtar NoneBrilliant. Let's put them in the diary, Mondays for the next four weeks, same time. I'll send you an invite. Cheers, both.