Insights

How to Build a Brand Voice That Sounds Like You

Generic website copy isn’t fixed by a warmer tone. Before-and-after examples of building a voice from the decision your buyer has to make.

By Angelica Sirotin

Brand Voice

5 min read

How to Build a Brand Voice That Sounds Like You — Sirotin Ventures Insights

If a website sounds generic, replacing the most obvious phrases may only get you so far. “Seamless collaboration” can become “easier teamwork” without telling the visitor much more about the product. Before deciding how warm or conversational the copy should sound, we’d want to understand what the reader is trying to do and what they need to know about the offer.

Those answers give the writer something specific to work with. They also provide language that belongs to the business, rather than a list of adjectives that could describe almost any company.

To show how that affects the writing, we’ll use a fictional company selling software for managing service requests. The examples below are illustrative copy, not client quotations or measured results. Its prospective customer is a department manager considering whether to replace a shared email inbox with the software.

Explain the work before choosing the tone

Imagine that the manager reaches a benefits section promising “seamless collaboration,” “complete visibility,” “flexible control” and “improved performance,” followed by a “Learn more” button. The claims sound positive, but the visitor has to work out what each means for the requests their team handles.

We’d give that section a more specific heading: “Know which requests need your team’s attention.” Beneath it, the copy could explain what the manager would see and do:

  • One queue for incoming requests shows unanswered requests and their owners.

  • Assignment tools route a request to the team that handles it, without forwarding an email.

  • Administrator-controlled access determines which teams can view and assign requests.

  • Status information shows which open requests are in progress and which need more information.

A button reading “See the queue in action” now has a clear purpose. The manager has enough information to decide whether the demonstration might answer a question they already have. The language is more recognizable because it describes their work, which also makes it easier for the company to sound like it understands the customer.

Follow the question when another reader joins

If the manager brings an IT lead into the evaluation, that person is likely to ask about access and setup. Repeating the same benefits in more technical language would leave those questions open, so we’d give the IT reader an explanation that addresses them directly:

“Choose which teams can view and assign requests. Requests from your customer portal enter a shared queue, and your administrator approves each team’s access before launch.”

A link to “Review setup requirements” would follow naturally. The wording belongs to the same company, but it helps this reader with a different part of the decision. It also identifies the administrator, which raises a responsibility the company needs to explain properly before someone buys.

That responsibility should carry into the implementation section. “Get started with ease. We support you throughout implementation” offers reassurance without saying what either side will do. A more useful explanation might read:

“What we handle before your team starts. We configure the request queue and test the portal connection. Your administrator approves user access before launch.”

We would confirm that division of work before publishing it. If the customer must configure permissions as well as approve them, the copy needs to say so. Otherwise a friendly promise can leave the buyer and delivery team expecting different things, and the wording will have created a problem rather than clarified one.

Separate a capability from a promised result

The same care is needed when a page moves from describing what the product does to claiming what it achieves. A manager with unanswered requests would welcome faster service, but “Our platform cuts response times from day one” needs evidence beyond the existence of a queue.

Without that evidence, we’d explain the capability the buyer can assess: “Find the requests still awaiting a reply. The queue shows which requests need a response and who owns them, so you can reassign a request when its owner is unavailable.” A demonstration can then show how assignment works.

A response-time claim would need records and a defined measure, including when the clock starts and stops. Workload and staffing may affect the comparison, and findings from one team or a limited trial should retain that scope. Making the sentence sound confident cannot resolve those questions.

Interactive figure: who is reading this page?

To establish what belongs on the page, we speak with the people who sell and deliver the offer, then compare their answers with the existing copy. They can explain where customers hesitate and which promises require more detail. Their language also gives us a starting point for the voice, because it reflects how the business discusses its own work.

Let the style change without changing the promise

Once those facts are settled, there is still plenty of room for different voices. A company writing for procurement teams might use “What we handle before your team starts,” followed by the implementation explanation above. Another might prefer a more conversational heading: “Two jobs for us, one for you.”

Its copy could read: “We set up your request queue and test the portal connection. Before launch, your administrator signs off on who gets access.” The wording is less formal, but the responsibilities remain the same. A writer can change the rhythm without quietly giving the supplier more work or suggesting the customer has nothing to do.

That distinction belongs in the voice guidance. Alongside examples of the preferred style, we’d explain which facts each version must preserve and why the manager and IT lead need different answers. Otherwise a future rewrite might combine the pages and remove the very detail that made them useful.

Interactive figure: same facts, different voice

Executives need individual treatment too. For a global payments firm, we produced more than 25 articles for five C-suite executives, writing in each person’s voice. A shared company context does not mean every executive should sound identical; their way of explaining an issue matters as much as the terminology they use.

Check whether the reader can follow the explanation

Before finishing a draft, we read it aloud as an explanation to the client and then as a visitor deciding whether to keep reading. That makes it easier to notice a missing connection, an unclear responsibility or a paragraph that repeats what the reader already knows. Sometimes the fix is to join two thoughts and explain how they relate, rather than shorten both into separate statements.

The result should give the business language it can keep using, with enough guidance that the next page feels like it comes from the same place. That takes more than removing a few AI phrases, but it also gives your team something more useful than an instruction to “sound authentic.”

If your website could belong to almost any company in your market, send a page to angelica@sirotinventures.com and tell us who it needs to reach. At Sirotin Ventures, we work with your team to clarify the offer, rewrite the explanation and develop voice guidance that carries those decisions into the rest of your materials.

Angelica Sirotin

Written by

Angelica Sirotin

CEO, Sirotin Ventures