monetisation flows
Most early SaaS experiments fit one of three paths. Choose one, paste the matching instruction into Claude, Codex, Cursor, or Windsurf, and keep the payment, email, and setup rails aligned.
One paid plan, direct feedback, and the fastest path to proving someone will pay.
Best for: New builders validating a narrow B2B workflow with a small number of early customers.
one paid plan
manual onboarding is acceptable
clear beta expectations
no free tier or plan matrix
agent instruction
Use the paid beta monetisation flow. Keep one paid plan, clear buyer expectations, manual onboarding copy, and a short feedback loop. Do not add a free tier or complex plan matrix.
A useful free tier with one paid upgrade when the user hits a natural limit.
Best for: Products where users need to try the workflow before trusting the paid plan.
one free tier
one paid tier
visible limits
upgrade prompt at the limit
agent instruction
Use the freemium with upgrade monetisation flow. Keep one free tier and one paid tier. Make limits visible in the UI and preserve the existing usage-limit and verification logic.
One-time founder access for early cash, launch momentum, or a small proof-of-demand test.
Best for: Simple early launches where the buyer wants payment proof without subscription complexity.
one one-time price
founder access language
clear support boundaries
no unlimited custom work promise
agent instruction
Use the lifetime deal monetisation flow. Keep one one-time price, clear founder access copy, and explicit support/update boundaries. Do not imply managed hosting or unlimited custom work.
handoff sequence
Pick one launch flow.
Copy the flow instruction.
Paste it into the handoff prompt.
Run setup checks and verify.