Description

A focused course, tailored for you

The Independent IT Consultant's Legacy-to-Modern Proposal Playbook

Win the next modernisation engagement with a written method that turns a thirty-year track record into a proposal a CIO actually signs.

The judgement that comes from thirty years of building the legacy and the modern side is real. The bottleneck is turning that judgement into a written proposal a CIO signs, a CFO funds, and an auditor defends.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Independent IT consultants who have lived through the full arc, from writing legacy applications to standing up modern cloud-native systems, hold a kind of judgement the in-house team rarely has. The constraint on the next engagement is almost never the technical answer. It is the proposal motion. A CIO wants a one-page recommendation by Friday. The board wants a modernisation answer for the next quarterly steering. The CFO wants a funding case that does not collapse under a sensitivity analysis. The audit committee wants a risk register that does not read as marketing. Every one of these artefacts has a specific shape the buyer recognises, and the difference between getting the work and losing it to a Big4 firm with a polished deck is whether the artefact arrives in that shape on the day it is asked for. This course is the written method for producing those artefacts on demand.

What you walk away with

A one-page modernisation recommendation a CIO can put in front of a board steering committee without rework.
A strangler-pattern sequence that funds itself one slice at a time and survives a CFO sensitivity analysis.
A risk register that an audit committee accepts on the first read and does not return with twenty questions.
A proposal pack that competes with a Big4 deck without a proposal team behind it.
A close-out artefact that turns the current engagement into the next engagement with the same client.

The 12 modules

Module 1. The Discovery Conversation That Surfaces Real Constraints

The first conversation with the CIO or CTO usually surfaces a sanitised version of the problem. This module walks through the discovery questions that get to what is actually constraining the modernisation. Vendor lock-in on the data layer, an audit finding the in-house team is quietly working around, a regulatory deadline nobody named in the brief, and the political constraint of which incumbent vendor cannot be displaced. Each question has a written prompt and a worked example.

Module 2. The Legacy Inventory Method That Avoids Months of Discovery

Most modernisation engagements lose the first quarter to inventory. This module gives a written method for producing a usable legacy inventory in two weeks, using a combination of source-code static analysis, runtime telemetry, and three structured interviews with the people who actually run the system. The output is a single spreadsheet the CIO can hand to procurement and audit on the same day.

Module 3. The Strangler-Pattern Sequence That Funds Itself

Big-bang replatforms get killed at the funding stage. The strangler pattern works because each slice pays for itself before the next slice is funded. This module gives the written sequence for choosing the first slice, the metric that proves the slice paid for itself, and the renewal conversation that funds the second slice. Includes the template that lays the whole sequence out for a CFO on one page.

Module 4. The Cost Case That Survives a CFO Sensitivity Analysis

Most consultant cost cases collapse the moment the CFO runs a sensitivity on the input assumptions. This module gives the written method for building a cost case that holds. The assumption register on its own page, the sensitivity range stated up front, the comparison to the run-rate of the legacy on its own line, and the three scenarios the CFO is going to run anyway. The CFO funds the case because the work was already done.

Module 5. The Risk Register an Audit Committee Accepts on First Read

Audit committees reject risk registers that read as marketing or as a list of generic IT risks. This module gives the written shape of a risk register that gets accepted on first read. Each risk is named in the language the auditor uses, mapped to a control the in-house team can actually operate, and tied to a residual rating the audit committee can defend. Includes a worked example from a bank core modernisation.

Module 6. The Vendor Selection Method That Does Not Look Bought

Vendor selection done by an independent consultant has to look genuinely independent. This module gives the written scoring method, the artefacts each vendor has to produce before scoring, and the conflict-of-interest declaration that goes to the audit committee. The output is a written recommendation a procurement function can defend if it is later questioned by an internal auditor or a regulator.

Module 7. The Proposal Pack That Competes With a Big4 Deck

Big4 firms win on the proposal pack, not on the technical recommendation. This module gives the structure of a proposal pack an independent can produce in a week, that competes on credibility with a Big4 deck. The cover memo, the one-page approach, the team page that turns a long career into a credible delivery story, the references page, the price page, and the assumptions page. Each section has a written template and a worked example.

Module 8. The Reference Architecture Diagram a CIO Forwards

Most reference architecture diagrams sit in a proposal and never leave. This module gives the rules for a diagram a CIO forwards inside the organisation as their own recommendation. One page, the legacy on the left, the modern on the right, the strangler boundary in the middle, the regulatory constraints overlaid, and the funding sequence numbered. Includes a draw.io and a slide template.

Module 9. The Implementation Plan a Steering Committee Can Govern

Implementation plans that read as a Gantt chart get governed as a Gantt chart, which is to say poorly. This module gives the written shape of an implementation plan a steering committee can actually govern. Decisions the steering committee owns, decisions the consultant owns, the escalation path, the change-control method, and the monthly steering pack. Each artefact has a template.

Module 10. The Knowledge Transfer Method That Does Not Get Skipped

Knowledge transfer is the line item that gets cut when the budget is tight, which is exactly when the client is most exposed. This module gives the written method for embedding knowledge transfer into the work itself, so it cannot be cut without the work itself being cut. Pair programming windows, written runbook obligations on each delivery slice, the operator handover document, and the post-engagement review.

Module 11. The Close-Out Artefact That Wins the Next Engagement

Most engagements close with an invoice and a thank-you. The close-out artefact this module specifies wins the next engagement with the same client. The written summary of what was delivered, the named risks that remain on the client's roadmap, the recommended next slice with a written rationale, and the conversation script for the renewal meeting. Same client, second engagement, no procurement cycle.

Module 12. The Written Point of View That Brings Inbound Inquiries

Independent consultants who publish a written point of view on legacy-to-modern modernisation get inbound inquiries from CIOs who have already half-decided. This module gives the method for producing one written point of view per quarter, what each piece has to contain to be credible to a CIO, where to publish it, and the follow-up motion that turns a reader into a conversation. The output is a publication cadence sustainable alongside a full delivery load.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

When the CIO asks for a one-page recommendation by Friday and you need a written method to produce it cleanly, modules 1, 3, and 8 are the working set.

When the CFO is about to run a sensitivity analysis on your cost case, modules 4 and 9 are the artefacts you bring to the meeting.

When the audit committee has rejected the last risk register and the CIO needs a clean version, module 5 is the one you open first.

When the engagement is closing and the client has not yet committed to the next slice, modules 10 and 11 turn the close-out into the next sale.

What you get with this course

Twelve written modules with worked examples drawn from real legacy-to-modern engagements.
Downloadable templates for every artefact named in the modules, including the one-page recommendation, the cost case, the risk register, the proposal pack, and the close-out summary.
The hand-built implementation playbook, tuned to the consultant's specific account mix and current pipeline, delivered alongside course access.
Lifetime access to the course in the Art of Service learning environment.
Thirty-day refund if the method does not produce a proposal artefact the consultant can use on a live engagement.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours of purchase the learning environment account is provisioned and the tailored implementation playbook is delivered alongside course access.

Modules can be worked in sequence or pulled individually as a current engagement demands.

Templates are downloadable from day one and usable on a live engagement immediately.

Before and after

Before

Every new engagement starts with a blank page. Proposals get written from scratch each time. The cost case is improvised. The risk register comes back from audit with twenty questions. Big4 firms win the work that should have gone to the independent because their proposal pack arrived in the right shape on the day it was asked for.

After

Every new engagement starts from a written method. The proposal pack assembles in a week from templates that already exist. The cost case survives sensitivity analysis on first review. The risk register gets accepted by audit on first read. The close-out artefact turns the current engagement into the next engagement with the same client, no procurement cycle, no Big4 competing.

What happens if you do not address this

Independent IT consultants who do not codify their proposal motion stay capacity-bound. Every engagement is a one-off. The next engagement competes with a Big4 firm on the proposal pack, and the Big4 firm wins the work the independent should have won on judgement. The thirty-year track record stays inside the consultant's head instead of being visible in the artefacts the buyer sees.

Who it is for

Independent IT consultant with a long career spanning legacy application development through modern systems work. Typically advising banks, telcos, government agencies, and regional groups in the Middle East and wider region on whether and how to modernise a core. Wins work on reputation and the last engagement. No back-office marketing function, no proposal team. The bottleneck on the next engagement is almost always the proposal, the cost case, and the risk artefact, not the technical recommendation.

Who this is NOT for. Not for in-house enterprise architects on a salary. Not for Big4 partners who already have a proposal factory behind them. Not for early-career consultants who do not yet have the engagement record this method depends on.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly eight to twelve hours of reading across all twelve modules. The templates are usable on a live engagement on the day of purchase. The implementation playbook is tuned to current pipeline, so the time-to-first-use on a real proposal is the same day.

Why $199 is the right number

Free LinkedIn posts on legacy modernisation describe the trend, not the method. Generic PMI or PRINCE2 templates assume an in-house delivery function, not an independent consultant. A Big4 firm's internal proposal kit is not available to independents at any price. This course is the written method for the proposal motion an independent IT consultant actually runs.

FAQ

I have thirty years in IT. Will this teach me anything I do not already know?

The technical recommendations in your head are not what this course teaches. It teaches the written method for turning that judgement into the proposal, cost case, risk register, and close-out artefacts the buyer recognises. Most experienced independents already know the answer. The course teaches the written shape that gets the answer funded.

Is this just templates I could find elsewhere?

Templates exist for many of the artefacts on the open web. What is not on the open web is the written method for which artefact to produce, in what order, with what content, for which conversation in the engagement. The course is the method. The templates are the implementation.

I work mostly with banks and telcos in the region. Does this apply?

Yes. The method is built around the conversations a CIO, CFO, and audit committee have in any regulated environment. The worked examples include bank core modernisation and telecom OSS/BSS replatforms. The regulatory overlay in module 5 is adaptable to the local supervisor and the local audit standard.

How fast can I put this to use on a live engagement?

Same day. The implementation playbook delivered alongside course access is tuned to current pipeline, so the first template the consultant downloads is one the current engagement actually needs.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.