SaaS Homepage Teardown: How to Review Your Own

Read the page as a stranger, in a fixed order: who it is for, the promise, the proof, the next action, then the objections. Write one line for each. A line you cannot write, or one that comes out vague, goes on your fix list.

You cannot read your own page as a stranger, because you know the product. Show it to two people who have never heard of it. Give them ten seconds on the first screen of a phone, then ask what it sells and who it is for. Their answers are the first result of your teardown. If you cannot find two people, send a screenshot of the first screen to anyone outside your company and ask the same two questions.

Leave colour, type and animation out of this. They matter once the page says the right thing, and no layout fixes a page that does not.

Each pass asks one question and looks in a few places on the page. Run them in this order: name the buyer and the job before you judge the proof.

Finish this sentence from the first screen alone: this is for ___ who ___. If you have to guess, the page fails the pass.

Teams, businesses, companies and everyone are placeholders. A real answer names a role and a situation: the owner of a six-person design agency who chases late invoices. A narrow page loses the visitors who were never going to buy. A broad page loses the ones who were, because they cannot tell it is about them.

Check the first picture too. A stock photo of people smiling at a laptop tells a visitor nothing. A screen from the product with the job visible in it tells them who the page is for.

A promise says what happens when someone uses the product. Test the headline by covering your logo and pasting a rival's name in its place. If the line still reads as true, it names a category, and the visitor learns nothing that sets you apart.

Supercharge, streamline, unlock and AI-powered describe the vendor's effort. They say nothing about the visitor's result. Write the action and the outcome in words the buyer already uses: the product emails late clients so the buyer stops chasing them. Put the how in the subhead, in one sentence.

The buyer's words come from the people you have spoken to: interviews, support emails, sales calls. If you have none, go and ask before you write the headline.

Proof is anything a stranger can check in a minute. Show the product doing the job you promise, on a screen of a real task. Add a quote from a named person at a named company who agreed to it, a number with its count and its period, or a plain statement of your stage such as private beta. "Trusted by leading teams" with no names, a quote signed with a first name and a job title, a dashboard picture with no real data in it and a bare "40% faster" all ask the visitor to take your word.

Place each piece of proof beside the claim it backs. A logo bar floating under the headline proves nothing about the promise. A screen of the reminder email belongs next to the sentence that says you send it.

If you have little proof, say so in your stage line. One real screen and a plain "private beta" reads as honest. The same product behind a vague logo bar reads as invented.

Give the first screen one primary action, with a label that says what happens. Count the buttons. Two buttons of equal weight hand the visitor a decision before they know enough to make it.

"Connect your accounting package" beats "Get started", because it tells the visitor what the click does. Under the button, add one line on what comes next, such as whether it asks for a card and what the first step is.

Repeat the same action at the bottom of the page. Then open the page on a phone and check that the button sits on the first screen.

Write the questions a sceptical buyer asks before clicking. Take them from your support inbox and your sales calls: price, who sees their data, whether it works with what they already use, what happens when it goes wrong and what it takes to leave. Then look for each answer on the page.

An objection the page leaves unanswered is a reason not to click. Start with price. If your buyer wants to try the product before talking to anyone, put the price on the page. Contact sales tells that buyer the product is not for them.

Put the answers near the action, as a short FAQ or as lines under the button.

Paidwren is a made-up SaaS tool that emails clients about unpaid invoices for design agencies with two to twenty people. It connects to one accounting package and drafts a reminder for each overdue invoice. It sends a reminder after the agency approves it, and it stops chasing an invoice once the package shows it paid. The homepage below is what a stranger sees.

A stranger leaves Paidwren knowing it has something to do with money and AI, and nothing more. The product does one clear job and the page never says it.

What works: the nav has four links and one button, so nothing competes for attention. Smart reminders is the one feature name that points at the real job.

Start with the headline, replace the vague proof and make the next step clear. These three changes cover all five passes.

The headline says what Paidwren does: it emails your clients about unpaid invoices. The subhead names the buyer and answers two questions: the agency approves each reminder, and Paidwren stops once the invoice is paid. The button says what the click does. The stage line covers the last two: Paidwren works with one accounting package, and the price is further down the page.

Pick the one competitor a buyer would open in the next tab. Run the same five passes on their page and write one line for each. Then mark two things: the pass where your page is clearer, and the pass where theirs wins. Build on the first and fix the second.

Use their page to learn what buyers in your category already expect to see, such as a working product screen near the top or a price. Leave their wording, their claims and their customers alone.

Website Second Opinion is iter0's free review tool. You paste the address of a page, add a goal such as more demo requests if you want one, and read the result. You need no account to see the review and the three designs. Free reviews have a daily limit.

iter0 reads the page you paste and searches the web for a similar site. The review has a summary, what already works, three changes to make first and the sources it checked. Three designs follow: first drafts of your homepage, built from your own words and images, side by side on a canvas.

To go further, pick design A, B or C and create an account. iter0 builds that design as an editable site in the builder. The build costs 1 credit, and the Free plan includes 3 credits a month. An AI edit costs half a credit and a manual edit is free. iter0 can publish one site at its own <name>.iter0.app address. You can also export the site.

The review suggests changes to your copy and layout and gives no score. It reviews one public page at a time, so paste the page you most want visitors to act on.

Treat it as a second reader. Compare its three changes with your five lines and act first on the ones you both found. Then watch your visitors: track your sign-up rate before and after you change the page.

These tools all start from a page address and return different things.

Pick Poper's analyzer when you want a score to track. It also checks SEO meta tags and technical performance, which the iter0 review leaves out. Pick BugSmash when you want a blunt roast of a live or staging address with no signup. Shuffle's roast also returns a redesign, so compare it with iter0's three designs before you choose.

Run two of them on the same page. Where their findings agree, fix that first.

Rewrite first. Passes one, two, four and five are about words. Pass three needs material you have to collect: real screens, named customers, real numbers. A new layout adds none of it, so gather the missing proof before you redesign. When the words are right and the layout still buries them, redesign.

When you redesign, keep the content that works. iter0 can redesign an existing site from its address. The upgrade guide covers keeping your useful content and your URLs.

Start with the five lines. If you want a second reader, paste the page into Website Second Opinion.