Falnor / Tools
What to automate first
List the processes you are thinking about and move six sliders for each. You get a ranked order by how much each is worth and how ready it is, and a flag on any that should keep a named person approving the result. Free, no sign-up.
Book a discovery callYour candidate processes
The starting rows are examples. Rename them and move the sliders to match your own work.
Where to start
Talk through starting with Invoice entry and matchingInvoice entry and matching
Start here- Priority16.0 of 25
Value 4.0 of 5, readiness 4.0 of 5.
Monthly reporting pack
Next- Priority15.0 of 25
Value 3.0 of 5, readiness 5.0 of 5.
New customer onboarding checks
NextNeeds a named approver- Priority10.0 of 25
Value 3.3 of 5, readiness 3.0 of 5.
Invoice entry and matching scores highest: it is worth the most and is the most ready.
Worth checking against the real work
A 30-minute discovery call goes through these inputs with you, checks them against how the work really runs, and tells you plainly if it is not worth building. Your numbers are filled in for you.
How the score works
Value is the average of how often it runs, how long each run takes and how often it goes wrong. Readiness is the average of how clear the rules are and whether the data is already in systems. The priority is value times readiness, so a result runs from 1 to 25. A score of 9 or more is worth starting.
Cost of a wrong result does not lower the score. It flags the process as needing a named person to approve it, because high-stakes work should keep a person in the loop even when it is a good candidate. This is an estimate from the numbers you enter, not a quote. Real projects differ once the work is mapped.
Why start with the order, not the tool
Most automation that disappoints was pointed at the wrong process: one that looked painful but runs rarely, depends on judgement every time, or lives in inboxes and paper. Ranking first is cheap and avoids that.
The six questions
- How often it runs, how long each run takes, and how often it goes wrong. Together these set the value.
- How clear the rules are, and whether the data is already in systems you can reach. Together these set how ready it is.
- The cost of a wrong result. This does not lower the score. It decides whether a named person should approve the outcome.
How the score is worked out
Value is the average of the first three answers, from 1 to 5. Readiness is the average of the next two. The priority is value times readiness, so it runs from 1 to 25. A score of 9 or more is worth starting. Anything below that is better left until the rules or the data are easier to reach.
Where a person stays in the loop
When a wrong result is costly in money, in law or with customers, the process can still be a good candidate. It just needs a person who approves the outcome before it takes effect, with the evidence in front of them. That is how we build: the system does the reading, checking and drafting, and a named person decides where judgement matters. See human-in-the-loop systems and human-in-the-loop automation.
Once you know which process comes first, test the numbers with the automation return on investment calculator.
Questions people ask
How many processes should I score?
Two to six. Fewer than that and there is nothing to rank. More than six and the list is probably covering more than one team, so split it.
What does a score of 9 mean?
It is the line this tool uses to separate worth starting from not yet. For example, a value of 3 with a readiness of 3 scores 9. It is a rule of thumb, not a measured threshold.
Why does a high-risk process still rank well?
Risk and value are different things. A risky process can be very valuable. The flag tells you to build it with a named approver, not to avoid it.
Are the starting rows real?
No. They are examples so the page shows a ranking straight away. Rename them and move the sliders to match your own work.
Is this a quote?
No. It is a ranking from what you enter. A real project is scoped once the work has been mapped.