SAAS (SaaS)

SaaS teams publish microcopy everywhere: onboarding, emails, changelogs, and UI elements. Small grammar slips in those places reduce clarity and user trust.

Short rules, many before/after pairs, three-context examples (work, school, casual), and ready-to-copy rewrites you can paste into product copy or Slack.

Quick answer - the mistakes to catch first

Prioritize predictable slipups that matter most in product writing: its/it's, their/there/they're, effect/affect, apostrophes used for plurals, missing hyphens in compound modifiers, and subject-verb agreement. Most fixes are one-word swaps or a brief rewrite.

its vs it's - its = possession; it's = it is / it has.
their / there / they're - possession / place / they are.
effect (noun) vs affect (verb) - check part of speech.
Apostrophes ≠ plurals - use for possession or contractions only.
Hyphenate compound modifiers before a noun: user-friendly interface.
Match the verb to the head noun: The list of features is extensive.

Core mistakes - short rules and many fixes

Keep fixes concrete: pick the correct word, or rewrite the sentence for clarity. Below are key categories with copy-ready before/after pairs.

Possessives vs contractions: its / it's
Their / there / they're
Effect / affect and other homophones
Apostrophes for possession, not plurals
Hyphenation for compound modifiers
Subject-verb agreement when the subject is split

Wrong: The dashboard lost it's value after the update.
Right: The dashboard lost its value after the update.
Wrong: Their deploying a fix tonight.
Right: They're deploying a fix tonight.
Wrong: This change will effect user retention.
Right: This change will affect user retention.
Wrong: Please read the FAQ's before you submit.
Right: Please read the FAQs before you submit.
Wrong: We launched a user friendly onboarding flow.
Right: We launched a user-friendly onboarding flow.
Wrong: The list of features are extensive.
Right: The list of features is extensive.
Wrong: Login's broken for several users.
Right: Logins are broken for several users.
Wrong: The user's settings are saved automatically.
Right: The users' settings are saved automatically.

Hyphenation & spacing - patterns that change meaning

Hyphens join words that act together as a single adjective before a noun. Small spacing errors stand out in UI text and can change meaning.

Hyphenate adjective + noun combos that modify a following noun: real-time dashboard, customer-facing portal.
Don't hyphenate when the modifier follows the noun: the dashboard is real time.
Remove stray spaces before commas and periods; use consistent dash styles (en dash for ranges, em dash for breaks).

Wrong: We launched a realtime analytics page.
Right: We launched a real-time analytics page.
Wrong: This is a customer facing settings panel.
Right: This is a customer-facing settings panel.
Wrong: Please confirm your email , then continue.
Right: Please confirm your email, then continue.
Wrong: Support hours: 9am - 5pm
Right: Support hours: 9 a.m.-5 p.m.

Apostrophes and possessives - avoid plural errors

Apostrophes mark ownership or form contractions. They don't create plurals. In short product copy, prefer clear rewrites over awkward possessive forms.

Plural nouns: customers, APIs, CDNs - no apostrophe.
Singular possessive: user's session. Plural possessive: users' sessions.
Rewrite if a possessive sounds awkward: use "the security of customer data" instead of "customer data's security."

Wrong: Enable the users' setting to proceed.
Right: Enable the users' settings to proceed.
Wrong: We support multiple API's for integrations.
Right: We support multiple APIs for integrations.
Wrong: The companys roadmap is public.
Right: The company's roadmap is public.
Wrong: Customer's data's encryption is strong.
Right: The encryption of customer data is strong.

Subject-verb agreement - find the true subject

Ignore intervening phrases (of, including, along with) when locating the head noun. Collective nouns can be singular or plural based on whether you mean the unit or individual members.

Verb agrees with the head noun, not the nearest noun in the phrase.
When unsure, rewrite long subjects into a simple subject + verb.
Collective nouns: prefer consistency in product docs; use singular for the unit (The team is) unless you mean the members (The team are).

Wrong: The collection of feedback are available in the dashboard.
Right: The collection of feedback is available in the dashboard.
Wrong: A group of users have reported the same bug.
Right: A group of users has reported the same bug.
Wrong: The list, including several examples, were added yesterday.
Right: The list, including several examples, was added yesterday.
Wrong: The team are launching the feature next week.
Right: The team is launching the feature next week.

Effect vs affect and other homophones

Mixing homophones is common. Ask whether you need a noun (effect) or a verb (affect), and substitute a short paraphrase if you're unsure.

Effect = result (noun). Affect = influence (verb).
Also check accept vs except, then vs than, complement vs compliment - meaning matters, not sound.
Substitute "this causes" (affect) or "this result" (effect) to test the choice.

Wrong: The update had little affect on load times.
Right: The update had little effect on load times.
Wrong: We will except this change in the next release.
Right: We will accept this change in the next release.
Wrong: This setting complements the feature.
Right: This setting complements the feature.

Try your own sentence

Test the whole sentence in context. Small changes elsewhere often reveal the correct choice.

Real usage - strict places and more forgiving spots

Apply stricter rules where mistakes hurt comprehension or legal meaning. In lower-risk channels, brand voice can bend grammar - but avoid ambiguous homophones everywhere.

High-risk (be strict): buttons, confirmation modals, pricing, legal text, API docs.
Medium-risk (clarity first): release notes, knowledge-base articles, customer emails.
Low-risk (voice allowed): social posts, internal Slack - still avoid mistakes that could mislead.

Example - High-risk: Button text - "Reset password" (imperative, no contractions).
Example - Medium-risk: Release note - "We've fixed login errors; affected users may need to clear cache."
Example - Low-risk: Internal Slack - "We're on it; will update soon." (fine internally; not for customers)

Examples you can copy - work, school, and casual

Use the "Right" lines directly in documents or messages.

Work: release notes, customer emails, onboarding tips.
School: reports, essays, teacher feedback about SaaS topics.
Casual: Slack, tweets, quick internal messages.

Work - Wrong: Release notes: We fixed login issues, its now faster.
Work - Right: Release notes: We fixed login issues; it's now faster.
Work - Wrong: Email subject: They're updated our pricing tiers.
Work - Right: Email subject: We've updated our pricing tiers.
Work - Wrong: Onboarding tip: Add your team's members to the project.
Work - Right: Onboarding tip: Add team members to the project.
School - Wrong: Essay: The softwares ability to scale is impressive.
School - Right: Essay: The software's ability to scale is impressive.
School - Wrong: Report: Its results indicate a significant effect.
School - Right: Report: Its results indicate a significant effect.
School - Wrong: Feedback: The data's incomplete and needs more tests.
School - Right: Feedback: The data are incomplete and need more tests.
Casual - Wrong: Slack: Their working on the fix rn.
Casual - Right: Slack: They're working on the fix rn.
Casual - Wrong: Tweet: Login's broke for a lot of people :(
Casual - Right: Tweet: Logins are failing for many users :(
Casual - Wrong: Message: Can you send me the report's link?
Casual - Right: Message: Can you send me the report link?

Rewrite help - short templates and multiple rewrites

When a sentence has several problems, a brief rewrite is faster and safer than piecemeal edits. Use the templates below and adapt the bracketed parts.

Split long sentences: action in the first sentence, detail in the second.
Turn passive into active: "A fix was deployed" → "We deployed a fix."
Templates are below-replace bracketed sections with your specifics.

Rewrite: Before: "We are improving our security features." → After: "We've improved security by adding two-factor authentication."
Rewrite: Before: "The softwares growth was big." → After: "The software's growth was substantial and measurable."
Rewrite: Before: "Their fixing it now." → After: "They're fixing it now - we'll update the ticket when it's done."
Rewrite: Before: "A number of users is experiencing issues with login." → After: "Several users are experiencing login issues; we're investigating."
Template: [Problem summary]. [What we did]. [Impact/next step]. Example: "Login failures detected. We've deployed a patch. Affected users should retry after clearing cache."

Memory tricks, quick checklist, and similar mistakes

Quick mnemonics and a short checklist speed up edits for one-sentence pieces of copy.

ITS trick: If you can expand to "it is" or "it has," use it's; otherwise use its.
THEIR trick: their = owns; there = place; they're = they are.
60-second checklist: its/it's → their/there/they're → effect/affect → hyphenation → subject-verb agreement → apostrophes.
Also watch which vs that, unnecessary comparatives (more easier → easier), and comma placement in coordinate adjectives.

Wrong: The feature, which improves speed is live.
Right: The feature, which improves speed, is live.
Wrong: This is more easier to use than the old UI.
Right: This is easier to use than the old UI.

FAQ

How do I know when to use its or it's in release notes?

Try expanding to "it is" or "it has." If that makes sense, use it's. If not, use its. Example: "It's fixed" = "It is fixed." "The app lost its token" = possession, so its.

Should I hyphenate "product-led growth" or "product led growth"?

Hyphenate when the compound modifies a following noun: "product-led growth strategy." When the phrase follows the noun, hyphenation is optional: "the strategy is product led."

Is it okay to use contractions in customer emails?

Yes, if it matches your brand voice and you want a friendly tone. For formal notices (billing, legal, major outages), avoid contractions for clarity.

What's a fast way to check subject-verb agreement in a long sentence?

Find the head noun and read the sentence with only that noun and the verb. Remove intervening phrases mentally. If it still feels wrong, rewrite into two sentences.

Can automated tools catch hyphenation and spacing issues in SaaS copy?

Grammar tools catch many hyphenation and spacing problems but won't enforce product-specific style. Use a checker plus a short team style note (for example, "hyphenate compound modifiers before nouns") in your handbook.

A practical next step

Before you ship high-impact copy (buttons, pricing, legal), run the 60-second checklist and paste the sentence into a grammar tool for a second opinion.

Copy the 60-second checklist into your PR template or onboarding doc to reduce simple mistakes across the team.