# How do I know how my business is going without waiting for a report?

Track business performance as the work happens: ask in plain words, and see the records behind every answer instead of waiting for a report.

Published: 2026-10-11  
Canonical: https://felesh.ai/blog/how-do-i-know-how-my-business-is-going

## How to track business performance without waiting for a report

If you have ever caught yourself waiting for a report to find out how your business is going, you already know the problem. The report is late because someone had to write it up after the work was done. The fix is to let the work be written as it is done. Keeping track is then not an extra task. It is the ordinary trail of notes, promises and tasks you leave behind as you work.

When you ask three people how things stand, you often get three answers. Each one is true from where they sit, and none of them is complete. You cannot usefully compare those answers, because they were written from memory. The alternative is a trail that is already there: what happened today, who promised what, what is waiting for a yes. Then the question “how are we doing?” has somewhere to go.

That is the shift. You do not need a report, a meeting, or a mood. You need what happened written at the time, not from memory.

## Why a number you cannot trace is not worth much

A single verdict, such as “we are on track” or “we are behind”, is useful if you can follow it back to the work. Anyone can produce a number. It is harder to produce a number that still points to the notes, dates and promises it came from. If the number has no trail, it is an opinion formatted as a fact.

So ask where it came from. “What is this based on?” If the answer is “the notes from last week”, that is traceable. If the answer is “I just know”, then the figure is not worth much, no matter how confident it sounds. This is not about distrust. It is about having a conversation with the records, not with someone’s memory.

In a small business, the useful records are not complicated. They are the promises you made to customers, the promises customers made to you, the tasks waiting for your decision, and the notes written on the day something happened. When those records exist, a number can be checked. When they do not, a number is a guess.

## What to look at, in plain words

Before any dashboard, the picture you need is four questions.

What is waiting? Something is often held until a person says yes: a draft, a quote, a plan, a change. Each waiting item should have the reason it is waiting beside it. Then you can see what needs your decision, and what is stuck because no one has decided.

What is overdue? A promise has a date. If that date has passed, the promise is overdue. The list should be short and exact. It is not a judgement of anyone; it is a list of things that were promised and have not happened.

What has gone quiet? A conversation with a customer can go quiet. A piece of work can go quiet. People are not being watched; the work itself goes quiet. A customer with no new note for a while is easy to see, and worth your attention before anyone has to ask.

What was promised? A business carries a lot of promises. You promised a customer a date. A customer promised you an answer. A colleague promised to hand something over. When promises are written down and dated, you know what the work is actually carrying.

You need the list, looked at honestly, on a regular basis.

## How this goes on Felesh

Felesh is built around this idea: the work is done there, so what happened is already there.

1. Do the work on Felesh. Add the customers and companies you work with, as an import you review. Then work as you normally would. After a call, a visit, or a decision, say one typed sentence: “what happened.” Felesh turns that sentence into a note and dated promises, drafted for your yes, each with its reason next to it, and adds any task directly. A customer message Felesh cannot answer goes to Needs you with the reason shown.

2. Ask in your own words. You do not need to build a chart. Type “what did I promise this customer?” or “what is still open with them?” and Felesh answers from your own records. The answer is not a separate report. It comes from the work itself.

3. Read the records behind the answer. Open the number or answer and it leads to the notes, dates and promises it came from. If something is overdue, you can open that promise and see what was promised, to whom, and when.

4. Set a routine once. If you want a morning or weekly summary, you build a routine that runs on a schedule, for example “each morning, find what is overdue and what has gone quiet and tell me”. It runs only because you set it up; nothing is sent by default.

This works because Felesh knows what is done on Felesh: the notes, tasks, promises and queues. It also knows the contacts and companies you imported, and anything you chose to tell it. It does not read your mail or your drives, and it does not connect to other tools. Its picture is made of work done on it, not a guess.

## If you prefer numbers

Dashboards open on your own numbers from the first day. You can start from a template instead of a blank page. Pick a period and switch on compare to see it against the previous period. Click any number to open the records behind it.

## What it will not do

Felesh does not run the business. It does not decide for you. If a task is overdue, you still have to choose what to do about it. If a customer has gone quiet, you still have to make the call. Felesh keeps the business known, and it does the work you approve.

Nothing is surfaced that you did not set up. If you never build a routine, Felesh simply holds the work and answers when you ask.

It will also not watch people. A conversation can be quiet and a promise can be late, but that is about the work, not about a person.

If you want to see how this works, see asking your work anything.