Custom solutions
We automate the circuit
that eats up your day.
Every company has processes that only work because people keep repeating the same steps. We map them, write them down as rules and put them to work on a system where everything stays on record.
It comes in where your customer already writes
The order or the enquiry arrives on the channel that person already uses, written the way people write there. There is no new form to learn.
It is checked against your rules
Prices, availability and balances come from your data and from written rules, never from an estimate made by whoever is answering.
Whatever does not fit stops
When no rule covers the case, the work stops and goes to a person with everything already assembled, not as a bare alert someone has to investigate.
When it is worth
taking this step.
You do not need an exotic problem. These are the signs that a circuit is already asking to be automated.
The process lives in someone’s head
The rules exist but are not written down, and they get applied differently depending on who is around that day.
The data is scattered
Contacts in a phone, orders in a chat, payments in a bank statement. Every question forces someone to rebuild the picture by hand.
Repetitive work crowds out the important work
Entering, cross checking, answering where something is. Tasks that need no judgement, filling the day of people who have it.
Volume grew faster than the back office
It no longer holds together by sheer effort, but it does not yet justify hiring 3 more people. That is the exact window.
Your kind of business
Your business has its own words,
its own steps and its own rules.
A kind of business is not an industry picked from a dropdown. It is a vocabulary of its own, data you always have to ask for, a sales path with its own steps, and rules whoever answers already knows by heart. The system takes all of that as configuration: the same screen changes its words, its fields and its stages depending on how the company sells.
- What things are called
- Enquiry · Customer · Product · Order · Quote
- The path of a sale
- EnquiryContactedInterestedOrder builtSold
- What is always asked for
- For the product: SKU, stock on hand, sizes, colours, brand, weight. For the enquiry: whether it is wholesale and the delivery area.
- What the agent does not do
- It does not confirm stock the catalogue does not report, and it does not offer wholesale pricing if the enquiry falls short of the minimum quantity.
- What things are called
- Enquiry · Customer · Product · Order · Quote
- The path of a sale
- EnquiryContactedMeasurements inQuotedSold
- What is always asked for
- For each opening: width, height, number of panels and how it is fitted (to the wall, to the ceiling, inside the frame). For the product: price per unit of measure, minimum billable amount, cutting waste, whether fitting is included.
- What the agent does not do
- It does not give a closed price. It gives a range, says plainly that it is indicative, and leaves the quote loaded with the measurements and the photos for a person to confirm.
- What things are called
- Enquiry · Client · Service · Matter · Proposal
- The path of a sale
- EnquiryContactedMeeting bookedProposal sentEngaged
- What is always asked for
- For the enquiry: type of matter, whether there is a real deadline and who referred it. For the service: hourly rate, estimated hours, minimum retainer term, deliverables.
- What the agent does not do
- It does not weigh in on the substance of the matter and does not estimate outcomes. It takes the enquiry, orders it, books it and hands it to the professional.
- What things are called
- Prospect · Customer · Product · Sale · Quote
- The path of a sale
- NewContactedQualifiedProposalWon
- What is always asked for
- Nothing of your own yet. The fields of your operation come out of the mapping, and from then on the system always asks for them.
- What the agent does not do
- It does not make up facts about the business. Whatever is not loaded, it hands to a person.
None of these options is an industry: they are ways of selling. One business can need 2 at once, and 2 very different industries often share the same one. That is why the system has no per-industry edition: it has a configuration, and that configuration is written from what we survey in your operation.
What gets configured,
and what gets built.
Changing words, fields and stages is enough to make the system feel like yours. It is not enough to make it do your work. A solution has 3 layers, and the top one is the one you see.
- 01
The modules
Code that already exists and gets switched on for your account: your customers with their full history across every channel, the catalogue with its prices, sales with partial payments, tasks, the memory of what has already been done. They get switched on, not written.
- 02
The configuration of your kind of business
The vocabulary, the data that always has to be asked for, the stages of the path, how a price is worked out, and what whoever answers can and cannot do. It is the layer you just saw, and it is configuration: there is no screen programmed per industry.
- 03
The processes
The concrete steps of your operation, written once and run the same way every time, with the points where a person signs before it moves on and what gets checked at each step.
If your circuit needs something the system does not have yet, it gets built. And it gets built as a module of the system, not as a patch for your account. That has 2 consequences in your favour: it can be quoted with closed scope and closed price, and the improvement later developed with another company reaches you with your subscription.
You are also better off knowing the other half: when something in your operation does not exist yet, we say so plainly, with what has to be built in plain sight, before you sign anything.
Tell us which process is eating up your day.
You tell us how it works today and we tell you what can be automated, and in what order.