Install
$ agentstack add skill-peterod99-consultant-skills-retainer-architecture ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Retainer Architecture
When to use
Your clients hire you for one-off projects (3–6 month engagements). You finish. They come back 6 months later with a new project. You want to turn this into recurring monthly revenue, so you're not starting from zero every 6 months. You need a framework for converting project-to-project chaos into stable, predictable income.
The framework
- Identify the recurring need: What problem does your client face every month that you solve every time they hire you? (e.g., sales funnel optimization, content calendar planning, team coaching). Not every project work converts; only work with a clear monthly heartbeat.
- Define retainer scope as ongoing access, not deliverables: A project gives 3 reports. A retainer gives 2–3 hours of your availability per month. Scope is "advising on sales strategy" not "deliver 2 emails + 1 audit." Availability beats deliverables.
- Price as 1.5–2x the equivalent project rate, monthly: A $10K project typically requires 4 months of your time at $2.5K/month. A retainer offering the same value costs $4K–5K/month because it's recurring, predictable, and requires lighter infrastructure. Never price retainer = project fee ÷ months. That's underselling.
- Anchor the retainer to an outcome, not a task list: "Grow your email list" or "Optimize your sales process" beats "Monthly strategy call + email feedback." Outcomes allow you to pivot tactics within the scope. Tasks lock you in.
- Lock in longer-term commitments: Retainers work at 3–12 months minimum, not month-to-month. Shorter terms destroy value: you spend Month 1 onboarding, Month 2–3 delivering, Month 4 they cancel. Require 6+ month minimums. This is non-negotiable for stability.
How to apply it
A fractional sales director works with 3-person SAAS startups. Each founder hires her for a 4-month "Sales Playbook" engagement: she audits pipeline, designs rep workflow, trains the team, hands off. The project is $8K. She finds that 60% rehire her 6 months later for "help us scale to 2 reps" or "our open rate dropped, audit our messaging." Patterns emerge.
She designs a retainer: "Ongoing Sales Leadership": 6 hours monthly access to design experiments, audit results, coach reps, plan hiring. She prices it at $4K/month (project equivalent = $8K ÷ 2 months × 1.5 margin multiplier) and locks in a 6-month minimum. No deliverables list. One rule: 48-hour response time on async questions. Everything else is flexible.
She markets it to her past 3 clients who hired her twice. 2 sign retainers, 1 doesn't. She now has $8K monthly recurring. The 4-month "new client ramp" is gone; she onboards a new retainer client every 6 weeks instead. Her monthly revenue moves from lumpy ($0–16K depending on projects) to stable ($8K–12K retainer + new projects). The retainer buyers become her warm network for referrals and case studies.
Common traps
- Treating retainer like a part-time job: You charge $3K/month for 10 hours (=$300/hr equivalent). That's a tier below your project rate, not above it. Retainers command premium pricing because they're stable and strategic, not because you're cheaper.
- "Month-to-month" retainers that flip every 90 days: You are not building stability; you're building anxiety. Require 6-month minimums. Clients want continuity; they'll accept it.
- Retainer scope creep: "6 hours monthly" with no definition becomes 15 hours within 2 months. Track hours. Set a clear process: email = logged, calls = logged, overflow = upsell. This is how you protect margin.
- Retainer without a clear outcome: If you can't articulate "we're solving X every month" the retainer devolves into "I'm available whenever." Define the outcome: pipeline growth, content velocity, team capability. That's what you're accountable for.
Source credits
- Alan Weiss (Value-Based Fees): Core framework of retainers as 1.5–2x equivalent project fee, monthly pricing for predictability, and tying scope to outcomes not deliverables.
- Alan Weiss (The Consulting Bible): Retainer strategy as leverage (stable revenue, deeper client relationships, monthly touchpoints that uncover upsell opportunities).
- Ken Yarmosh (Scalable Service Offers): Positioning retainers as a scalable offer that builds recurring revenue without time proportionality.
- Kathryn Porritt (100K Offer System): High-touch availability and commitment as defining elements of premium offers (retainers exemplify this).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: peterod99
- Source: peterod99/consultant-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.