LEARN. PRACTICE. GROW.Define what is actually being bought
A migration proposal may include installation while excluding recovery, training, or decommissioning. Before comparing prices, describe outcomes, mandatory requirements, acceptance criteria, and each party’s responsibilities. Identify assumptions depending on the customer, such as providing access or test data. In the twenty-server example, adding five changes the set described in the proposal; an internally calculated unit price does not create agreement. Use a requirements table to locate exclusions and request clarification. Also compare the cost horizon: a low entry price may leave operation or exit uncontracted. The aim is to compare solutions to the same problem.
Choose conditions compatible with uncertainty
Fixed price for defined scope and hourly purchasing distribute exposure differently. No contract label removes the need to read conditions, exclusions, and changes. If dependencies remain unknown, a bounded investigation can produce information before committing the complete migration. Define the knowledge expected, authorized effort, and when to decide whether to continue. In hourly purchasing, the rate supports expenditure calculation but does not itself establish total effort. With fixed price, still consider supplier capacity, quality, and customer interfaces. The choice should consider who can manage each uncertainty and which conditions have been negotiated.
Calculate without confusing forecast and authorization
Calculate each component with the correct unit. In this lesson’s comparison, EUR 80 per hour for 120 to 200 hours produces EUR 9,600 to 16,000; EUR 95 for 100 to 140 hours produces EUR 9,500 to 13,300. These ranges remain estimates. An authorization ceiling does not automatically reduce required work. If EUR 20,000 has been consumed and 80 hours at EUR 100 remain, total forecast is EUR 28,000. Against EUR 24,000 authorization, a EUR 4,000 gap needs attention. Present options and assumptions before committing additional expenditure.
Negotiate options within authority
Prepare negotiation by distinguishing mandatory requirements, preferences, budget, deadlines, and viable alternatives. An alternative helps only if it can actually be executed under the required conditions. In the conditional-discount case, a public reference requires separate authorization and window exclusivity may affect other projects. Another offer can be explored without promising acceptance. Confirm who represents each party and what they may decide. Record proposals, conditions, and points still awaiting approval. The PM can coordinate technical and financial analysis with procurement and other owners; participating in negotiation does not mean being authorized to sign any organizational commitment.
Track evidence, changes, and commitments
Consumed hours, invoices, and presentations are useful data, but they do not replace evidence of agreed outcomes. If four milestones exist and two are accepted, identify their weights before calculating an overall percentage. Request remaining work and forecast alongside spent effort. An invoice containing unsupported hours should be reconciled against required records without inventing entries to close the gap. When new scope appears, follow the change condition described in the case: record the request, analyze impacts, and obtain an authorized decision before execution. Expose any commitment depending on an unconfirmed resource reservation.
Conclude procurement and prepare operation
Before closure, compare every obligation with fulfillment evidence: deliverables, scripts, documentation, training, temporary access, and agreed outstanding actions. In one case in this lesson, the service responds but editable scripts and access revocation are missing; the operational result does not prove closure of those obligations. Also distinguish defect correction from daily operation when the terms separate them. If nobody has accepted responsibility for night alerts, coverage remains missing even with a warranty. Keep ownership and deadlines for open actions and use the defined authority for changes or exceptions. These examples teach decisions under explicit conditions without interpreting real contracts.
Guided exercise: compare EUR 80/h for 120–200 hours with EUR 95/h for 100–140 hours. Calculate the ranges and identify information needed to decide. Then add the assumption that no contractual cap exists and explain why the upper estimate cannot be treated as a guarantee.
Common pitfalls
Comparing only rates; confusing estimates with caps; assuming fixed price removes every risk; accepting a partial demonstration as complete delivery; interpreting defect warranty as daily operation; negotiating beyond authority.
Related topics: Lead without becoming the bottleneck · Stakeholders, mandates, and cross-team decisions · Integrated planning: capacity, dependencies, and forecasts
Procurement should connect the required outcome to conditions, forecast cost, and acceptance evidence. Exercises use fictional contracts; real application depends on terms and competent owners.
Reference: The special challenges of project management under fixed-price contracts · PMP ECO July 2026; DR PMP 2026.5