Vardot Explains How Nonprofits Should Define Drupal Support RFPs

Nonprofit Drupal support RFPs should quantify expected support needs before vendors submit proposals, according to a guide published by Vardot. Mohammad Azouqa, vice president of business development at Vardot, wrote the guide, which was published on 14 June 2026 and updated on 21 July 2026. He argues that vague requests for ongoing support leave bidders making different assumptions about monthly hours, ticket volume, response times, and resolution targets.

The guide separates Drupal support agreements into proactive maintenance, reactive support, and growth work. Vardot places Drupal core and module updates, security patches, and monitoring under maintenance; bug fixing and editor assistance under support; and integrations, new features, and additional languages under growth work. It argues that defining those areas separately gives bidders a clearer basis for estimating the expected work.

For procurement, Azouqa recommends disclosing ticket volume from the previous 12 months, expected monthly support hours, urgent-ticket response expectations, service windows, hosting details, platform size, content update frequency, and internal team structure. For takeover projects, the guide advises attaching the Drupal Field list, Available updates, and Status reports and requiring a documented website audit before transition. It also recommends assessing bidders on relevant Drupal and nonprofit-sector experience rather than relying primarily on price.