Built 6 n8n workflows + 1 insurance speed-to-lead pipeline. 0 sales so far. Here is the distribution mismatch I just uncovered.
Hey Indie Hackers,
Over the past two weeks, I built and tested 6 production-grade n8n automation workflows (WhatsApp appointment booking with Google Calendar, Stripe failed payment recovery, customer recall sequences, and a missed-call text-back engine). Technically, they were solid—stress-tested with real webhooks, zero unhandled errors.
Then came the distribution reality check:
- 140 LinkedIn impressions.
- 14 views on developer forums.
- 0 clicks. 0 sales. Exactly $0 in revenue.
At first, I thought the copy wasn't punchy enough. But looking at the numbers objectively, the problem wasn't the conversion rate—it was a complete audience mismatch.
The Mistake: Selling to Builders
My initial distribution channels were the n8n community forum, dev.to, and my personal tech network.
The flaw in that logic? Everyone hanging out in dev forums knows how to build workflows. When a developer sees a template for "WhatsApp appointment booking", they don't buy it—they reverse-engineer the logic and build it themselves in 30 minutes.
The real customer who desperately needs these automations (local clinics losing patients to missed calls, service businesses with empty calendar slots) isn't reading dev.to or hanging out on GitHub.
The Pivot: The "Agency Reseller" Route
Instead of trying to reach non-technical small business owners directly (which requires long-term SEO and cold outbound), I'm shifting to a B2B builder angle: Automation Freelancers and Local Marketing Agencies.
An agency owner charging a $1,500 setup fee to a local dentist doesn't want to spend 10 hours configuring Meta webhook signatures, timezone offsets, and TCPA opt-out logic. Paying $29–$39 for an agency-licensed, production-ready workflow saves them a full workday and pays for itself immediately.
We just completed a 95-node speed-to-lead demo for an insurance brokerage using this exact model.
Have you ever experienced this "building for the wrong audience" trap? How did you bridge the gap between building tools and finding the buyers who actually value saved time over writing code?
I recognize this from my own space: a cheap tool/template almost never sells itself, and the real money shows up where it's "do this for me," not "here's a tool." Your $350 client is a signal. When we went through vendor types for scraping, the same thing came up: self-serve tools are cheaper on paper, but their own weak spot is "requires time to maintain, breaks on complex cases" — which is exactly why the managed model pulls in money faster, even though it costs more on paper.
The $350 sale and the $29-39 template price two different things, a product and a service, and only one of them has real cost data behind it. Before betting the next two weeks on the agency reseller pitch, it's worth logging exactly how many hours went into that $350 build, the client calls, the webhook debugging, the TCPA and timezone edge cases you mentioned. Twelve hours on that job means the $350 gig pays less than the $29-39 template would at thirty sales, and the real product is probably a fixed-scope service at a higher rate. Two hours means you've already found the product, and the reseller pitch should lead with delivery speed rather than price. Freelancers doing custom builds like this tend to undercount the hours that don't feel like real work, the scope calls, the debugging that isn't billed separately, which is the same blind spot that shows up in time tracking generally. Do you have an actual hour count for that first $350 job, or was it priced by feel?
Fair challenge, honestly no. I priced that first job by feel, not tracked hours. Rough guess is 3-4h on the client-specific part, since the core flow was already built.4h on the client-specific part, since the core flow logic was already built.
(typo above from copy-paste, sorry — meant: 3-4h on the client-specific part, since the core flow logic was already built.)
That $350 sale is almost annoying because it points to the service, not the template 😅 I’d sell the implementation again and watch which parts clients keep asking you to handle. The repeatable product might show itself there.
The audience mismatch is pretty clear from the 0 clicks. Have you tested whether agencies will actually pay $29–$39 for the workflow, or is the reseller route still a hypothesis?
Honestly, still a hypothesis. I have not closed a single 29-39 dollar sale yet, so I cannot claim agencies will pay that for a packaged workflow.
The one real data point I have cuts the other way: someone paid around 350 dollars for a done-for-you build of the exact same flow (insurance speed-to-lead). That suggests the value sits in the implementation, not the template - n8n already has a free template library, so just the JSON is a weak wedge.
So I am switching from waiting on passive store traffic to actively pitching the reseller angle: direct outreach to agencies and local-traffic freelancers who would deploy this as a client add-on. If that gets zero bites in a couple of weeks, the reseller thesis is probably dead and it becomes a productized-service play instead.
Will report back either way.
That $350 implementation sale is a much stronger signal than the $29–$39 template test. If you’re open to it, what’s the best email to reach you on?
No problem - thiago.cavichi.projetos@gmail.com. Drop me a line with what you have in mind and I'll get back to you.
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
Happy to talk. Easiest is to DM me here on IH so I don't have to post an address in a public thread - or say here what you have in mind and I'll follow up.
I only use email for this, and I don’t think Indie Hackers has a DM feature. If you’re open to it, what’s the best email to reach you on?