Who Posted is
Posted is a creator marketing platform, a two-sided marketplace where brands run campaigns and creators get paid to post. Roughly 1,500 brands enter the funnel every month.
One thing is different about this page: we run revenue at Posted ourselves. Every system below was built by us and is operated by us, day in, day out. It’s our living lab, everything we install for clients runs here first, on real pipeline, with our own targets on the line.
“The team at Krassowski & Co added over $2,000,000 in revenue in the last 18 months. We had a good product and traffic, but zero systems in place when they started. They deployed, scaled, and now maintain all of our client acquisition infrastructure.”
— Steven Cravotta, Founder, Posted
Before
Good product, real traffic, zero systems
Posted had the hard part figured out: a product people wanted and traffic arriving every day. Underneath it, nothing was systematic, and every month of growth made the manual version more expensive.
Sounds familiar? Map my current funnel →Step 1 · Map
What we mapped
Before building anything, we laid out the whole funnel end to end, from first visit to paying brand. What we found:
- No pipeline infrastructure, deals living in inboxes and memory
- Leads arriving faster than anyone could triage them, with no scoring to say who mattered
- No connection between the product backend, payments, support, and the CRM
- Support tickets stacking with no system behind them
- No reliable numbers to steer by
One economic fact shaped the whole design: a small share of brands drive the large majority of revenue, and the data says exactly which ones. So the engine's job is to find those brands fast and let none of them slip through untouched.
How the Map works as a service →Step 2 · Groundwork
The clean foundation
- One event layer. The backend (Firebase), Stripe, Intercom, and the CRM wired together. Signups, payments, product usage, and support activity land on the customer record automatically.
- Data that can't drift. Real-time webhooks carry events as they happen, and a full reconciliation sync runs every 24 hours on top, so the CRM never quietly falls out of sync with the backend.
- Clean inputs. Phone numbers validated before a lead reaches a call list, local-time calling windows, and UTM tracking on every booking link so every demo has a source.
Step 3 · Installs
The build sprints
On the clean foundation, we installed the systems one sprint at a time:
- Brand scoring and the buy-or-die list. Every brand gets scored against the ICP on arrival. Seven out of ten or higher lands on a dedicated list that gets worked until the brand starts or says stop. Low scorers route to self-serve.
- Campaign Engine. Campaigns run from CRM data, ordered by score. The flagship play: February 2026 was set up to be a slow month, so we re-mined the existing CRM and ran targeted outreach at the best past leads. Result: 426 demo calls booked in one month, 234 of them from leads the CRM already contained.
- Signal Engine. No paid-for lead dies quietly. Signups that bounce before the trial get dialed and re-booked, started trials trigger their nurture, and stalled, paused, or never-launched campaigns each fire their own follow-up. Cancellations get caught in the save window: win-back starts while paid time still remains, and every save is tracked.
- Call Intelligence. Every demo call is recorded, summarized by AI, and written to the CRM, with a post-call summary in Slack and the full call linked on the record.
- Support AI, twice. One Intercom workspace per side of the marketplace, each with its own help center and AI agent. Creator side: 11,166 tickets at a 79.1% AI resolution rate. Brand side: 5,593 tickets at 68.3%.
- A CRM cut along the team. Setters get the dial list, fed by the Signal Engine and ordered by score. Closers get the call pipeline and big-brand views. Support runs Intercom and Slack.
Step 4 · Growth
What we do to scale it
The engine isn't a handover, we run it. New builds land here first, existing ones get tuned against real numbers, and the system grows as the team and the product grow. Outreach runs across iMessage, SMS, calls, and email from one place, and the whole thing is maintained week over week.
How Growth works as a service →After · The outcome
$2,000,000 in 18 months
Added between January 2025 and July 2026, on infrastructure that didn't exist when we started. The engine caught the traffic that was already arriving, converted the leads that were already paid for, and turned support from a queue into a system.
That's the point of this page: when we install one of these systems for you, it's not a design we think will work. It's a copy of something already running here.