Technical due diligence
A field-service platform's core still runs on .NET Framework, with a WinForms client alongside it
A field-service and facilities-management platform whose core scheduling, CRM and billing system runs on an older .NET Framework foundation, paired with a legacy WinForms desktop client — a combination that's been in maintenance-only mode since 2020. Technical due diligence for this pattern: $10,000–$25,000, one to three weeks.
What we find
The core scheduling, CRM and billing platform runs on an older .NET Framework foundation, not the current .NET line, paired with a legacy WinForms desktop client for field technicians. Both have been in maintenance-only mode since 2020 — meaning no further feature investment from Microsoft on the framework itself, only security patches, while the vendor keeps building on top of it. That's a common pattern in small vertical-market software: the framework choice made sense when the product was built, and nobody has had the budget or the reason to revisit it since.
Why it matters for a PE holder
For a buyer evaluating this kind of platform, the risk isn't that it stops working — .NET Framework is stable and well-supported for years yet. It's what the framework choice costs going forward: a shrinking pool of engineers who want to work in it, a WinForms desktop client that can't share code with any future web or mobile build, and a migration that gets more expensive the longer it's deferred. None of that shows up in a demo or a sales call. It shows up in a codebase.
What the engagement checks
The diligence engagement scopes the framework-migration path, cost and timeline for both the legacy desktop client and the back end — before or after close. That means what actually depends on .NET Framework versus what could move to the current line without a rewrite, what the WinForms client would cost to retire or wrap, and a realistic estimate of engineering time, not a guess.
$10,000–$25,000, one to three weeks. We read what a target company's codebase, dependencies and infrastructure actually run, find the specific legacy-stack or security exposure it carries, and hand back a report scoped enough to become the remediation plan — if the deal proceeds and one is warranted.
This pattern is drawn from public research on a real, small software company, not a completed Shashtram engagement. Named engagements with measured figures replace it as clients clear being named.
One pattern, not the whole offer
This is one pattern. The full technical due diligence offer covers pricing, what the report contains, and answers to the questions PE operating partners actually ask.
Diligence is Map, scoped to one question and priced on its own — not a separate product, and never an assumed rewrite.
Questions
Straight answers.
What if we don't proceed to a rebuild after the report?
Then the report is what you paid for, and the engagement ends there. Nothing about the diligence commits you to a modernization project — most of the value in a $10,000–$25,000 read is knowing what you're actually buying, whether or not you act on it afterward.
Start here
Bring us one workflow.
Tell us the process that crosses the most systems. You get a scope, a measure and a delivery plan back — and a straight answer if we think it is not worth building.
Get in touch