The requirement
Capture the current problem, desired outcome, services involved, and the date driving the project. Identify the sponsor and the people who will operate the service. Separate essential requirements from preferences.
Our approach
A provider shortlist is more useful when the buying team agrees on the problem it is meant to solve.
The starting point is a suitable project, a real business need, and a buying team prepared to work through the decision.
Establish company scope, buying authority, project scope, decision timing, and whether the advisory need is a fit.
Record the problem, operating constraints, essential requirements, and a practical description of success.
Use the same brief to examine provider scope, assumptions, trade-offs, and unresolved questions.
Confirm the selected provider’s scope, implementation responsibilities, and the support arrangement before commitment.
Prepare a decision the team can review
A shortlist is an intermediate step. The working record should show why an option meets the requirement, what remains uncertain, and who needs to resolve it.
Capture the current problem, desired outcome, services involved, and the date driving the project. Identify the sponsor and the people who will operate the service. Separate essential requirements from preferences.
Use the same questions for each provider. Record its answer, the supporting evidence, exclusions, dependencies, and costs. Mark an unconfirmed capability as an open item instead of treating a demonstration as a contractual commitment.
Explain the proposed choice, alternatives considered, remaining risks, and conditions of approval. Give finance the cost assumptions and give the operating team the proposed handoffs, tests, and support responsibilities.
Start with a short explanation of the business need, your buying role, project location, and timing. Existing proposals, renewal dates, or a rough requirement can help later, but you do not need to complete a technical specification before describing the project.
The Project Fit form covers security, communications, contact centers, SD-WAN, business internet, and multi-site connectivity. There is no minimum project budget or company-size cutoff. Sending the form shares an enquiry for Mischa's advisory review; it does not commit either party to an engagement.
Confirm which evaluations, provider discussions, and project stages the engagement covers. Identify the decisions your organization retains and any specialist work that needs a separate scope. Implementation ownership and continuing advisory involvement should be documented rather than assumed.
Mischa DuPont sits on the advisory panel. His background includes technology advisory, strategic accounts, and project delivery. Read his experience and professional background.
Implementation and ongoing service responsibilities should be agreed explicitly. Ask who owns the transition, who accepts the work, and who handles issues after go-live. The scope of any continuing advisory involvement should be documented for the project.
Our buying guides and Decision Brief help you prepare these questions before a consultation.
Create a decision brief ↗For active business projects
We review your business need, buying role, and timing before discussing a call.