DEV Community: StackPick

How to Make Money Training AI: A Practical, No-Hype Guide

StackPick — Sat, 15 Aug 2026 15:31:00 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

Training AI for money usually means collecting or reviewing data that a model needs: reading a voice script, filming an everyday action, photographing a specified object, labeling information, or evaluating an output. The work can be real, but it is project-based. A published rate does not create available tasks or guarantee approval.

Start with the AI training jobs comparison and earnings calculator to see which claims come from official sources. Then use the process below to judge an actual task rather than a promotional example.

The real path from signup to payout

1. Create one truthful account

Use your real age, country, language, identity, and payment information. Platforms and individual projects may have different location, device, tax, or language requirements. Trying to unlock another market with a VPN or false profile can invalidate work and put a balance at risk.

2. Read the brief before accepting

A useful brief should identify what to capture, the compensation unit, the technical standard, the deadline, eligibility rules, review criteria, and how the data may be used. If the rate is “per approved hour,” ask what counts toward that hour. If it is per clip or image, calculate the preparation and retry time too.

Skip a task when the instructions, consent, rate, or permitted use are unclear. Time spent guessing is rarely paid.

3. Prepare the recording environment

For voice work, reduce echo, fans, traffic, and notification sounds. For video, clean the lens, stabilize the phone, check light and framing, and remove private documents from view. For photos, follow the requested angle, background, file type, and quantity.

Do a short test before a long session. Repeating two minutes is cheaper than losing an hour to clipping, blur, the wrong orientation, or a missed instruction.

4. Match the brief exactly

Natural does not mean improvised when the task requires a script. Creative does not mean adding people, brands, locations, or personal information the brief did not request. Keep a private note of the task, rate, submission date, and status, but do not publish confidential instructions or customer data.

5. Wait for review

Submission is not payment. A platform may approve, reject, hold, or return work for correction. Look for a reason and a legitimate appeal or resubmission route when one exists. Count only accepted work in your earnings record.

6. Request a small first payout

Confirm the minimum balance and payment method inside your account. Identity, tax, sanctions, or fraud checks may happen before funds are released, and a bank or provider may charge fees or apply its own exchange rate. A completed small withdrawal is stronger evidence than a calculator screenshot.

A simple way to estimate a task

Do not begin with “headline rate × 160 hours.” Begin with what you can observe:

Expected approved value = available work × stated task rate × your actual approval share − payment and conversion costs.

Availability and approval are unknown before you have personal history. Use a conservative range, include setup and rejected time, and never spend money you expect to recover from work that has not been approved.

Quality checklist before submitting

The account, country, device, and language match the eligibility rules.
Every step and duration requirement in the brief is complete.
Audio has no clipping, interruptions, or unrequested processing.
Video is steady, correctly oriented, well lit, and free of private material.
Files use the requested format, naming, sequence, and count.
Every identifiable person has provided the required consent.
You reviewed the entire recording or sample set once before upload.
You saved only the records you are allowed to keep.

Privacy and scam checks

Your face, voice, home, device metadata, and location can be personal data. Read both the platform policy and the specific task consent. Avoid capturing passwords, financial papers, medical information, minors, bystanders, vehicle plates, or screens unless the task expressly covers them and the required permission exists.

Do not pay a stranger to “unlock” tasks, share a one-time login code, install remote-access software, or send account credentials through messaging apps. Use the platform's official domain and support channel. Keep tax and earnings records appropriate to your country.

The FTC's basic job-scam rule is useful here: an honest employer or work platform will not charge you to get a job, send a check and ask you to return part of it, or demand gift cards or cryptocurrency. Protect each account with a long, unique password and multi-factor authentication where available.

Hub or Crowtado?

Hub.xyz publishes a US$5 worker-hour rate in its API, but suitable tasks and approved hours still depend on the project. Crowtado advertises voice examples from US$18 to US$40 per hour and payout requests from US$10, while its terms expressly state that availability, acceptance, and earnings are not guaranteed.

There is no universal winner. Create an account only after reading the current terms, then compare the briefs actually available to you.

Disclosure

StackPick may receive referral compensation if you join Hub through the button below and later produce approved work under Hub's rules. The worker's published rate is not reduced by the link. StackPick had no realized Hub referral commission at this guide's publication date.

See whether Hub has a matching project →

Official sources

Originally published on StackPick — verified SaaS pricing, cost calculators and tool comparisons. Free n8n templates: github.com/marcelobm33/stackpick-n8n-templates

I Turned 25 SaaS Pricing Pages Into One Queryable Decision Dataset

StackPick — Sun, 09 Aug 2026 13:09:47 +0000

Most SaaS comparison pages begin with the same number: the cheapest advertised plan.

That number is easy to collect and often useless.

Zapier counts tasks. Make counts credits. n8n Cloud counts workflow executions. Email tools may bill by contacts, sends or both. WhatsApp platforms add their own subscription to Meta's usage charges. A $9/month badge does not tell you what the same workload will cost.

I rebuilt StackPick around a small public dataset instead of another collection of generic reviews.

The row is more important than the ranking

Each tool now has a machine-readable record with:

entry price in USD;
the billing unit;
whether a real free plan exists;
published plan tiers;
verification date;
the vendor pricing page used as the source.

The current data is available as CSV and JSON. The human-readable landing page explains the verification method.

The important constraint is provenance. A price without a source and date quickly becomes misinformation, so the dataset treats verification metadata as part of the value, not an editorial footnote.

Entry price still does not answer the decision

A usable recommendation needs at least three additional inputs:

the job to be done;
expected monthly volume;
the operator's priority, such as ease, depth or scale.

That became Find My Stack. It filters only partner routes that are currently active, but commission size never enters the ranking score.

The second interface is Switch & Save. A cheaper list price is not a saving if the migration breaks workflows or requires weeks of rebuilding, so every suggested switch links to a staged migration and rollback path.

The third interface is a set of Plan Finders. They answer a narrower question: which published tier actually covers the volume?

What I learned from modeling pricing units

Comparable workloads need explicit assumptions

Ten thousand automation events are not automatically ten thousand billable units on every platform. A scenario must state how a workflow maps to tasks, credits or executions.

“Free” is a property, not a headline

A free trial, a free plan and a sales demo are different states. The dataset stores a free-plan flag separately and the interface labels trials and paid entry tiers honestly.

A negative saving is still a valid result

The switch calculator can recommend staying put. Hiding that outcome would turn a decision tool into an affiliate funnel.

Dated data is more useful than false precision

Pricing changes. A verified date and source URL let a reader challenge or update a row. An undated $29 presented to two decimal places is not more accurate.

Making the dataset discoverable

The landing page now includes Schema.org Dataset and DataDownload metadata for both formats. The CSV remains a plain file that works in a spreadsheet, while JSON keeps full tier arrays for software consumers.

There is also a free embeddable finder and cost-calculator library. The iframe supplies the interactive tool; a normal attribution link outside it gives readers and crawlers a path back to the source.

The test is not page count

The real funnel is:

decision run → partner click → approved referral

More generated pages are not the goal. If the decision interfaces do not create qualified clicks, the next move is to improve the model or distribution — not create hundreds of query variations.

The dataset is open to download and cite with attribution. If you find a stale row, the vendor source and verification date make the correction auditable instead of subjective.

Gallabox vs AiSensy vs Wati — the platform fee is the least interesting number

StackPick — Wed, 05 Aug 2026 16:35:07 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

Most WhatsApp BSP comparisons lead with the monthly subscription. That is usually the least interesting number.

I maintain a pricing index for WhatsApp Business API tools, so I checked the public pricing pages of Gallabox, AiSensy, and Wati (verified August 2026). The three serve different buyers, and the real cost driver sits below the plan fee.

The prices you see first

BSP	Entry list price (annual billing)	Notes
AiSensy	~$45/mo (₹1,500 Basic)	Budget entry, India/LatAm focus, WhatsApp-only
Gallabox	$112/mo (Basic, annual)	WhatsApp + Instagram + web inbox, AI credits included
Wati	~$59–$89/mo (depending on tier)	Shared inbox + campaigns, strong for teams

Meta per-message fees (marketing, utility, authentication) sit on top of every plan. No BSP absorbs Meta's bill.

What actually moves your monthly bill

Team seats. AiSensy prices per plan; Gallabox and Wati price per user tiers and charge for extra agents. A 5-person team can easily pay more in seats than in software.
Channels. AiSensy is WhatsApp-first. Gallabox bundles Instagram and web widget. Wati bundles campaigns and inbox. If you need Instagram DM, the cheaper WhatsApp-only option suddenly costs an extra tool.
Chatbot depth. Basic plans across all three include simple flows. Advanced AI qualification, routing, or full-funnel agents push you to Gallabox's higher tiers or Wati's Pro.
Meta category mix. Marketing templates cost several times a utility message. If you blast weekly campaigns, the Meta layer dominates — the "cheap" BSP on subscription becomes irrelevant.

When each makes sense

AiSensy — tight budget, WhatsApp-only broadcasts, India/LatAm market expectations. Lowest entry, but Instagram and advanced automation need add-ons.
Gallabox — you want WhatsApp + Instagram + web in one inbox with AI lead qualification out of the box. More expensive, but replaces buying separate tools.
Wati — shared team inbox + broadcast campaigns for a sales/support team that lives on WhatsApp. Strong playbooks for e-commerce.

My working numbers

I keep a WhatsApp cost calculator that models Meta category × country × volume so the platform fee stops being the only input.

For a side-by-side with disclosed affiliate links, start at best WhatsApp automation tools — and when WhatsApp + Instagram + AI inbox is the requirement, try Gallabox. If pure budget WhatsApp is the requirement, try AiSensy.

Bottom line

Do not buy a BSP on the subscription fee alone. Model team seats × channels × chatbot depth × Meta category mix. The BSP that looks cheapest on the homepage is rarely the cheapest at 1,000 real conversations.

WhatsApp Business API pricing at 1,000 conversations — the bill is not the BSP fee

StackPick — Wed, 05 Aug 2026 00:01:03 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

Most WhatsApp BSP comparison posts list a monthly platform fee and stop. That number is usually the small part of the bill.

WhatsApp Business API cost has two layers:

Meta conversation charges — billed by category (utility, authentication, marketing, service) and by country.
BSP platform fee — what Wati, AiSensy, Gallabox, respond.io charge on top for inbox, bots, multi-agent, templates.

I keep a pricing index for WhatsApp tools, so I modeled a realistic SMB volume: 1,000 conversations/month in Brazil/India-style markets, mix of utility + a few marketing blasts.

What actually moves the bill

Cost layer	Who bills it	What changes it
Meta conversations	Meta (via BSP)	Category + destination country
Platform seat/inbox	BSP	Agents, bots, CRM features
Template approval / extras	BSP	Marketing templates, flows

The trap: teams pick the cheapest BSP fee, then burn budget on marketing-category conversations that cost several times a utility message.

Rough shape of the math (order of magnitude)

At ~1k conversations/month:

If most traffic is utility/service, Meta cost stays relatively contained and BSP fee matters more.
If you blast marketing templates weekly, Meta cost can dominate — the "cheap" BSP suddenly looks expensive because every failed campaign still bills.

Exact rates change by country and Meta's current category table. Always verify the Meta conversation-based pricing page before committing.

How to compare BSPs without lying to yourself

Fix volume: conversations/month + % marketing vs utility.
Fix country (Brazil ≠ US ≠ India on Meta rates).
Add BSP platform fee + seat count.
Ignore "unlimited messages" marketing copy — Meta still bills conversations.

If you want a working model, use the calculator: WhatsApp cost calculator.

For BSP shortlists with disclosed affiliate links, start at best WhatsApp automation tools — and when a BSP fits India/SMB WhatsApp workflows, try AiSensy.

Bottom line

Don't buy a BSP on platform fee alone. Model Meta category mix × country × volume, then layer the BSP. The tool that looks cheapest on the homepage is often not the cheapest at 1,000 real conversations.

I compared 5 email marketing tools by real cost at 5,000 contacts — the spread is 4x

StackPick — Wed, 29 Jul 2026 19:28:51 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

Most "best email marketing tool" posts stop at the starting price. That's useless, because email tools bill in two completely different ways:

Per contact — you pay for list size, even contacts that never open.
Per send — you pay for emails actually delivered. Contacts are free.

I maintain a small pricing database for these tools, so I ran the numbers at a realistic SMB volume: 5,000 contacts, 4 campaigns/month (20,000 sends).

What 5k contacts actually costs (2026 pricing pages)

Tool	Model	Approx. monthly cost at 5k contacts
Mailchimp (Standard)	per contact	~$100/mo
Mailchimp (Essentials)	per contact	~$75/mo
GetResponse	per contact	~$54/mo
Moosend	per contact	~$48/mo
Brevo (Starter)	per send	~$25/mo (contacts unlimited)

Same list, same sending volume — roughly a 4x spread between the most and least expensive mainstream option.

When per-send wins (and when it doesn't)

Per-send pricing wins when:

Your list is big but engagement is concentrated in a segment.
You email 1–4 times a month, not daily.
You're storing lots of "cold" contacts you may re-engage later.

Per-contact wins when:

You email the whole list very frequently.
Your list is small (< 2,500) and you're inside a free tier anyway.

The trap: teams keep a 5k–20k contact list on a per-contact plan while emailing a 20% engaged segment. They're paying for 80% of contacts that generate nothing.

The free tier is the other honest difference

For side projects and early SaaS, the free tier matters more than the paid tier. Brevo's free plan is 300 emails/day with unlimited contacts — enough to run a waitlist or an early-product newsletter without touching a credit card: try Brevo free.

Mailchimp's free plan caps at 500 contacts, which you outgrow in weeks.

Full comparison data

I keep the numbers updated against the vendors' pricing pages:

The calculator is the point of this post: don't trust any table (including mine) at your volume. Run your own contact count and send frequency — the winner flips depending on where you are.

My click tracker said 518 humans. Only 134 people loaded the page.

StackPick — Sun, 26 Jul 2026 07:30:44 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

For a few weeks my analytics told me a comfortable story: 518 humans had clicked an outbound link in the last 30 days. Then I put that number next to a different one from the same database — 134 page views — and the story fell apart.

Nobody clicks a link on your site more times than they load a page on your site. A ratio above 1.0 is not a suspicious trend to monitor. It is arithmetic proof that the tracker is wrong.

Mine was at 3.9.

The setup

The site is a static build on Cloudflare Pages. Outbound links do not point straight at the destination — they go through a redirect worker at /r/{slug}, which records the click server-side and then 302s the visitor onward. Standard pattern, and it survives ad blockers, which is why I used it.

Each click row stores a source_page so I know which page produced it. The worker fills it like this:

const sourcePage = request.headers.get("Referer") || `cta:${ctaId}`;

The fallback exists for a real reason. Some browsers and privacy settings strip the Referer header, and I did not want those clicks landing in the database as anonymous rows I could never attribute. So if there is no referer, fall back to the CTA id, which I already have.

Downstream, the bot filter decided whether a click was human. Its reasoning, roughly: a real browser on my site sends context, so a row that has a source_page came from a browser, and an empty one is suspect.

-- what "human" used to mean
WHERE source_page IS NOT NULL AND source_page != ''

Read those two snippets together and the bug is obvious. It was not obvious to me for weeks, because they live in different files written on different days.

Why the fallback poisoned the filter

ctaId comes from the query string. The link in the HTML is literally:

<a href="/r/wati?cta=best-whatsapp-wati">Try Wati</a>

A crawler fetching that URL sends no Referer. So the worker takes the fallback branch and writes source_page = "cta:best-whatsapp-wati".

That is a non-empty source_page. Which is exactly what the filter accepted as proof of a browser.

The fallback was not recording "a human whose referer was stripped". It was recording "the value that was already sitting in the href" — a value any crawler following the link reproduces perfectly, because it is in the markup. I had built a bot detector whose evidence of humanity was a string the bot could read off the page.

The fix

One condition. A real browser referer is an absolute URL, so require that shape instead of mere presence:

-- source_page now has to look like a referer, not like something copied from the href
WHERE source_page LIKE 'http%'

Reclassifying the whole table moved 518 "humans" down to 218. Ratio went from 3.9 to 1.6.

1.6 is still wrong, and that is the useful part

The honest reading of 1.6 is "still inflated, just less". Plenty of crawlers do send a Referer, so the new rule catches the lazy ones and misses the polite ones. I did not want to ship a number I would have to re-litigate every month, so the reporting script now prints both figures and the ratio between them:

"reality_check_30d": {
  "page_views_js": 134,
  "redirect_clicks_human": 218,
  "inflation_ratio": 1.6,
  "verdict": "inflated"
}

That block is deliberately annoying. As long as the ratio sits above 1.0, every report I read carries a note that the click number is not trustworthy. A metric that announces its own error bar beats a metric that quietly looks fine.

What I would generalise from this

Cross-check server-side counts against a client-side one. Server-side tracking is popular precisely because ad blockers cannot stop it — but that same property means bots cannot be stopped either. The JavaScript page_view event undercounts (blockers, no-JS) while the server-side click count overcounts (bots). Neither is truth, and the gap between them is the diagnostic. One number alone would never have told me anything was wrong.

Write down the invariants your data must satisfy. Not thresholds like "alert if clicks drop 20%" — invariants, things that cannot be true in a working system. Outbound clicks ≤ page views is one. They cost nothing to assert and they fail loudly the moment a fallback quietly changes meaning.

Watch fallback values that come from the request. A default is fine when it encodes something you know independently. It is dangerous when it echoes attacker- or crawler-controlled input back into your data, because downstream code cannot tell the echo from the real thing. My fallback did not fabricate the value — it copied it from the href, which made it indistinguishable from the genuine article.

The bug is rarely inside one file. Both snippets were reasonable in isolation. Neither author — both of them me — was thinking about the other. The defect lived in the seam, and the only thing that surfaced it was comparing two numbers that had no business disagreeing.

I keep a public verified pricing index for automation and messaging tools, which is what the redirect endpoint was tracking clicks on in the first place. If you want the arithmetic-check idea without the write-up, the short version is: find two metrics in your system that must hold an order relationship, and assert it.

n8n vs Make

StackPick — Sun, 26 Jul 2026 02:21:05 +0000

Feature lists won't settle this one; both platforms can build almost any workflow. The decision comes down to two things: how each one bills, and whether you're willing to self-host. Use the Quick answer, cost table (1k / 10k / 50k) and 3-year TCO above — then read the billing caveats below.

The billing unit is the whole game

Make bills in credits — standard module runs generally consume one credit, while some Make AI features use variable credits. A 15-module standard scenario that runs 1,000 times is roughly 15,000 credits.
n8n bills per execution — one full workflow run counts once, whether it has 5 nodes or 50.

That means workflow shape matters. A multi-module workflow can consume many Make credits per run while n8n Cloud generally bills one workflow execution. AI modules and retries can change actual usage; measure both before choosing.

Simple, short scenarios flip it: Make's free and low tiers are generous when workflows are 2–4 modules, and its per-operation price is tiny at small scale.

Self-hosting: n8n's trump card

n8n's Community Edition is source-available and free with unlimited executions on your own server — a $5/month VPS runs serious automation loads. Make has no equivalent. If your team can run Docker, Cloud TCO above is the ceiling, not the floor: self-host drops execution fees to $0. That's also the honest caveat: self-hosting means you own updates, backups and uptime. The cost table shows n8n Cloud so SaaS quotes stay comparable to Make.

AI workflows

n8n treats AI agents as first-class citizens: native LangChain agent nodes, vector stores, RAG pipelines, and a template library where 67% of new templates already use AI nodes. Make has AI modules and an assistant, but agentic patterns (tool-calling loops, multi-agent handoffs) fit n8n's model more naturally. Most of the ready-made AI agent templates you'll find — including ours — ship as n8n JSON.

Hidden costs and limits

n8n Cloud caps active workflows on lower tiers (5 on Starter) — automation-heavy teams hit that before they hit execution limits.
Make credits can rise when scenarios include iterators, retries or variable-credit AI modules; model a worst-case month in the automation cost calculator.
n8n's learning curve is real: expressions, JSON wrangling and node debugging. Make's UI is friendlier for marketers.

When to choose neither

Two apps, one trigger, no logic — Zapier's free tier or a native integration does it with less friction (see Zapier vs Make). Enterprise governance needs (SSO, audit logs, SOC2 reporting) point to Workato instead.

Choose n8n if workflows are complex or AI-driven, someone on the team is technical, or you want the self-hosted free option in your back pocket. Choose Make if visual simplicity for non-developers matters more and your scenarios stay short.

If the real pain is slow lead response (not tool price), model incremental gross profit with the lead recovery ROI calculator before you buy more seats.

Pricing sources

n8n pricing — verified 2026-07-01
Make pricing — verified 2026-06-12

Originally published on StackPick — verified SaaS pricing, cost calculators and tool comparisons. Free n8n templates: github.com/marcelobm33/stackpick-n8n-templates

How to Make Money with n8n (2026)

StackPick — Sun, 26 Jul 2026 02:19:36 +0000

Disclosure: this post contains links to paid products and affiliate programs. I may receive compensation if you sign up or buy through them. Pricing shown is verified against the vendor's public pricing page.

How to make money with n8n in practice means shipping value someone pays for — not “set and forget” YouTube schemes. n8n is free to self-host and bills Cloud by workflow execution, not per step. That cost shape is why freelancers and agencies productize automation. Four paths that match real demand:

Quick answer

Product — free JSON proof → paid pack with docs
Service — migrate Zapier/Make → n8n for a niche
Media — pricing comparisons + affiliate (slow)
Ops — use n8n inside your own business to stop lead leakage

Start with one niche pain you already understand. Distribution beats another unused template.

1. Sell ready-made workflows (product)

Ship a tested n8n JSON for a painful niche job: missed-call → WhatsApp reply, lead enrichment, invoice chase. Price a free starter JSON to prove competence, then a paid pack with docs and support.

Free reference: WhatsApp lead-reply gist · GitHub templates
Low-friction paid entry (no n8n required): WhatsApp Meta Template Kit ($19) — Meta-ready copy + approval checklist
Full automation pack: dealership lead-recovery pack ($49)

Reality check: buyers want setup notes, template message approval steps and failure modes — not a raw export.

2. Freelance / agency automation (service)

Charge setup + monthly care for Make/Zapier migrations onto n8n Cloud or a VPS. Typical offer: audit current Zaps → rebuild critical paths → document ownership.

Compare cost units before quoting clients: n8n vs Make · Zapier vs Make · automation cost calculator.

3. Affiliate + comparison content (media)

Publish honest pricing pages for tools your workflows use (WhatsApp BSPs, email, CRM). Disclose affiliate links. Revenue only appears after someone buys — clicks alone pay $0.

StackPick model: verified pricing tables → tracked /r/ links → VPS metrics. See how we make money.

4. Internal ops (save money = make money)

If you already run a business, n8n recovers leaked leads and after-hours calls. Model ROI before buying seats: lead recovery ROI calculator · lead follow-up stack.

What does not work

“Set and forget” schemes with no niche, no distribution, no support
Scraping random templates without testing Meta WhatsApp / API credentials
Expecting Google page-1 traffic on day one for head terms like “best automation software”

Minimal stack to start

n8n Cloud trial or $5–10/mo VPS self-host
One painful workflow in a niche you know
One distribution channel (Reddit niche, community.n8n, client outreach)
Optional: affiliate programs for tools you already recommend (pricing index)

FAQ — how to make money with n8n

Can you make money with n8n as a beginner?

Yes, if you pick a narrow job (one industry + one workflow) and sell setup help or a documented JSON. Broader “AI automation agency” pitches without a niche usually stall.

Is selling n8n templates profitable?

Some people earn from Gumroad/marketplaces; most revenue comes from the docs + support, not the file. Free templates build trust; paid packs convert after proof.

n8n Cloud or self-host for a side business?

Self-host if you want margin control and can maintain a VPS. Cloud if clients need reliability without you babysitting Docker. Model executions: n8n vs Make pricing.

Next reads

Originally published on StackPick — verified SaaS pricing, cost calculators and tool comparisons. Free n8n templates: github.com/marcelobm33/stackpick-n8n-templates