Resource Procurement Planner

A startup founder whose resource acquisition pattern is entirely reactive: he buys equipment or services when a specific need creates pain, not when the plan requires it. The result is a mix of emergency purchases at premium cost and delayed procurement that creates bottlenecks. He has never mapped what the business needs over a defined horizon before buying anything.

Frame the planner as a demand-ahead map, not a shopping list. 'The goal here isn't to list what you want - it's to map what the business will need, in what order, and on what timeline. Once we have that picture, the purchases stop being reactive and start being planned.' The resistance is velocity: he's in execution mode and planning procurement feels like slowing down. Name the cost of the current pattern: 'Every emergency purchase costs more and creates disruption. The plan pays for itself in the first two emergency purchases it prevents.'

Watch the priority tier assignments in the procurement plan. Clients in reactive mode often assign everything as Priority 1 - everything feels critical because they're making decisions under urgency rather than from a plan. If more than three items are Priority 1, he hasn't differentiated, and the procurement plan will replicate the reactive pattern. Also watch the acquisition model column: founders often default to purchase when lease or subscription options would preserve capital during early growth.

Start with Priority 1 items. 'You've listed five Priority 1 items. What happens to the business if each of these doesn't arrive in the next 30 days?' That question usually differentiates genuine P1 from habitual-urgency P1. Then look at the budget summary by tier: 'What's the total for P1 items? Is that capital you have available right now?' The question that creates movement: 'If you had to sequence these five P1 items and could only acquire one per month, what's the order - and does the plan hold up under that constraint?'

A professional services owner with several resources she believes are underused - a studio space, specialized software licenses, equipment. She's considering whether to expand. But she has never measured actual utilization of what she has. The current resource inventory section of the planner, which asks for utilization rates, may reveal that her existing resources aren't underused - they're just unevenly used across the week.

Before she fills in the procurement plan, anchor her in the inventory section. 'Before we talk about what you need, let's establish what you have and how much of it you're actually using. Utilization data changes the procurement decision significantly.' The resistance is the assumption: she believes she knows her utilization pattern. 'Utilization feels obvious until you measure it. Let's see what the actual numbers say before we plan the next acquisition.'

Watch whether she can provide actual utilization figures or estimates. If all her utilization entries are estimates ('maybe 60%'), she doesn't have the data - she has a belief. The distinction matters: if the actual utilization is higher than she believes, procurement is justified. If it's lower, she has unused capacity she hasn't addressed. Also watch the budget summary: clients who haven't measured utilization often project acquisition costs without modeling the revenue the acquisition would generate.

Start with utilization. 'Read me the utilization rates in the current inventory. Which ones are estimates and which ones are based on actual tracking?' Then: 'If your estimates are off by 20% in either direction, how does that change the procurement case?' Then look at the procurement plan: 'Of the items you're planning to acquire, which ones are replacing genuinely low-utilization assets versus filling a real gap?' The question that creates movement: 'Before we finalize the procurement plan, what would you need to measure for 30 days to know whether you need what you're planning to buy?'

A department manager at a mid-size organization who knows exactly what her team needs: new software, additional equipment, a contract resource. She has asked her director twice and been told to resubmit with 'more justification.' She has the needs identified but has never structured the business case in a way that maps priority, cost, timeline, and acquisition model in a form that a financial decision-maker can evaluate.

Frame the planner explicitly as a business case document, not an internal worksheet. 'What you've built before were requests. This tool produces something different: a structured procurement plan with priority tiers, cost estimates, acquisition model rationale, and timeline. That's the format that finance reviews - not a description of the need, but a plan.' The resistance is frustration: she's described the needs clearly and doesn't understand why that wasn't enough. Name the audience translation gap: 'Finance reviews hundreds of requests. The ones that get approved are the ones that answer their questions before they ask them.'

Watch the acquisition model column specifically - this is the column that demonstrates financial thinking rather than operational thinking. If every item is listed as 'purchase' without considering lease, subscription, or phased acquisition, she hasn't addressed how the organization prefers to manage capital. Also watch whether the budget summary by priority tier includes a cost-per-outcome frame - finance is more responsive to 'this $12,000 investment enables $X in output' than to 'we need this equipment.'

Start with Priority 1. 'For each Priority 1 item, what does the business gain that it can't currently do without this resource?' That frames the case. Then look at the acquisition model: 'Have you considered whether any of these could be leased or subscribed rather than purchased - and does that change the upfront ask?' The question that creates movement: 'If your director saw this plan in the next budget meeting, what question would he ask first - and does this document answer it?'