Check Buyer Implementation Capacity Before Promising a Start

Map buyer-side decisions, availability and ongoing ownership with a worked CRM cleanup readiness card and honest prepare, reduce-scope or defer options.

10/24/20263 min read

Alder’s available files contrast with unresolved ownership and paused full execution.
Alder’s available files contrast with unresolved ownership and paused full execution.

A buyer may have a relevant problem, a credible sponsor and an available budget yet still lack the capacity to implement a change. If the proposal ignores data preparation, internal decisions and ongoing ownership, the project can stall after approval. Explore the work the buyer would need to perform before promising a start date.

This is not a test of the buyer's commitment or willingness to work hard. It is a practical dependency review. Capacity includes authority, availability, access and operational support, not just the number of employees on an organization chart.

List buyer-side work explicitly

Identify the inputs and decisions your delivery depends on. Examples may include approving a field definition, supplying an authorized sample, confirming access or assigning a process owner. Do not assume the seller can perform those tasks merely because they affect the project.

For each item, ask who owns it, whether the person has accepted the responsibility and what competing work affects availability. Keep estimates as estimates. Avoid turning a rough discussion of effort into a guaranteed internal commitment.

Worked example: a small CRM cleanup

Fictional buyer Alder Services wants to clean a research database before a new process begins. The seller can propose mapping and validation work, but the buyer must decide which source is authoritative for account ownership. The relevant manager is unavailable during the proposed start period, and no delegate has been confirmed.

The completed readiness card reads: source files, available through an approved route; ownership definition, unresolved; decision owner, named but unavailable; authorized delegate, none confirmed; technical review, provisionally available; ongoing steward, not yet assigned. The result is not ready for full execution even though the files can be opened.

A useful alternative is a bounded preparation phase using synthetic data and a draft mapping, with no irreversible live cleanup. Another is to defer until the ownership decision can be made. The seller does not silently choose the definition or promise that delivery can absorb an unapproved policy decision.

Distinguish temporary gaps from structural ones

A person's holiday may create a short scheduling dependency. No role responsible for ongoing stewardship is a different problem. The latter can remain after implementation and should influence whether the proposed service is sustainable.

Ask what happens after the seller leaves. Who reviews exceptions, maintains definitions and approves changes? A process that works only while a consultant manually resolves every issue may not match the buyer's intended operating model. State that dependency honestly rather than calling the solution self-managing.

Offer scope changes with clear trade-offs

Reducing the first phase can be sensible, but explain what the smaller phase will not establish. Preparing a mapping is not equivalent to completing a validated migration. A pilot using synthetic records cannot prove that all live data issues have been resolved.

Do not remove security, privacy or quality checks merely to fit limited capacity. If a required review cannot happen, the dependent action should remain paused. Capacity pressure is not authorization to broaden access or bypass an approval owner.

Confirm readiness at the right time

A discovery conversation can identify likely dependencies, but readiness may change before work starts. Recheck material items at the agreed handoff. Preserve the buyer's actual commitments and do not treat silence as acceptance of new tasks.

The final artifact is a buyer-side dependency list with owners, availability, evidence and unresolved gaps. It supports proceed, reduce scope, prepare only or defer as legitimate decisions. Provenance and privacy principles help keep the input record accurate and proportionate, but the capacity worksheet is not a guarantee of delivery success.

A realistic plan protects the buyer from buying a service they cannot yet use effectively. It also protects the seller from promising an outcome that depends on internal decisions and effort nobody has agreed to provide.

Sources and related reading