.NET and SQL Modernization Trigger Radar for LongTermCapabilities

Full report

On this page

Executive finding

The strongest commercial position is not a generic “move legacy .NET to the cloud” assessment. Microsoft already offers funded migration and modernization assessments through Frontier Accelerate for Azure, while AWS Transform now automates portions of full-stack Windows modernization across .NET applications, SQL Server databases, and legacy user-interface frameworks. A cloud-readiness-only offer therefore risks being compared with subsidized or tool-assisted assessments.

LongTermCapabilities should reposition the approximately $30,000 blueprint as a:

Strangler and Data-Boundary Modernization Blueprint for one business-critical Microsoft application

The offer should determine how to modernize safely while the system remains in production, rather than merely identify outdated technologies. Microsoft’s current migration guidance supports this positioning: it says most production ASP.NET Framework migrations are non-trivial because session state, authentication, logging, caching, configuration, hosting, middleware, and request processing differ materially in ASP.NET Core. For larger systems, Microsoft recommends an incremental, strangler-style migration in which a new ASP.NET Core application proxies requests to the existing Framework application.

The blueprint’s core deliverables should be:

1. A route-by-route strangler sequence identifying the first production slice.
2. Authentication, session, configuration, caching, logging, and error-handling coexistence designs.
3. A SQL dependency map covering schemas, stored procedures, linked databases, jobs, SSIS or SSRS dependencies, reporting consumers, and transactional boundaries.
4. A supported-runtime and third-party-dependency matrix.
5. A target architecture with explicit decisions among ASP.NET Core, retained .NET Framework components, Windows or Linux containers, Azure or AWS services, and SQL deployment options.
6. A ninety-day implementation plan with effort ranges, rollback points, acceptance tests, and business sequencing.

The strongest immediate direct-account cohort is MRI Software, GFL Environmental, Porter Airlines, Zotec Partners, Motorola Solutions, and Allstate. DC Office of the Attorney General and the Judicial Branch of Arizona in Maricopa County have exceptionally strong evidence but should generally be approached through an existing public-sector prime, contract vehicle, or referral rather than as speculative direct pursuits.

Two older public-sector signals—New York Homes and Community Renewal and the Louisiana Department of Insurance—remain technically compelling, but the public evidence is too stale to justify active selling without a fresh procurement, budget, job, or program-status signal. Hiring, acquisitions, and modernization postings throughout this radar are treated as evidence of operating change, not evidence of distress or present buying intent.

Evidence model and offer design

Evidence rules

An account was admitted only when an organization-controlled source showed either direct legacy-stack evidence or multiple coherent signals. Examples include named use of ASP.NET Web Forms, WCF, classic ASP.NET MVC, Windows Services, .NET Framework, VB.NET, older Entity Framework, SQL Server stored procedures, SSRS, or an explicit migration to modern .NET, cloud infrastructure, or a new database platform.

A C# or generic “.NET developer” opening by itself was not considered sufficient. No personal repositories, private-person profiling, scraped contact data, vulnerability scanning, or speculative technical fingerprinting was used.

The account entries use four explicit categories:

• Verified public fact: What the organization or responsible public body actually disclosed.
• Analyst inference: A bounded interpretation of the likely architecture or business problem.
• Unknown: Information that cannot be established from the public evidence.
• Required human decision: A judgment LongTermCapabilities must make before spending selling or delivery capacity.

The ranking index is not a win probability. It combines seven favorable factors on a five-point scale: fit, evidence strength, speed to revenue, likely contract value, recurring potential, delivery ease, and access ease. Delivery ease is the inverse of delivery risk; access ease is the inverse of access difficulty. A stale-evidence cap was applied where the only direct signal was more than twenty-four months old.

Recommended commercial packages

The internal cost ranges assume a loaded principal delivery cost of $150–$180 per hour. That is not a public fact and must be replaced with LongTermCapabilities’ actual opportunity cost, benefits, non-billable overhead, and subcontractor economics before final pricing.

At $30,000 for 80–110 hours, the implied external rate is approximately $273–$375 per hour. Public GSA schedules show 2026 application and cloud-application architect rates ranging from roughly $131 to $228 per hour in one schedule, while another schedule lists a senior software architect rate of about $408 per hour. The proposed blueprint therefore sits above commodity architecture labor but below some senior-principal benchmarks; it is commercially defensible only when it produces decision-grade artifacts, executive facilitation, and a bounded implementation path rather than a tool-generated inventory.

The message must also avoid unsupported end-of-life fear. Microsoft states that .NET Framework 4.8 remains the latest Framework release and is supported according to the lifecycle of its parent Windows operating system. Some older Framework releases, including 4.5.2, 4.6, and 4.6.1, have ended support, while newer cross-platform releases such as .NET 6 have also reached end of support. The credible value proposition is therefore reduced change risk, deployment flexibility, talent leverage, delivery speed, data decoupling, and platform-option creation—not a blanket claim that every Framework application is unsupported.

Ranked trigger radar

Score notation: Fit / Evidence / Speed / Value / Recurring / Delivery ease / Access ease. Five is most favorable. The index is an opportunity-prioritization aid, not a probability.

Highest-priority direct and public-route opportunities

Qualified second-wave accounts

Lower-priority, partner, and watchlist accounts

Commercial economics and procurement

Why the strangler and data-boundary wedge is strongest

Application portfolio modernization sequencing is the best upmarket extension for product companies such as MRI Software, Wolters Kluwer, Thinkproject, and organizations with several court or agency applications. It supports $45,000 or larger engagements because the deliverable informs capital allocation across several systems.

Strangler-path architecture should be the central $30,000 offer. It directly addresses Microsoft’s recommended incremental-migration approach and the areas where production migrations become difficult: authentication, session state, configuration, logging, caching, hosting, middleware, and request semantics. System.Web adapters can support intermediate coexistence, including shared authentication and session behavior, but organizations still need application-specific decisions about routes, state, ownership, and cutover.

SQL dependency and data-boundary mapping should be inseparable from the strangler blueprint. Microsoft’s SQL assessment tools can identify target compatibility and sizing issues, including unsupported features, but they do not decide business ownership of tables, stored procedures, reporting workloads, cross-database transactions, or service boundaries. Microsoft’s own assessment guidance distinguishes configuration and performance readiness from the broader migration plan, and its rules show that features such as Service Broker and SQL Agent jobs can materially affect the feasible Azure SQL target.

Supported-runtime and dependency remediation is a useful $18,000 entry offer, especially when the public signal is clear but the strategic program is not. It should not be the flagship because .NET Framework 4.8 can remain supported, and the business value of a package report alone is limited.

Cloud migration readiness should be an extension or partner-funded work package rather than the headline offer. Microsoft advertises funded modernization assessments, Azure credits, and partner engagement funding, while AWS now supplies agentic modernization tooling. LongTermCapabilities should charge for the application-specific decisions those programs do not resolve, or deliver the architecture work under a qualified partner’s funded engagement.

AI enablement of a legacy Microsoft system should be offered only when the account has an explicit AI signal and a bounded use case. MRI’s posting explicitly references AI-assisted modernization, and the Maricopa court plan lists GitHub Copilot in the target environment. In those accounts, an AI addendum could define which legacy data and actions may be exposed to an assistant, the authorization model, audit requirements, retrieval boundaries, and prerequisite modernization. AI should not be used as a generic prospecting hook for the remaining accounts.

Procurement paths

For mid-market commercial accounts, the likely path is a direct fixed-fee professional-services agreement, an existing master services agreement, or a referral through Microsoft, AWS, a private-equity operating team, or an industry consultancy. The analyst sales-cycle estimate is four to ten weeks when a named application owner and decision deadline already exist.

For large regulated enterprises, direct vendor onboarding can involve security review, legal review, insurance requirements, data-handling terms, and preferred-supplier controls. The estimated cycle is eight to sixteen weeks unless LongTermCapabilities enters through an incumbent integrator.

For state, local, and federal accounts, the most credible first-revenue path is generally a subcontracted architecture work package. A principal-led boutique should not absorb the cost of an open-ended public procurement pursuit unless it has a relevant vehicle, a prime invitation, a small-purchase path, or a funded referral. Estimated subcontract cycles are four to twelve weeks after prime sponsorship; direct cycles can extend from twelve to thirty-six weeks.

For Capgemini, EPAM, and Leidos, LongTermCapabilities is not selling the blueprint as an enterprise transformation to those firms. It is selling a fixed-price, specialist architecture package that they can insert into a client program without hiring a permanent principal.

Recurring-revenue path

The blueprint itself is project revenue. Recurring value is credible only when it converts into one of three bounded continuations:

• A monthly architecture governance retainer for migration decision records, design reviews, and dependency exceptions.
• A sequence of application-by-application blueprints within a portfolio.
• Independent implementation assurance at defined gates: first route cutover, authentication coexistence, first database boundary, production readiness, and post-cutover review.

A practical continuation is $8,000–$15,000 per month for 20–40 principal hours, with a three-month minimum and explicit limits. LongTermCapabilities should not offer indefinite fractional-architect availability without a capacity cap, decision authority, and a defined portfolio.

Market-validation program

The ninety-day experiment should be deliberately narrow: six direct accounts, two public-sector prime routes, and three partner channels. It should test the offer, access model, pricing, and procurement friction—not assume that public signals translate to intent.

Opening month

The direct cohort should be MRI Software, GFL Environmental, Porter Airlines, Zotec Partners, Motorola Solutions, and Allstate. Each account receives a separate one- or two-page memo containing:

• The exact public signal and date.
• One architecture hypothesis, clearly marked as an inference.
• One diagram showing the likely decision space, not a claimed representation of the private system.
• The SDB-30 or RDR-18 scope.
• A request for a forty-five-minute technical validation conversation.

The public-sector track should target prime or contract-holder introductions for DC OAG and Maricopa County. No direct claim should be made that either body is ready to purchase the blueprint. The message to primes is that LongTermCapabilities can deliver an independent, fixed-price architecture and SQL-boundary package inside a larger modernization program.

The channel track should approach the .NET or cloud-modernization practice at Capgemini and EPAM, plus the relevant modernization delivery function at Leidos. The proposition is overflow architecture, independent validation, and client-ready work-package definition—not generic subcontract labor.

End-of-month evidence gates should be:

• At least six substantive responses from the eleven-account cohort.
• At least four technical validation conversations.
• At least two conversations in which a named application, decision deadline, and buyer role are identified.
• Clear evidence on whether $30,000 is viewed as a small professional-services purchase, a procurement-heavy engagement, or too high for pre-discovery work.

Failure to meet those gates should trigger a messaging or account-selection review, not increased outreach volume.

Middle month

The second month should convert qualified conversations into one of three artifacts:

• A two-page SDB-30 statement of work.
• A smaller RDR-18 statement of work where application scope remains uncertain.
• A PARTNER-20 subcontract work package.

LongTermCapabilities should conduct no unpaid code review and should not accept broad application inventories without a paid engagement. A pre-sale session can validate scope, decision authority, data access, environment constraints, and desired outcomes; it should not produce the blueprint’s core architecture.

The offer test should compare two messages:

Business-sequencing message: “Select the first modernization slice and prevent the migration from becoming a multi-year rewrite.”

Data-boundary message: “Determine what must move together, what can be separated, and where SQL coupling will defeat the application plan.”

Cloud savings, unsupported-platform warnings, and AI should not be the lead message unless the public signal directly supports them.

Closing month

The final month should aim for:

• One paid blueprint or remediation sprint in delivery.
• One additional proposal with an identified decision date.
• One qualified prime or integrator relationship capable of introducing a second client.
• A documented loss or no-go reason for every approached account.

The commercial review should compare:

• Direct versus partner-originated cycle length.
• SDB-30 versus RDR-18 acceptance.
• Required unpaid pre-sale hours.
• Legal and procurement burden.
• Actual principal delivery hours.
• Whether the output creates a credible implementation-assurance or portfolio follow-on.

The experiment should stop or materially change if twenty carefully selected, evidence-led approaches across ninety days produce fewer than three qualified technical discoveries; buyers consistently classify the work as a free cloud assessment; procurement costs exceed the expected gross profit; or qualified buyers demand implementation responsibility that LongTermCapabilities cannot staff safely.

Unknowns and required decisions

Verified conclusions

There is a current, visible market of organizations operating mixed .NET Framework, modern .NET, SQL Server, WCF, Web Forms, Windows Services, desktop Microsoft technologies, and cloud platforms. Several organizations explicitly describe incremental modernization, monolith decomposition, runtime migration, or database-platform changes in their own job or procurement materials.

Microsoft’s current migration guidance supports a specialized architecture service because the most difficult work is not simply recompiling code. It is preserving behavior and operating continuity across authentication, session, caching, configuration, logging, request processing, hosting, and mixed old/new application states.

Generic cloud discovery and automated source conversion are becoming less differentiated because Microsoft and AWS provide assessment funding, migration tools, and agentic modernization capabilities.

Analyst conclusions

The most defensible wedge is strangler sequencing plus SQL dependency and data-boundary mapping. It sits between inexpensive automated assessment and expensive implementation, and it produces a decision buyers must make before either internal teams or large integrators can execute safely.

The $30,000 price is plausible for a principal-led, decision-grade engagement, but it is not validated merely because public GSA rates can support the implied hourly rate. The market experiment must establish whether target buyers perceive the blueprint as a discretionary architecture purchase, part of implementation, or something a cloud provider should subsidize.

The most promising recurring model is not a generalized retainer. It is a sequence of application blueprints and implementation-assurance gates.

Material unknowns

Public sources do not establish the number of applications at most commercial accounts, the current architecture decision maker, available budget, incumbent consultancy, code quality, test coverage, deployment frequency, production constraints, data sensitivity, or whether a posting represents a funded program rather than ordinary team hiring.

The public evidence also does not establish whether job openings are net-new positions, replacements, or temporary capacity needs. None should be characterized as distress, urgency, or buying intent.

The true internal delivery cost is unknown. Gross-margin figures in this report depend on a provisional loaded principal cost of $150–$180 per hour and exclude unusual travel, insurance, security review, legal negotiation, sales time, bad debt, and subcontractor markups.

Required human decisions

LongTermCapabilities must decide whether it will:

• Maintain the $30,000 fixed price while enforcing an 80–110-hour delivery ceiling.
• Offer RDR-18 as a lower-friction entry or require every account to begin at the full blueprint.
• Work through public-sector and enterprise primes despite flow-down terms and lower account control.
• Pursue AWS as well as Azure modernization, or keep the practice Microsoft-cloud-centered.
• Include hands-on proofs of concept in fixed-price work, and if so, how much code or infrastructure work is permitted.
• Accept regulated healthcare, financial-services, airline, court, or public-sector data access.
• Carry required cyber, professional-liability, and errors-and-omissions insurance.
• Productize follow-on architecture assurance or remain blueprint-only.
• Build a repeatable SQL analysis toolkit while ensuring the client understands that tools inform—but do not replace—business and architectural decisions.

The principal no-go rule should be:

Do not pursue an account without a bounded application or portfolio, an identifiable title-based owner, a credible direct or partner procurement route, and delivery economics that remain acceptable after legal, security, and pre-sale effort.

Under that rule, MRI Software, GFL Environmental, Porter Airlines, Zotec Partners, Motorola Solutions, and Allstate warrant immediate validation; DC OAG and Maricopa warrant prime-route development; the next-wave commercial accounts warrant limited qualification; and New York HCR and the Louisiana Department of Insurance warrant monitoring but no active sales action until a fresh official signal appears.