LinkedIn · X.com · and more — calibrated voice · approval gate
Amplify collects signals from LinkedIn, X.com, GitHub, and more — scores intent, and drafts a reply in your calibrated voice. Then it waits — in Slack, as a button — until you approve. Every action lands on an HMAC-chained audit ledger. Signals in. Voice out. Approval in between.
Most operators stitch five tools together to run social outbound and quietly pretend that's a workflow. Amplify is one workflow. Signals from LinkedIn, X.com, GitHub, and more surface high-intent prospects every day — collected via enterprise residential IP infrastructure (Bright Data), not datacenter scraping. Every signal writes to signed, timestamped storage before anything else touches it.
Post-commenter and liker enrichment runs next, and every enriched record is HMAC-signed as it lands. Then Claude scores ICP fit, drafts a reply in your calibrated voice, and posts the draft to Slack with Approve, Edit, or Skip buttons.
Nothing publishes without your thumbs-up. Approved actions fire through the platform API as your authenticated identity — no scraped session, no stolen cookie, no headless browser logged in as you. Every event, at every stage, writes to the audit ledger.
The loudest buyer anxiety we hear is, "this bot is going to sound wrong under my name." It's the right thing to worry about. Here's what a generic LLM drafts from a real signal, next to what Amplify drafts after a week of voice calibration, next to the brand-voice exemplar that steered it. All signals blinded. Operators are labeled; real names never leave the engine.
Drafts come to you. Approvals go out. Nothing in between.
The Amplify contract
The approval loop and the audit ledger are in every tier. That's the product, not a premium feature. Bring your own HubSpot is the default. If you don't have one, we'll set up Managed HubSpot Starter on the same invoice for $250 a month.
One operator, one to three brands. Your own LinkedIn, your own voice, your own Slack channel. The full loop and the full ledger from day one.
For the operator running a small portfolio of brands or an in-house comms team covering several executives. Priority approval-gate SLA. Longer retention. Same loop, same ledger.
Run Amplify on behalf of your clients. Unlimited brands under one unified ledger search. Priority plus a written SLO. Minimum term is a year because we staff onboarding around it.
Add-on: Managed HubSpot Starter, $250/mo. Flat tier pricing — no per-seat, no per-post, no overage charge on any plan.
Amplify has two distinct layers, and it matters that you understand both. Signal collection reads public content — posts, engagement, profiles already visible to any logged-in user — using enterprise residential IP infrastructure (Bright Data). Not datacenter IPs. Not a session logged in as you. Public content, read the way a person would read it.
Signal publishing is a different path entirely. Approved actions fire through the platform's official API — LinkedIn's Content API, the X.com developer API — as your authenticated identity. No scraped session, no stolen cookie, no headless browser logged in as you at 3am. The things platforms actually penalize aren't in the architecture. You approve a draft. It publishes through the same path official partners use.
Sees: public signals from LinkedIn, X.com, GitHub, and other platforms — posts, engagement, and profiles already visible to any logged-in user. Drafts you generate inside the Slack app. CRM metadata you've explicitly connected.
Does not see: your DMs. Your saved items. Your connections' private profiles. Any email account you haven't explicitly linked. The rest of your HubSpot portal outside the objects you've scoped. Your personal calendar. Anything private that the platform, HubSpot, or your email client doesn't expose via a public API key that you control.
Amplify is in production at Studio B's own five-brand portfolio, at a specialized agency running a cohort of fund principals, at a holdco-comms team running portfolio-company CEOs, and at a vertical comms shop running executives under its brand. Every outbound post in 2026 from those teams has published through the approval loop.
Every action — signal scored, draft generated, approval granted, post published — writes to an HMAC-chained ledger. Below is the last ten events, live. Operators, brands, and post IDs are blinded on the engine before the feed reaches this page; the chain head at the bottom lets a technical buyer verify the architecture.
| Timestamp (UTC) | Signal | Event | Operator | Brand | Score | Action | Hash |
|---|
For agencies running brands on behalf of clients, and for operators running their own LinkedIn under their own name. We reply within 48 hours. Your first approval request arrives in Slack in about two weeks.