One-Workflow Assessment
Find out whether a process is worth automating.
Before you spend money building an automation, I’ll review the process with you, identify the technical constraints, and write up a recommended approach. You can use that document to decide whether to proceed and who should build it.
One-Workflow Assessment
When an assessment is useful
You know which part of the work is causing problems, but you’re not sure whether software would help or what it would take to build it.
For example, your team might spend hours chasing documents or looking for answers in internal files. You might also need to establish whether a proposed AI system can meet your data restrictions. We agree which process to review before starting. The assessment covers that process, rather than the whole business.
This is a paid engagement. The scope, fee, schedule, and deliverables are agreed in writing before work begins. The free initial consultation is a chance to discuss whether I can help. It does not include the assessment work.
What you receive
What’s in the assessment
01
How the process works today
I document who does the work, which tools they use, and where information moves between them. We record the current effort or error rate so there is something to compare an automation against.
02
What can be automated
I identify which tasks software could handle, which decisions still need a person, and what might prevent the proposed approach from working. This includes restrictions on where your data can be processed.
03
My recommendation
I explain what I would use and why, including the drawbacks. That might be an existing product, custom software, or an AI-assisted process. I may recommend leaving the process as it is.
04
A proposal for a small pilot
The brief describes what a first version would do, what it would leave out, and how we would test it. It also identifies any missing information needed to estimate the build.
05
The report and a review meeting
You receive the findings in writing. We go through them together, discuss any open questions, and consider whether to proceed, change the approach, or stop.
What to bring
What I’ll need from you
- Someone who knows the process and can explain how the work gets done.
- A walkthrough of the tools you use and a few examples with sensitive information removed, or made-up examples that show the same problem.
- An estimate of how much time the process takes or how often things go wrong, and what you want to improve.
- Any restrictions on the data or systems involved, and who would maintain the software.
You do not need to give me access to your systems for the first conversation. If the assessment needs access or sensitive information, we agree what is needed and how to provide it.
Scope
What the assessment does not include
The assessment does not include production code, a deployed pilot, a penetration test, security certification, legal compliance advice, or ongoing support. Those need a separate agreement. Any estimate will state the assumptions it depends on and the information that is still missing.
You can use the report to discuss the project internally or ask another team to build it. There is no obligation to hire Falcon for the build.
If you decide to proceed, I can prepare a separate proposal for a pilot. If I recommend against building, the report will explain why. See the full engagement process.
Start a conversation
Talk to me about the process you want to improve.
In the free introductory call, we’ll discuss the problem, the tools involved, and whether an assessment would help. You do not need to prepare a technical specification.