iter0 templates
Lead with something that runs. An API gets a quickstart, a platform gets a deploy command, an editor tool gets a diff, a docs product gets code tabs and a desktop tool gets a download button. Pick the template closest to how developers meet your tool, then replace every sample with your own.
Put code, a terminal or a diff on the first two screens and keep the first action one click away. The sections after that cover production: access, logs, versions and moving over from another tool.
Step 1
The buyer asks: What is it, and how fast can I try it?
Name the job in plain words and put the first action beside it: read the quickstart, deploy a sample, download the tool. Email API Website pairs its headline with Read the quickstart. Cloud Platform Website shows a terminal with a deploy command in the hero. Developer Tool Website leads with a download button.
See it in the templates
Step 2
The buyer asks: What happens when I run it?
Show the request and what comes back. Email API Website puts a send call beside the delivery event and the log entry it creates. Developer Documentation Website shows code tabs for cURL, JavaScript and Python. AI Coding Tool Website shows the change before it is made. Use your real endpoint and a real response, and run the code exactly as printed before you publish.
See it in the templates
Step 3
The buyer asks: What are the steps, in order?
Number the steps. Cloud Platform Website runs from connecting a repository to configuring a service to reviewing the preview. AI Coding Tool Website runs from choosing context to planning to reviewing a diff. Developer Documentation Website goes from repository to preview. Use as many steps as your product needs.
See it in the templates
Step 4
The buyer asks: Who can change what, and what gets logged?
Keep the security checklist in one block. Cloud Platform Website has a Secure by default block with private networking, access controls, environment secrets, audit events, deploy approvals and service identity. AI Coding Tool Website has team boundaries and a review record. Developer Tool Website has a preferences section for what the launcher searches and what the team shares. List only the controls your product has.
See it in the templates
Step 5
The buyer asks: What happens when it breaks or changes?
Show the bad day as well as the good one. Email API Website has a section for logs and suppression. Cloud Platform Website shows release evidence: build checks, preview access and the change record side by side. Developer Documentation Website gives versions a section of their own.
See it in the templates
Step 6
The buyer asks: Can I move off what I use now?
Tell developers how to leave the tool they use now. Email API Website lays out a four-step cutover: inventory the sends, map templates and domains, reconnect events, change the default. Developer Documentation Website covers a content inventory, route and version mapping, and component conversion.
See it in the templates
Choose by where developers meet your tool: an API call, a deploy, an editor, a docs site or the desktop.
Devtools
Devtools
Devtools
Devtools
Devtools
AI Coding Tool Website also works for an AI product: its Keep change and Request revision controls are the approval step.
AI product templatesYes. Replace the sample with a call to your own API and the response it returns, then run it before you publish. The templates use placeholder keys and example domains, so swap those too.
For a tool used through code, start from Email API Website and lead with the quickstart. For a tool used through an interface, start from Developer Tool Website or AI Coding Tool Website and lead with the interface.
Next to the first action. If you have a free tier, state what it includes beside the quickstart or the deploy button.
Keep exploring
Page patterns for software that teams buy and roll out.
Pages that show what the AI does and who can stop it.
How to test a template against what your buyer needs to decide.