Use hiring evidence to sharpen these questions, rather than to accuse a supplier of being understaffed:
- Which named people will deliver our project? Distinguish presales, architecture, configuration, migration and support.
- Which commitments are confirmed? Ask about start dates, substitution rights and competing allocations.
- Which work remains ours? Make data cleansing, control decisions, evidence review and acceptance explicit.
- Who owns integrations after go-live? Include monitoring, fixes and changes in source systems.
- What is the administrator handover test? Require the buyer’s team to perform representative changes.
- What capacity is included after launch? Define hours, service scope, exclusions and change pricing.
- Who evaluates AI changes? Include new model versions, prompt changes and permission-sensitive use cases.
- 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
- workiva.wd503.myworkdayjobs.com ↗workiva.wd503.myworkdayjobs.com