DIGITAL HOSPICE CARE — SERVICE SPEC v2025
Nobody builds a bad system on purpose. They build the right system for the problem they had — and then the business grows around it for ten, fifteen, twenty years until the system is holding everything up and nobody quite remembers how. That system doesn't need a $1.4 million rewrite quote. It needs someone who has been in this room before.
Hospice is an uncomfortable word. It's supposed to be. It names something everyone in the room already knows but hasn't said out loud.
In medicine, hospice isn't about giving up. It's about bringing genuine expertise to a situation that's been ignored too long — maintaining quality of life, managing pain, making hard decisions with clear information, and ensuring a dignified transition when the time comes. The people who do it well are some of the most skilled practitioners in the field.
Legacy systems need exactly this. And almost nobody in tech is honest enough to say so.
Digital hospice care is what happens between "we know it's a problem" and "we know what we're doing about it." It's the period — sometimes months, sometimes years — when the system needs to stay running, stay stable, and be genuinely understood before anyone makes a move.
Done right, it ends in a clean transition on your terms. Done wrong — or ignored entirely — it ends in a crisis on the system's terms.
I've spent 15 years doing this work. I'm good at it. And I'm the only person in this space willing to call it what it is.
The question isn't whether to act. It's whether you do it on your terms — assessed, stabilized, and planned — or whether a security breach, a talent departure, or a platform end-of-life forces your hand under pressure. One of those scenarios is significantly cheaper than the other.
Every hospice situation looks slightly different on the surface. Underneath, the symptoms are almost always the same.
SYMPTOM 001
This isn't a side system or an internal tool nobody uses. It's the thing the business depends on daily — the lead engine, the order processor, the client portal. Which is exactly why nobody will touch it.
SYMPTOM 002
The developers who built it are gone. The ones who inherited it learned just enough to keep it running and stopped there. The codebase IS the documentation — and it's written in a language half your team has never seen.
SYMPTOM 003
Every fix added something. Nothing was ever removed. Business logic is distributed across files, stored procedures, and config tables. Making a change means tracing dependencies nobody mapped and hoping you found them all.
SYMPTOM 004
The rewrite quotes have been terrifying. The risk of disruption feels worse than the cost of staying still. So the decision gets deferred — one more quarter, one more year — while the system gets more fragile and the options get more expensive.
SYMPTOM 005
The developer pool for legacy platforms shrinks every year. The ones who remain command a premium — and most won't take the job at any price. When your maintainer leaves, you may not be able to replace them.
SYMPTOM 006
Not in a dramatic way. In the slow tax of deferred decisions — workarounds that became permanent, features that couldn't be built, integrations that couldn't be made. The meter runs whether you're watching it or not.
"It's not failing. It's fragile. And that distinction matters — because fragile systems don't announce their failure. They degrade quietly until something forces the issue."
— DANIEL J. ALLEN · DRAFTINGDAN
Every engagement is different because every system is different. But the progression is always the same — and the sequence is not negotiable. We don't plan before we assess. We don't act before we understand. The work that looks like "doing nothing" at the beginning is the work that prevents catastrophic failure at the end.
| PACKAGE | DELIVERABLES | SCOPE & ENGAGEMENT | STRUCTURAL OUTCOME |
|---|---|---|---|
|
HOSPICE-01
SYSTEM STABILIZATION
Emergency Assessment & Risk Containment
ENTRY POINT
STARTING AT
$5,000
|
|
Fixed engagement. Codebase access required.
Delivered in 5–7 business days. NDA standard.
Does not require commitment to further engagement.
|
The acute risks are named and contained. You know what's
genuinely dangerous versus what's just old. The system is
stable enough to make a deliberate decision instead of
a panicked one.
|
|
HOSPICE-02
SYSTEM ARCHAEOLOGY
Full Business Logic Extraction & Options Assessment
FULL DIAGNOSTIC
INVESTMENT
$15,000
|
|
Fixed engagement. Requires codebase access and sessions
with current maintainers. Delivered in 10–15 business days.
NDA standard. Includes all deliverables from HOSPICE-01.
Feeds directly into Legacy Modernization engagement if
migration is the chosen path.
|
You know exactly what you're dealing with. Business logic
is documented. The options are real and costed. The decision
about what comes next can be made on evidence instead of fear
— and whichever path you choose, you start it informed.
|
|
HOSPICE-03
ONGOING STABILIZATION
Fractional CTO — Hospice Oversight
RETAINER
FROM
$3,500/mo
|
|
Monthly retainer. Minimum 3-month engagement.
Designed for organizations not yet ready to migrate
but unwilling to leave a critical system ungoverned.
Scale of involvement adapts to system stability
and organizational readiness.
|
The system is managed, not just maintained. Risk is
monitored. Leadership has a senior technical voice in
the room. When the decision to transition comes —
and it will come — you're ready for it instead
of scrambling.
|
"I've spent 15 years in the codebases people are afraid to touch. That's not a liability. That's the job."
— DANIEL J. ALLEN · DRAFTINGDAN
Most consultants who talk about legacy modernization have done it once or twice. I've spent the better part of 15 years doing almost nothing else — keeping aging systems stable, extracting the business logic nobody documented, and helping organizations make clear-eyed decisions about what comes next.
My background in civil engineering trained me that you never remove load-bearing structure without knowing what it's supporting. That discipline governs every hospice engagement I run. Nothing gets deprecated until we understand what depends on it. Nothing gets rewritten until the business logic is extracted and confirmed.
I'm completing a Master of Science in Software Engineering with an AI Engineering concentration. I'm not selling AI because it's a trend — I'm using it because it materially changes the economics of legacy work. Business logic extraction, code analysis, documentation generation — tasks that drove up costs for years are now AI-acceleratable.
I know how to apply these tools correctly, where they need human oversight, and where they fail. That distinction matters when your production system is on the line.
If the description on this page fits a system you're managing right now — tell me about it. We'll spend 30 minutes on the phone. I'll tell you what I'm hearing. If it makes sense to go further, we'll talk about what that looks like.
No sales deck. No proposal before I understand the problem. Just a straight conversation with someone who has been in this room before.
// SCHEMA: request.type = "hospice_assessment" → payload.destination = "draftingdan.com"