Process map and use-case scores
We map the tasks that fill your team’s week and score each candidate on hours saved, data readiness and risk. You receive: a ranked list of use cases, with the reason each one sits where it does.
AI consulting
A short paid review of how your team works, ending with two or three use cases priced against the hours they save, and the ones to skip.
Book the AI reviewWhat AI consulting is
AI consulting services here means a short paid review of how your team works. It ends with two or three use cases priced against the hours they would save, the ones to skip, and what each would cost to build.
We list the tasks that fill your team’s week, how often each happens and how long it takes. The hours come from your own people.
Each candidate is scored on hours saved, data readiness and risk, then priced. Two or three make the list, with the cost of building each.
Some work should stay with a person, and some isn’t worth its price yet. The review says which, so you don’t spend on them.
Review first or build first
Both end with something running. The difference is whether the choice of what to build is made before the money is spent or after.
| Starting with a buildBuild, then learn | A paid AI reviewDecide, then build | |
|---|---|---|
| First step | Pick a tool or a use case and begin | Map the work and score each candidate use case |
| What you can skip | Found out during the build, after the spend | Use cases that fail on data, risk or hours saved |
| How it’s priced | One price for the build that was chosen first | A written scope for the review, then a price per use case |
| Who it suits | A team that already knows the one job to automate | A team with several ideas and no way to rank them |
| What you hold afterward | The finished build and its documentation | A ranked list, a risk memo and a pass line for each build |
If you can name the one job, say who does it today and how long it takes, you can go straight to a build from $3,500 per workflow. The review is for the team with a list of ideas, a vendor pitch on the desk, or no idea where to begin. We say which one you are on the first call.
What the sources say
What NIST and the FTC say about AI risk and AI claims, with the source under each.
NIST released AI RMF 1.0 on January 26, 2023, for voluntary use. It is a guideline, not a law, and NIST says it is being revised. We borrow its four functions as the headings of the risk memo, so the memo follows a structure a board or an insurer already knows.
NIST AI 600-1, the Generative AI Profile, came out on July 26, 2024. It helps organizations identify risks that are specific to generative AI and proposes actions to manage them. A use case built on a language model is read against it.
Its September 25, 2024 sweep, Operation AI Comply, named five cases, including a “robot lawyer” service that paid $193,000. For a buyer, it is a reason to ask any vendor, ours included, what a tool was tested on before it was sold.
The FTC said Workado advertised its AI content detector as 98 percent accurate, while independent testing found 53 percent on general-purpose content. Its final order, August 28, 2025, requires competent and reliable evidence for such claims. Our evaluation plan sets the pass line before anything is built.
The scope
Six parts of the work. Each ends in a document you can open, check and forward.
We map the tasks that fill your team’s week and score each candidate on hours saved, data readiness and risk. You receive: a ranked list of use cases, with the reason each one sits where it does.
For each use case we look at where the data lives, who can see it, how clean it is and what permission covers using it. You receive: a one-page readiness note per use case, with what to fix first.
Where a product already does the job, we say so and name the trade-offs: cost, where your data goes and what you can change. You receive: a build-or-buy note for each use case, including the ones where buying wins.
We write down what the tool may see, what it may never do, who approves its output and what happens when it is wrong. The memo follows the four NIST functions. You receive: a risk memo and a short staff policy you can adopt or edit.
Before any build, we agree the test set, the pass line and who reads the results, so accuracy is a number you can read. You receive: an evaluation plan for each use case you approve.
The use cases that cleared the review are put in order, each priced against its hours saved, with the skips listed under them. You receive: a one-page plan and a fixed price for each workflow you choose to build.
How it runs
You approve the scope before any work starts. Each stage hands you a map, a list or a plan to keep.
Task map
| Task | Hours a week | Steps |
|---|---|---|
| Confirming appointments | 6 | 4 |
| Copying intake forms into the system | 4 | 5 |
| Insurance verification calls | 7 | 6 |
| Treatment plan follow-up calls | 5 | 4 |
| Building the weekly report by hand | 2 | 7 |
Our stack
The models and tools a use case gets tested on.
OpenAI’s models read, write and summarize language, and also handle images and audio.
We run your own sample questions and documents through its models and record how many each one gets right.
Questions
Keep exploring
Salesforce, HubSpot or Zoho, set up around how your team sells.
AI built on your documents and data, tested before launch.
HubSpot configured, connected and loaded with clean data.
A website chat that answers from your approved content.
Agents that act in your CRM, calendar and inbox, with approvals.
An AI phone line that answers, books and hands off.
Phone lines for reminders, status calls and after hours.
Zoho CRM and Zoho Books set up with clean data.
One repeated process mapped, then automated.
Start here
Tell us where your team loses time. We’ll send back a written scope for the review, with its price, before you agree to anything.