When to Say I and When to Say We
Voice · 9 min read ·
Founder voice and company voice both have a place. How to choose between I and we in launch copy, support replies and updates, and keep one tone.
Small words carry large signals. "I" says there is a person here who will answer for what is written. "We" says there is a group, perhaps a company, speaking as one. Neither is better. Each is right for some occasions and wrong for others, and the confusion of the two is one of the quieter ways a launch loses its voice.
This guide helps you choose between them, and keep a voice that stays consistent as the team grows.
What each pronoun says
"I" is personal. It signals ownership, accountability and warmth. It suits founder notes, personal replies and statements of opinion or decision. It can also feel small, or risky if the product will outgrow one person.
"We" is collective. It signals a team, shared effort and institutional continuity. It suits product descriptions, policy, support replies and statements about what the whole organisation does. It can also feel distant, or evasive if a single person made the call.
A third option is no pronoun: "The app syncs your notes." This is often the clearest choice for describing what the product does.
A simple test for choosing
Ask three questions.
- Who decided? If one person made the decision, say I. If the team did, say we.
- Who will act? If you personally will do the thing, say I. If it will be done by the team, say we.
- Who is accountable? If you want the reader to know whom to hold to the promise, name the person.
For example, "I will reply to every message in the first week" is a personal promise. "We offer support by email" is a statement about the service. Both are honest; they promise different things.
Where each one fits
Founder note and about page
Use I for the founder's story and reasons, with a note about "we" when describing the team. "I started this after my own tools failed me. Now a small team helps me keep it going."
Product description
Mostly no pronoun or the product's name. "Plotline keeps your shoot schedule in one place." Use "you" to address the reader. Use "we" sparingly.
Pricing, terms and policy
Use we and you, consistently, with precision. Legal and policy text benefits from the formality of a company voice. Legal terms are binding documents; take professional advice on their wording.
Support replies
Either, depending on the size of the team. In a very small team, "I" is warm and honest: "I looked into this and found..." As the team grows, "we" with a signed first name keeps warmth: "We have fixed it. Priya". A personal sign-off keeps the human feel.
Announcements and updates
Use we for what the team has done and I for the founder's own reflections. "We shipped export today. I want to thank everyone who asked for it."
Apologies and corrections
Prefer I where one person is responsible, and we where the organisation is. In both cases avoid the passive voice that hides responsibility: "mistakes were made" is not an apology. "We got this wrong. Here is what we are doing" is.
The danger of the royal "we"
A solo founder who writes "we" throughout to sound bigger risks being found out. Visitors who see "we" and then meet one person may feel misled. There is nothing wrong with being a solo founder; it is often a strength. If you are one person, say so, or use "I" and mention any help you have: "I build it, with help from a part-time designer."
Truthful descriptions of your size help your credibility. Google's guidance on helpful content asks pages to be clear about who is behind them. Honesty about the size of the team is part of that clarity.
The danger of the overly personal
The opposite error is writing "I" in places where the company is acting. A policy that says "I will not share your data" is risky if the policy is for a team of ten, because "I" suggests a personal promise that outlasts the individual's involvement. Use "we" for commitments the organisation must keep when people change roles.
Similarly, as a company grows, a founder who continues to write every reply in the first person may be implying a level of personal attention that is no longer realistic. Keep promises about personal replies to what you can deliver.
Keeping a consistent tone
Voice is not only pronouns. It is the overall feel: warm or formal, playful or serious, plain or technical. A consistent voice makes a product feel like one thing, not many.
Write a short voice guide, one page, with:
- Three adjectives for the tone: for example, warm, plain, honest.
- Pronoun rules: where to use I, we and no pronoun.
- Words we use and words we avoid. For example, "people" rather than "users", "start" rather than "onboard".
- Three sample sentences in the right voice and three in the wrong one.
- Rules for apologies and corrections.
- Rules for humour: when it is welcome and when it is not.
Share it with everyone who writes for the product, including freelancers and new hires. Plain English principles, such as using short sentences, common words and the active voice, are a good base for a guide.
Personal branding and the product
Many founders build a personal presence alongside the product. Personal branding, in the general sense, is the practice of shaping how one is perceived publicly. If your voice becomes known, the product benefits, but it also depends on you. As the team grows, you may want to share the stage, with colleagues writing, speaking and appearing, so that the product's voice does not depend on a single person.
A practical approach: keep your personal voice for your own channels and for the founder note, and let the product's channels carry the team's voice, with names attached where helpful.
A worked example
A small team of three starts with a founder who writes everything in the first person. The founder note says "I built this because my own spreadsheets drove me mad". The support replies say "I will look into it". The pricing page says "I will never charge you without notice".
When two colleagues join, replies start to go out under different names, and the pricing page's promise looks odd. The founder writes a one-page voice guide. The founder note keeps "I" for the story. Product pages drop the pronoun. Support replies use "we", signed with the responder's first name. The pricing page changes to "We will always tell you before changing a charge", reviewed by the team and checked against the terms.
Readers notice nothing except that the tone feels consistent, which is exactly the aim.
A checklist
- Decide for each page type whether it speaks as I, we or neither.
- Use "I" for personal stories, decisions and promises.
- Use "we" for team actions and organisational commitments.
- Be honest about the size of the team.
- Name the accountable person for apologies and corrections.
- Write a one-page voice guide and share it.
- Review the pages when the team changes.
Examples across a product's pages
To see how this works in practice, take one product and write the same message in three places.
On the launch page, in the founder note: "I built this because my own shoot schedules lived in six places. It is the first version, and I read every message."
In a support reply: "Thanks for telling us. We have fixed the export bug, and it should work now. If it does not, reply to this message. Priya"
In the terms and policies: "We will give you notice before we change how we charge you."
Each sentence uses a different pronoun because each has a different job. The first is a personal statement, the second is the team acting with a human sign-off and the third is a commitment the organisation must keep whoever runs it. A reader moving between the three would feel one consistent voice, not three, because the tone, plainness and honesty are the same.
Questions teams ask
Can freelancers or agencies write for us? Yes, with the voice guide and an example or two. Review their drafts the first few times, and edit for pronouns and tone as well as facts.
What about translations and variations? This site is in English only, so the voice guide can assume one language. The principles of plain, honest, accountable writing hold in any language.
Should the team's names appear in announcements? Where it helps: when a person did a piece of work, name them with their agreement. People like credit, and readers like to see real names.
What if our founder leaves? Plan for it. Keep commitments in the company voice, and make sure the founder's personal promises are ones the company is willing to honour or clearly retire.
Summary
"I" and "we" both have their place. Use "I" when one person decided, acts or is accountable, and "we" when the team does. Use neither when describing what the product does. Be honest about your size, avoid promises in "I" that the company must keep, and write a short voice guide so that the tone stays consistent as you grow. The right pronoun tells readers exactly who is speaking and who will answer.
Questions and answers
- Should a small company write in the first person singular?
- When one person is speaking for their own views or decisions, yes. When the whole team is acting, use we.
- Does using we hide who is responsible?
- It can. If accountability matters, name the person: I decided this, I will fix it.
- How do I keep the tone consistent as the team grows?
- Write a short voice guide with examples and have new people read it before they write publicly.
- Can the same page use both?
- Yes, if the shift is clear. The founder note can use I, while product descriptions use we or the product's name.