
On this page
Every software company is asked for a roadmap. Most of them produce one, with quarters and feature names, and then quietly miss it.
We would rather not do that. A missed date is worse than no date, because someone planned around it.
So this is not a roadmap. It is a description of how we choose work, and the themes that keep appearing.
How we decide
Three filters, in order:
- Does it remove a step someone does every day? A feature that saves a click on a task done fifty times a week beats a feature that impresses in a demo.
- Does it work for a five-person team? If it needs an administrator, a consultant, or a two-week rollout, it is probably not for us yet.
- Can we explain it in one sentence? If the explanation needs a diagram, the design is not finished.
Anything that fails all three waits.
Theme one: fewer places to look
The most common complaint about running a service business is not a missing feature. It is having four places to check: the phone, the inbox, the diary, and the notebook.
Most of our work goes into collapsing those into one view, with the history attached. It is not exciting to demo. It is the thing people thank us for.
Theme two: messages that get a reply
Sending a message is easy. Getting an answer is the hard part.
That means two buttons instead of a paragraph, a deadline instead of “let us know”, and a reply that lands somewhere a person will see. Small design decisions, large effect on whether a reminder actually protects an appointment.
Theme three: reporting that fits on a page
Dashboards are easy to add and hard to use. A page with forty numbers gets opened once.
We keep coming back to three questions: are we full, who is not coming back, and where is the desk losing time. Anything that does not help answer one of those is a setting, not a report.
What we are not building
Worth being explicit, because these requests come up:
- A full accounting system. We send payment links and record payments. We are not replacing your bookkeeper.
- A website builder. Your site is your site.
- An all-purpose project manager. If you need one, use one. We would rather do the front desk well.
- Anything that requires a dedicated administrator. Small teams do not have one.
How changes get announced
When something ships, it gets a short post: what changed, who it is for, and how to turn it on. No countdown, no teaser campaign.
If a change affects how existing customers work, there is a note in the app and a line in the post explaining what to do. Nobody should discover a change by accident on a busy Monday.
What we get wrong
Some things take longer than we expect. Some things we build and then remove because nobody used them.
When that happens, we say so in the post rather than quietly deleting the announcement. A product that only ever moves forward is either very young or not being honest.
How to influence it
Tell us the step you hate. Not the feature you want — the step.
“Every Friday I copy appointments into a spreadsheet for the accountant” is a problem we can work with. “Better reporting” is not.
The requests that get built are usually the ones described as a specific, repeated annoyance, with the workaround spelled out.
Where BittaFlow fits
BittaFlow is the product, and this is how it grows: one removed step at a time, for teams small enough that nobody has time to learn a system.
No dates. When it ships, you will read about it here.


