Book a Consultation

Navigation

Book a Consultation
← How It Works

A fictional example of our approach

Understand the work before choosing the fix.

At Cornerstone Plumbing, capable people keep piecing together job details before they can act. Follow the information, the gaps, and a modest first step using tools the business already has.

Cornerstone Plumbing and every record on this page are fictional. This is an illustrative Morales Software example, not a real client, case study, testimonial, proof of results, or promise of an outcome.

Follow the example →

The situation

The answers existed. They just did not live together.

Cornerstone Plumbing is an owner-led plumbing contractor. Job readiness, substitutions, approvals and exceptions keep returning to Elena because the team cannot reliably find the current answer or its owner.

The first question is what happened in the work, rather than which software to buy. These fictional notes illustrate the kinds of sources we would compare.

Inspect the fictional source notes

Guided owner input

Owner Discovery Guide

Elena describes how work, decisions, tools, and knowledge operate across the business.

“Most days include repeated questions about labor allowances, parts substitutions, customer credits, schedule changes, and whether an installation is ready.”

Fictional owner input. Not a real client record.

Employee input

Employee Worksheet: Dispatcher

Maya explains why missing field records create more office follow-up.

“I do not want another place to check. I want the current system to show the answer.”

Fictional employee input. Not a real client record.

Customer intake

Customer Intake CP-JOB-2461

A minimized request connects a customer need to a site estimate without direct contact data.

“Replace aging gas water heater and review slow hot-water delivery.”

Fictional business record. Not a real client record.

Accepted estimate

Estimate CP-EST-2026-1187

A $7,240 water-heater project establishes scope, approval, deposit, and job lineage.

“Deposit due at acceptance: $2,896.00.”

Fictional estimate. Not a real client record.

Employee communication

Material Readiness Email

Jordan and Sam's exchange shows that the purchase order was received while a required valve remained unverified.

“Everything on the PO is here and staged. I do not see the isolation valve Luis mentioned in the site photos.”

Fictional communication. Not a real client record.

Conflicting process records

Two Installation Checklists

The March checklist was described as current while the older November copy remained in the truck binder.

“"The March version in Drive" and "the November version" in the truck binder were both still in use.”

Fictional version conflict. Not a real client record.

Field closeout record

Job Closeout CP-JOB-2448

A job marked complete is missing the final reading and photo the office needs.

“Final pressure: Missing from original field entry. Final photo: Missing from original field entry.”

Fictional field record. Not a real client record.

What the evidence suggests

The pattern was bigger than missing documents.

We compare conversations and records, keep contradictions visible, and separate observations from conclusions. These findings apply only to this fictional business.

  1. Routine decisions still come back to ElenaThe team has capable employees, but unclear decision boundaries prevent safe delegation.Evidence: Owner Discovery Guide, Estimator Employee Worksheet, and 1 moreReview evidence

    Fictional example. Not a real client or guaranteed result.

    Supported conclusion

    Pricing exceptions, substitutions, customer credits, and schedule exceptions repeatedly depend on Elena.

    Evidence
    What it means for the work
    Routine and unusual questions share escalation paths, which fragments owner attention and can delay estimates.
    Why it matters
    The team has capable employees, but unclear decision boundaries prevent safe delegation.
    Status and limit
    Evidence-supported in this fictional Assessment. The interruption count represents one sampled week, not an annual baseline.
  2. The team has to piece together whether a job is readyA crew can be scheduled while a required readiness condition is still uncertain.Evidence: Owner Discovery Guide, Document and Evidence Inventory, and 3 moreReview evidence

    Fictional example. Not a real client or guaranteed result.

    Supported conclusion

    Scope, deposit, schedule, labor, material, access, and final readiness are split across records and people.

    Evidence
    What it means for the work
    Jordan manually reconstructs readiness, and one represented job moved a day after a missing valve was found.
    Why it matters
    A crew can be scheduled while a required readiness condition is still uncertain.
    Status and limit
    Evidence-supported in this fictional Assessment. The short sample does not establish an annual delay effect.
  3. Estimate approval has unwritten triggersClear boundaries can preserve risk control while allowing routine work to move.Evidence: Estimator Employee Worksheet, Discovery Part 2, and 1 moreReview evidence

    Fictional example. Not a real client or guaranteed result.

    Supported conclusion

    Luis cannot consistently distinguish routine authority from an exception that belongs with Elena.

    Evidence
    • Estimator Employee Worksheet
    • Discovery Part 2
    • Estimate Approval Email for CP-EST-2026-1196
    What it means for the work
    Some estimates wait while the approval rationale remains in a message.
    Why it matters
    Clear boundaries can preserve risk control while allowing routine work to move.
    Status and limit
    Evidence-supported in this fictional Assessment. The evidence does not establish an effect on customer acceptance or revenue.
  4. Field and office closeout mean different thingsThe team cannot reliably use the job record as the complete handoff.Evidence: Dispatcher worksheet, Discovery Part 2 (60-call sample), and 2 moreReview evidence

    Fictional example. Not a real client or guaranteed result.

    Supported conclusion

    Physical completion can be recorded before the office has readings, photos, acknowledgment, and follow-up context.

    Evidence
    What it means for the work
    Maya or Brooke calls the field before customer communication or billing can finish.
    Why it matters
    The team cannot reliably use the job record as the complete handoff.
    Status and limit
    Evidence-supported in this fictional Assessment. The sample does not isolate every cause of incomplete closeout.
  5. The team isn’t sure which information is currentOrganized, owned knowledge can support continuity, employee use, and later bounded AI assistance.Evidence: Owner Discovery Guide, Field Technician Employee Worksheet, and 2 moreReview evidence

    Fictional example. Not a real client or guaranteed result.

    Supported conclusion

    Employees can often identify whom to ask, but not which record is current.

    Evidence
    What it means for the work
    The business depends on Elena, Jordan, and Andre for context that is difficult to retrieve or teach.
    Why it matters
    Organized, owned knowledge can support continuity, employee use, and later bounded AI assistance.
    Status and limit
    Evidence-supported in this fictional Assessment. The source set does not represent every operating document or field example.
Inspect the connected fictional business views

The records below illustrate how we organize sources, findings, and unanswered questions while assessing a business. This is an example reading view, not an included application, client portal, or standard customer deliverable.

Choose a connected fictional business view to explore

Our internal working view

Company Snapshot

Company · Current-state overview · Source-linked business view

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Shows what the business does, its size, what works, and what limits it today.

What we learned

Employees
13
Service model
Service calls and installation projects
Current constraint
Important job state and decision context are distributed

“The company can deliver routine work reliably, but exceptions and multi-step projects require significant manual coordination.”

Finding this view supportsOwner dependency and knowledge concentration
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Source-linked business view, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Decision Ownership

People and responsibilities · Responsibility map · Owner and employee evidence

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Makes current owners, decision boundaries, backups, and unresolved responsibility visible.

What we learned

Routine service dispatch
Maya, with Jordan as backup
Installation readiness
Jordan coordinates the decision
Estimate exceptions
Elena reviews amount, discount, labor, warranty, and substitution triggers

“Several decisions have an owner but no written decision boundary.”

Finding this view supportsRoutine decisions still come back to Elena
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Owner and employee evidence, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Customer Work Model

Customer work · Current-state operating map · Records, conversations, and tool evidence

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Traces customer work from the first request through payment, follow-up, and exceptions.

What we learned

Start
Phone, website, referral, or property-manager email
Middle
Estimate, acceptance, deposit, schedule, and readiness
Finish
Work, closeout evidence, invoice, payment, and follow-up

“The systems are individually useful. The current record shows no single owned readiness and closeout standard across them.”

Finding this view supportsReadiness and closeout are reconstructed
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Records, conversations, and tool evidence, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Knowledge Location Map

Systems and knowledge · Knowledge-location view · Owner and employee evidence

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Shows where operating answers live, who usually holds them, and what is difficult to retrieve.

What we learned

Pricing
Drive workbook plus Elena and Luis
Readiness
Sheet, vendor email, whiteboard, and physical staging
Troubleshooting
Andre's phone photos, notes, and experience

“Personal photos are not governed knowledge.”

Finding this view supportsCurrent knowledge lacks a reliable version and ownership pattern
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Owner and employee evidence, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Contradiction Register

Governance · Known contradiction · Cross-source comparison

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Preserves conflicting evidence without silently selecting the most convenient answer.

What we learned

Claim A
Readiness is checked 48 hours ahead
Claim B
Four of nine sampled installations were checked later
Treatment
Standard and practice are recorded as different current-state facts

“The stated standard and sampled practice differ; no required readiness record was found.”

Finding this view supportsThe team has to piece together whether a job is ready
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Cross-source comparison, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Known-Gap Register

Governance · Known gap · Evidence sufficiency control

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Names missing or uncertain knowledge and records what evidence or decision could resolve it.

What we learned

Owner interruptions
One sampled week, not an annual baseline
Employee adoption
No shared-record pilot had been run
AI boundaries
Allowed context, tasks, tools, and reviewers were not approved

“Which callback causes are avoidable and how often each occurs remains unknown.”

Finding this view supportsLimits every related finding
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Evidence sufficiency control, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Our internal working view

Findings Register

Assessment · Consultant analysis · Multi-source analysis

Fictional backstage view. Draft that still needs review; human review is required.

What this view helped answer

Connects each conclusion to evidence, confidence, and a limitation that must travel with it.

What we learned

Classification
Supported conclusion
Confidence
High within the represented source set
Limit
Annual delay effect remains unresolved

“Installation readiness is an understood concept but not one consistently owned record.”

Finding this view supportsAll five selected findings
Sources and what still needs review

Draft that still needs review. Not approved. Human review is required within this fictional example.

Source type: Multi-source analysis, preserved within the fictional source set.

Fictional example. Not a real client or guaranteed result.

Inspect illustrative deliverables and their limits

Actual deliverables depend on the agreement, evidence and business need.

01One-Page Business SnapshotCurrent-state artifact

Fictional example. Not a real client or guaranteed result.

Purpose

Give a reader enough business context to understand the evidence and findings that follow.

“Growth has increased the cost of decisions that still depend on one person or one message thread.”

Evidence connection

Synthesizes owner input, customer-work evidence, business scale, operating strengths, and current constraints.

02Current-State Operating MapCurrent-state artifact

Fictional example. Not a real client or guaranteed result.

Purpose

Show how leads, estimates, scheduling, field work, closeout, payment, and exceptions connect.

“Decision rationale may remain outside the durable job record.”

Evidence connection

Links each stage to the fictional people, tools, decisions, handoffs, gaps, and sources that describe it.

03Key Findings SummaryFinding

Fictional example. Not a real client or guaranteed result.

Purpose

Present the smallest evidence-supported explanation of the operating problem and the first action.

“Important decisions and job states are not represented consistently enough for the team to act without reconstructing context.”

Evidence connection

Draws from the findings register while carrying short-sample limits and unresolved questions forward.

04Assessment ExcerptFinding

Fictional example. Not a real client or guaranteed result.

Purpose

Demonstrate evidence classification, limitations, and a proportionate recommendation.

“The practical first action is a four-week readiness and closeout pilot using existing tools.”

Evidence connection

Connects the selected observations, supported conclusions, known gaps, and implementation boundary.

05Knowledge and Responsibility ControlsCurrent-state artifact

Fictional example. Not a real client or guaranteed result.

Purpose

Keep missing knowledge, document ownership, and approval boundaries visible instead of guessed.

“Which callback causes are avoidable and how often each occurs remains unknown.”

Evidence connection

Pairs the known-gap register with decision ownership so a future pilot can resolve specific questions.

A proportionate next step

Test clearer handoffs with the tools already in place.

The proposed four-week readiness and closeout pilot would test an operating standard and employee use before deciding whether a technology gap remains. It is an illustrative recommendation, not an implemented change or a service promise.

  1. Define

    Name Jordan as readiness-record owner and agree on the minimum readiness and closeout evidence.

  2. Use

    Run one readiness record and one closeout standard inside the tools the team already uses.

  3. Review

    Check adoption, missing fields, owner interruptions, exceptions, and operating friction weekly for four weeks.

  4. Decide

    Correct the operating standard, then evaluate whether a remaining gap justifies integration, automation, AI, or custom software.

AI, integration or custom software would be considered only if the evidence later supported it.

The condition worth testing

Now imagine the same Monday with the answer in view.

Priya is preparing an installation and needs to know whether the job is ready.

She checks accepted scope, deposit confirmation, permit responsibility, crew, material receipt, customer access, and the current checklist in the readiness record. A missing condition keeps its owner and current status visible.

“CP-JOB-2461 is blocked. The isolation valve is not verified in staged material. Sam owns material verification; Jordan owns the final readiness decision. Do not mark ready until the missing item and updated schedule are recorded.”

This illustrates how organized knowledge could support an employee. It is not a record of an implemented system or achieved result. This is a possible destination, not an achieved result.