Why we write plainly

Most software writing is designed to sound impressive. We would rather be understood on the first read, even if that means shorter posts and fewer adjectives.

The BittaFlow team

3 min read

On this page
  1. The problem with impressive writing
  2. The rules we try to follow
  3. Words we avoid
  4. The test we use
  5. Why this matters for a product blog
  6. What plain writing is not
  7. Where we still fail
  8. The bylines
  9. Where BittaFlow fits

Open any software blog and you will find the same paragraph, rewritten by a different company. Solutions that empower teams. Seamless workflows. Unlock potential.

None of it is false. None of it is useful either.

The problem with impressive writing

Impressive writing is written for the writer. It signals that the company is serious and the product is advanced.

Plain writing is written for the reader. It assumes they are tired, busy, and looking for one specific answer.

We are on the reader’s side, mostly because our readers are people running a dental practice at 6pm, not people evaluating software for a living.

The rules we try to follow

  • One idea per paragraph. If a paragraph has two, split it.
  • Short sentences when the point matters. Long sentences when the detail needs nuance.
  • Name the thing. “Reminder message”, not “engagement touchpoint”.
  • Use the customer’s words. If they say “no-shows”, we say “no-shows”.
  • Cut the warm-up. The first sentence should already be doing work.
  • Say what it costs, or link to the page that does. Vague pricing wastes everyone’s afternoon.

Words we avoid

Not because they are forbidden, but because they usually hide a missing thought:

  • Seamless
  • Leverage
  • Robust
  • Solution
  • Empower
  • Best-in-class
  • Game-changer

If a sentence needs one of these to work, the sentence probably does not have a point.

The test we use

Read the paragraph out loud. If you would not say it to a customer across a desk, rewrite it.

This catches most of the problem. Nobody says “we leverage automation to streamline your front desk” while standing in a clinic corridor.

Why this matters for a product blog

Two reasons.

Trust. A business that writes clearly about a no-show policy is probably clear about its invoices too. The writing is a sample of how the company thinks.

Usefulness. A post that explains one small process, with the wording you can copy, gets read twice and bookmarked. A post about transformation gets skimmed and forgotten.

What plain writing is not

It is not dumbing anything down. Some of these posts explain migrations, triage, and consent rules. The ideas are not simple; the sentences are.

It is also not short for the sake of it. A post needs enough detail to be usable. Cutting the detail to hit a word count is just a different kind of laziness.

Where we still fail

Some posts are longer than they need to be. Some repeat a point because it felt important. Some have a heading that promises more than the section delivers.

We fix them when we notice. If you spot one, tell us which post and which paragraph, and we will rewrite it.

The bylines

Four names appear on this blog. Each covers a different area, which keeps the voice consistent within a topic: one person on calls and bookings, one on CRM, one on industry playbooks, one on comparisons and the company posts.

The point is not to invent personalities. It is so you know whose writing you are reading when a topic is unfamiliar.

Where BittaFlow fits

BittaFlow is the product, and this is how we write about it: what the thing does, who it is for, what it does not do, and what it costs.

If a sentence here needs a second read to make sense, that is our fault. Tell us and we will fix it.

Useful? Send it to someone who runs the phones.