Skip to content
VorsaLogic

The assessment

AI Readiness Assessment: your AI use cases, ranked by P&L impact and risk

Two days at your operation. A scored backlog of every AI use case we find, ranked by what it does to your P&L and how much risk it carries. Then we build the top one in two weeks. You keep the backlog either way, and you don't pay for the build if it misses the mark.

This is not a questionnaire. It is the plan you would pay a consultancy for, with the first result built in.

From $10,000, credited in full against your first workstreamFounder-ledHouston-based, on site across Texas, remote anywhere in the US
AI readiness assessment: a use-case backlog scored by P&L impact and risk

Who the AI readiness assessment is for

Companies that run on operations, not on software: trucking and logistics, contractors and field service, industrial shops, hospitality groups, and any business where the work happens in a TMS, an FSM, an ERP, and a dozen inboxes and portals.

The pattern is the same everywhere. Systems that do not talk to each other. A person standing in the gap, re-keying and checking. An owner who cannot get a straight number on margin, cash, or on-time rate without someone building a spreadsheet. If that is you, an AI readiness assessment is the right first step, because the question is not "which AI tool" but "which job, first, and what is it worth."

What it is not

It is not a maturity score. Plenty of vendors will grade your "AI readiness" on a five-point scale and send a PDF. A score does not tell you which job to hand to an agent first or what it is worth.

It is not a technology recommendation. We do not arrive with a platform to sell. Most of what we recommend runs inside software you already pay for.

It is not a discovery call dressed up as a deliverable. Two days on site, with your dispatch, billing, and office staff, is work. The output is a document your team will argue with, which is the point.

And it is not a commitment. You keep the backlog and the governance notes whether or not you build with us, and they are written so anyone competent could act on them.

What we measure: the P&L lens

Every use case we find is scored on what it changes in one of five places: revenue, margin, labor hours, cash cycle, and error cost. If we cannot name the line, it does not make the backlog.

That is the difference between this and an AI strategy deck. A deck tells you AI is important. The backlog tells you that the AP capture agent saves roughly this many hours a month, touches these two systems, and carries this much risk if it codes an invoice wrong, so it ranks third, behind the two things that pay back faster with less exposure.

Risk is scored too: data sensitivity, what happens if the agent is wrong, how many systems it touches, and how much a person needs to stay in the loop. High value and low risk goes first. High value and high risk gets a governance plan before it gets built. Low value goes on the list with a note, because the list is also a record of what you decided not to do and why, which is useful the next time a vendor pitches it.

How the two days run

Day one: people, process, technology. We walk your operation with the people who do the work, not only the people who manage it. Dispatch, billing, intake, scheduling, reporting. We see the four browser tabs, the re-keying, the spreadsheet that runs the company. We inventory your systems and what each one can and cannot exchange.

Day two: scoring workshop. With the owner and the managers in the room, we put every candidate on the board and score it on value and risk. We argue about the numbers. We settle on a ranked list and on the one thing to build first.

What you leave with. The ranked backlog, with the P&L line and the systems for each item. A recommended first workstream with success criteria written down. Governance notes: where a person must stay in the loop, what data needs care, and what the documentation should say. A systems inventory: what each one can exchange, what has an API, what does not. All of it yours, whether or not we do anything else together.

Before we arrive. We ask for read access to your main systems where practical, a list of the people we should talk to, and the three things that frustrate the owner most. We do not need clean data or a data team. We need a morning with the people who do the work.

Then we build the number one use case in two weeks

The assessment includes the first build. We take the top-ranked item, agree on what "working" means in numbers, and put it into production in two weeks inside the systems you already run.

If it misses the agreed mark, you don't pay for the build. You keep it either way: code, data, accounts, runbook. Most clients ask for an AI agent for a back-office job first: AP or AR, dispatch status, intake, or the weekly owner report. The twelve agents we build most →

Price and credit

The AI Readiness Assessment starts at $10,000. That amount is credited in full against your first workstream, so if you go on to build with us, the assessment costs nothing net. Larger operations with more sites or systems are quoted before we book.

Prices verified September 2026. Full pricing →

Proof

A Houston trucking company tracked 600 to 700 import containers a month by checking port and steamship-line websites by hand. After a scoped start, we built a monitoring agent inside their TMS, their tracking provider, and Microsoft Teams; dispatch now gets a daily digest and alerts when a last-free-day moves, and a person handles only the exceptions. They own the system and keep us on a managed plan. More on what we build for trucking →

Founder-built by Jonathan Klein and Chip Ray. Insured: cyber liability, technology E&O, and general liability.

Book your assessment

Tell us about your operation. A founder replies within one business day to confirm fit on a 30-minute call, then we schedule the two days.

Prefer to talk first? Call 346.560.5759. A founder answers or calls back within one business day.

Frequently asked questions

A free assessment is a sales call with a checklist. This is two days inside your operation with the people who do the work, a scored backlog you keep, and the first use case built and running. The fee is credited against the build, so it is free in the way that matters: you get the plan and the first result for the price of the result.

No. Finding out how clean your data is part of the assessment. The first workstream often includes a cleanup step, and we tell you what the mess limits before you commit to anything.

Then we say so, you keep the backlog, and you have spent $10,000 to learn that the honest answer is "not yet" and why. That has happened. It is rare, because most operations have at least one workflow a person does by hand every day that pays back quickly.

Day one: the people who do the work, plus their managers. Day two: the owner or the executive who can decide, the ops lead, and whoever owns the numbers. We keep day two to the people who can say yes.

Yes, for companies outside Texas. We do it in person in Greater Houston, Austin, San Antonio, and Dallas–Fort Worth, and by video elsewhere. In person is better for day one; video works for day two.

It is yours. It is written so that any competent engineer or vendor could pick up the top item and build it. Nothing in it depends on us.

Two days. A ranked list. The first one built.