Licensed capability goes unused
The business may already own document, portal, CRM, workflow, or automation features that could solve the problem with better configuration and ownership.
AI workflow decisions for service businesses
Decide whether one costly workflow is worth changing.
When rework, overtime, outsourcing, or capacity loss persists across systems and teams, Compical examines one workflow before the business funds AI, automation, or another software product. Leadership receives a configure, buy, build, defer, or stop recommendation.
Best fit: a multi-location or multi-team service business with a repeated workflow, measurable operational cost, and an executive sponsor prepared to act on the recommendation.
The 30-minute call is for fit only. Detailed analysis and scoping begin in a paid engagement.
What the Blueprint resolves
1 workflow · 4 to 6 weeks · 1 decision
- 01Cost poolWhere time, rework, and outside spend collect
- 02Existing stackWhat licensed products can already solve
- 03Control pathWhat data, review, and evidence are required
- 04DecisionConfigure, buy, build, defer, or stop
15 yearsBuilding and launching software
AppleDatacenter systems
Chime MyPayStaff engineer from early development through launch
Remote + on-siteAvailable across the United States
Why firms get stuck
The first question is not which AI tool to buy.
The useful question is whether a specific workflow is expensive enough, controlled enough, and technically ready enough to justify changing it.
The workflow has no baseline
Leadership hears that a process is slow, but cannot see the annual volume, rework, exception rate, or cost that would support an investment.
A pilot has no decision rules
Without acceptance thresholds, human review, data boundaries, and a named owner, a demonstration cannot become an accountable production decision.
The Workflow Blueprint
Build the evidence before you fund implementation.
A focused decision engagement for service businesses evaluating one costly workflow before committing to implementation.
- 01
Frame
Name the decision, workflow boundary, executive sponsor, process owner, and conditions that would justify further investment.
- 02
Examine
Document the current process, systems, data, controls, volumes, bottlenecks, and work that staff must redo.
- 03
Test
Assess existing software first, then test only the remaining gap with synthetic or minimized data. Use representative records only with the business's explicit approval.
- 04
Decide
Present the economics, risks, evidence, and implementation choices so leadership can proceed, revise, defer, or stop.
What leadership receives
A decision package, not a generic AI roadmap.
The scope stays with one workflow and the evidence leadership needs for its next investment decision.
Current-state evidence
A map of the workflow, systems, handoffs, owners, volumes, rework, and known failure points.
Conservative business case
A baseline for the addressable cost or capacity, the assumptions behind it, and the conditions required for an investment to make sense.
Existing-stack fit and gap
An assessment of capabilities the business already licenses, where configuration may be enough, and where a material gap remains.
Feasibility and control design
A bounded test plan, evaluation thresholds, data boundaries, human review, failure handling, and the evidence required before production.
Executive decision package
A recommended configure, buy, build, defer, or stop decision with a sequenced implementation plan, resource needs, dependencies, and budget range.
Workflow examples by industry
Start with work the business already knows is expensive.
Each page presents one workflow hypothesis, the people needed to examine it, and the decisions that must remain with qualified staff. These are starting points, not client results.
Regional tax firms
Tax Workflow
Compical helps regional tax firms examine one costly workflow, test the limits of existing software, and decide whether to configure, buy, build, defer, or stop.
See the document-intake hypothesis Regional law firmsLaw Firm Workflow
Compical helps regional law firms examine one costly administrative workflow, test the limits of existing software, and decide whether to configure, buy, build, defer, or stop.
See the matter-opening hypothesis Independent insurance agenciesInsurance Agency Workflow
Compical helps independent insurance agencies examine one costly service workflow, test the limits of the existing AMS and other software, and decide whether to configure, buy, build, defer, or stop.
See the service-inbox hypothesis Residential property management companiesProperty Management
Compical helps residential property management companies examine one costly maintenance workflow and decide whether to configure, buy, build, defer, or stop.
See the maintenance-intake hypothesis HVAC and plumbing companiesHVAC and Plumbing
Compical helps multi-crew HVAC and plumbing companies examine one costly service workflow and decide whether to configure, buy, build, defer, or stop.
See the service-intake hypothesis
John KellyFounder and principal consultant
Product execution in complex operating environments
From ambiguous product idea to launch.
John Kelly spent 15 years building and launching software. At Apple, he worked on datacenter systems. At Chime, he was a Staff Software Engineer on MyPay from early development through launch.
MyPay lets eligible members access some of their pay before payday. Chime reported that MyPay reached more than $400 million in annualized revenue in Q4 2025. John worked on the product as a Staff Software Engineer from early development through launch.
A focused first conversation
Bring one workflow that may be worth changing.
The fit call is free. John will ask about the business problem, current systems, decision owner, and timing. Detailed analysis begins only in a paid engagement.
Book a 30-minute fit call