Choosing a WordPress development partner affects SEO, security, and delivery speed for years. Portfolio thumbnails look alike; differences appear in git history, field Core Web Vitals, and how the team behaves when checkout breaks on a Friday.
Use this evaluation guide and checklist before signing — whether you consider Digital Neuma or other vendors.
Evidence to request in an RFP
Three references in your industry with named contacts willing to discuss problems — not only successes. Sample repository or anonymized code review showing theme structure, tests, and CI.
Lighthouse or WebPageTest before-and-after on a property similar to yours. Incident response SLA and who answers P1 overnight.
Allowlist and blocklist of plugins — partners who cannot explain banned plugins are guessing.
Red flags that predict pain
Only page-builder demos without custom block or theme work. Unlimited revisions without definition of done. No staging environment in the proposal. Hosting kickbacks without disclosure. No rollback story after failed updates.
Pre-kickoff and go-live checklists
Before kickoff: SOW with acceptance criteria, DPA if personal data, separate staging, design system attached. Before go-live: tested rollback, lowered DNS TTL, monitoring on checkout funnel, hypercare window defined.
Run a paid one-to-two-week trial sprint on a bounded deliverable — performance fixes or one custom block — before awarding a large fixed-price rebuild.
Technical interview questions
Ask about WooCommerce HPOS, object cache strategy, multilingual performance, when headless is justified, and who owns DNS at launch. Weak answers on checkout and caching matter more than buzzwords.
Contracting and governance
Define acceptance criteria per sprint: performance budget on templates, accessibility checks on forms, and security scan on dependencies. Change control in writing prevents scope arguments mid-release.
Require access to staging, version control, and deployment logs. You should be able to roll back without calling one person’s mobile phone.
Measuring partner performance
Track lead time from brief to production, defect rate in first thirty days, and Core Web Vitals on key URLs. Quarterly business reviews beat annual surprises.
If velocity drops while hours stay flat, inspect technical debt: plugin count, custom code without tests, and hosting misconfiguration.
Red flags when hiring
- No staging environment or “we edit live”.
- Parent theme edits without child theme.
- Twenty-plus plugins with overlapping features.
- No written backup and restore test in the last quarter.
Handover and knowledge transfer
Insist on recorded deploy runbooks, ADR for theme architecture, and a shadow sprint where your engineer ships one feature with partner review. Knowledge should live in repo and docs, not one consultant’s head.
Define a thirty-day warranty period after major releases for defect fixes at no additional scope cost — written in the SOW.
Frequently Asked Questions
- Freelancer for tiny scope; squad for roadmap and SLAs.
- Strong signal — reduces fixed-price surprises.