Symptom-to-capability diagnostic
Find and win customers
The capability to build: One visible path from first inquiry through qualification, estimate, follow-up, and a clear decision.
Recognizable symptoms
- New inquiries sit in several inboxes, phones, or notebooks.
- Quote follow-up depends on one person remembering.
- The owner cannot tell which opportunities need attention or which sources bring suitable work.
Useful first checks
- List every place a new inquiry can arrive.
- Choose one owner for the next action at each stage.
- Define what must be recorded before an opportunity moves forward.
Practical artifacts
- Inquiry-capture checklist
- Simple pipeline stages and ownership rules
- Quote follow-up rhythm and message prompts
Ways to build it: Learn it can help a team define the stages; Build it with us can map the real flow; Have us build it can configure and document a focused pipeline.
Scope boundary: A narrow advertising-buying problem or regulated sales advice may need a specialist. No process can guarantee demand or a sale.
Symptom-to-capability diagnostic
Schedule and deliver the work
The capability to build: A consistent sale-to-work handoff with visible status, required job information, change ownership, and customer-update triggers.
Recognizable symptoms
- Sold work reaches the field without the details needed to start.
- Schedule changes are known by one person but not everyone affected.
- Customers call for status because there is no reliable update point.
Useful first checks
- Follow one recent job from acceptance to completion.
- Mark every place information was re-entered, chased, or guessed.
- Identify the earliest point a missing detail could have been caught.
Practical artifacts
- Sale-to-work handoff record
- Schedule status definitions
- Change and customer-update checklist
Ways to build it: Learn it suits a team ready to improve its own handoff; Build it with us suits a cross-role workflow; Have us build it suits a defined handoff and supporting system.
Scope boundary: Trade-specific engineering, safety, dispatch optimization, or contractual requirements may need qualified professional input.
Symptom-to-capability diagnostic
Get paid and know the numbers
The capability to build: A visible path from completed work to invoice and payment, paired with a small review rhythm that connects measures to decisions.
Recognizable symptoms
- Completed work waits for paperwork before it can be invoiced.
- Owners discover margin or cash problems after the useful decision point.
- Weekly reports contain numbers but do not trigger clear action.
Useful first checks
- Write down the event that makes work ready to invoice.
- Identify who can confirm that event and what evidence is required.
- Choose three measures that would change a decision this week.
Practical artifacts
- Completion-to-invoice checklist
- Exception and collection queue
- Weekly operating scorecard with decision owners
Ways to build it: Learn it can establish a review habit; Build it with us can clarify the full process; Have us build it can connect the agreed steps and reporting.
Scope boundary: Accounting, tax, lending, valuation, and legal questions belong with appropriately qualified professionals.
Symptom-to-capability diagnostic
Build a team that can operate
The capability to build: Clear roles, decision rights, usable work instructions, onboarding practice, and a named owner for keeping the process current.
Recognizable symptoms
- Routine decisions return to the owner even when somebody else holds the role.
- New people learn important work through observation and memory.
- A process exists, but nobody knows who may change it or resolve exceptions.
Useful first checks
- Track the recurring questions that reach the owner for one working week.
- Separate missing knowledge from missing authority.
- Choose one repeated task and ask a team member to follow the current instruction without coaching.
Practical artifacts
- Role and decision-rights map
- Task instruction with exception path
- Onboarding and competency checklist
Ways to build it: Learn it fits a capable internal lead; Build it with us fits work that crosses roles; Have us build it fits a bounded documentation and rollout need.
Scope boundary: Employment law, compensation, workplace investigations, and clinical or safety-critical training require the right professional expertise.
Symptom-to-capability diagnostic
Run and understand the company
The capability to build: A practical operating rhythm with agreed measures, explicit decisions, action owners, and one maintained source for essential knowledge.
Recognizable symptoms
- Meetings review activity without deciding what changes next.
- Important operating knowledge lives in personal files or conversations.
- Several tools report different versions of the same business fact.
Useful first checks
- Review the last three recurring meetings for decisions and named owners.
- List the facts the owner repeatedly asks someone to assemble.
- Identify one source that should be authoritative for each fact.
Practical artifacts
- Weekly review agenda and decision log
- Measure definition sheet
- Business knowledge map and maintenance owner
Ways to build it: Learn it supports a self-led operating rhythm; Build it with us helps choose useful measures; Have us build it can establish a bounded reporting and knowledge system.
Scope boundary: Strategy, financing, regulated reporting, and governance obligations still require owner judgment and relevant professional advice.
Symptom-to-capability diagnostic
Reduce admin and use AI practically
The capability to build: A stable process first, followed by narrow automation or AI support with approved inputs, human review, fallback, and a measure of usefulness.
Recognizable symptoms
- People copy the same information between systems or repeatedly rewrite standard material.
- AI experiments happen without a defined owner, review step, or data boundary.
- Automation hides exceptions instead of making the process easier to operate.
Useful first checks
- Observe the task before choosing a tool.
- Remove unnecessary steps and define the correct output.
- Classify the data and decide where human review is mandatory.
Practical artifacts
- Task and data-boundary worksheet
- Human-review and exception checklist
- Small experiment plan with baseline and stop rule
Ways to build it: Learn it fits low-risk guided experiments; Build it with us fits process and control design; Have us build it fits a narrow approved workflow with documentation and handoff.
Scope boundary: Do not begin with confidential or regulated data in an unapproved public tool. High-consequence decisions require accountable human and professional review.