ServicesThree pillars, one system

OutboundPipeline from cold↗ABMNamed accounts, warm market↗RevOpsData, routing, reporting↗

OUTBOUND

Pipeline you can plan around

Low volume, high intent, inboxes that actually land.

GTM BrainFOR OUTBOUND

It gets sharper with every reply it reads.

← All skillsOPERATIONS

The Skill That Writes Skills

Describe a process once and it becomes a command.

›[skill-writer]Leave your work email and Claude writes your version of this skill from your domain, against your ICP, your offers and your market. We send it over when it is built.PERSONALISED INSTANTLY · NO CALL REQUIRED

EXAMPLE RUN

[skill-writer] our QBR prep processReading the description, asking for the missing decisionsStructuring triggers, inputs, steps and output shapeWriting the skill file and 5 starter promptsSkill file ready. Installed and shareable across the workspace.

THE SHORT VERSION

Every team has a job only one person does properly. This is how that job stops being a person and starts being part of the system.

YOU GIVE ITA plain description of how you do something today.

YOU GET BACKA finished skill file, starter prompts, and a troubleshooting guide. Shareable across your whole workspace.

It interviews you first

A description of a process is always missing the decisions the person making them stopped noticing years ago. The skill asks about those: what happens in the edge case, which field matters, what makes an output wrong. Then it writes.

What it produces

A finished skill file with triggers, inputs, steps and a defined output shape

Five starter prompts, so nobody faces a blank box

A troubleshooting guide for the day it returns something strange

Something shareable across the whole workspace rather than living in one person's history

Why the output shape matters

Two people running the same skill should get results in the same format. That is what makes the output reviewable, comparable week to week, and safe to put in front of a client. A prompt cannot promise that; a skill file can.

The real use case

Every team has one job that only one person does properly, and that person is a bottleneck and a risk. This is how that job stops being a person and becomes part of the system.