LinkedIn Post — Hidden Revenue Scan
Skill: #2 of 5 — Hidden Revenue Scan
Type: Tool handraiser (comment REVENUE to receive)
Target post date: Mar 27, 2026
Hook strategy: Money hook — where practice owners look for revenue vs. where it actually lives
Word count: ~250 words (before signature)
V2 — QC APPLIED
Most practice owners look for new revenue in their pipeline.
The bigger number sits in clients they already serve — in the emails they read every day.
Nobody reads those emails with a revenue lens. They read for delivery. The money signals pass right through.
→ The client asking about your process, not just your output — upgrade signal
→ "Quick asks" that expanded into ongoing access — unbilled scope
→ Shorter emails where they used to write paragraphs — retention risk
→ "You should talk to my friend who..." — referral readiness
I built a Claude skill that catches them.
Paste 3-5 client emails. Get back every revenue signal, what each one means, and a ready-to-send email for each opportunity.
The signal from a specific email, the opportunity it points to, and the message to open the conversation — ready to send.
I tested it on one client. 4 emails. It found 12 signals across all 6 types — scope that had crept across 4 workstreams without a pricing conversation, invisible work I'd absorbed without billing, and a business event about to close that maps to 3 new system builds.
The upgrade script for the top opportunity took 30 seconds to send. The skill wrote the email from the signal.
The scan takes 2 minutes.
It's called the Hidden Revenue Scan. I'll send it to you for free.
1. Connect with me (so I can DM it)
2. Like this post (so other practice owners find it)
3. Comment REVENUE below
Kathryn Brown — Advisory OS
Claude skills for professional services practices.
One skill at a time. Deployed, not taught.
Hook Analysis
Strategy: Money hook. Where do you look for revenue? Most practice owners say "pipeline." The bigger number is in existing clients. This reframes before the skill reveal.
Signal breakdown: Four concrete examples (→ arrows) mirror Skill #1's time breakdown format. Each names a real email pattern and labels the signal type. Reader recognizes their own inbox by line 3.
Proof element: "Every advisory engagement I run starts with reading client correspondence for revenue signals." This is Kathryn's actual process — not a fabricated test story. Positions the skill as an automation of what she does for clients.
Key difference from Skill #1: Skill #1 sold time (15 min → 2 min). Skill #2 sells money (revenue you're not seeing). Money is a stronger hook. The post leans into it.
Image — Handraiser Visual
Same visual system as Skill #1. Screenshot this mockup for LinkedIn — content flows naturally to 4:5 portrait ratio.
Free Claude Skill
Hidden Revenue Scan
Paste client emails. See every signal.
Paste 3-5 client emails
▼
1
Work You're Not Billing
Scope that crept without a pricing conversation
2
Problems You Already Solve
Needs they mentioned that map to your services
3
Clients Ready for More
Language that means "I want to go deeper"
4
Pricing That Hasn't Kept Up
Engagement grew, the fee didn't
5
Revenue About to Leave
Disengagement patterns before they say it
6
Referrals Waiting to Happen
Clients ready to send you business
+ Upgrade Scripts — ready to send
2 minutes
Comment below to get it free
REVENUE
Advisory OS
Production note: Screenshot this HTML mockup at 1080×1350 (4:5 portrait — LinkedIn max vertical ratio) for the LinkedIn post image. Taller = more feed real estate. Same visual system as Skill #1 — dark background (#0a0a0a), gold left borders (#b79d64), numbered rows.
Copy QC — V2 Changes
- P4 killed: "Not because they're bad at pricing. Because nobody reads..." → Direct statement: "Nobody reads those emails with a revenue lens." Eliminates Not-Because-X construction.
- P1 compound fixed: V1 had P4 + P7 (two correction-revelation patterns). V2 has one P7 instance ("Most practice owners...") with evidence exception. Within limit.
- Three-beat "specific" fixed: "The specific signal from a specific email, the specific opportunity" (3× specific) → "The signal from a specific email, the opportunity it points to, and the message" — varied structure, 1× specific.
- R8 adverbs killed: "quietly expanded" → "expanded." "had already written it" → "wrote the email from the signal."
- R1 weak endings fixed: "they already have" → "they already serve." "reads for them" → "catches them." "had already written it" → "wrote the email from the signal."
- Economy: "one of my own clients" → "one client." Cut redundant bridge paragraph ("These signals show up..."). Post tighter by ~30 words.
- Justified repeats: "signal" ×3 (technical term), "revenue" ×3 (topic word), "client" ×3 (audience word), "email" ×4 (the input medium — unavoidable). All within tolerance.
- CTA format matches Skill #1: Same 3-step structure. Unique keyword per skill — REVENUE (Skill #1 used PRACTICE). Enables tracking which post drove engagement and gives returning commenters a fresh action.
Teaching Story
Source: Jenn/TRG revenue scan (2026-03-26). Anonymized in post.
Real numbers: 12 signals across all 6 types. 4 emails. Scope creep across 4 workstreams. PE acquisition = top revenue signal mapping to 3 system builds. 6 invisible work items across 6 of 7 value areas. Project management absorbed without billing.
What's in the post: "12 signals across all 6 types" + "scope that had crept across 4 workstreams" + "a business event about to close that maps to 3 new system builds." Specific enough to be credible, anonymized enough to be ethical.
Open question: Did Kathryn send the PE acquisition upgrade script? If yes and there's an outcome, that's the v2 proof line.