TheUltimateChecklistforaWordPressDevelopmentCompany

Most WordPress vendor searches start with a portfolio review and end with a price comparison, and that's how businesses end up with a site that looks fine at launch and falls apart at the first plugin conflict. The questions that actually predict a good outcome are more specific than "can you show me examples."

Ask about their build stack before you ask about price

Not all WordPress is the same. Find out whether they build on a page builder (Elementor, Divi, Bricks), a block-based theme using the native Gutenberg editor, or a custom theme with Advanced Custom Fields and a component library. Each has a different cost-to-flexibility tradeoff:

A vendor who defaults to a page builder for every project regardless of client need is optimizing for their own delivery speed, not your five-year cost.

Get specific about hosting and who owns it

Ask directly: will the site be hosted on infrastructure you control, or on the agency's reseller account under their name. We've inherited client sites where the agency owned the hosting account, the domain's DNS, and the only admin login, and the client had no recourse when that agency stopped answering emails. Insist on WP Engine, Kinsta, or a managed VPS billed directly to your business, with your name on the account and a separate admin user for the agency.

Security and update practices, not just "we handle it"

Ask what their patch cadence is for WordPress core and plugin updates, and what happens when an update breaks something. A competent shop runs updates on a staging environment first, has automated backups (BlogVault, UpdraftPlus, or host-native snapshots) with at least 30 days of retention, and can tell you their process if a plugin has a known CVE — do they patch within 48 hours or wait for a scheduled window.

The checklist to walk into a vendor call with

• Do they build multisite or single-site by default, and does that match your plan to add more brands or locations
• What's their plugin philosophy — do they minimize plugin count or stack ten plugins to avoid custom code
• Can they show a site they built more than three years ago that's still running well, not just recent launches
• Do they test for WCAG 2.2 AA compliance, and can they show you an accessibility audit from a past project
• Who writes the content model — do they just build templates around whatever copy you hand them, or do they map content types first
• What's included in their post-launch support, and is it hourly, retainer, or bundled
• Do they disclose subcontracting — is the person pitching you the person who'll actually build it

Red flags worth walking away from

A quote that's dramatically below market ($2,000–$3,000 CAD for a multi-page business site) usually means either heavy template reuse with no customization or an offshore subcontractor with no ongoing accountability. Equally suspect: a vendor who can't explain their staging-to-production workflow, or one who insists you sign a contract before they'll answer basic technical questions about their build approach.

What a healthy engagement looks like from week one

Expect a discovery phase that produces a sitemap and content model before any design work starts, a staging URL you can review before launch, and a documented handoff that includes admin credentials, a list of installed plugins with licence keys, and written guidance on how to make basic content edits yourself.

If you're evaluating vendors right now and want a second opinion on a proposal you've already received, send it our way and we'll tell you plainly whether the scope and price line up.