Blogs / What Should My Form's Submit Button Say?

What Should My Form's Submit Button Say?

Nov 20, 20267 min read
Pulkit Khurana

Founder, SproutMe

A line drawing of a door swung open, illustrating how to write submit button text that states what the visitor gets.

Your landing page has a sharp headline, a short form, and a button at the bottom that still says "Submit", because that's what the form builder shipped with. It's the last thing a visitor reads before handing over their details, and it tells them nothing about what they get in return.

Your submit button should say what the visitor gets, in their own terms: a verb plus an object, such as "Get my quote" or "Book my demo". "Submit" describes what the system does, not what the person wants. Match the label to the page's promise, and say only what actually happens after the click.

Why doesn't "Submit" work?

"Submit" describes what your system does with the data. It says nothing about what the visitor is doing, or why. Every form on the internet submits, so the word carries no information. It's the interface equivalent of a door with a sign that says "Door".

That matters more on a form than anywhere else on the page. The submit button sits at the point of highest friction. The visitor has typed a name and a work email and is now deciding whether the offer is worth handing them over. The button is your last chance to restate that offer. "Submit" spends that moment on a generic verb, and the verb quietly frames the exchange as compliance rather than a choice the visitor is making for their own benefit.

Be clear about the evidence, though. Most published button-copy wins come from vendors and agencies, and they rarely isolate the button. The headline or the form length usually changed in the same test. The case for replacing "Submit" rests on clarity, which is reason enough. It does not rest on a guaranteed uplift.

What should the button say instead?

A good label is a verb plus the thing the visitor gets, written so it completes the sentence "I want to…". Two to five words is usually enough.

Start with a specific verb

"Get", "Book", "Download", "Start", "Send" and "Create" each tell the visitor what kind of exchange this is. "Book" means a calendar slot. "Download" means something immediate. "Send" means a message to a person.

Avoid verbs that describe the mechanics, such as "Submit", "Enter", "Click here" and "Go". They describe the interface rather than the outcome.

Name what they get

The noun does the persuading. "Get my quote" beats "Get started" because the visitor knows exactly what will land in their inbox. Take the noun from the page's headline so the promise carries through. If the headline offers a pricing breakdown, the button should not suddenly offer "a consultation".

| Form | Weak label | Better label | | ------------- | ---------- | ------------------------ | | Demo request | Submit | Book my demo | | Quote request | Submit | Get my quote | | Gated guide | Submit | Download the guide | | Contact form | Send | Send my question | | Free trial | Sign up | Start my free trial | | Newsletter | Subscribe | Send me the weekly brief |

Promise only what actually happens

The label is a contract. Say the button reads "Book my demo", but the visitor actually gets an email from a sales rep two days later asking for a time. You've broken the contract at the first touchpoint, and "Request a demo" was the honest version. The same applies to "free": use it only if no card is required and nothing is attached.

A single line of microcopy under the button can carry what the label can't. That might be your real response time, or a note that you won't add them to a newsletter. Then the page they land on has to finish the job. What your thank-you page says should confirm exactly what the button promised and nothing it didn't.

When is the answer different?

The verb-plus-object rule covers most lead-generation forms, but three situations change it.

Multi-step forms. Buttons on the intermediate steps should orient the visitor, not persuade them. "Next: company details" tells people how far they've got. Save the outcome label for the final step, where the commitment actually happens.

Payments and checkout. Here clarity beats persuasion, because the visitor wants to know that money is about to move. "Place order" or a button that states the amount does better than anything clever. At checkout, surprise is the enemy.

Formal submissions. For job applications, insurance claims or regulatory filings, the visitor really is submitting something and expects the word. "Submit application" is accurate and reassuring there. Dressing it up as "Launch my career" reads as tone-deaf.

There is also a limit to what the label can do. The button can't rescue a form that asks for too much. If people abandon halfway down the form, the label isn't the problem. How many fields your form asks for is the bigger lever, so fix that first.

How do you test submit button text?

Change the button and only the button. If you rewrite the headline in the same test, you won't know which change moved the number. That's the flaw in most of the case studies you'll find on this subject.

Pick two or three labels that differ in a meaningful way, such as a different noun or a different promise. Don't test "Get my quote" against "Get your quote" unless voice is the specific question you want answered. Run the variants on the same traffic until each one has enough conversions to separate signal from noise. On a low-volume B2B form that can take weeks. That's a reason to test fewer variants, not to stop early.

Then judge the winner on what happens after the form. A more generous-sounding label like "Get my free audit" can raise form fills and lower lead quality. It attracts people who wanted the freebie, not the conversation.

Compare variants on qualified leads or pipeline, not on submissions alone. When your ad, analytics and CRM data sit in separate tools, that comparison means joining them by hand, and it rarely gets done. SproutMe Companion reads spend, performance and HubSpot pipeline from one data lake, so you can ask whether a label change lifted pipeline as a plain question.

Conclusion

"Submit" is a default, not a decision. Replace it with a specific verb and the thing the visitor actually gets, and take the noun from your headline so the promise holds from top to bottom. Keep the label honest about what happens next. Reserve plain wording for checkout and formal submissions, where clarity is the point. When you test, change one thing at a time and judge the result on lead quality, not raw form fills.

See how Companion answers whether a landing page change lifted pipeline, not just submissions, from your live spend and CRM data.

Frequently Asked Questions

Two to five words covers almost every case. That's long enough for a verb and a clear object, such as "Download the guide", and short enough to fit on a mobile screen without wrapping onto a second line. If the label needs more explanation than that, put a short line of microcopy beneath the button. Don't stretch the button itself into a sentence.

First person ("Get my quote") reads as the visitor speaking, which completes the "I want to…" sentence naturally and adds a sense of ownership. Second person ("Get your quote") reads as the brand speaking. Neither wins everywhere. Pick one, keep it consistent across the form and page, and test it only after you've settled the verb and the noun.

Colour matters mainly for visibility. The button has to contrast clearly with the page so it reads as the main action. Beyond that, no colour is reliably better on its own, and colour test results usually reflect contrast on one particular page. Fix the wording first, because a highly visible button that says "Submit" still tells the visitor nothing.

Grow smarter with AI marketing tips

Join our newsletter to get practical insights, automation ideas, and performance tips straight to your inbox.

Get a complimentary audit to uncover AI opportunities hidden in your data.

Put these strategies to work