Current-state evidence
A map of the workflow, systems, handoffs, owners, volumes, rework, and known failure points.
One paid decision engagement for service businesses
Decide whether to configure, buy, build, defer, or stop.
The Blueprint examines one costly workflow before the business commits to software or implementation. Compical documents the current process, tests what the existing stack can do, defines the control requirements, and gives leadership a decision package it can act on.
What leadership receives
One decision brief, backed by its evidence.
The Blueprint gives leadership the evidence needed to decide whether implementation is justified and, if so, what it will require.
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.
Example structure
What the written decision brief contains.
This example shows the sections John prepares for leadership. It contains no client data, findings, or results.
Decision and scope
The workflow boundary, sponsor, process owner, decision rights, and evidence required to justify further investment.
Current state and economics
The process, systems, handoffs, volumes, rework, cost assumptions, and limits of the available baseline.
Existing-stack assessment
Capabilities the business already licenses, how they are used, and the material gap that remains after configuration or process changes.
Controls and feasibility
Data boundaries, evaluation thresholds, human review, failure handling, and the evidence required before production.
Recommendation
A configure, buy, build, defer, or stop recommendation with the assumptions and stop conditions behind it.
Implementation path
The sequence, dependencies, responsible roles, resource needs, and budget range if leadership chooses to proceed.
The engagement
Start with the decision, not the model.
John checks the business's existing products and process before considering custom work. If configuration, vendor services, adoption, or a process change can solve the problem, the recommendation will say so.
- 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.
Existing software first
Do not build what the business already owns.
Portals, inboxes, CRM or practice-management systems, document tools, field-service platforms, workflow products, and automation features may already cover part of the workflow. The Blueprint checks what the business licenses, how it is configured, and why the desired result is not happening.
A configuration, vendor-service, adoption, or process change may be the right answer. The recommendation does not have to include custom AI.
Decision criteria
The facts leadership should know before it proceeds.
The exact measures depend on the workflow. Compical documents the baseline and assumptions rather than presenting unsupported savings or adoption claims.
- Annual workflow volume and cost pool
- Capabilities already licensed and their actual use
- Cycle time, rework, exception volume, and outsourcing or overtime
- Data access, security, retention, and human-review requirements
- Resources, dependencies, and decision authority
- Evidence required before a controlled production launch
Client participation
A decision needs owners, access, and review.
- An executive sponsor and a named process owner for kickoff, access, assumption review, and the final decision meeting
- One site visit and up to eight stakeholder interviews unless the written scope states otherwise
- Participation from operations, finance, the relevant domain owner, and IT or security
- Access to current process documentation, system information, and baseline data
- A business-approved environment and explicit approval before representative records are used in any feasibility test
- Timely review of assumptions, controls, and the final decision package
- Named owners, contracting and security preflight, the approved environment, sample data, and baseline exports before the 4 to 6 week delivery clock begins
Outside the Blueprint
Work that requires a separate decision.
- Production implementation, ongoing operation, or a guaranteed launch
- Professional advice or autonomous decisions about tax, law, insurance, housing, safety, eligibility, pricing, claims, payments, or customer outcomes
- Core-system migration, company-wide data cleanup, or replacement of the system of record
- Software licenses, travel, external legal or security opinions, or third-party audits
- A compliance certification or promise of savings, revenue, accuracy, or adoption
Start with one decision
Bring the workflow leadership is being asked to change.
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