services/pilot.md
We design your next pilot or redesign the one that's running. The goal is a pilot you can replicate, scale and convert. We sit in on your pilots and talk with the people in them. Then we rebuild the criteria, the buyer, the date and the path to a contract.
Usually [2 to 3 weeks]. It works before kickoff or in the middle of a pilot.
From conversations to instructions your agents run
how-it-works.md
We sit in on pilot check-ins. We talk one to one with your pilot team. We talk with the customer's champion and users when they're available. We look at past pilots too.
Check-ins and interviews are transcribed with your permission and your customer's.
We write up what's blocking conversion. We show the pattern behind the pilots that stalled. It's usually missing criteria, a missing buyer, no decision date or no agreed contract.
We turn the readout into the pilot file. It holds the criteria the customer signs, the named buyer, the decision date and the contract. We add a skill that reads your usage data and check-in notes every week. Both go into a restricted project only your pilot team can see.
pilot.md
A pilot converts when everyone agrees on what a yes looks like before it starts. Everyone also knows who says yes. Every pilot we design has these. The next pilot can run the same way.
Three at most. Each one is measurable. The customer agrees to them in writing.
Named and in the room by week two. The champion brings them in.
On the calendar from day one. The conversion conversation is booked before the pilot ends.
Scope, price and term are agreed up front.
A check-in tracks results against the criteria. Warning signs get raised the same day.
Results against each criterion. It's ready for the CFO the week the pilot ends.
Already running a pilot that's drifting? We redesign it. We reset the criteria with the customer. We bring the buyer in. We set the date.
what-you-keep.md
Each file is a set of instructions. It tells an agent what to read, what to do and what to produce. A person approves anything that goes out. We optimize them for your tech stack. They feed your agents from the day we hand them over. The readout is the working document behind them.
What the pilot people said. What's working and what isn't. The pattern across your pilots. Customer names stay out of shared copies.
How it's loaded
It lives in your gtm/ folder as the source. Shared copies leave out customer names.
One file per pilot. It holds the success criteria and who's who. It holds the decision date, the contract and a weekly log. It's restricted because it names the customer's people.
How it's loaded
It lives in a restricted project or folder. Only your pilot team and their agents can read it.
The kickoff checklist and weekly check-in prep. The warning signs. The conversion conversation.
How it's loaded
We install it as an Agent Skill. It reads the pilot file and your usage data. It also reads the check-in notes.
Twenty minutes. You'll leave knowing whether you're in a red ocean or a blue one. You'll know what that means for how you sell.
Book a 20-minute call