You are being asked to spend $1,500 to find out whether to spend more. That deserves a straight answer about what the money buys. Here it is, day by day and deliverable by deliverable.
The AI Opportunity Review does not start with a tool. It starts with the work slowing your team down, and it ends with a decision you can act on: test one workflow, or wait.
Why a review comes before the tools
Using AI and investing in it are different things. In Bluevine's 2026 survey of 942 US small businesses, 74% were using or testing AI tools, and about half of those had seen a return on the spend. The gap is rarely the tools. It is a named owner, a baseline to measure against, a review step before anything reaches a client, and a decision rule for what happens next.
The review exists to put those four in place for one workflow, before you commit to building anything.
Who it is for
Owner-led service firms with 10–50 people: agencies, consultancies, and B2B professional services. The qualifying rule is that you have:
- A recurring workflow taking at least 20 staff hours a month, or causing measurable delays
- Existing digital systems such as Microsoft 365, Google Workspace, a CRM, or project-management software
- An owner or operations lead who can approve changes, plus a named process owner
- Representative work samples and time for staff to participate
If one of these is missing, the scoping flow says so before you pay anything.
The 10 business days
1. Kickoff
You name the person who owns the workflow and show us how the work is done today. For an agency, that means the proposal owner walking through how a proposal is built, from discovery notes to the version that goes out. Together we agree what improvement would mean.
2. Review
Up to three interviews, up to three workflows, and representative work samples. Each workflow is scored on benefit, effort, data suitability, and operational risk. Good candidates repeat, can be measured, and have someone on your team who can review the output: proposal preparation, client onboarding, finding information in approved documents, and recurring reports are useful starting points.
Here is what the scorecard looks like, with illustrative data, not a customer result. Proposal preparation scores 13 out of 15, client onboarding 10, recurring reports 8. Benefit, ease of implementation, and data suitability are each scored out of five and equally weighted. The recommended first pilot in that sample: test proposal first drafts, with the proposal owner reviewing every output. Your review may conclude that no workflow is ready yet.
3. Business case
Setup and ongoing costs against released capacity, in conservative-to-optimistic scenarios. Capacity is reported as hours, not as payroll savings. Time released, cash savings, and revenue effects are reported separately, because released capacity does not automatically reduce payroll costs.
The sample review shows how the arithmetic is laid out. Its illustrative assumption: 12 proposals a month × an assumed 90 minutes released each ≈ 18 hours of monthly capacity. Against that sit the costs to include: review and implementation, software, usage charges, staff review time, and maintenance. And the business case names what remains uncertain: actual time released, rework required, staff adoption, and whether released time can be used productively.
The starting assumptions follow published vendor benchmarks (8–12 proposals a month, 4–6 hours each; Pitchsite, 2026). They are assumptions, not GradeCircle data. Your review replaces them with your own evidence.
4. Decision meeting
We go through the findings with you. You leave with one of two things: a recommended first pilot at a fixed price, or a recommendation to defer AI and what would need to change. Either way the findings are yours.
What you receive
- Kickoff, up to three staff interviews, and a review of up to three workflows and representative work samples
- Opportunity scorecard covering benefit, effort, data suitability, and operational risk
- Business-case calculator with setup and ongoing costs, capacity gains, and conservative-to-optimistic scenarios
- Recommended workflow, proposed tools, and human review requirements
- Pilot brief with baseline, success measures, responsibilities, scope, and a fixed implementation quote
- Decision meeting to review the findings; deferring AI can be the right recommendation
When the answer is "not yet"
Fixed scope, clear pricing, and deferring AI is a valid result. If no workflow is ready for testing, you receive the reasons and what would need to change. You learn that for $1,500, at the end of 10 business days, instead of partway through a build.
If a workflow is ready, you receive a pilot brief with scope, responsibilities, and success measures, plus a baseline and a fixed implementation quote. You know what the test would cost and how it would be judged before you agree to it.
What comes after, only if you choose
The review stands alone. You can finish there with the findings.
A pilot is a separate decision. The AI Workflow Pilot is $5,000 over four weeks: one workflow, one team of up to five, measured against your own baseline, ending with a recommendation to expand, revise, or stop. If you approve a pilot, the review and pilot together cost $6,500. Software subscriptions and third-party usage charges are additional and disclosed before you commit. Optional AI Performance Support is $750 a month after deployment.
For what those four weeks look like on a proposal workflow, see Inside a Four-Week AI Workflow Pilot.
Scoping is free. Five questions about the work you want to improve, and you see whether the review fits before you share contact details or pay anything.
GradeCircle builds and runs six products of its own: AfroSynergy, CallerBridge, HealthSquire, Heyzl, Lexfora, and LukeAPI, two of them in beta. The assumptions in our models come from operating those systems, not from a framework. See what we run.
Scope your AI opportunity: five questions, and you see a preliminary fit summary before sharing contact details.



