WordPress Marketing Website Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A custom WordPress block theme with 8 page templates listed in Schedule A and up to 16 custom Gutenberg blocks.
2. 2.2Agency population of up to 20 pages using client-supplied final copy and images. Remaining pages are populated by the client using the trained editor workflow.
3. 2.3Three HubSpot forms embedded and styled (contact, newsletter, gated asset), with submissions routed to the client's HubSpot portal.
4. 2.4Configuration of the plugins listed in Schedule B: SEO, caching, security, redirects and forms.
5. 2.5Technical SEO setup: XML sitemap, meta fields, Open Graph tags and 301 redirects for up to 150 legacy URLs.
6. 2.6Deployment to the client's managed WordPress host with staging and production environments.
7. 2.7A 60-minute editor training session and a written editing guide.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Copywriting, content strategy, photography and illustration.
2. 3.2Population of pages beyond the first 20.
3. 3.3Multilingual sites, membership areas, e-commerce and custom post type archives not listed in Schedule A.
4. 3.4Integrations other than HubSpot forms, such as CRM sync, ATS feeds or event platforms.
5. 3.5Hosting, domain, premium plugin licenses and email delivery services.
6. 3.6Ongoing content updates and plugin updates after the 30-day warranty period.

Designs include two consolidated revision rounds per template on desktop and mobile. The staged build includes one consolidated round of visual fixes before launch. Content changes after population are the client's to make in the editor.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1Each template renders correctly in the latest two versions of Chrome, Safari, Firefox and Edge, and on iOS Safari and Android Chrome.
2. 5.2Lighthouse performance score of 85 or higher on mobile for the home page and one representative inner page, measured on staging with final images.
3. 5.3All forms submit to HubSpot and trigger the agreed notification emails.
4. 5.4The client has five business days after staging handoff to report defects. Launch counts as acceptance.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1Final, approved copy and images for agency-populated pages arrive before the population phase starts.
2. 6.2The client provides hosting access and DNS changes within two business days of request.
3. 6.3One marketing lead consolidates stakeholder feedback.
4. 6.4Brand guidelines exist and are not being changed during the project.

A change is any new template, block, form, integration, plugin, language or page population beyond the cap, and any change to an approved design. The agency replies with a change order within two business days stating the work, hours, cost and effect on the launch date. Small changes under 2 hours may be batched into one monthly change order with the client's agreement.