Monetization best practices

Turning a Flow public is only the first step. Follow these guidelines to convert visitors into paying users and keep refunds low.

1. Nail your pricing

The single most important factor in having a high conversion rate is setting the right price. Too high? Users bounce. Too low? You leave money on the table. The best way to find your sweet spot is to test different prices and see what converts best.

You know your audience best, but here are some general guidelines:

Flow type	Typical sweet-spot	Why
Quick utility (JSON snippet)	$1–$4	Impulse-buy range; low risk for users
Personalized avatar/portrait packs	$6–$12	Doesn’t look highly complex, but tempting if enough images are included
Complex logic with images (DnD campaign generator with character portraits)	$10+	Users expect higher price due to perceived complexity and the bonus of images

How to choose

Build something your audience relates to and would want to use.
Run it yourself first — go to Dashboard → Run and watch the Charges tab. Know your exact infra cost (training minutes, inferences, zips).
Target 2× cost as a starting margin — leaves room for the platform fee and promos while staying attractive.

However, this is just a starting point. Perhaps most of your audience isn’t willing to pay $10, but $7 is a no-brainer — which could massively increase your conversion rate and overall revenue.

✦

Rule of thumb: if your net margin is less than $1, you’re likely under-pricing. If conversion tanks, you’re likely over-pricing — or your Flow doesn’t resonate with your audience.

2. Test before you publish

Run at least one full public-style run (using the same input and datasets you expect from users).
Preview the public Flow page to make sure it looks good and there’s nothing confusing.
Verify every step finishes and the outputs are as expected.

A single broken step is the #1 refund trigger.

3. Optimize the first impression

Checklist	Why it matters
Hero and preview images	Users buy with their eyes — show 3–5 diverse examples.
Short, benefit-led title	”Forge My Adventuring Party!” converts better than “DnD Character Flow”.
Clear form labels and placeholders	Reduce drop-offs caused by confusion.
Custom submit button	”Start Adventure” feels friendlier than “Submit”.

4. Keep runtime predictable

Limit datasets — e.g., "max": 15 images. Asking for too many might scare users off or lead to low-quality uploads.
Batch inferences — one ImageGenerator step for all images is much faster than 10 separate steps.

Aim for runs under 5 minutes. Over 10 minutes? Consider breaking into two Flows (e.g., pay upfront to train, free second run to generate).

5. Communicate value

Answer “What do I get?” early.
Mention output counts (“You’ll receive 120 HD portraits + a ZIP of everything”).
If training is involved, emphasize uniqueness (“model is fine-tuned only on your photos and deleted after 7 days”).
Make it clear the Flow is unique, made by you, and hand-tailored to them.

6. Provide refund-resistant outputs

Always include a Zipper step so users can download everything at once.
Add an Objects widget so advanced users can copy raw JSON (and it makes debugging easier for you).
If you rely on user datasets, enforce file counts (min, max, dataset: true) to avoid midway failures or poor results.

7. Market your Flow

Custom slug ("slug": "anime-sticker-maker") — memorable and shareable.
Share on socials with a direct link and your preview images.
Encourage early users to share results (UGC is the best ad).
Offer limited-time discounts by temporarily lowering runPrice — the URL stays the same.

8. Monitor and iterate

Dashboard → Runs shows completion rate and errors.
Dashboard → Billing → Charges reveals profit per run.
If conversion is poor:
- Lower the price in $1–2 steps
- Shorten the input form
- Improve hero images
- Try a different Flow — simpler or more complex, depending on audience feedback

9. Checklist before going live

Tested end-to-end with real datasets
Title and description are concise
Preview images uploaded and assigned
Run price covers at least 2× infra cost
UI colors readable on both light/dark
Zipper step present (if results include multiple files)
Payout method set (Wallet or Connect)