Competing Regulatory and Revenue Requests Against One Fixed Budget
Two business units want the same $480,000. Regulatory Affairs needs a document-retention control by 31 March to close an open finding; missing the date carries a penalty of up to $50,000 per month and a mandatory disclosure. Sales wants a CRM integration supporting a pipeline the CFO has forecast at $1.2M this year. Engineering estimates retention at $310,000 and 11 weeks with the current two-person team; the CRM work at $260,000 and 9 weeks. Done sequentially, retention finishes in late April. Contracting one additional engineer for the quarter costs $95,000 and cuts each estimate by three weeks, but onboarding eats two of those weeks. Nobody has validated the $1.2M pipeline figure; the retention penalty and disclosure are contractual and confirmed by Legal.
1. Which work proceeds, and how do you handle the fact that the constraint is people rather than money?
Read the worked answer
Retention first, with the contractor, and CRM sequenced behind it.
The constraint is two engineers, not $480,000, so the real question is how many engineer-weeks exist before 31 March. Eleven weeks from today misses the date; adding the contractor nets three weeks of relief against a two-week onboarding cost - one week of gain, at $95,000, which is roughly two months of penalty exposure. That trade is favorable only if the one week is the difference between making and missing 31 March. Check that arithmetic before signing: if the schedule has float, the contractor buys nothing.
The CRM work does not compete on the same axis. Its value is an unvalidated forecast; the retention exposure is contractual, dated, and triggers disclosure. A disclosure has consequences that don't appear on the project P&L, which is exactly why it wins a contest against a revenue estimate with no evidence behind it. Reasonable answer: fund retention fully, fund the contractor only if it closes the gap, defer CRM with a stated start date, and send the $1.2M forecast back for validation before it earns a place in the queue.
2. Sales escalates to the CFO, who asks you to "just run both in parallel and accept some risk." How do you respond?
Read the worked answer
Don't argue priorities; argue capacity. Give the CFO a single arithmetic statement: two engineers, N weeks to 31 March, X engineer-weeks of confirmed work, therefore parallel execution means the retention control lands at a specific date - give the date - and the gap is not "some risk," it is a missed regulatory date with a stated monthly cost and a disclosure obligation.
Then offer the real options, priced:
- Retention only - date met, CRM starts in April.
- Retention plus contractor - date met, CRM starts earlier, cost $95,000.
- Parallel - retention date slips to a named date, penalty exposure from that date, disclosure triggered.
- Parallel plus two contractors - if a second contractor is actually obtainable and can be onboarded inside the window; often the answer is no, and saying so is useful.
Present it as a menu with consequences and let the CFO choose, in writing. That is not abdication; it is putting the trade where the authority is. The failure mode to avoid is accepting "some risk" as a phrase - convert every risk into a date and a number before it leaves the room.
3. What would make you reverse the sequencing decision?
Read the worked answer
Name the triggers in advance so the decision is auditable. Reverse or re-plan if any of these becomes true:
- The 31 March date moves or the finding is closed by other means (compensating control accepted by the regulator). Then retention's urgency collapses and CRM may lead.
- Retention estimate proves soft. If week-two discovery shows 11 weeks was optimistic, adding CRM in parallel doesn't just risk the date, it guarantees the miss - replan rather than push.
- The $1.2M forecast gets validated with a dated, contracted pipeline and a named customer commitment contingent on the integration. Then the revenue is no longer speculative and the comparison changes.
- A second contractor is available, which converts a sequencing problem into a money problem - usually the cheapest kind.
What would not change it: escalation volume, organizational seniority of the requester, or a promise that CRM will "pay for itself." Those are arguments about who wants it, and the decision is about which obligation has a date and a consequence attached. Also worth stating: if you find yourself reversing under pressure without one of these triggers being true, the original decision was probably made on preference rather than evidence.