Sample decision · fictional project

Should Northwind delay its CRM go-live?

A worked example of Mizan for Project Managers, from the documents a project manager uploads to the brief they receive. The company, project and figures are made up.

The case

Northwind is replacing its customer relationship management (CRM) system. The approved plan says go live on 15 March 2027, and the steering committee meets next week.

The February status report is amber. Data migration is almost done, but only 6 of 14 integrations have passed testing, and billing sync failed its last two test cycles. Meanwhile, the sales team's renewal season, about 60% of yearly revenue, starts on 1 April.

The project manager has to recommend whether to keep the date or delay to May. She uploaded three project documents and asked Mizan to debate it.

The question and the options

Should we delay the CRM go-live from 15 March to May 2027?

Brief in English · audio included

The documents she uploaded

Every fact in the debate and the brief comes from these files and cites them. Download them to check.

Listen to the debate

Download MP3

Watch the debate

Hear the same review in Arabic

The same documents and decision, argued in Modern Standard, Egyptian and Saudi Arabic.

Arabic (Modern Standard)

Arabic – Egyptian

Arabic – Saudi

The decision brief she received

MIZAN | ميزان · Decision brief

Should we delay the CRM go-live from 15 March to May 2027?

The decision is whether to keep the approved 15 March 2027 CRM go-live or delay it to May. The choice hinges on whether the current testing and defect levels are safe enough to support billing and renewal-season activity from day one.

The case for: Go live on 15 March

The approved plan already targets 15 March 2027, so this option stays aligned with the baseline schedule. Data migration is 92% complete, and the remaining Q2 2027 legacy CRM licence cost of USD 38,000 would be avoided if go-live does not slip past 31 March, which suggests a delay has a direct cost. (Status report Feb 2027.pdf, p.1; Budget.xlsx, sheet Budget, rows 1–7)

To choose this, you'd need to believe:
  • The remaining integrations and defects can be resolved before go-live without creating billing or renewal-season failures.
  • The cost of delay would outweigh the risk that billing does not work from day one.
  • Training progress is sufficient for sales staff to use the new CRM at launch.
The case for: Delay go-live to May

Only 6 of 14 integrations have passed end-to-end testing, billing-sync failed its last two test cycles, and the vendor estimates the remaining 8 integrations need 5 weeks with the current team; this suggests 15 March is too close to finish testing safely. UAT closed with 41 open defects, including 5 severity 1, and the steering committee required billing to work from day one, so delaying to May better fits the stated go-live quality bar. (Status report Feb 2027.pdf, p.1; Status report Feb 2027.pdf, p.2; Business case.docx, part 1)

To choose this, you'd need to believe:
  • The remaining 5 weeks of testing and defect fixing will materially reduce go-live risk by May.
  • The May delay will avoid a failure during the 1 April to 30 June renewal season.
  • The extra delay cost is smaller than the operational and revenue risk of launching on 15 March.

Main risks

  • A failed go-live during the 1 April to 30 June renewal season could disrupt quotes and invoices for existing customers, and about 60% of yearly revenue is renewed then. (Business case.docx, part 1)
  • Billing-sync failure at go-live is rated medium likelihood and high impact, which is especially material because billing must work from day one. (Status report Feb 2027.pdf, p.2; Business case.docx, part 1)
  • The key integration developer may leave at the end of April 2027 with high likelihood, which could make a May delay harder to execute if critical knowledge is lost. (Status report Feb 2027.pdf, p.2)
  • If go-live slips past 31 March 2027, the Q2 2027 legacy CRM licence cost becomes payable, adding USD 38,000 to the delay case. (Budget.xlsx, sheet Budget, rows 1–7)

Key assumptions

  • The remaining integrations can be completed by May with the current team or any replacement support.
  • The open UAT defects, including severity 1 items, are all fixable before launch.
  • A May go-live would occur before or during renewal season in a way that materially lowers risk, not raises it.

Open questions

  • Can the 8 remaining integrations realistically be fully tested and signed off before a May go-live?
  • Will the 41 open UAT defects, including 5 severity 1 defects, be cleared before either go-live date?
  • If go-live slips to May, how will the team mitigate the risk of the key integration developer leaving at the end of April 2027?
Recommendation

Delay go-live to May, because the evidence points to unresolved integration and billing risk being more important than the USD 38,000 licence saving. The remaining testing load, failed billing-sync cycles, open severity 1 defects, and the requirement that billing work from day one make the March date look too risky, even though the exact May timing still needs confirmation. (Status report Feb 2027.pdf, p.1; Status report Feb 2027.pdf, p.2; Budget.xlsx, sheet Budget, rows 1–7; Business case.docx, part 1)

Confidence: High · The key facts on testing progress, billing risk, open defects, and the renewal-season exposure are clear, and they consistently point toward delay.

Based on: Status report Feb 2027.pdf, Budget.xlsx, Business case.docx
Generated by AI from your documents (and the public sources listed) to support your decision, not to make it. Check key figures against the sources before acting.

The full debate

Each colour is one side of the debate.

GPT — Go live on 15 March
Claude — Delay go-live to May
David

Welcome to this decision review.

This debate was generated by AI from your project documents. It is here to support your decision, not to make it.

Our topic is: Should we delay the CRM go-live from 15 March to May 2027?

The advocates will use only facts from your documents: Status report Feb 2027, Budget, Business case.

GPT argues for: Go live on 15 March.

Claude argues for: Delay go-live to May.

Let's hear the case for each option.

Round 1

David

GPT, please start us off.

GPT · Go live on 15 March

I strongly advocate for the decision to go live on 15 March, as delaying could incur unnecessary costs and impact revenue generation. The status report indicates that 92% of customer records have been successfully migrated and reconciled, which demonstrates a high level of readiness. Moreover, the legacy CRM license for the second quarter of 2027 is $38,000, a cost we can avoid by launching on schedule. Additionally, the sales team’s annual renewal period from 1 April to 30 June brings in about $14 million, roughly 60% of our annual revenue. Successfully launching on 15 March positions us advantageously to capture this significant revenue. Delaying would risk losing momentum and could jeopardize these critical sales opportunities.

David

Claude, how would you respond to GPT?

Claude · Delay go-live to May

The strongest point is the renewal revenue, and I agree it matters. But that is the reason to delay. The business case, part 1, says about $14 million, roughly 60% of yearly revenue, renews between 1 April and 30 June, and a failed go-live would disrupt quotes and invoices for existing customers. Migrated records and a $38,000 license saving don't offset that exposure.

The status report shows only 6 of 14 integrations have passed end-to-end testing. Billing-sync failed its last two cycles on duplicate invoice records, and the vendor says the remaining 8 integrations need 5 weeks with the current testers. UAT also left 41 open defects, 5 of them severity 1. The committee required billing to work from day one, and the risk register rates billing-sync failure as high impact. I'd expect a May go-live to be the safer way to protect that $14 million.

Round 2

David

GPT, how would you respond to Claude?

GPT · Go live on 15 March

While I acknowledge the importance of protecting the $14 million renewal revenue, we must consider the financial implications of delaying the go-live. The status report indicates that data migration is 92% complete, meaning we are very close to full readiness. The legacy CRM license of $38,000 only applies if we go past 31 March, a cost we can avoid by launching now. Furthermore, the sales team's contract renewal season aligns with our planned go-live date, allowing us to leverage the new CRM to streamline processes and enhance customer engagement during this crucial period. Ultimately, proceeding with the 15 March go-live provides a vital opportunity to realize immediate efficiency gains and cost savings.

David

Claude, how would you respond to GPT?

Claude · Delay go-live to May

The strongest point is the $38,000 legacy license, and even taking that figure as given, it's small beside the roughly $14 million, about 60% of yearly revenue, renewed from 1 April to 30 June, according to the business case. Migration progress doesn't offset the status report, page 1: only 6 of 14 integrations have passed end-to-end testing, and UAT closed with 41 open defects, 5 of them severity 1. The vendor says the remaining 8 integrations need 5 weeks with the current testers, which I'd expect to run well past 15 March.

David

Thank you, GPT and Claude.

The decision brief sets out the strongest case for each option, the main risks, and the open questions.

This concludes our decision review.

Start your own decision — US$29