Notes on legacy .NET migrations, system integrations, and software projects that need rescuing, written up from the engagements they came out of.
August 19, 2026
An agency was let go mid-build and the application sat unowned for two months. What that gap cost beyond the calendar, and what decays while nobody is responsible.
Read: Nobody at Our Company Owns the .NET Application AnymoreAugust 4, 2026
The documentation makes the migration look mechanical. On a production system it is a new project that reuses code, and verification is where the schedule goes.
Read: Migrating from .NET Framework to Modern .NET: Realistic Timeline and ScopeJuly 28, 2026
Outside help fixes a capacity shortage cleanly and a knowledge shortage only if structured for transfer. Misdiagnosing which you have is where money goes.
Read: When to Bring in Outside Help for an Integration vs. Handling It InternallyJuly 28, 2026
Four causes account for most schedule overruns, each with a distinct signature. Scope creep and communication issues are categories, not diagnoses.
Read: When a Software Project Runs Months Behind ScheduleJuly 21, 2026
3E, Aderant and Elite hold the canonical client and matter record. Integrations touching them inherit matter lifecycle state, fiscal period logic, and rate confidentiality.
Read: The Real Scope of Connecting Time and Billing Systems to Everything ElseJuly 21, 2026
Rescuability depends on two conditions: the completed work represents real progress, and the remaining scope is now accurately understood. Spend to date is not an input.
Read: Our Software Project Is Six Months Late and Over Budget: Is It RescuableDescribe the system and where it's stuck. You'll get a straight answer about what the work involves, including if the answer is that you don't need to hire anyone.
Get in touch