Booking Q4 deliverystart with a free workflow plan Denver · Phoenix · Remote
Get my free plan
Sample audit

See what your audit delivers.

Follow a fictional service business from workflow map to ranked opportunities, an economic worksheet, and a phased recommendation. All inputs and modeled outcomes are illustrative; they do not represent a client engagement, measured results, or a quote. See what the full audit includes.

The auditSpec
Fixed price$3,500–$8,500
Timeline2 to 4 weeks
OwnershipYours outright
Page 1 / 4 · Sample workflow map Fictional example · Not client work

Workflow map: service requests

Example business: a neighborhood repair company. The question: where does a new service request slow down before a job is scheduled? All roles, tools, and workflow details below are illustrative.

StepWhat happensWho touches itToolWhere it breaks
01 A customer requests a repair by email or web form Intake coordinator Shared inbox Requests wait when the usual coordinator is away
02 Customer, address, and job details are copied into the job tracker Office manager Job tracker Missing details are discovered after the record is created
03 The team asks for photos, access details, or a clearer description Intake coordinator Email and phone Colleagues cannot see which questions have already been asked
04 The job is assigned to the right service category and available crew Dispatch lead Job schedule Routing relies on one person knowing every exception
05 The customer receives the agreed next step and the job record is updated Office manager Email and job tracker Updates are typed twice; customers call to ask what happens next
Page 2 / 4 · Where AI pays Fictional example · Not client work

Where AI pays: ranked

An illustrative priority order for the same fictional business. Effort and potential payoff are judgment ranges, not measured outcomes. A real audit would validate volume, handling time, exceptions, and tool access before recommending a build.

  1. 01

    Intake triage & routing

    Prepare a service-request summary, identify missing details, and suggest a routing category. The intake coordinator checks the draft; the dispatch lead owns assignment. Validate first: request volume and the rules behind routing exceptions.

    Effort: low–mediumPayoff: medium–highDecision: validate before quoting
  2. 02

    Missing-information follow-up

    Draft one clear request for the missing photos or job details, using the existing conversation. A person reviews it before sending. Validate first: which follow-ups repeat often enough to justify automation.

    Effort: mediumPayoff: medium–highDecision: validate before quoting
  3. 03

    Confirmed-status updates

    Use an approved scheduling change to prepare a customer update and keep the job tracker aligned. Deterministic integration may be enough; a model is only useful where interpretation is needed. Validate first: available connections and the authoritative status field.

    Effort: medium–highPayoff: mediumDecision: check tool access first
Page 3 / 4 · The economic decisionFictional assumptions · Not a forecast

Would the first workflow justify the investment?

Start with intake preparation. Compare a cautious case with a higher-coverage case before deciding whether to build. The example keeps human review in both cases and values only preparation time; it assumes no additional sales.

Requests per month600
Manual preparation12 minutes per request
Review after preparation5 minutes per eligible request
Value assigned to capacity$40 per hour
Tools and operating allowance$300 per month
Illustrative build budget$18,000
How the decision changes with eligible request volume
Monthly estimate30% eligible60% eligible
Preparation capacity returned21 hours42 hours
Value assigned to that capacity$840$1,680
After the operating allowance$540$1,380
Build cost ÷ monthly net capacity value33.3 months13.0 months

Calculation: requests × eligible share × (12 − 5) minutes ÷ 60 = preparation hours returned. Hours × $40 − $300 = monthly net capacity value.

Capacity is not cash savings. These assumptions are fictional. The recovery period values freed time; it does not show money earned or payroll reduced. If that time cannot be put to useful work, the benefit may be much lower or zero. Figures exclude discovery fees, taxes, optional Managed Services, separately scoped hardware, and the client's training/change effort. The build budget is an example within the published sprint range, not a quote. Actual scope, price, and audit-credit terms are agreed separately.

Page 4 / 4 · The phased recommendationIllustrative decision · Not a delivery commitment

Validate intake first. Expand after it earns its place.

A higher modeled return is a reason to investigate, not approval to automate. Each phase ends with evidence for the next decision.

  1. 1. Measure the current work

    Sample ordinary requests and exceptions. Confirm monthly volume, preparation time, tool access, and who owns routing decisions. Use the measured inputs to replace this worksheet's assumptions.

    Decision: pause if request volume is too low, the process keeps changing, or useful work for the returned capacity is unclear.

  2. 2. Scope one workflow

    Define the prepared summary, required fields, permitted actions, reviewer, and failure route. Compare a simple form or integration with an AI-assisted approach. Agree acceptance criteria and a fixed price before building.

    Decision: proceed only if the operating need and economics support the agreed scope.

  3. 3. Test with human review

    Use approved examples to compare the original process with prepared work. Count review time, corrections, missed details, and handoff failures as part of the result.

    Decision: launch only when the agreed acceptance criteria pass; otherwise revise the workflow or stop.

  4. 4. Review before expanding

    Compare actual workload and costs with the estimate after launch. Consider missing-information follow-up next. Add scheduling updates only when the source of truth and integration access are established.

    Decision: expand where the evidence supports it. Monitoring and maintenance are scoped separately.

What a real audit replaces: fictional inputs become observed workflow data, named owners, documented constraints, cost assumptions, and a recommendation your team can challenge.

Explore your own assumptions in the ROI calculator
See what your audit delivers.

Your audit uses your workflows, evidence, and priorities. The resulting document belongs to you, whether or not you commission the build.

Read the full audit spec
Fair questions

About this sample document.

Want the numbers?

The full price list is published — audits, sprints, managed services, all on one page.

Read the price list →
01What is this page?+

Four sample pages show a workflow map, ranked opportunities, an economic worksheet, and a phased recommendation. The business, inputs, costs, and modeled results are fictional; they are not a client result or quote.

02What does the full audit cost?+

$3,500–$8,500, fixed in writing, over 2 to 4 weeks.

03How do I get one with my workflows in it?+

Start with a free 30-minute assessment to discuss one workflow and the next step. If substantial discovery is needed, we scope a paid audit; a fixed build quote follows an agreed scope.

Start here

Start with a free 30-minute assessment to discuss your workflow and whether an audit would help. If substantial discovery is needed, we scope the paid work before it begins. We reply to assessment requests within 24 hours.

This illustrates part of the AI Readiness Audit deliverable. See what it costs, or a build one led to in the MARCUS case.

Book a free assessment →

A fixed price, quoted in writing before we start, and a straight answer within 24 hours.

— Christopher Myers, Founder