AI workshops for go-to-market teams

Hands-on AI workshops for sales, marketing, business development and RevOps teams, built on their own pipeline, reporting and follow-up. The team sets up its own ways of working with agents, so more of its time goes to customers and partners.

Where it starts

Go-to-market teams spend much of the week on the work around the customer.

Reports to assemble, notes to file, follow-ups to send, and a CRM to keep current. What leaders of these teams tend to see:

  • weekly reports and dashboards filled in by hand
  • partner and customer calls with no time left for the follow-up
  • a CRM that only a few people fully understand
  • people using AI on their own in ways that clash in shared tools

What teams like this work on

Go-to-market teams already work from a playbook.

Writing down how the team scores a prospect, what a good follow-up looks like and what each field means turns that playbook into something agents can follow. The sessions start there.

Each workshop runs on the team’s own work. From go-to-market teams so far:

Weekly reporting

One weekly readout of progress against goals, pulled together across channels and written for the team to read.

After the call

A summary, a CRM update and a follow-up drafted after each partner or customer call, ready for a person to send.

Prospect scoring

Prospects scored against the team’s own written criteria, so a famous name doesn’t outrank a better fit.

Quotes

Quotes built across the CRM and the order system from rules the team writes and edits itself, each one approved before it goes out.

Brand checks

Marketing materials checked against the brand’s own standards before they’re used.

What stays human

Go-to-market teams keep the relationship.

  • Anything a customer or partner reads, which a person checks before it’s sent.
  • The thinking. Some work a person has to do to understand it, and that stays with them.
  • Changes to shared tools. Agents propose updates with their sources, and a person approves them until the team trusts the results.

What changes

More of the week goes to customers and partners.

On one business development team, a person who started the sessions filling in reports by hand now runs eleven skills of their own, including a daily briefing and a partnership research skill that replaced a six-step manual process. At Flare, the head of marketing went from a brand compliance check to an agent trained on how their product marketer thinks.

Questions

Will it write to our CRM on its own?

Not at first. Connections start read-only. Agents propose updates with links to their sources, and a person approves them until the team trusts the results.

Is our customer and partner data safe?

Each connection gets only the permissions it needs, email stays draft-only, and each tool goes through the team’s own security review first.

Can my team change the rules after the workshop?

Yes. The rules live in plain-language files the team edits, so the people who know the work keep them current.

If it gets a number or an account wrong, who catches it?

A person, with help. Math is done in code, outputs cite their sources, a second agent can check the first, and nothing reaches a customer without review.

Other teams

Start with a call.

Thirty minutes about your team and its work. If a workshop would help, Harry would be glad to put one together.