AMPLIFY · For accredited 506(c) fund principals · 506(b) funds referred out at intake · Personal brand, not fund marketing · As of 2026-04-17
Amplify · LinkedIn Platform for 506(c) GPs

Your compliance officer hates Taplio.
She'll approve this.

Dripify, Sprinklr, and Taplio were built for SaaS marketers. You are a 506(c) fund manager — every public post is a regulatory surface. Amplify is the first LinkedIn growth platform with an approval gate your CCO can sign off on. Claude drafts in your voice. You approve in Slack. Every draft, every edit, every click lands in an audit ledger. Fund marketing is out of scope by design1 — personal brand is in.

Studio B runs Amplify on five brands today, including Wasala, a private credit fund managed by the same person who founded Studio B. Dogfood isn't a feature list — it's the moat.

Exhibit A · The problem

506(c) fund marketing is illegal.
Your personal brand isn't.

Until 2013, private funds couldn't advertise at all — period. JOBS Act Rule 506(c)2 opened general solicitation for funds that verify accredited-investor status. The rule does not create a safe harbor for every post. Every LinkedIn comment, every boosted article, every "check out our Q4 letter" becomes a regulatory surface your compliance officer has to defend.

Personal brand is different. A GP talking about markets, operators, deals she's seen — that isn't fund marketing. But she still can't use Dripify, Taplio, or Sprinklr: those tools auto-engage, auto-DM, and leave no audit trail her CCO can hand to an examiner. The SEC examiner doesn't care how elegant the automation is. She cares about the paper trail.

Amplify draws the line explicitly. Every draft labeled. Every approval logged. Every outbound action traceable to a named human. Dripify sends the post; we send the post and the log.

  1. Fund marketing under Advisers Act Rule 206(4)-1 (the "Marketing Rule") and FINRA communications rules is explicitly out of scope. Amplify rejects content classifiers for fund performance claims, return projections, investor solicitation language, or capital-raise calls-to-action.
  2. SEC Rule 506(c) of Regulation D permits general solicitation for private placements only where all purchasers are verified accredited investors and issuer takes reasonable steps to confirm status. Amplify does not perform investor verification.
Exhibit B · Architecture
Four layers. Every layer logged.

Amplify is a pipeline, not a point tool. Each layer has a purpose, a status, and a paper trail. Layers 1–3 run live today across five brands; Layer 4 is gated on LinkedIn Community Management API approval (application submitted 2026-04-16).

L1
Discover
Six LinkedIn Search phantoms surface high-intent prospects against a keyword + geography + role graph. Results land in a public S3 CSV with SHA-256 manifest.
● Live
L2
Extract
Six Post-Commenter and Liker phantoms resolve engagement signals to named individuals and post them back to webhook-router via signed webhook.
● Live
L3
Score & Route
Claude scores each prospect against the GP's stated ICP, drafts an opening message in the GP's calibrated voice, and posts to Slack #clients with Accept / Edit / Reject buttons. Every approval is upserted to HubSpot with the full decision trail.
● Live
L4
Execute
Approved actions fire through the LinkedIn Community Management API as the GP's authenticated identity. Every send stamped, every click logged, every error surfaces back to Slack for CCO review.
◇ Pending LI approval
Exhibit C · The audit trail
What your CCO sees.

Every approval writes an entry like this to the Amplify ledger. Exportable as CSV or SIEM-friendly JSON. The examiner gets the paper trail; the GP keeps the voice.

AMPLIFY LEDGER · ENTRY sha256 9c4f7b…a201
entry_id
ampl-2026-04-17-00421
tenant
[gp-partner-redacted]
operator
kevin@b.studio · authenticated 2026-04-17 09:22 CDT
action
comment · LinkedIn post urn:li:activity:[redacted]
draft
"Worth flagging — the sector rotation you mentioned is exactly what we saw in the 2018 trade-finance cycle. Different catalyst, same liquidity dynamics."
classifier
personal brand · no fund references · no return claims · no capital-raise CTAs
approval
✓ approved · kevin@b.studio · Slack #clients · 2026-04-17 09:23 CDT · response time 72s
execution
posted · 2026-04-17 09:23:44 CDT · LinkedIn comment_id 7289445612 · HTTP 201
retention
7 years · SOC 2 Type I in progress
Exhibit D · Pricing
Three seats at the table.

Pricing reflects the work and the regulatory surface. We don't have a $49 tier because a $49 tier doesn't buy a CCO-reviewable audit trail. It buys exposure.

Tier 01
GP Personal
$1,200 / seat / mo
Single GP. Voice calibration + Slack approval loop. Everything in the ledger.
  • One calibrated voice profile · updated weekly
  • Layer 1–3 pipeline dedicated
  • Slack approval channel (yours or shared)
  • HubSpot CRM upsert + amplify_score
  • Full audit ledger, CSV + JSON export
  • CCO review packet on request
Annual billed; 30-day pause allowed.
Tier 02 · Most common
Fund
$3,000 / fund / mo
Up to 5 principals under one fund entity. Shared ICP, shared compliance config.
  • Up to 5 calibrated voice profiles
  • Per-principal Slack routing
  • Fund-level ICP config (one ruleset)
  • Shared compliance classifier
  • Per-principal ledger + fund roll-up
  • Quarterly CCO briefing (30 min)
Most 506(c) shops land here.
Tier 03
Enterprise Fund
$6,000 + / mo
6+ principals, multi-fund family, or white-label. Bring your own CRM.
  • Unlimited calibrated voices
  • Multi-fund tenancy · per-fund config
  • White-label option (your brand)
  • SOC 2 Type I pack + custom DPA
  • Direct API (Affinity, DealCloud, HubSpot)
  • Dedicated voice calibrator
Custom. Start with a conversation.
Exhibit E · A note from the founder
Founder's note

"I built Amplify because I am a 506(c) GP. My compliance officer wouldn't approve Taplio either."

Studio B runs five LinkedIn brands today on Amplify — Studio B, Wasala (a private credit fund I'm GP on), Ästhetik, Weathervane Hill, and my personal account. 35 of 50 PhantomBuster slots running continuously. Claude drafts, we approve in Slack, every action writes to the ledger I'll hand to our auditor next quarter. The system hasn't been a thought experiment for six months; it's been the thing.

Amplify goes GA when the LinkedIn Community Management API approval lands (submitted 2026-04-16, 10–14 business days to decision). Until then the waitlist below gets you the onboarding sequence, the CCO review packet, and a 30-minute conversation about whether your fund structure is a fit. If it isn't — if you're a 506(b), or if your target post is really about your fund rather than you — I'll tell you directly. We don't need the revenue more than we need the audit surface.

Kevin Bibelhausen Founder, Studio B · GP, Wasala Fund I
Exhibit F · Questions asked by our general counsel
Direct answers.
Is this fund marketing?
No. Fund marketing — performance claims, return projections, capital-raise CTAs, anything that promotes the fund itself — is out of scope by design. Amplify's classifier rejects it before it reaches the Slack queue. We're a personal-brand platform for GPs, not a growth tool for funds.
We're a 506(b) fund. Can we use this?
No. 506(b) prohibits general solicitation; a LinkedIn automation platform creates exactly the kind of surface that puts 506(b) offerings at risk. We'll refer you to compliance counsel — or, if you're in the middle of a 506(b) → 506(c) conversion, we'll wait for you.
What exactly does the audit ledger contain?
For every executed action: entry_id, tenant, operator (authenticated), action type, full draft, classifier output, approval decision + approver + timestamp + Slack channel, execution timestamp + LinkedIn IDs, and 7-year retention. Exportable as CSV or SIEM-friendly JSON. Sample shown in Exhibit C.
Who owns the voice model?
You do. Amplify calibrates against your public writing and your approved drafts; the resulting voice profile is your tenant's data. Export on request. Delete on offboarding. We never train a cross-tenant model — your voice doesn't improve someone else's drafts.
Why Slack for approvals?
Because 506(c) GPs already work in Slack and because the Slack message IS the regulatory artifact. An approval in a web dashboard is a database write; an approval in Slack is a timestamped message in a channel with a retention policy. Your CCO can audit Slack exports. She can't audit a SaaS dashboard.
Can we run this without the LinkedIn API?
For Layers 1–3, yes — that's what we run today. Discovery, extraction, scoring, and draft generation all work; execution happens manually from the Slack approval message. Layer 4 lights up when LinkedIn approves the app (10–14 business days from 2026-04-16). You'll get the first 90 days on us when it ships.
Request access
Join the waitlist.

Private beta, 506(c) GPs only. Tell us about your fund and we'll schedule a 30-minute conversation to confirm fit. If you're not a fit, we'll say so — and refer you to the right place.