From Claudient — Small Business
- You run a creative, marketing, design, dev, or content agency with 2-25 people - Proposals are eating your senior team's time — each one takes 4-8 hours and you're losing deals to faster competitors
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudient-small-business:agency-operationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- You run a creative, marketing, design, dev, or content agency with 2-25 people
Say:
"I run a [agency type — creative, marketing, dev, content, design, PR, etc.] agency with [N] people in [city / remote]. We're [generalist / niche-specialist] in [specialty]. Our average engagement size is [$X] over [timeframe]. Our brand voice is [direct-and-confident / collaborative-and-warm / playful-irreverent / consultative-precise]. Our top 3 deliverables by revenue are [list]. Our typical client looks like [persona]."
The single highest-ROI agency workflow is proposal automation. Most agencies lose deals to competitors who get proposals out in 24 hours when the agency takes 4-7 days.
Say:
"We just had a discovery call with [prospect — name, company, role, industry]. Their stated problem is [problem]. The underlying problem we read is [your read]. They mentioned budget around [$X] and timeline [Y]. Draft: (1) a proposal email summarizing what we heard, (2) a 1-page scope draft including deliverables, timeline, team structure, and price, (3) three references from past work most similar to this engagement."
You get the draft within 90 seconds. Your senior team edits — usually 15-20 minutes of work — and you have a proposal out before the prospect's coffee with your competitor.
Status updates are the most-skipped operational task in agencies. They're skipped because they're tedious and the format isn't standard across PMs.
Say:
"For client [name], here's what happened this week: [deliverables shipped, blockers, decisions, dependencies, next steps]. Draft a structured weekly status update email in our voice: clean structure, no fluff, ends with a clear "what we need from you" section."
Make this a Friday afternoon ritual across the agency. Every PM uses the same workflow. Clients notice the consistency.
When you win a deal, you need a clean SOW.
Say:
"Based on the approved proposal for [client], draft a Statement of Work covering: (1) deliverables with acceptance criteria, (2) timeline with milestones and dependencies, (3) team structure and named leads, (4) pricing and payment schedule, (5) scope-change procedure, (6) IP and confidentiality terms (reference our standard MSA)."
Edit, route to your legal review, get the client signature.
After a project closes:
Say:
"Here are the notes from our [client] project retrospective. [Paste team notes.] Synthesize: (1) what worked, (2) what didn't, (3) what we'd do differently, (4) what's a one-off vs what's a pattern across recent projects. Flag anything that should change our standard process."
The pattern detection is what compounds — most agencies hold retros but never aggregate the patterns. Claude makes the aggregation feasible.
When you hire:
Say:
"We're onboarding [new hire role — junior strategist, designer, dev]. Their first 30 days should cover: (1) understanding our methodology, (2) reading the X most representative past projects, (3) shadowing on Y client meetings, (4) producing Z first deliverables under senior review. Draft a 30-day onboarding plan tailored to this role, with specific reading lists from our project archive."
You'll get a structured plan. Edit, hand it to your office manager or HR lead, and the new hire's first week stops being chaotic.
Use Pricing Optimizer for the structured pricing experiment workflow. For agency-specific pricing decisions:
Say:
"We're considering moving from project-based pricing to [retainer / value-based / outcome-based]. Our current average project is [$X] over [Y months]. Our typical client engagement length is [Z months]. Draft: (1) the case for and against the move, (2) the new pricing structure with rationale, (3) a 90-day transition plan including how to talk to existing clients."
You run a 9-person content marketing agency. You handle 12 active client engagements at any time, averaging $18K/month each — about $216K MRR. Your senior team (you plus 2 senior strategists) spends 4-6 hours on each new proposal.
Your win rate is 35% — solid but you're losing 65% of qualified deals. In post-mortems on lost deals, you keep hearing the same thing: "we went with [competitor] because they came back to us faster."
You set up the proposal workflow. Two weeks later, a discovery call with a Series B SaaS company concludes Wednesday at 4pm. Their VP of Marketing is doing other vendor calls Thursday and Friday and wants to decide by Tuesday.
By 5pm Wednesday, you have a draft proposal email and a 1-page scope from Claude. By 9am Thursday, your senior strategist has edited and you've reviewed. Proposal goes out Thursday at 10am — beating two of three competitors who haven't yet sent anything.
You win the deal. Annualized: $216K in engagement value, of which a meaningful portion is attributable to the speed differential.
Across the next 6 months, your win rate moves from 35% to 47%. You attribute roughly half of that lift to faster proposal turnaround. At your average deal size, that's $1.2-1.5M in incremental annualized revenue from one operational workflow change.
The agency-wide rollout is harder than the personal use — getting all your strategists to use the workflow consistently takes a quarter. But by month 9, every proposal goes out within 48 hours of the discovery call, every status email is structurally consistent, and the senior team is back to focusing on the strategy work that justifies their salaries.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub claudient/claudient --plugin claudient-small-business