Business automation consulting
First the process. Then an artificial employee to run it.
Most companies do not have an automation problem. They have a process problem, and automation only makes it louder.
Consulting first, software second. The software runs on your server, not ours.
Which invoices from this week are still unpaid?
Three. Two are still inside terms. One is six days past due.
Remind the client, and put it back on my desk on Monday.
Done. Reminder sent to the client, and yours is set for Monday 09:00.
- Monday, 09:00
- wrote first
Paid on Friday evening. Nothing from last week is still open.
02 The method
Setting up business processes through artificial employees
Not a chatbot bolted onto a website. A process is written down, an owner is named, and a worker who never forgets it is put in charge.
- 01Written process
- 02Named role
- 03Working employee
- 04Human owner
Every step exists on paper before it exists in software.
03 What this is for
Work that should not be done by hand twice
If several of these are true, there is a process here worth setting up properly.
- 01
The work lives in chats
Requests arrive in four places and none of them has a status.
- 02
One person is the system
Only one employee knows how it really works. Their holiday is a company risk.
- 03
The same answers, every day
Hours a week repeating explanations, and never quite the same way twice.
- 04
Documents retyped by hand
Orders and invoices move between systems by hand, and the errors surface a month later.
- 05
Nothing moves without a reminder
Follow-ups depend on somebody remembering. What is forgotten is lost.
- 06
Growth means another salary
More volume has one known answer, and it costs three months of somebody else's time.
Fits companies with real operational routine and non-technical staff: service, retail and wholesale, clinics, logistics, small production.
04 The difference
A tool, or an employee
| A tool | An employee | |
|---|---|---|
| Belongs to | The person who opens it | The process |
| Its memory | Leaves with that person | Stays with the company |
| On Monday | Starts from nothing | Picks up where it stopped |
| Answers to | Nobody in particular | A named owner on your team |
| When unsure | Guesses, and you find out later | Stops and escalates before acting |
If the person who runs this process goes on holiday, should the knowledge of the process stay behind?
If yes, it should be an employee.
05 The employees
What an artificial employee actually is
An isolated worker running a real agent session: its own instructions, its own access, its own knowledge, and its own history with the people it works with.
What it does today
- Holds a real working conversation in Telegram, with the people you allow
- Works from your documents, rules and past decisions, kept on your side
- Uses the systems you approve, so it records results and does not only talk
- Acts on a schedule, so routine checks happen without anyone remembering
- Gains new skills over time, without rebuilding the setup
What it is not
- A replacement for your team. It takes the repeatable part, people keep the judgement.
- Free to touch money, contracts or anything irreversible. It stops and waits for a person.
- A one-off installation. An employee nobody supervises drifts away from the process.
You can pause it, restrict it or shut it down at any moment.
06 Roles
Four shapes this fits
- 01
Request intake
- Takes in
- Client messages, across your channels
- Does
- Answers what is known, classifies the rest, records it with a status, and hands the unusual case to the right person
- Human keeps
- Pricing exceptions, complaints, anything that changes an agreement
- 02
Internal reference
- Takes in
- Questions from your own staff
- Does
- Answers from your written rules and past decisions, the same way every time, and flags where the rules contradict each other
- Human keeps
- Approving what goes into the rules in the first place
- 03
Document handling
- Takes in
- Incoming orders, invoices, specifications
- Does
- Reads them, pulls out the fields that matter, checks them against what you already have, and flags what does not match
- Human keeps
- Signing, paying, and anything marked unclear
- 04
Routine follow-through
- Takes in
- A schedule and a list of open items
- Does
- Checks what has moved and what has not, chases the owner, and reports the state of things before you have to ask
- Human keeps
- Deciding what to do about the things that are stuck
Process shapes, not a catalogue. What your company needs is decided in the audit.
07 The interface
Deliberately as simple as a message
The storekeeper, the cashier, the person on reception will not learn a new system. They will use the one already open on their phone.
The engine is the same. We built a cab people can actually sit in.
Behind the chat is a full agent session with real tools and real access. A simple door, not a weaker product.
08 The platform
It runs on your machine, not on ours
The employee is not a tenant in somebody else's system. Conversations and model traffic stay on a server that belongs to you.
A sovereign node
Your own isolated node: the employee in a container, a local gateway, a local key vault, a local model proxy.
Conversations stay with you
Chat content leaves the node only to reach the model provider you are paying.
Your own model account
Your provider token, held in the vault on your box. You see the cost and can revoke it without asking us.
Supervised support
Access is agreed in writing, limited by role, and written to an audit log. Suspending the node ends it.
- 01The employee
- 02Gateway
- 03Key vault
- 04Model proxy
- 05Knowledge base
- Configuration
- Usage counters
- Encrypted snapshots
Chat content never reaches our control side
The connection runs one way. The node connects out, and we do not reach in unless you have granted it.
09 How we work
Four stages, and you can stop after the first
The first stage is deliberately separable. You end it with something useful whether or not you continue with us.
- 01
Process audit
We map how the work moves today, with the people who do it, and split it honestly into what is worth automating, what should be fixed organisationally first, and what should be left alone.
You getA written process map and a fixed-scope proposal
You can stop here - 02
Employee design
The role, written the way a job is written: responsibilities, boundaries, escalation rules, and which systems it may touch.
You getA role specification, agreed in writing
- 03
Setup and going live
We provision your node, install the employee, connect your channel and your knowledge, and run it alongside the current way of working.
You getA working employee your team is already using
- 04
Supervision and expansion
Rules change and edge cases appear. We keep it correct, review what it has been doing, and add the next process once the first is genuinely stable.
You getAn agreed support arrangement
10 Before you write to us
Where we will tell you no
Three cases where the honest answer is that you should not buy this.
When the process is broken, not slow
Automating a process nobody agrees on multiplies the disagreement. Sometimes the answer is two meetings and one written rule.
When the volume does not justify it
Four times a month, ten minutes each, should stay a person's job. We would rather lose that scope than sell it.
When the decision must be a person's
Where being wrong is expensive and hard to reverse, the decision stays human. We build the preparation around it, not the decision itself.
11 Contact
Tell us what keeps repeating
What your company does, and which piece of work is done again and again by hand. That is enough for a first conversation.
Emailadmin@fisher.tech