The people behind the blog

Four bylines, four beats. Here is who writes what, why we split it that way, and how a post gets from a rough note to something you can use.

The BittaFlow team

3 min read

On this page
  1. The four beats
  2. Why the beats are narrow
  3. How a post gets written
  4. What we do not do
  5. Why the names matter
  6. Tell us what is missing
  7. Where BittaFlow fits

You will see four names on this blog. That is deliberate.

One person writing about everything tends to sound the same everywhere, and readers can tell. Splitting the topics keeps each area consistent and makes it obvious who to blame when a post is wrong.

The four beats

Maya Patel — calls, bookings, and the front desk. Missed calls, text-backs, reminders, deposits, no-show policies. The practical stuff that happens between a phone ringing and a customer arriving.

Daniel Okafor — CRM and automation. Contact records, fields, follow-up schedules, migrations. The unglamorous work of keeping information in one place and making it act on time.

James Whitfield — industry playbooks. Dentistry, clinics, real estate, legal, home services, salons, hospitality. Each post starts from how that trade actually runs its day, not from a generic template with the nouns swapped.

Priya Sharma — comparisons, product notes, and company posts. Buying guides, what different tools do and do not do, and the occasional post about how we work.

Why the beats are narrow

A narrow beat means fewer posts and better ones. It also means the person writing about dental recalls has read about dental recalls for a while, rather than being handed the topic on a Tuesday.

It is not a claim of expertise in the clinical sense. These are operational guides, written for the person running the desk, not for the clinician making a diagnosis.

How a post gets written

The process is boring, which is the point:

  1. A question that keeps coming back. From support, from a sales call, from a conversation with a practice manager.
  2. A rough note. The answer, in bullet points, before any writing.
  3. A draft with a specific scene. Not “businesses often struggle with no-shows”, but a Tuesday evening and a phone that nobody answered.
  4. A read-through for claims. Every number removed unless it is arithmetic the reader can check. Every compliance claim removed unless it is a link to the regulator.
  5. A final check on the useful part. Can a reader copy something from this? A script, a checklist, a sequence.

If step five fails, the post does not go out.

What we do not do

  • No invented statistics. If we do not have a number, we do not make one up to sound authoritative.
  • No fake case studies. No “one clinic increased bookings by 40%”. If we cannot show it, we do not say it.
  • No stock photos of people pretending to be customers. The covers are simple graphics for that reason.
  • No ghostwritten thought leadership. If a post is dull, that is our problem, not a reason to add adjectives.

Why the names matter

A byline is a promise that someone stands behind the words. It also makes corrections possible: if a post about legal intake is wrong, you know which beat it came from.

The four names are the ones who write. They are not a directory of the whole company, and this page is not a team page. It is a note about who writes what.

Tell us what is missing

The best posts on this blog started as a question someone sent us. If there is a process you cannot find a decent guide for, send it in. If it fits a beat, it gets written.

Where BittaFlow fits

BittaFlow is the product these posts are about, and the writing follows the same rule as the software: solve one real problem, explain it plainly, and leave the rest alone.

Four beats, one standard. That is the whole arrangement.

Useful? Send it to someone who runs the phones.