A completed acquisition
Two organizations now operate under one brand, but it is not yet established which processes were integrated and which were simply inherited.
We draw the operation before we change it.
Spendda is an evidence-backed operating transformation firm. Work, decisions, handoffs, controls and systems are surveyed and drawn to scale before change is prescribed.
Buyer situations
Call us when the operation is changing faster than its operating model.
Before you standardize, integrate, replace or automate an operation, establish how it actually works.
An investor or board has directed standardization
Leadership has been asked to standardize across a platform, portfolio or group of locations, but the current operating model has never been reliably drawn.
You are preparing to automate with AI
Before automating a workflow, establish what the process is, whether it is consistent, where judgment enters and whether it should be automated at all.
Core system migration or replacement
Before changing scheduling, EVV, payroll, CRM, ERP or other operational infrastructure, establish which process actually exists and what the replacement must preserve or change.
Multi-location growth
The same work has begun to operate differently across locations, while policy and management reporting still assume one model.
Recurring manual reconciliation
People spend regular hours making two records agree, and nobody owns the discrepancy.
A stalled technology implementation
The software is live but the work has not changed, or has moved back outside the system.
Compliance or control pressure
A control depends on memory, a private channel or one experienced person.
Referral
Work enters by phone, portal or partner system and is accepted against capacity.
Routing
Availability, obligation and need are reconciled into an assignment.
Delivery
The service is performed, recorded and confirmed against the agreed plan.
Exception
Change, absence or escalation is handled, often outside the formal workflow.
Settlement
Payroll, billing, quality and management read the same event and must agree.
Where the operating system breaks
The problem is usually visible in the handoff.
Fragmented record
The schedule, operational record, finance record and management report disagree, leaving people to reconcile the truth manually.
Unowned handoff
A process crosses a team, system or shift boundary and accountability becomes ambiguous.
Invisible exception
Overrides, corrections, misses and escalations leave the controlled workflow and move through messages, spreadsheets or memory.
Untraceable number
An outcome reaches management without a practical path back to the underlying record, rule and reviewer.
Premature digitization
Technology is selected before the operating model is sufficiently understood, automating the existing fragmentation rather than resolving it.
Three disciplines. One operating transformation.
Model the operation.
Follow work across people, systems, decisions and exceptions until the current operating model is explicit.
Operating model · 01Establish what the evidence supports.
Every material conclusion is connected to its evidence and given a declared claim state.
Evidence integrity · 02Deliver and measure the approved change.
Translate the reviewed roadmap into implementation with named controls, acceptance criteria and measurable release conditions.
Controlled delivery · 03Starting Market · 01
Home Care operations digitization.
Home-based care is expanding while the operating burden around it becomes more digital, more regulated and more interconnected.
The question is not simply whether an organization uses software. It is whether intake, scheduling, visit verification, documentation, staffing, payroll, billing, quality controls and management decisions operate as one coherent system.
Spendda begins with the operation as performed. We identify where information originates, how it moves, where it is re-entered or reconciled, which system is authoritative, where exceptions leave the formal workflow, and which decisions still depend on memory.
The resulting roadmap identifies what should be standardized, what existing technology should be configured, what systems should be integrated and where a controlled new capability is justified.
Home health and personal care aide jobs in 2024
BLSProjected employment growth, 2024–2034
BLSProjected openings each year
BLSFederally required for covered Medicaid-funded personal care and home health services involving in-home visits
CMS / Medicaid.govSources | U.S. Bureau of Labor Statistics · CMS / Medicaid.gov
The diagnostic record
What leaves the room.
Operating map
How work actually moves across people, systems, decisions and exceptions.
A1 referral → A2 routingA4 exception · unownedRe-entry points: 3Specimen fragment
Evidence register
What was examined, where it came from and what it can support.
EX-014 rota exportEX-015 escalation procedureReceived · sensitivity · ownerSpecimen fragment
Claims register
Supported · Assumption · Unverified · Rejected.
CL-031 supportedCL-032 assumptionCL-033 not establishedSpecimen fragment
Opportunity portfolio
Candidate changes ranked through declared rules and reviewed judgment.
OP-07 configure schedulingOP-08 integrate payrollRule set v1.2Specimen fragment
Approved roadmap
The selected sequence of operational and technology changes.
Phase 1 standardizePhase 2 configureAcceptance criteria namedSpecimen fragment
Observe • Map • Deliver • Measure
The work as performed, not as described.
Spendda models how an organization actually operates, tests that model against evidence, declares the status of material conclusions, and converts the reviewed record into an approved roadmap.
A finding without a source is an opinion. We are not paid for opinions.Spendda evidence standard · § 1.2
- 01
Observe
See the operation as actually performed across intake, delivery, exceptions and the records people really rely on.
- 02
Map
Make the operating system, evidence, handoffs and failure points explicit. Every material claim receives a declared state.
- 03
Deliver
Implement approved changes from the reviewed roadmap, with named owners, controls and acceptance criteria.
- 04
Measure
Determine adoption, exceptions and whether the change worked against the operating data it was meant to move.
Every conclusion should explain itself
The recommendation is not the evidence.
Source
The record, export or account the work is read from.
Rule
The declared, versioned test applied to that source.
Finding
What the record shows once the rule is applied.
Claim state
Supported, assumption, unverified or rejected.
Reviewer
A named second party who is not the author.
Decision
What leadership chooses to do, recorded separately.
Spendda separates what the record shows from what the team infers and what leadership ultimately chooses to do. That distinction remains visible through the engagement.
Engagement sequence
Transformation Diagnostic
See how the organization operates and establish the evidence-backed roadmap.
Transformation Implementation
Deliver the selected changes under explicit scope, controls and acceptance criteria.
Managed Intelligence
Monitor adoption, exceptions and operating change after implementation. Later-stage positioning, not a self-service product.
Common questions
What is a Transformation Diagnostic?
A bounded examination of how work actually moves, what the evidence supports, where the operating model fails and which changes deserve priority.
How long does a diagnostic take?
Duration follows the agreed scope. Bands, caps and milestones are stated in the proposal before work begins.
What information does Spendda need?
Policies, schedules, visit and task records, care documentation, incidents and system exports, plus access to the people who do the work.
Do you replace our existing software?
Not by default. Standardization and configuration of what you already run are considered before integration or any new build.
Can Spendda implement the roadmap?
Yes, as a separately scoped Transformation Implementation with named owners, controls and acceptance criteria.
How do you decide whether to configure, integrate or build?
Against the evidence: what the operating model requires, what current systems can do, and what remains unresolved after configuration.
Practice publication
Spendda Operating Notes.
Occasional field notes on operating models, integration, AI readiness and evidence-backed transformation.
Issue register
The first public note will be issued when its supporting record is ready. Future notes will be dated, sourced and reviewed.
Receive Spendda Operating Notes