iter0 templates
Put the product on the first screen. Say who it is for and what job it does, then show a piece of it working beside the headline. The SaaS templates below do this with a booking preview, a team workspace or an analytics window. Open the one closest to your product and replace every word and image with your own.
Work down the page in this order. Each section comes with the question a visitor is asking when they reach it and the templates that already answer it. A section you cannot fill with something true comes out.
Step 1
The buyer asks: What is this, and is it for a team like mine?
Say who the product is for and what job it does in the headline, then put a working piece of the product beside it. Scheduling SaaS Website opens on a booking preview with a date and a time to pick. SaaS Workspace Landing Page opens on a workspace with notes, procedures and decisions in one view.
See it in the templates
Step 2
The buyer asks: Does it cover what my team does every week?
HR Software Website groups People, Lifecycle, Payroll, Devices + apps, Expenses + spend and Reporting under one workspace, so six modules read as one product. Fintech SaaS Landing Page names its modules by outcome instead: see live cash across every entity, flag payment risk before funds move. Label yours the way a customer would on a call.
See it in the templates
Step 3
The buyer asks: What happens when two teams touch the same thing?
A feature list cannot show modules handing work to each other. A worked example can. HR Software Website follows one role change through People, IT and Finance. Product Analytics Website follows one signal from a funnel to a session to a release decision. SaaS Workspace Landing Page runs short stories about a weekly review, a decision trail and a handoff. Pick an example your best customer would recognise from their own week.
See it in the templates
Step 4
The buyer asks: Who can see and change what?
Write this section so your buyer can forward it to a manager or an IT lead. HR Software Website shows three levels, Can access, Can view and Can request. Cybersecurity Software Website pairs each access policy with the person and the device. Product Analytics Website gives the data path and the warehouse export a section. Use the permission names your product uses.
See it in the templates
Step 5
The buyer asks: Will it work with what we already run, and who sets it up?
Answer this on the page, so nobody has to book a demo to find out. Fintech SaaS Landing Page lays out three routes: build without heavy lifting, use a connected partner, or build your own control layer. Scheduling SaaS Website gives calendar connections their own section. List the integrations that exist today and nothing else.
See it in the templates
Step 6
The buyer asks: What does it cost, what is the catch and what do I do now?
Close with the answers a buyer would otherwise email you for, then give one action sized to the product. A product people can try alone ends on a trial or a sample. A product sold to a finance team ends on a demo. Cybersecurity Software Website puts plans and a security FAQ ahead of its closing button. Scheduling SaaS Website ends on Create a booking page. Fintech SaaS Landing Page ends on a demo request.
See it in the templates
Choose by what your buyer needs to see first. The closer a template's first two screens are to yours, the less you rewrite.
SaaS
Fintech
HR Tech
Security
SaaS
SaaS
SaaS
No. Keep a section only if you can fill it with something true. A plans section needs real plans, and a permissions panel needs your own permission names. Delete the rest, or pick a template that does not have them.
Use Scheduling SaaS Website or SaaS Workspace Landing Page. Each ends on a single action that you can point at a trial or a waitlist. Say what works today in the hero and leave plans out until you have them.
Previewing a template costs nothing. Building a page from it uses one credit, the same as any page build. The Free plan includes 3 credits a month, Hobby is $5 for 15 and Pro is $25 for 100.
Keep exploring
Pages that show what the AI does and who can stop it.
Pages that put the quickstart and the first deploy up front.
How to test a template against what your buyer needs to decide.