What should the CTA button say on a SaaS homepage?

It should name the first thing the visitor will do inside the product, as a verb plus an object, such as Summarise a sales call or Tag 200 survey replies. The screen after the click should do exactly that. Generic labels like Get Started leave the visitor guessing what the click will cost her.

Is Get Started a bad CTA for a SaaS website?

It is not wrong, but it says almost nothing. It could lead to a form, a card, a calendar or a sales call, and visitors who cannot tell often do nothing. Replace it with the specific action your first screen performs, and keep Get Started only if your product truly has no single first action.

Should CTA button text use my or your?

First person, like Save my spot, often reads more naturally on a button, but it is a minor choice. Naming the object matters far more than the pronoun. Analyse my file and Analyse your file are both clearer than Get Started.

How long should SaaS CTA button text be?

Two to five words covers most good buttons. That is enough room for a verb and an object, and short enough to fit on a phone without wrapping. Put anything longer, such as whether a card is needed, in a small line under the button instead.

What should a book a demo button say instead?

Say what the call is about and who she will meet, such as Walk through it on your files or Plan your rollout with an engineer. Add the length in the line underneath. A demo button that names the topic filters out people who only wanted to try the product alone.

What text should go under a CTA button?

One short line that states the cost of the click: what to have ready, whether a card is required, and how long until the first result. For example, Paste a Zoom link or upload an MP3. No card. It answers the questions that make visitors hesitate, without adding a slogan.

Should every CTA on my website use the same wording?

Yes, for the main action. The navigation, hero, pricing page and footer should repeat the same label so visitors learn one path. Secondary links can differ, but they should look clearly quieter than the main button.

SaaS CTA Button Text Examples: Say What Happens Next

The best SaaS CTA button text names the first thing a person will do inside your product, as a verb plus the thing they bring: Measure my first floor plan, Summarise a sales call, Tag 200 survey replies. Get Started, Sign up and Try it free only promise that something will happen. Write the button so it says what, and make the screen after the click the one the button named.

This matters more for a small AI team than it looks. You know exactly what happens after the click, because you built it. A stranger on your homepage does not. A button that hides the next step asks her to accept a cost she cannot see. Most visitors who hesitate are not unsure about your product. They are unsure about the next five minutes.

Get Started, then six screens before the product

Picture an AI tool, used here as an example, for small renovation contractors. An estimator uploads a floor plan PDF and the tool counts the materials: square metres of drywall, metres of skirting board, the number of doors and sockets. The trade calls this a takeoff. Done by hand, it eats an evening per bid.

The hero says Win more bids with AI. Under it sits one orange button: Get Started. Press it and the visitor meets, in order, a Create your login form, a screen with six boxes for an emailed code, an About your business page asking for company name and number of crews, a grid of chips titled Which trades do you cover, and a Connect QuickBooks screen with Skip in tiny grey text. Then comes the dashboard. Its main panel reads No estimates yet. A small button in the top right corner says New estimate.

That is six screens between the promise and the product, and none of them mention a floor plan. He arrived with the PDF sitting in his downloads folder. The first place he can use it is a button called New estimate, on the seventh screen, which he has to find on his own.

Measure my first floor plan, then the upload box

Now the rewrite. The button reads Measure my first floor plan. Under it, in small grey text: Upload a PDF plan. Material counts before you make an account.

Press it and the next screen is an upload box with one heading, Drop your floor plan here. Below it is a link: No plan handy? Try a sample two-bedroom flat. The counts fill in room by room, and each wall the tool measured lights up on the plan so he can check it. The account form shows up only when he presses Export to spreadsheet, and it asks for an email and nothing else. Crews, trades and QuickBooks move to a settings page nobody is forced through.

The button gained a few words. The real change is that the button and the first screen now say the same thing. He pressed Measure my first floor plan and the product asked for a floor plan. Nothing on the way surprised him, so nothing on the way gave him a reason to stop.

Why Get Started makes visitors hesitate

A visitor hovering over your button is doing a quick sum. What will this cost me, and what do I get back? Get Started answers neither half. It could mean a form, a card, a calendar or a call from sales. People who cannot see the cost guess the worst one, and close the tab.

Most CTA advice works on the wrong layer. Add urgency words like now and today. Try first person. Test the colour. Keep it short. Those are small adjustments to a button that still does not say what happens. A green Get Started Now is exactly as vague as a blue Get Started.

So here is the claim, and plenty of people will disagree with it: write the button last. Design the first screen after the click, then name the button after that screen. If the screen cannot keep the button's promise, change the screen, not the words. A specific button that leads into a six-step signup is worse than a vague one, because now it has broken a promise in the first minute.

The reason founders miss this is simple. The founder reads Get Started and fills in everything that follows, because he knows his product and nobody else does. The stranger has only the two words. Which button leads, a trial or a demo, is a separate decision, set out in our post on sign up vs book a demo. This post assumes you have picked one and are now writing the words on it.

Ten before and after CTA button text examples

Every pair below is an illustration, not a real company. The first label is the generic version. The second names an action and an object, and assumes the first screen does exactly that.

Get Started becomes Measure my first floor plan. For the takeoff tool above. The first screen is the upload box.
Start free trial becomes Summarise a sales call free. For a call notes tool. The first screen asks for a recording or a Zoom link.
Try it free becomes Tag 200 survey replies free. For a research tool. The number tells her the free part is real and how big it is.
Sign up becomes Connect my bank feed. For a bookkeeping assistant whose first useful output needs real transactions.
Create account becomes Save my takeoff. For the moment after the first result, when an account finally has a reason to exist.
Request a demo becomes Walk through it on your files. For a demo-led product. It says the call is about her work, not a slide deck.
Book a call becomes Plan your rollout with an engineer. For a call that is really setup help. Say who she will meet.
Learn more becomes See a finished episode page. For a podcast tool's quiet second link. Show the output, not a features page.
Join the waitlist becomes Save my spot in the April beta. A date turns a waitlist into a plan instead of a void.
Submit becomes Send me the sample report. For a lead form. The button repeats what she asked for.

The pattern under all ten is the same. The verb comes first. The object is something she already has or clearly wants. A number appears when the free part has a limit. None of them could sit on another product's homepage unchanged.

The grey line under the button

The button names the action. A short line under it names the cost. Only three things belong in that line: what she needs to have ready, whether a card is required, and how long until the first result. A few examples that match the pairs above:

Under Measure my first floor plan: Upload a PDF plan. Material counts before you make an account.
Under Summarise a sales call free: Paste a Zoom link or upload an MP3. No card.
Under Walk through it on your files: A 20-minute call with an engineer, not a sales pitch.

Keep it to one line on a phone, never a slogan. If a card really is needed, say so. A surprise on the next screen costs more trust than a plain warning before it.

What a vague button costs before the next raise

Picture the founder of the takeoff tool on a Monday. He reads out signups in standup, and they are up after a paid campaign. He has tested an orange button against a blue one, and Get Started against Start free trial. He has not pressed his own button on a phone since the week the site went live. The number that matters, users who export a finished takeoff, has not moved.

Every one of those signups was paid for, in ad spend or in his own hours on LinkedIn. Product-led benchmarks, measured on SaaS companies, put activation at 20 to 40 percent for most products. On the same benchmarks, a ten point improvement in activation typically drives a 15 to 25 percent increase in free-to-paid conversion. A button that sends people into six screens of setup spends that budget on visitors who quit at screen three.

An AI product has less room for that waste. AI product builders average around 52 percent gross margin, against 70 to 80 percent for traditional software, because inference sits in the cost of goods. The visitors who do get through and run a confused first try cost tokens as well as ad spend.

A public launch puts the same pressure on the button. When we designed the site for Chariot, a speech AI lab whose Chariot-1 TTS model was opening to the public for the first time, the main action on the page is Try Chariot TTS. It sits in the top navigation and again under the opening line. Before anyone presses it, the page plays a You write and Chariot speaks pair, a line of text and the voice reading it back, so the visitor has heard the output the button leads to.

Rewrite your main CTA button this week

Monday: press your own main button on a phone. Count the screens until the first useful output and write down the heading of each one.
Monday: circle the first screen where the visitor does the thing they came for, like uploading a floor plan or pasting a call link.
Tuesday: write the button as a verb plus that object, two to five words. Read it aloud next to that screen. If the screen does something else, either the button or the flow is wrong.
Wednesday: move every step that does not serve the first output to after it. Team size, trades and integrations can wait. Our SaaS onboarding design guide covers which steps usually can.
Thursday: write the grey line. What to have ready, card or no card, time to first result.
Thursday: use the same wording in the navigation, the hero, the pricing page and the footer. One action, said the same way everywhere.
Friday: start tracking two numbers for two weeks. Clicks on the button, and the share of those clicks that reach a first output the same day. If clicks rise and first outputs do not, the button now promises something the flow does not keep.

The headline above the button is its own job, and our guide to SaaS hero section design covers it.

Most of what we fix at Studio Maydit sits right here, between the words on a button and the screen it opens. We design websites that AI founders' buyers understand on first read, and for a self-serve product we start with the first run, since a sharper label pointing at the same six setup screens just relocates the drop-off. Projects run on a fixed scope of three to four weeks, in Framer, Webflow or custom code, and our website design work for AI companies shows the approach. If your hero still says Get Started and you suspect strangers read it differently than you do, book a 30-minute call with Studio Maydit.