Opens in a new tab
Our Process

A clear process for better WordPress development.

From the first brief to launch and ongoing improvements, we approach WordPress projects with clear requirements, practical technical decisions, careful development and thorough testing. The exact workflow adapts to your project, not the other way around.

  1. 01DiscoverBrief, goals and constraints
  2. 02ScopeDeliverables and a plan
  3. 03DesignSupplied by you, or sharedIf included
  4. 04BuildArchitecture and code
  5. 05ReviewTesting and feedback
  6. 06LaunchRelease and handoff
  7. 07SupportFixes and improvementsWhen scoped
Typically part of the workOnly when included or scoped
Overview

The right steps for the right project.

A brand-new WordPress build, a complex WooCommerce integration and a small technical fix are different engagements, so the process scales to fit. An agency that brings approved Figma screens does not need to buy design from us, and an urgent fix does not go through a seven-stage discovery workshop.

Defined requirements before development

What is being built, and what is not, is written down first.

Staging and review where appropriate

Changes are checked in a safe setup when the project calls for it.

Testing before release

Key journeys are checked against the agreed scope.

Clear handoff and documented next steps

You know what was done, and what could come next.

This page covers how the work is delivered. For how we collaborate with agencies, including communication, approvals and white-label coordination, see How We Work.

How We Work →
The stages

Seven stages, used as the project needs them.

Think of these as stages of thinking rather than a fixed checklist. Which ones a project uses, and how deeply, depends on its size, risk and starting point.

Stage 01Discover & Understand

Start with the actual problem.

We review the brief, goals, existing website and technical constraints. For established sites, we identify the dependencies and integrations that could affect the work.

Potential outputs
RequirementsRelevant access checklistKnown constraintsInitial questions
Dependencies we look forIllustrative
Theme and builderPluginsHosting and DNS
Existing siteWhat the work touches
IntegrationsForms and emailData and content

For an established site, we map the dependencies that could be affected before any scope is written.

Stage 02Scope & Plan

Turn requirements into a workable plan.

We define the deliverables, assumptions, responsibilities and a realistic implementation approach. For larger engagements, we map dependencies and milestones so everyone knows what will be built and reviewed.

Potential outputs
ScopeEstimateMilestonesAssumptions and exclusions
A scope, in outlineIllustrative
DeliverablesWhat will be built and reviewed
AssumptionsWhat we are relying on to be true
ExclusionsWhat is out of scope, written down
ResponsibilitiesWhat we handle, and what your team provides
Milestones and review points
  1. Milestone 1Agreed per project
  2. Review pointFeedback gathered
  3. Milestone 2Where it applies
  4. DeliveryFinal approval
Stage 03Design & ExperienceIf included

Work from the right design foundation.

We implement approved designs from your team, or collaborate on design when it is part of the agreed scope. Responsive layouts, content structure, accessibility and usability are considered before complex build decisions are locked in.

Design is never a requirement. If your team already has approved layouts, this stage is simply skipped.

Two routes to the same foundationIllustrative

Supplied by your team

  1. Approved layouts and specs
  2. Technical review

Part of the agreed scope

  1. Collaborative design
  2. Your approval
Then the build decisions are locked in

Responsive layouts, content structure, accessibility and usability are considered first.

Stage 04Architecture & Development

Build for maintainability, not just launch day.

We choose appropriate WordPress patterns, plugins, custom code and integrations, then implement functionality with attention to clean structure, performance and future changes. That may include Bricks, Breakdance, Elementor, ACF, WooCommerce, PHP, JavaScript or custom APIs, as relevant to the project.

Layers we plan aroundIllustrative
  • Templates and componentsResponsive layouts as reusable parts
  • BuilderBricks, Breakdance or Elementor, as the project needs
  • Custom codePHP and JavaScript where plugins fall short
  • Plugins and integrationsACF, WooCommerce, APIs and third-party services
  • WordPress and hostingThe foundation everything else depends on
Stage 05Quality Assurance & Review

Test what matters before release.

We review responsive layouts, critical user journeys, forms, store functionality, integrations and regressions according to scope. Feedback is collected and addressed before final approval.

Possible checks
FunctionalityKey browsers and devicesPerformance basicsAccessibility checksRegression review
What a review can coverIllustrative
  • Responsive layoutsKey browsers and devices
  • Critical user journeysThe paths that matter most to the site
  • Forms, store functionality and integrationsAccording to what is in scope
  • Performance basics and accessibility checksPractical checks, not an audit unless scoped
  • Regression reviewNothing that worked before has quietly broken
Feedback collectedAddressedFinal approval
Stage 06Launch & Handoff

Release carefully, then hand over clearly.

Once approved, we coordinate deployment, validate key functionality and provide a clear handoff. Launch steps are adapted to hosting, access and the complexity of the website.

Potential outputs
Launch checklistPost-launch verificationAgreed documentation or training, where included
Release, step by stepIllustrative
  1. Before

    Final approval

    Launch checklist

  2. Release

    Coordinated deployment

    Steps adapted to hosting, access and complexity

  3. After

    Key functionality verified

    Handoff, with documentation or training where included

Stage 07Support & EvolveWhen scoped

Keep improving after launch.

When additional support is needed, we can handle fixes, feature requests, updates and ongoing maintenance as separately agreed work. Support may be project-based, as-needed or recurring under a defined scope.

WordPress Maintenance & Support →
Three ways support can workIllustrative
  • FixesSomething needs repairing after launchAs needed
  • Feature requestsNew functionality, scoped on its ownProject-based
  • Updates and ongoing maintenanceRegular care of the siteRecurring, defined scope

Not automatic. Support is agreed separately, and only where it is wanted.

Project paths

Not every project follows the same path.

Three generic, illustrative examples of how the same stages are used differently. They describe the shape of the work and imply no fixed completion times.

UsedUsed in a lighter formNot needed on this path
APath

Agency-supplied design to WordPress build

Starting point: Approved Figma layouts.

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
Focus
  1. Technical review
  2. Implementation
  3. Responsive QA
  4. Handoff

Design stage: skipped when it is not included in the work.

BPath

Existing WooCommerce store to custom integration

Starting point: A working store with an additional requirement.

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
Focus
  1. Audit the existing configuration
  2. Scope the dependencies
  3. Develop on a safe test setup
  4. Checkout and shipping regression checks
  5. Release
CPath

Bug fix or feature improvement

Starting point: A defined issue or request.

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
Focus
  1. Reproduce
  2. Diagnose
  3. Implement
  4. Verify

A streamlined version of the process, not a complete rebuild.

Handoffs

Clarity throughout the project.

What an agency can expect to understand at each point along the way.

Before we start

  1. A clear understanding of what is in scope

  2. A practical estimate or proposed next step

While we build

  1. Visibility into milestones and dependencies, when applicable

  2. A predictable feedback and review point

When it ships

  1. Careful testing and release coordination

  2. A clear handoff of deliverables and outstanding items

These are working principles, not promises of particular tooling, instant response windows, unlimited revisions or guaranteed schedules.

How we collaborate with agencies →
Questions

Questions about the process.

Short answers about designs, small fixes, existing sites and what happens at launch.

Yes. We can build from supplied designs and specifications. Design work is only part of the engagement if we have agreed to include it.

No. For a focused issue or feature request, we scale the workflow to the work involved while still testing the change carefully.

Yes. We can review the current setup and assess how to add functionality or resolve problems without unnecessary rebuilding.

We review the agreed functionality, address feedback, coordinate approval and verify essential workflows around deployment. The exact testing and launch plan depend on scope.

Yes, when included in the agreement or arranged separately. We offer as-needed development and scoped recurring maintenance.

Start a conversation

Have a project in mind? Let's map out the right approach.

Tell us what you're building, improving or trying to solve. We'll start by understanding the requirements and defining a practical next step.