01 Assess / AI service
Find the workflow improvements worth investing in.
A paid, bounded engagement that turns a vague sense that something is slow into a specific workflow, a measured baseline, and a scoped recommendation you can approve or decline.
01 / Assess
What problem does this address?
You can feel the constraint but cannot price it. Estimates take longer than they should. Follow-up depends on who remembers. Billing lags the work. Somebody rebuilds the same report every week and you are still the person routine decisions wait on.
Buying an AI tool at that point is a guess. The assessment replaces the guess with evidence: which workflow costs the most, what a realistic change is worth, what it would take to implement, and who it affects.
02 / Assess
What do we do?
We follow real work, not a process diagram. One transaction or job type, end to end, across every person and system it touches.
- Observe the work and interview the people who do it, including the workarounds that keep the official process running.
- Establish a baseline with authorized records: volume, elapsed time, hands-on time, rework, and exceptions.
- Assess data and systems readiness: what information exists, where it is reliable, and which interfaces are stable enough to build on.
- Identify workforce effects early. Which tasks change, whose hours or earnings could be affected, and what participation and support the change needs.
- Compare the options honestly: remove the step, configure what you already own, integrate, automate with rules, or apply AI where it earns its place.
03 / Assess
What do you receive?
A validated workflow map
The observed flow with owners, systems, evidence, exceptions, and approval points, confirmed by the people responsible.
A measured baseline
Metric definitions, sources, observation period, accountable owners, and the limitations of the sample.
A ranked opportunity register
Options with expected effect, effort, dependencies, confidence, and clear reasons to defer or reject.
A workforce effects summary
Affected tasks, likely role changes, employee input, open questions, and the support that would need to be funded.
A decision-ready business case
Assumptions you can inspect, arithmetic you can reproduce, costs of change included, and estimates kept visibly separate from results.
An implementation scope
One prioritized initiative with acceptance criteria, controls, a rollout boundary, and the approval required to proceed.
Worked example
What a business case looks like.
Below is a fictional example of the arithmetic an assessment produces for a field-service business. Every figure is an assumption or a proposed target. None of it is a client result, a quotation, or a forecast for your business.
The point of showing it is the discipline, not the numbers. Assumptions are stated so you can challenge them, the calculation is simple enough to reproduce, and the estimate never gets promoted into a result.
- 120Assumed comparable jobs each month
- 35 minAssumed administrative time per job today
- 9 daysAssumed median from completion to invoice-ready
| Measure | Assumed baseline | Proposed target |
|---|---|---|
| Comparable jobs per month | 120 | 120 |
| Administrative time per job | 35 minutes | 20 minutes |
| Administrative time per month | 70 hours | 40 hours |
| Median days to invoice-ready | 9 calendar days | 3 calendar days |
| Capacity released per month | Not applicable | 30 hours |
| Realized cash benefit | Not established | Not established |
Who validates it
The operations manager confirms the workflow, the administrator and technicians confirm the effort, and the finance owner confirms what invoice-ready actually means and how it relates to collection.
Known limitations
Invoice readiness is not payment, and a short observation window can miss seasonality, larger jobs, and exceptional customers. A pilot has to track field capture effort too, because moving office work into the field is not an improvement.
Workforce effects
Thirty hours of released administrative capacity needs a destination the business can name and budget before it counts as anything. If later evidence points to fewer hours or roles, the workforce commitment is reopened and support is funded rather than assumed away.
04 / Assess
What do we need from you?
An assessment depends on access to the real operation. Without it we are describing an idealized process that nobody follows.
- A sponsor who can make decisions and authorize access.
- Time with the people who do the work, arranged around operating demands.
- Written authorization for the records, systems, and interviews in scope.
- Someone who can confirm operating rules and financial assumptions.
- A candid conversation about employee concerns and what support could be funded.
05 / Assess
How is success evaluated?
The assessment succeeds when you can make a confident decision, including a confident decision not to proceed. A recommendation to configure an existing system better, simplify a process, or leave the workflow alone is a valid and useful result.
We judge it on whether the baseline holds up to scrutiny, whether the assumptions are inspectable, and whether the recommended scope is small enough to finish and large enough to matter.
06 / Assess
What is outside scope?
The assessment does not authorize production writes, autonomous execution, unrestricted data extraction, or a company-wide rollout. It is not a commitment by either side to an implementation.
Employment, legal, tax, and other specialist decisions stay with the responsible professionals. We surface dependencies; we do not replace that review.
07 / Assess
What happens next?
We review the evidence together and you choose. If you approve an implementation, the scope, acceptance criteria, and workforce plan carry straight into an AI Workflow Implementation engagement under a separate agreement.
Your AI operating partner.
Tell us where the work gets stuck.
A short first conversation about the operation, the people it affects, and whether there is a useful question to investigate. It is free and it is separate from the paid assessment.