Arabic (Modern Standard)
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.
Status report Feb 2027.pdf
Two-page status report: amber status, integration testing, open defects, risks R-07 and R-11, training.
DownloadBudget.xlsx
Approved budget against spend for each line, including the legacy CRM licence needed only if go-live slips.
DownloadBusiness case.docx
The renewal season and the revenue at stake, the expected benefits, and the steering committee's billing requirement.
Download
Listen to the debate
Watch the debate
Hear the same review in Arabic
The same documents and decision, argued in Modern Standard, Egyptian and Saudi Arabic.
Arabic – Egyptian
Arabic – Saudi
The decision brief she received
The full debate
Each colour is one side of the debate.
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
GPT, please start us off.
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.
Claude, how would you respond to GPT?
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
GPT, how would you respond to Claude?
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.
Claude, how would you respond to GPT?
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.
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.