Controlspan / Field notes   Enterprise GRC intelligenceResearch edition · October 2026 · US market
Hiring signals / RESEARCH NOTE 11

What should procurement ask implementation and managed-service suppliers?

CONTROLSPAN RESEARCH DESKSECTION 05 · PAGE 11 OF 13Last updated 28 October 2026

Use hiring evidence to sharpen these questions, rather than to accuse a supplier of being understaffed:

  1. Which named people will deliver our project? Distinguish presales, architecture, configuration, migration and support.
  2. Which commitments are confirmed? Ask about start dates, substitution rights and competing allocations.
  3. Which work remains ours? Make data cleansing, control decisions, evidence review and acceptance explicit.
  4. Who owns integrations after go-live? Include monitoring, fixes and changes in source systems.
  5. What is the administrator handover test? Require the buyer’s team to perform representative changes.
  6. What capacity is included after launch? Define hours, service scope, exclusions and change pricing.
  7. Who evaluates AI changes? Include new model versions, prompt changes and permission-sensitive use cases.
  8. What leaves with us at exit? Specify configuration documentation, data relationships, attachments, history and runbooks for validation.

The distinction between sales and delivery is visible in the sample: Workiva’s role is explicitly presales, while LogicGate’s is implementation-focused. Our recommendation is to retain the useful presales evidence but contract against named delivery responsibilities and accepted outputs. (workiva.wd503.myworkdayjobs.com)

Sources cited on this page

  1. workiva.wd503.myworkdayjobs.com ↗workiva.wd503.myworkdayjobs.com
← PREVIOUS PAGEHow can buyers test whether a candidate or implementation team can do the work?NEXT →How should this desk monitor hiring signals without overstating demand?

Find the evidence.

Search across 188 research pages and 12 sections.