Best-fit conditions
A partner needs to test technical fit, client interaction, workstream boundaries, and the smallest credible next step without requesting extensive free presales.
Not a fit when
- There is no named client problem, opportunity, decision, or participant group.
- The partner expects a complete assessment, proposal response, or production architecture within the workshop fee.
- Required technical and account stakeholders cannot attend preparation, working sessions, or readout.
- The request is open-ended free presales or speculative solution design without a funded path.
What the buyer receives
- Joint discovery agenda and stakeholder map
- High-level current-state system or workflow map
- Named technical gaps, unknowns, and dependencies
- Preliminary workstream boundary and responsibility split
- Proposal-ready next-engagement recommendation
Delivery sequence
- Confirm partner role, account control, client trigger, timing, and commercial model.
- Conduct focused technical and operational discovery with direct stakeholder access.
- Map the system, decision, dependencies, and specialist workstream.
- Deliver the gap summary, responsibility split, and smallest credible next scope.
Decision value
- A low-risk test of technical and client-working fit
- A shared map before proposal commitments
- Clear partner, specialist, and client responsibilities
- A bounded next scope instead of open-ended presales
- A concrete bid, no-bid, team, or stop decision
Client responsibilities and scope assumptions
Client responsibilities
- Bring a named client problem and legitimate buying or capture context
- Provide direct access to relevant technical stakeholders
- Disclose known deadlines, eligibility, security, and commercial constraints
- Avoid submitting restricted or sensitive material through public channels
- Review and act on the next-scope recommendation promptly
Scope assumptions
- One named decision owner and one named technical owner
- A bounded system or workstream with timely access to representative evidence
- Public-safe qualification before confidential material is exchanged
- Client reviewers available for domain questions, disputes, and acceptance
Explicit exclusions
- A complete assessment or implementation plan
- Unlimited proposal writing or capture support
- Hidden staff augmentation
- Free custom architecture or code review beyond the workshop
- Commitment to bid, team, or perform before qualification is complete
Acceptance and commercial boundary
Acceptance: Accepted when the workshop, system map, gap summary, and next-scope recommendation are delivered.
Commercial boundary: The workshop is a paid qualification and scoping engagement. It does not reserve future capacity or guarantee a proposal, teaming relationship, or award.
Commercial partner-entry price. Solicitation-specific capture, proposal, and performance work is separately scoped.