Restored Workshop / walnut and parchment

A legacy application modernisation proposal for a company running its core workflows on an old .NET application. It covers what the application does today and its downtime, how each workflow moves while the old system keeps running, a seven-month timeline, the team, a similar client’s results and three options from roadmap to full replacement.

Legacy Application Modernization Proposal

<h1 style="font-family:var(--proposal-font-heading);font-weight:400;line-height:1.08;letter-spacing:-.03em;text-align:left"><span style="font-size:clamp(36px,6.3cqw,58px)">Legacy<br>modernization</span></h1>

<p style="font-family:var(--proposal-font-heading);text-align:left;font-size:18px;line-height:1.5">Proposal for {{CLIENT_COMPANY}}<br>by {{SELLER_COMPANY}}</p>

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Thank you for the demo</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">You want to replace your quoting system without a day when your brokers cannot work.</p>

Brokers, account handlers and renewal staff

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">What the application does today</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">From the demo, a review of the code and your support log.</p>

Hours the application was down, by quarter

The application today

<h2 style="font-family:var(--proposal-font-accent);font-weight:500;line-height:1.14"><span style="font-size:clamp(30px,4.2cqw,52px)">We recommend replacing the application one workflow at a time, while the old system keeps running.</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Each workflow moves only when it passes the same tests as the old one.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">How each workflow moves</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Four parts, repeated for quotes, policy changes and renewals.</p>

<p>Before changing anything, we write automated tests that record what the old application does today: every rate rule, screen and document. About 300 tests for quotes alone.</p><ul><li>Tests run against the old and new versions</li><li>Any difference is flagged before release</li></ul>

Record what it does

<p>The new workflow is a web application on .NET 8 and Azure. It uses your current database at first, so both versions always see the same data.</p><ul><li>Rates kept in settings your team can change</li><li>Screens in the same order as today</li></ul>

Build alongside

<p>Ten brokers use the new quotes screen for two weeks, then half the team, then everyone. The old screen stays available until you switch it off.</p>

Switch over in stages

<p>When a workflow has run for a month without problems, we remove it from the old application. When all three have moved, the old server is switched off.</p>

Retire the old part

Our recommendation

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Seven months for all three workflows</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Work starts on {{START_DATE}}. The recommended plan covers the first two stages; you decide on the rest after quotes go live.</p>

<p>Code and database review, recorded tests for quotes, and a roadmap with costs.</p>

Assess

<p>The new quotes workflow, tested against the old one and rolled out in three stages.</p>

Quotes

<p>Same method, with account handlers testing the new screens.</p>

Policy changes

<p>Renewals move last because of the month-end batch. Then the old server is switched off.</p>

Renewals and switch-off

<p><strong>Not included:</strong> changes to how you price policies, new features beyond what the application does today, and Azure or third-party licences, which are billed to you directly.</p>

Timeline

Who you will work with

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Results for a similar client</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A freight broker, seven months from the first test to the last release.</p>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Options and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Three options. We recommend First workflow live.</p>

Four weeks to know the cost and risk of each step.

Assessment and roadmap

First workflow live

Every workflow moved and the old server switched off.

All three workflows

<p>Fees are in USD and exclude tax. Azure hosting and any licences are billed to you directly. This proposal is valid until {{VALID_UNTIL}}.</p>

Options and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Common questions</span></h2>

Questions

<p style="font-size:18px;letter-spacing:.08em;text-transform:uppercase">{{SELLER_COMPANY}}</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Next steps</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">How we start.</p>

Legacy Application Modernization Proposal - Preview