Proof Strategies Website: Backend Development & CMS Implementation
| Estimated Investment | $15000 CAD |
| Pricing Basis | Fixed Fee |
Overview
Proof Strategies is rebuilding its corporate website alongside an active rebrand. A separate front-end developer is building the visual layer in Cursor, staged on the WordPress server, and the underlying WordPress backend and CMS still need to be built to support it.
This engagement covers that backend: a modular way to build and reuse content across pages, front-end integration and quality review, content architecture, migration, and the supporting infrastructure to launch and maintain the site.
Goals
- Integrate the front-end developer's components cleanly into a working WordPress build
- Migrate existing content over as desired, understanding slugs and structure may change as part of the rebrand
- Fully componentize the building-block system so Proof Strategies' team can create and assemble new pages on an ongoing basis without developer support for routine content
- Establish a reliable development, staging, and production workflow for review and approval
- Support lead generation and analytics needs, forms, personalized contacts, CTA tracking, using third-party tools where applicable, without owning the underlying marketing stack
Scope of Work
WordPress CMS & Modular Content System
Set up a flexible WordPress backend with a reusable module system: standard components available across pages, specialized ones scoped to specific pages. Editing happens natively in WordPress's block editor, not a third-party visual builder like Elementor or Divi. Modules are built as a mix of custom blocks and structured, field-based blocks depending on complexity, whichever keeps development efficient without compromising the editing experience. Once in place, Proof Strategies' team can assemble future service, industry, article, and landing pages themselves.
Front-End Integration & Quality Review
Review the front-end developer's Cursor-generated code for WordPress compatibility, modularity, and portability into the CMS. Flag what needs to change, and push back on anything unsuitable.
Content Architecture & Filtering
Set up custom content types and taxonomies (industries, services, case studies, work, news, stories) and employee tagging, with filters prioritized over a full search build. Predictive search is added if time permits, otherwise it's scoped separately.
Forms, Contacts & Lead Tracking
Build contact forms, newsletter management, and personalized contact modules that connect a specific Proof Strategies employee to the relevant service or industry page, tied into the lead management process. Also includes reviewing the existing jobs-listing plugin and deciding whether to keep or replace it.
Analytics Hooks
Add GA4 and Google Tag Manager support, with unique IDs and selectors for CTA tracking by page. Proof Strategies' analytics team configures the actual tags. I test and confirm tracking with them.
Migration
One batch migration of existing blog and content into the new structure where applicable, using a custom plugin and AI-assisted rewriting where useful. Includes redirects and preserving existing Yoast SEO data where applicable.
Hosting, Environments & Infrastructure
Set up or connect development, staging, and production environments on the existing WP Engine setup, or a recommended alternative, and recommend the right balance of custom development versus third-party plugins.
Assumptions
- The front-end developer's components are reasonably WordPress-compatible. This estimate assumes standard integration work, not a rebuild of the front end
- The front-end code is structured so it can reasonably be broken into components. Getting it into that shape, if it isn't already, is further iteration by their developer, not part of this scope
- WordPress login, current plugin list, and hosting access are provided at kickoff
- The existing WordPress backend, plugins, and hosting setup are in reasonably standard condition. A backend needing significant untangling before new work can start would need revisiting
- Migration is intended as a single batch pass, with content moved over where applicable rather than guaranteed wholesale. This may adjust if it turns out to need incremental handling
- The content types (services, industries, case studies, and the rest) are similar enough structurally to share a common field architecture. Any that need a genuinely custom data model would add time
- Proof Strategies' analytics team owns GA4 and GTM tag configuration. This scope covers hooks and IDs only
- No fixed launch date is locked yet. Delivery follows the project-wide timeline once shared
- This price assumes I'm working the engagement solo, with no subcontracted help
- Modules pull from WordPress's own content (posts, custom post types, taxonomies). A module needing live data from an external API, a jobs feed being the likely case, is a different level of complexity and gets scoped separately if the jobs-listing plugin review turns up a need for it
What's Not Included
Outside the base scope unless added back in:
- Building every individual service or industry page, the modular system supports Proof Strategies' team doing this
- Writing new site content or copy
- Configuring GA4 or GTM tags themselves
- Preserving every existing plugin or site structure
- Predictive or advanced search, unless separately scoped
- Front-end visual design, reviewed for technical integration only
- Full brand strategy, logo, naming, or a full visual identity system
- Photography, video, illustration, or stock asset sourcing
- CRM, marketing automation, or back-office integrations beyond what's scoped
- A formal accessibility audit or WCAG/AODA compliance sign-off
- SEO strategy or ongoing optimization beyond standard best practice and preserving existing Yoast data through migration
- Paid licenses, plugins, or hosting costs, billed direct to Proof Strategies
- Content changes requested after approval, beyond the included support window
- Live integration with external systems or APIs beyond WordPress's own content, scoped and estimated separately if the jobs-listing plugin review turns up a need for one
Payment
Net 30. Late invoices carry a 1.5% monthly charge.
Changes to Scope
Anything outside the scope above, or requested after acceptance, is treated as a change request rather than absorbed into the fixed fee.
Additional work rate: $150/hour plus tax. Larger changes get a fixed-fee quote instead.
Review & Client Responsibilities
- Primary points of contact: Connor and Alex Pogor at Proof Strategies
- Proof Strategies provides WordPress login, hosting and environment access, and the current plugin list, and connects me directly with the front-end developer
- Either side can end the engagement with written notice. If work has started, James invoices the greater of work completed or 50% of the total fee, minus any deposit paid. Deposits aren't refundable once work starts
Warranty & Ongoing Support
90 days on defects in what was delivered, within the agreed scope. Doesn't cover new features, new content, third-party changes, client edits, or anything requested after delivery.
Ongoing support retainer available separately: 10 hours/month minimum at $1000/month. Open to discussing something broader if the project's ongoing needs go beyond that.
Recommended Approach
- Prioritize filters over a full search build for launch. Revisit predictive search later if scope and budget allow
- Treat the front-end code review as an early checkpoint, not a late QA pass, so WordPress-compatibility issues get caught before they compound
- Handle migration as one batch pass rather than several incremental ones, using AI-assisted rewriting to speed up moving older content into the new module structure
- Lean on established plugins where they genuinely save time, and reserve custom development for what's actually specific to Proof Strategies
- Build custom modules as WordPress dynamic blocks, React for the in-editor experience, PHP for what actually renders on the site, so the front end stays fast and standard rather than shipping extra JavaScript to visitors
- Use a structured, field-based block where a full custom editing experience isn't worth the build time, and reserve a fully custom block for modules that genuinely need it
Acceptance
Valid 30 days from the date on the cover. Pricing may change if accepted later.
Let me know if this looks right and I'll get started as soon as WordPress access is in place.