No-Code AI Automation Bundle: Score 31 — When "Passive Income" Is a Consulting Business in Disguise

The Asset at a Glance

This is a "no-code AI automation bundle" — a collection of 40+ workflow templates built for n8n and Make (formerly Integromat). The seller built the workflows over 18 months, sells them as a Gumroad product ($47–$197 per template pack), and offers setup support calls at $150/hour.

The listing reports "$900/month in revenue," 600+ total customers, and a library of templates covering lead generation, content repurposing, invoice automation, and AI-assisted email drafting. Asking price: $18,000.

We scored it using AI Asset Score v1.0. The analysis is based on listing data and our standard diligence framework for AI-native assets. We did not conduct a full due diligence review.

AI Asset Score: 31 / 100 — Demo or Toy

The Core Problem: One-Time Sales Aren't MRR

The "$900/month" figure in the listing is an average of trailing 12-month gross revenue, divided by 12. That's not MRR. MRR means monthly recurring revenue — customers who pay every month on a subscription. This asset has none.

Here's the actual revenue breakdown from the listing data:

• Gumroad template pack sales (one-time): ~$720/month average (highly variable — peaks around launches)
• Setup/consulting calls ($150/hour): ~$180/month average
• Recurring subscribers: $0

The distinction matters enormously for valuation. A business with $720/month in one-time product sales does not have $720/month in recurring revenue. When the seller stops posting on Twitter and Reddit — which they will, because they're selling — Gumroad sales drop to near-zero within 60 days.

Revenue: 5 / 25 — No Recurring, No Business

Revenue quality is the most heavily weighted failure mode here. Our scoring penalizes heavily when revenue is:

1. Not recurring (no subscriptions)
2. Tied to founder activity (posting, launches, support)
3. Not independently verifiable (Gumroad analytics are self-reported screenshots)

This listing scores 5/25 on Revenue because the $900 monthly average overstates the transferable revenue by roughly 10x. The templates themselves — as static files — generate zero revenue without ongoing distribution. The "consulting" component is the seller's personal labor at $150/hour, which cannot transfer.

What would a 15/25 Revenue score look like? A SaaS product charging $29/month with 60+ paying subscribers who renew regardless of whether the founder posts anything that week.

Traction: 6 / 25 — Downloads ≠ Retention

600 total Gumroad customers is cited as evidence of traction. It's not. It's evidence of sales history.

Retention requires customers to come back — to upgrade, to buy a new pack, to subscribe. In this case:

• Repeat purchase rate: unknown (seller doesn't report it, which is itself a signal)
• Active user base: not measured — these are one-time purchasers who may have never even opened the workflow files
• Organic search traffic: minimal — the Gumroad page ranks for nothing independently
• Referrals: the seller's Twitter audience refers occasionally, but that audience is non-transferable

600 downloads of a template pack is closer to a newsletter subscriber count than to 600 recurring customers. It tells you demand exists for the concept — not that a recurring business exists.

Transferability: 7 / 20 — Technical Assets Transfer; Value Doesn't

The workflow files themselves (JSON exports from n8n and Make) can be packaged and delivered. The Gumroad account can be transferred. The domain can be redirected. These are the technical transfer boxes — all checked.

What doesn't transfer:

• The audience. The seller has ~4,200 Twitter followers, a LinkedIn following, and a small email list of buyers. This is the distribution engine for sales. Without it, the Gumroad store is invisible.
• The setup knowledge. n8n and Make workflows require credentials: API keys, webhooks, account connections. Every customer who bought a template likely needed help configuring it. That help was the seller's time — and the $180/month in consulting is a floor estimate, not a ceiling.
• Vendor relationships. n8n cloud pricing is negotiated at account level. A new account may face current retail pricing, which is significantly higher than grandfathered rates some early adopters hold.

The Automation Irony: An Automation Tool That Runs on Manual Labor

Here's the central paradox of no-code automation bundles as sellable assets: the product is automation, but the business is consulting.

The seller built tools that automate other people's businesses. But to sell and support those tools, the seller:

• Writes Twitter threads, LinkedIn posts, and Reddit comments to drive Gumroad traffic
• Records demo videos and keeps them updated as n8n and Make change their interfaces
• Answers support tickets when workflows break after platform updates
• Runs setup calls when customers can't figure out credentials
• Updates templates when API changes break existing configurations

None of that is automated. All of it is manual labor attached to the seller's identity. The product automates other people's workflows; the business of selling and supporting it is 100% human-hours.

Automation score: 10/20. The templates themselves run without human involvement once configured. The business around them does not.

Risk: 3 / 10 — Platform Dependency and Zero Moat

Three platform risks apply here simultaneously.

n8n pricing shift (2024). n8n moved from a fully free self-hosted model to a paid cloud model with seat-based pricing starting at $49/month. Many of the seller's templates were built and documented for the free self-hosted version. Customers on the new paid model face different UX, different limitations, and — in some cases — templates that don't behave identically. The buyer inherits support debt from this transition.

Make (formerly Integromat) pricing changes. Make raised prices and restructured operation limits twice in 18 months. Templates built for 10,000 operations/month may now cost customers 3x to run at current pricing tiers. Support complaints from legacy customers are ongoing.

Zero IP protection. A workflow JSON file is not protectable intellectual property. Any buyer of the template can open it, understand the logic within hours, and rebuild it independently — or share it. There is no non-compete, no enforcement mechanism, and no meaningful moat. The only moat was the seller's brand credibility, which doesn't transfer.

What the $18,000 Ask Is Actually Pricing

The seller is using a 20× MRR multiple logic — $900/month × 20 = $18,000. But $900/month is gross one-time revenue, not MRR. That multiple doesn't apply.

A more honest valuation framework for a template library:

The gap between $5,100 (realistic ceiling) and $18,000 (asking price) is the seller's personal brand being priced as if it transfers with the asset. It doesn't.

When This Type of Asset Is Worth Buying

This isn't a blanket condemnation of no-code automation assets. Under specific conditions, a template library or workflow bundle can be a legitimate acquisition:

• If it has a real subscription component. A template library with $29/month "member access" — where customers pay recurring for ongoing updates and support — is a different asset entirely. Recurring revenue from subscriptions scores 20+ on our Revenue dimension alone.
• If the buyer already has distribution. A content creator with 20k engaged followers buying a workflow library to productize their existing audience is not paying for the seller's audience — they're paying for the product. For that buyer, $5k–$8k might be reasonable.
• If the seller will stay involved as a revenue-share operator. If the original seller is willing to continue content creation under a revenue-share model (e.g., 30% of sales they generate), the deal economics change substantially. Now the buyer gets distribution they don't need to build themselves.

None of those conditions apply to the listing we reviewed. The seller wants a full exit, the revenue has no recurring component, and the buyer has no existing distribution.

The Verdict

Score 31 puts this clearly in the "Demo or Toy" band — below our 50-point threshold for even conditional consideration. The asset contains code value (the templates), contact value (the email list), and concept value (the niche is real). But none of those add up to $18,000.

If a buyer wanted the templates as a starting point for building their own automation content business, $3k–$5k is a reasonable price. At $18,000, the seller is pricing in a personal brand moat that will evaporate the moment the handover completes.

Compare this to Case #1 (Score 74, automotive SaaS with real MRR and verifiable retention) or Case #2 (Score 43, GPT writing tool with real subscriptions but high churn and API costs). This case sits below both — not because the market is bad, but because the structure of this specific asset doesn't support the asking price.