Case Study · Origin Story
Last updated: Feb 2026

"Revenue Party engineered a completely
new reality for us."

How Revenue Party built Poplin's outbound revenue system — The Poplin Protocol.

"They took a manual, founder-led grind and turned it into a predictable, high-velocity cold outbound machine. I've never seen someone combine that level of operational rigor with the psychology of closing. If you are looking for a group that can build the revenue infrastructure you wish you had yesterday, this is the team."

Poplin

Moshe Fertel

COO & Co-Founder, Poplin

B2B Division — professional sports, government, hospitality*

Monthly Revenue

$20KMillions
Monthly contracted revenue = booked revenue from B2B division contracts (professional sports, government, hospitality). Baseline: ~$20K/mo at engagement start. Scope: Poplin commercial B2B division. Source: Internal reporting.

Sales Team

00+
Sales team = outbound reps (SDRs/BDRs) + managers supporting B2B motion; excludes contractor marketplace workforce. Scaled from Founder+1 to 50+ across the engagement. Source: Internal reporting.

US Cities

0+City coverage = active Poplin service areas as listed on poplin.co/service-areas. Source: Poplin Service Areas page.

Problem

Founder-led sales bottleneck; unscalable manual acquisition.

Internal baseline

Build

The Poplin Protocol (Prototype).

Prototype of the Revenue Party Engine

Result

Scaled sales team from 0 to 50+ reps; drove millions in contracted revenue; Poplin now operates in 500+ US cities.

Per poplin.co

Below is the build sheet: what we changed, what we built, and how it scaled.

Revenue Party productizes the outbound revenue system first built at Poplin as the Poplin Protocol.

The System built at Poplin (Prototype) = The System sold by Revenue Party (Production)

The revenue architecture described in this document serves as the Prototype for the commercial methodology now productized by Revenue Party. This document establishes the direct lineage between the operational systems built at Poplin and the Revenue Party Engine.

Poplin Protocol (Prototype)

  • Architects: Muneeb Ahmed (COO) & Caleb Estes (CEO)
  • Environment: Poplin (Commercial B2B Division — professional sports, government, hospitality)*
  • ICP definition & targeting
  • Automated sequencing
  • Daily call QA
  • Performance dashboard
  • Feedback flywheel

Revenue Party Engine (Production)

  • Founders: Muneeb Ahmed, Caleb Estes, Mariya Tamkeen
  • Launched: December 2025
  • ICP & channel fit audit
  • AI-enabled signal factory
  • Impact OS with live QA
  • Transparent client dashboard
  • Brand trust infrastructure

Revenue Party is a GTM architecture firm co-founded by Muneeb Ahmed, Caleb Estes, and Mariya Tamkeen in December 2025. Prior to founding Revenue Party, Ahmed served as the inaugural sales architect at Poplin (formerly SudShare), where he built the outbound revenue system credited with the company's growth from early-stage revenue to operations across 500+ US cities.

*Vertical examples from Poplin B2B division; details available upon request.

...
This is not a story about laundry.
01
The Crucible

Poplin's "Zero to One"

This is a story about the physics of growth. It is the story of how a revolutionary marketplace — Poplin, the "Uber for Laundry" — faced the same existential bottleneck that kills thousands of B2B startups, and how we engineered the system that broke through it.

Translation: we turned founder-led acquisition into a documented outbound operating system.

Before Revenue Party existed as a firm, our methodology was already proving itself in the wild. Our COO, Muneeb Ahmed, served as the inaugural sales architect for Poplin, taking them from a high-touch, door-knocking operation to a dominant market leader.

We didn't just get lucky. We didn't just "hire a good rep." We deployed a specific, replicable protocol that turned the chaotic gamble of early-stage sales into a repeatable, engineered system.

This document is not just a case study. It is the blueprint of our origin. It explains why we exist, how we view the asset class of Venture Capital, and why we believe the "Lone Wolf" sales hire is a relic of the past.

Poplin was the Prototype. Revenue Party is the production model.

Muneeb Ahmed joined Poplin at a critical juncture. The company was sitting on an inflection point. The concept was undeniable: a peer-to-peer marketplace for laundry. It was "Uber for Laundry" in the truest sense — a service that liberated customers from a chore and provided gig workers with a livelihood. The Product-Market Fit was visceral.

But the Go-to-Market Fit was broken.

At the time, Poplin's acquisition strategy was a grind. The founders — including Moshe Fertel, who was deeply involved in scaling his family's business — were physically driving to small businesses. They were walking into laundromats and dry cleaners, shaking hands, and knocking on doors. It was the classic "Founder Grind." It was heroic, high-effort, and completely unscalable.

They were sitting on roughly ~$20,000 in monthly sales at the time Muneeb joined (internal baseline), driven almost entirely by this manual effort.

Poplin
You cannot scale a marketplace on gas receipts. You cannot reach IPO velocity by knocking on one door at a time.

Muneeb's mandate was ambitious in its scope: Take this high-touch, face-to-face, founder-led magic and turn it into a cold, digital, scalable machine.

And this wasn't just about consumer apps. Muneeb was hunting whales. He was tasked with penetrating deep B2B sectors with complex laundry needs. He was selling to the NFL, the US Military, luxury hotels, and high-throughput multi-location service operators. [Internal]

This is the "Zero to One" problem that kills most B2B startups. It is easy to sell when the founder is in the room. The founder has the passion, the authority, and the reality distortion field. But you cannot clone the founder.

Muneeb had to build a system that could sell to an NFL equipment manager or a military logistics officer without the founder present. He had to build an engine that could articulate a complex value proposition and convert them into partners — all without ever shaking a hand.

If he failed, Poplin would remain a brilliant small business. If he succeeded, it would become a category-defining giant.

...
02
The Methodology

Deconstructing "Impact Selling"

Muneeb didn't just start dialing. He partnered with Caleb Estes (Revenue Party CEO), a strategist obsessed with the architecture of influence.

For months, they retreated to the laboratory, meeting for 10 to 15 hours a week to strip down standard sales methodologies and rebuild them from the ground up. They realized that most sales training is garbage because it focuses on rhetoric — what words to say to handle an objection.

They built a new protocol called Impact Selling.

The core thesis of Impact Selling is that sales is not about "persuasion"; it is about Action. Drawing from the roots of acting theory — specifically the action-based frameworks of Stanislavski and Uta Hagen — operationalized in resources like The Actor's Thesaurus — they realized that human interaction follows the laws of physics.

Action causes Reaction. Reaction creates Impact. Impact moves people and creates Change.

Sales is simply the engineering of change.

To operationalize this, they stacked three distinct "System Components" into the Poplin playbook. These are not tips; they are the architectural pillars of the Revenue Party Engine:

Component 1: Relationship Sales (The Connection)

  • The Source: Dale Carnegie.
  • The Problem: In a digital world, the human element is the scarcest resource. Bots don't build trust.
  • The Tactic: "The sweetest sound in any language is a person's name." Muneeb engineered the outreach to be radically personal. We didn't use templates that sounded like bots. We used language that signaled, "I know who you are, and I am speaking only to you."

Component 2: Consultative Sales (The Value)

  • The Source: Diagnostic Medicine.
  • The Problem: Most SDRs "pitch" solutions to people who don't know they have a problem.
  • The Shift: Stop selling the solution; start selling the problem. Instead of saying, "Poplin is a great laundry service," the engine asked, "How much revenue are you losing because you can't offer delivery?" We shifted the dynamic from "Vendor begging for money" to "Doctor offering a cure." We showed value immediately, often before the prospect even agreed to a meeting.

Component 3: Challenger Sales (The Control)

  • The Source: The Challenger Sale.
  • The Problem: Complacency. Most prospects will do nothing even if they are bleeding money.
  • The Action: If a prospect was complacent, we didn't "handle the objection" with a polite rebuttal. We reframed their reality. We forced them to recognize the unmitigated risk of doing nothing.
  • The Objective: We didn't aim to be "liked." We aimed to be "respected." If a prospect wasn't listening, Muneeb didn't tell a joke to be funny; he took an action to unsettle or to arrest their attention. The objective was to break their pattern and force them to see the opportunity.

These three components form the architectural pillars of the Revenue Party Engine deployed today.

See how the GTM Engine architecture works
...
03
The Execution

Unlocking Scale

Theory is useless without execution. Muneeb took this high-concept methodology and hard-coded it into Poplin's daily operations.

He built a cold outbound architecture that was surgically precise, integrating rigorous ICP Definition, automated Sequencing, and daily Call QA to ensure consistency. He moved the founders off the street and put them in front of a dashboard. While managing a junior team focused on the B2C flywheel, Muneeb personally architected the high-stakes B2B motion that landed institutional giants.

The Prototype Engine wasn't just about output; it was about Input. Muneeb treated every "No" as data. He built a "Feedback Flywheel" where the objections from the sales floor were instantly relayed to the Product and Engineering teams.

Operating Cadence

DailyCall blocks + QA scoring (live rubric)
WeeklyObjection library update + script diffs
MonthlyPlaybook release notes + product feedback memo

The Feedback Flywheel

Prospect says: "I need X feature."

Engine says: "Log it. Quantify it. Build it."

Iteration Loop

"No"DataProductClose

Hover each node to see real Poplin examples. Every “No” became data that fed back into the product.

The Scaling Arc

Month 1Foundation

ICP definition, sequencing infrastructure, first cold outbound campaigns live

Month 3First Traction

10 reps onboarded and ramped, B2B verticals (professional sports, government, hospitality) live

Month 6Institutional Deals

30+ reps active, institutional accounts onboarded, feedback flywheel operational

Month 12National Scale

50+ reps, millions in contracted revenue, 400+ US cities covered

The Result: From Bottleneck to Hypergrowth

It is important to be clear: We did not invent the demand for Poplin. The demand for an "Uber for Laundry" was massive. Poplin had visceral Product-Market Fit.

What we did was build the infrastructure required to capture that demand.

Before the engine, Poplin was throttled by the limits of manual, founder-led sales. After the engine, the bottleneck was removed. The scale was unlocked.

  • Team Growth: Muneeb scaled the sales organization from a "Founder + 1" setup to a force of 50+ sales representatives, supporting expansion across 400+ US cities.
  • Revenue Impact: The company grew from ~$20,000 in monthly sales to millions in contracted revenue.

The "Founder Grind" was officially retired. Moshe and his family no longer had to drive to laundry shops; they were now presiding over a self-driving revenue machine. Poplin had successfully crossed the chasm from "Promising Idea" to "Market Leader."

Rep Ramp Time

2 Weeks

New rep productive via Impact OS

Feedback Loop

< 24h

Objection-to-product relay cycle

Peak Velocity

40+ Cities/mo

New markets per month at peak

FoundationMonth 1First TractionMonth 3Institutional DealsMonth 6National ScaleMonth 12Revenue →
~$20K/moMillions

Poplin Today

We proved that when you combine Market Demand with Engineered Sales Infrastructure, you don't just get growth. You get dominance. Poplin now operates in 500+ US cities. Third-party press documented a 10x revenue jump in 2021 — the exact year Muneeb built the engine. That external corroboration distinguishes this story from a simple claim; the system built during Muneeb's engagement became the infrastructure that national scale ran on.

Proof Citations

  • 10x revenue jump in 2021 — corroborated by third-party reporting during the year Muneeb built the engine (source available upon request)
  • Poplin now operates in 500+ US cities — PublicPoplin Service Areas
  • Team scaled from Founder+1 to 50+ outbound reps — Internal
...
04
The Gap

The "Silent" Liability

We should have declared victory. But as we took this methodology — now evolving into the Revenue Party Engine — to other companies, specifically Managed Service Providers (MSPs) and Staffing Agencies, we hit a new, invisible wall.

The engine was perfect. The sales calls were elite. But deals were dying.

The heartbreak came with a massive staffing agency deal. This was a contract involving over 800 recruiters — a company-making deal. Muneeb and Caleb had navigated the grueling 2-month sales cycle perfectly. They had won over the stakeholders. The logic was sound. The ROI was proven. The deal was essentially done.

Then, the owner got involved.

He didn't talk to Muneeb. He didn't ask about the Impact Selling methodology. He simply opened a browser tab and looked at the client's website.

The site wasn't "bad" in a technical sense. It functioned. But the positioning was weak. The design language whispered "small business." It signaled "risk."

To an enterprise buyer, a weak brand isn't just an aesthetic annoyance; it is a liability. The owner looked at the site and decided that a company with that web presence was too small to safely do business with. He killed the deal.

Caleb and Muneeb realized they were powerless. Think of it as an electrical circuit. They were winning the argument on the phone (The Plug), but losing it on the web (The Outlet).

The Plug

Phone (Winning)

The Outlet

Website (Losing)

Deals lost to brand risk: 1 · Potential contract value: $800K+

The 800-recruiter staffing agency deal — killed by a single browser tab.

What enterprise buyers see when you aren’t in the room

What the buyer sees

Outdated Design
No Social Proof
Weak Positioning

After Revenue Party

CTA
Trust Signals
Social Proof
Enterprise Polish

Circuit repaired — the “Silent Salesperson” now works for you, not against you.

You can build the greatest engine in the world, but if the chassis looks like it's falling apart, no one will get in the car.

What enterprise buyers check (when you aren't in the room)

Website quality & speed
Visual credibility & polish
Team page & leadership
Case studies & proof
Trust signals (logos, testimonials)

This checklist is exactly what we audit in the Trust & Brand Risk Assessment.

...
05
The Completion

The Architect & The Party

The Diagnosis

We found ourselves here because of a philosophy built in 2020. Caleb Estes had long been obsessed with the "Venture Capital Paradox" — the reality that VCs price risk into their terms because early-stage sales is usually a gamble. He knew that to derisk the asset class, we had to replace personality with engineering. That philosophy built the Poplin Engine, but as we looked at the broken brands of our new clients, we realized the architecture was incomplete.

That philosophy needed a third architect.

We went looking for someone who understood that design is a commercial function, not a decorative one.

We found Mariya Tamkeen.

Mariya came from the world of the Fortune 100. She had architected visual narratives for PepsiCo, Beiersdorf, and Kia Motors. She didn't look at startups like a founder; she looked at them like an enterprise executive.

Her diagnosis of our problem was brutal and accurate. "You are obsessing over the 30 minutes you spend on the phone with the prospect," she told us. "But you are ignoring the three weeks they spend interacting with your brand when you aren't there."

She called this the "Silent Salesperson."

The Mandate

Mariya joined the team with a single, uncompromising mandate: A startup must look enterprise-ready from Day One.

She didn't just fix logos. She built Trust Infrastructure. She aligned the visual language of our clients with the psychological impact of our sales scripts. She ensured that when Muneeb arrested the prospect's attention, the brand was there to hold it.

The Result

On December 1, 2025, the three of us formally united as Revenue Party.

We realized that the "Lone Wolf" sales hire — the person most founders try to hire to solve their revenue problem — is a myth. No single human being can be:

StrategistCalebOperatorMuneebArchitectMariya

The Strategist

Caleb Estes (CEO)

Derisks the asset.

Primary deliverable: ICP & offer architecture

The Operator

Muneeb Ahmed (COO)

Engineers the engine.

Primary deliverable: Playbook + daily QA system

The Architect

Mariya Tamkeen (Chief Design Officer)

Builds the trust.

Primary deliverable: Trust assets & brand infrastructure

To solve the problem of growth, you don't need a person. You need a Party.

What changes when the architecture is complete

  • Close rate stability — deals survive stakeholder review
  • Cycle time reduction — brand trust shortens diligence phases
  • Reduced deal death — the "silent salesperson" holds attention when you leave the room
...
05b
The Comparison

Lone Wolf vs. The Engine

The traditional playbook says: hire a sales rep and hope for the best. The data says something different. Here is what the two paths actually look like side by side.

036912

Months

The “Lone Wolf” Hire

Recruit
Recruiting: Job post, interviews, negotiation — minimum 6-8 weeks
OB
Onboarding: CRM setup, product training, shadow calls
Ramp
Ramp (hope): 3 months of sub-par productivity while "learning the market"
Under...
Underperform: Missed quotas, pipeline stalls, excuses mount
End
Terminate: PIP → separation → restart the cycle from zero

↩ Cycle restarts from zero after termination

Revenue Party Engine

Deploy: ICP definition, sequencing infrastructure, tech stack integration
Outbound Live: First campaigns launched, daily call blocks begin
Mtgs
Meetings: Qualified appointments start flowing
Scale
Scaling: Playbook iteration, team expansion, vertical penetration
Steady
Steady State: Predictable pipeline, continuous optimization

✓ Steady-state pipeline by month 3 — timeline varies by ACV & ICP complexity

Time to first revenue

First revenue = first closed-won deal influenced by outbound motion (booked ARR or contract value).
6–9 mo

Lone Wolf

vs.
~4 wks

Revenue Party

...
06
The Invitation

Welcome to the Party

We formed Revenue Party to productize the exact system that built Poplin and fixed the "Branding Gap."

Every engagement ships three things: ICP & channel architecture, a custom outbound playbook with daily QA, and brand trust infrastructure that holds attention when you leave the room.

We don't just ask for your business; we engineer the certainty of it.

Stop hiring people. Stop gambling on headcount. Start hiring systems.

Welcome to the Party.

Poplin

"If you are looking for a group that can build the revenue infrastructure you wish you had yesterday, this is the team."

Moshe Fertel

COO & Co-Founder, Poplin

ICP & Channel Fit Audit

Outbound System Gap Analysis

Trust & Brand Risk Assessment

What happens after you book

130-minute diagnostic call — we map your current GTM architecture
248-hour Architecture Brief delivered (PDF + Loom walkthrough) — includes ICP snapshot, offer diagnosis, channel plan, and next-steps recommendation
3Go / no-go decision — zero pressure, full transparency