Monthly reporting that took half a day now takes half an hour
Kick Point's team had plateaued at using AI as a chat window. We ran a half-day workshop plus four weeks of reinforcement. Monthly client reporting that used to eat half a day now lands in their inbox ready for a 30-minute review.
Problem: The team had plateaued at the chat box
Gathering ideas, taking a first pass at a draft, editing something they'd already written. Useful, but nowhere near process change, and nobody knew what the next step looked like.
Approach: Pre-work, a half-day session, four weeks of follow-up
Questions sent out before the session, four hours with Keyfer and Clayton where everyone built something real for their own job, then weekly reinforcement emails on how to conceptualize the tool.
Result: Every team built something that stuck
A client intelligence database became the hub, month-end reporting dropped from half a day to a review pass, and “is there a faster way to do this” is now the first question people ask.
Who they are
Kick Point is an Edmonton digital marketing agency working across SEO, paid search and paid social, organic social, analytics (GA4 and GTM), and WordPress design and builds. Most of their clients are small and mid-sized B2B services businesses on long-term engagements.
Where they were
A couple of people were already out ahead. Dana, principal and co-founder, owns the analytics program and had been pushing into AI early. Laura, Managing Director, was running Zapier automations and had started using Claude to handle the parts Zapier couldn't: synthesis, judgment, anything that needed a decision rather than a trigger.
Everyone else had stopped at the chat box. Gathering ideas, taking a first pass at a draft, editing something they'd already written. Useful, but nowhere near process change.
Laura was hearing frustration. People were spinning their wheels any time they tried to do something more than basic chat, and nobody knew what the next step even looked like.
“There wasn't that level of, can we think about what kind of tasks could be done, actually thinking beyond just dealing in text. We needed a push to get us to what can we do to change our processes and save ourselves time.”
Why they brought someone in
“It would be really helpful to have somebody who has been doing this and gets it, who can see where we're at right now, imagine where we might be, and give us the structure to get from A to B. Having somebody external come in is just so much easier than having one person internally try to be that far ahead.”
What we did
Pre-work. A short set of questions sent to the team before the session. Most people came in saying they had no idea what they'd be able to build. The pre-work was the thing that broke that open.
“What I told everybody was, you don't need to know. Go do it. I remember getting messages from people saying, oh, this was so helpful, it changed my framing for how to think about this stuff. I saw the little bit of resistance fall really quickly.”
The session and the follow-up
A half-day session. Four hours with Keyfer and Clayton in the room. Everyone built something real for their own job, with breakouts and live help while they worked.
Weekly follow-up emails. Four weeks of reinforcement after the session, aimed at how to conceptualize the tool rather than step-by-step instructions.
Where they are now, four months later
A client intelligence database that became the hub. Laura built a system that pulls client information weekly and surfaces what she might have missed: red flags, conversations other team members had about work a client needs, context for the next contract conversation. It has opened up new work with existing clients and it's now connected to other systems in Notion that update automatically.
Monthly reporting went from half a day to half an hour. The end-of-month Google Ads change summary emails used to take Laura half a day across the client roster. They're now drafted automatically and need a review pass.
“That frees up brain space for everybody to come in and work on the thing that actually needs a human touch.”
What stuck
Every team built something that stuck. The PPC team has its own client intelligence layer. On the web team, Sarah built a set of skills to make content entry easier and has been iterating on it since. Nothing from the workshop got built once and abandoned.
The default question changed. “Is there a better way to do this, is there a faster or more automated way to do this” is now the first thing people ask, rather than something they have to be prompted toward.
“It's completely different. Before, things were siloed in tools. Now it's, we have this other tool that can see everything and do anything you want with it.”
Who this is for
Small and mid-sized companies running on a stack of tools that don't talk to each other, without a developer, an ops department, or an IT team to build the connective tissue. If your team is stuck using Claude as a glorified search engine while watching people on LinkedIn claim to do far more with it, that gap is the one this closes.