Events & Community • Published 30 June 2026 at 10:00 am • 1 min read

How a First-Time Marathon Got 189 Paid Signups With No Team or CRM

Before Engagement20 Contacts

After Engagement189 Paid Signups

Operator Review

Co-Founder — Full-Funnel Marketing & Organic Compounding

Co-founder leading organic search engineering, local presence strategy, and client growth architectures.

The Short Version

A group of corporate professionals wanted to launch a Mother's Day marathon in Bengaluru — with no community, no event experience, no CRM, no one available to make calls, a tiny budget, and 39 days on the clock. A standard lead-gen form would have buried them in enquiries they had no time to chase. So instead of collecting leads, we built a flow that collected commitment: a paid signup fee as the qualification filter, delivered entirely through Click-to-WhatsApp Ads and an n8n automation with zero human overhead. The result: 189 paid signups from roughly 1,400 conversations, at a strong 2.09 ROAS — a profitable, self-running registration engine built for people who had no time to run one.

*Note: this is an early-stage, in-progress engagement. The figures below are real and measured against the dealership's prior baseline, but reflect the first weeks of a young campaign on a deliberately modest starting budget.

The Hero: Passionate organizers with every constraint working against them

Our client wasn't a company. It was a small group of corporate employees who wanted to do something meaningful — launch a Mother's Day marathon in Bengaluru as a passion project. They came to us through a referral from a mutual contact, and they were refreshingly honest about where they stood: clueless on how to actually pull it off, and stacked with constraints.

In a discovery call, the real picture came out, and it was daunting:

This is the kind of brief most marketers would quietly decline. Every standard playbook assumes things this team didn't have: a list, a team, a CRM, time, and budget. The hero here was a group of enthusiastic people trying to do a good thing under constraints that made the usual approach impossible.

The Situation: The normal playbook would actively make things worse

The instinctive move for “we need 300 signups” is a lead-generation form: run ads, collect contact details, follow up. For this team, that approach wasn't just suboptimal — it was a trap.

A lead-gen form optimizes for volume of contacts. But contacts are worthless to a team with no one to contact them. Every form fill would have generated an enquiry that needed a call or a message — and there was nobody to make the call or send the message. Worse, lead forms are magnets for low-intent responses: people who fill them idly with no real intention of showing up. For a team whose single hardest constraint was “no time for time-pass leads,” a lead-gen form would have manufactured the exact problem they most needed to avoid: a pile of unqualified enquiries and no capacity to sort them.

So the real problem wasn't “how do we get leads?” It was: how do we get genuinely committed signups, without anyone having to qualify, chase, or manage them?

The Complication: The one resource they couldn't spare was human time

Strip the brief down and the binding constraint becomes obvious. It wasn't really budget, and it wasn't really the deadline. It was human attention. Every conventional registration method — forms, follow-up calls, manual WhatsApp triage, a CRM someone has to work — assumes a person on the other side doing the qualifying and chasing. This team had no such person and refused (sensibly) to hire one for a short-term passion project.

That single constraint invalidated almost every standard tactic. You can't “just follow up faster” when there's no one to follow up. You can't “nurture the leads” when nobody has an hour to spare. Any solution that created manual work was, by definition, a solution that would fail. The challenge wasn't marketing reach — it was designing a system that needed almost no human involvement while still filtering hard for real intent.

The Implication: What happens if you get this wrong

Picture the version where we'd run the obvious lead-gen campaign. Ads go out, a few hundred form-fills come in, and they land on a team with no time and no CRM. The genuinely interested people get no reply for days because nobody's watching the inbox — so they lose interest or sign up for a different event. The time-pass leads clog whatever attention the team can spare. The 39-day clock runs down while the organizers, exhausted by their day jobs, try to manually sort a mess they were never equipped to handle. The event under-fills, or worse, doesn't happen — not for lack of interest, but because the system drowned the team in the wrong kind of work.

For a passion project, that failure mode is especially cruel: people pour personal energy and a little of their own money into something meaningful, and watch it collapse under logistics, not lack of heart. The stakes weren't a quarterly target. They were whether a good idea, done by good people on the side, would happen at all.

The Need-Payoff: A system that qualifies and registers itself

Framed correctly, the need was sharp: a registration engine that filters hard for genuine intent and runs itself — converting interested strangers into committed, paid participants without anyone on the team having to make a call, work a CRM, or chase a lead. Solve that, and the budget and the deadline became manageable, because every conversation the system handled was one the team didn't have to.

The Resolution: Make payment the filter, and let automation do the rest

The core insight was simple and it solved everything at once: use the signup fee itself as the qualification filter. Anyone willing to actually pay to register is, by definition, not a time-pass lead. Money is the cleanest intent signal there is — far cleaner than any form question. So instead of collecting enquiries and qualifying them manually, we built a flow where the act of paying did the qualifying automatically. Only after someone paid would their details be passed to the team.

We built it on Click-to-WhatsApp Ads (CTWA) feeding an n8n automation, so the entire path ran with almost no human involvement:

We kept the setup deliberately lightweight to match a short-term project: no permanent accounts were created for them, and the whole thing ran on a new phone number they purchased for the event and their own social media, with ad targeting set to a precise radius — proper geographic inclusions and exclusions — so a small budget reached only the right local audience.

The elegance was in the restraint: no CRM, no hires, no manual triage. The system did the qualifying, payment did the filtering, and the team only ever touched genuinely committed participants.

The Results: A highly qualified conversion path and surplus revenue

Within the 39-day window, on a deliberately small budget, the self-running engine delivered:

Conversion StageVolume / RatioConversion Rate
Total Ad-Initiated Conversations~1,400 chats—
Interest-Qualified Leads~810 chats~58% chat-to-qualified
Paid Signups / Registrations189 registrations~23% qualified-to-paid
Blended Return on Ad Spend (ROAS)2.09x ROASSelf-funding surplus

*Results compiled for the full 39-day campaign cycle. All metrics verified via n8n transaction and conversational logs.

The honest context matters here, and it makes the result stronger rather than weaker. The team had aimed for 300+ signups; they reached 189, with the gap openly down to the small budget and the tight 39-day deadline — there simply wasn't time or spend to go further. But consider the starting point: a group with 20 known contacts, no community, no team, no CRM, and no time, who ended with 189 paying participants and an acquisition engine that ran at a surplus while running itself. A 2.09 ROAS means they didn't just cover their ad costs — the signup fees brought in roughly twice what they spent to acquire them, which for a self-funded passion project is an outstanding outcome.

What could push this further: Scaling the baseline model

It's worth being clear about what this result was not: it wasn't a maxed-out campaign. It was a deliberately bare-bones engine, built to run with almost no infrastructure because that's what the constraints demanded. Which means the levers that would scale it are mostly still untouched.

With even modest additions, the same approach could comfortably clear the 300+ target:

None of that was in scope this time — and that's the point. The 189 signups and 2.09 ROAS came without any of it. The honest read is that this was a strong result from a minimal setup, with a clear, obvious path to a much bigger one whenever the organizers want it.

Why it worked: We changed what we were collecting

The breakthrough wasn't a clever ad or a bigger budget. It was refusing the default — “collect leads” — and asking what the team could actually handle. The answer was: nothing manual, and no time-pass leads. So we stopped collecting leads and started collecting commitment, using a two-stage filter — interest checks to qualify genuine interest (~58% of conversations), then the paid fee to isolate the truly committed (~23% of those) — with automation as the workforce. Once the system itself did the qualifying, every constraint that had made this look impossible — no team, no CRM, no time — simply stopped mattering.

That's a core part of how Fluxsy works: we design the system around the real constraints, not the standard playbook. Sometimes the answer isn't more budget or more people. It's changing what you collect, and letting the right mechanism do the work no one has time to do.

Byline & operator credentials

Written by Deeptanshu Sharma, Co-Founder & Funnel Operations Lead at Fluxsy. This engagement is completely anonymized for confidentiality.

Compounding Growth Insights

Growth & Retrieval Intelligence

We document strict performance blueprints, privacy-centric analytics, and pricing structures directly linked to conversions.Highly recommended read for this page: Signal & Inertia