One agent skill, shipped live, with your team in the room. You leave the day with a real artifact your team can run on Monday — not a deck, not a roadmap.
Risk-free · Fixed price · 30-day warranty included
Risk-free. We don't invoice the Build Day until we've agreed on the skill we're shipping that day. If you walk out without something usable, you don't pay.
We pick the skill on the demo call. By Build Day morning, the scope is locked.
~2 hours
Walk through the deliverable your team produces today. Pin down inputs, outputs, and edge cases. Identify the data we need and where it lives.
~4 hours
We build the skill live in Claude Code. Your team watches and weighs in. We test it on real client data, not toy examples.
~2 hours
Run the skill end-to-end with your team. Walk through the docs. Cover how to modify, troubleshoot, and re-run. They use it themselves before we leave.
A skill isn't a chatbot. It's a parameterised process that produces a client-grade deliverable.
A skill replaces a recurring deliverable a junior currently produces in hours — turned into a 4-minute output the team triggers on demand. Below: real skill names and what they do.
weekly-client-report
Pulls data from Google Ads + GA4, drafts the performance summary, writes recommendations.
project-status-report
Generates the weekly client status update from the project tracker, risk register, and meeting notes.
research-synthesis
Synthesises stakeholder interviews and source documents into a structured findings doc.
client-onboarding-pack
Produces the engagement brief, intake doc, and first-month plan from a kickoff call transcript.
Don't see your work here? That's fine — we generalise from your actual process. The Demo Call shows you what yours could look like.
If the Build Day works, most clients want the next process built. That's the Skill Pack — same fixed-price, productized motion.
Three shipped skills, async delivery, handoff session, skill docs, 30-day warranty. Sold on count, not time.
Then we don't book the Build Day yet. We keep iterating on the demo call until we have a skill that's worth a day. We don't take payment for a Build Day that's not scoped.
The person who currently does the work, the person who decides what "good" looks like, and a process owner. Usually 2–4 people. Remote is fine if your team is distributed.
We scope so it doesn't. If a skill is genuinely larger than a day, we'd recommend the Skill Pack instead — that's where bigger or multi-skill scopes live.
Bug fixes and config tweaks. If the skill doesn't work as scoped on inputs you signed off on, we fix it free for 30 days. Behaviour changes (new outputs, new logic) are quoted as new scope.
No. Your team uses the skill, they don't build it. Running a skill is as simple as typing a command. We handle all the technical work.
Claude Code (we'll set you up). Beyond that, whatever your data lives in — we adapt to your stack, you don't adapt to ours.
Drop your details and we'll send a calendar link within 24h. On the call we run Claude Code on your actual work — live, no slides. If the Build Day's a fit, we ship a skill within a week. You don't pay if you don't walk out with something usable.