whitelabelwpView plans

HOW WE WORK WITH YOUR AGENCY

From first hello.
To a clear handover.

A shared brief, visible progress, and review points along the way. Know what happens next, what your team brings, and what we deliver.

Tell us about the work See every step

FROM REQUEST TO DELIVERY

A clear next step.
At every stage.

The same working principles apply to builds, custom features, and ongoing care. The depth of each stage depends on the work.

  1. Start with a conversation.

    A new site, a specific feature, or a queue that needs attention. Tell us where your agency needs help; a finished specification can come later.

    Your agency
    Share the type of work, public site URLs or references, and any target dates. Let us know what is already decided and what is still open.
    Our team
    Review the request, ask about the outcome, and identify the details needed to assess the work.

    READY TO MOVE FORWARDA shared understanding of the request and the next details to resolve.

  2. Agree on the work.

    Turn the request into a scope both teams can review. We define deliverables, boundaries, and what a successful result looks like.

    Your agency
    Confirm the pages, functionality, design direction, and priorities. Identify who can approve decisions on your side.
    Our team
    Estimate effort, flag dependencies, and recommend capacity. Agree on milestones, review points, and any work outside the scope.

    READY TO MOVE FORWARDAn agreed scope, estimate, and delivery plan before development starts.

  3. Get ready to build.

    Put the assets, access, and working arrangements in place. Resolve the decisions that would otherwise hold up development.

    Your agency
    Provide approved designs and content for the next stage. Arrange the required access through an agreed secure channel and confirm your project contact.
    Our team
    Check access and the WordPress setup, prepare the review environment, and confirm where tasks, questions, and approvals will be tracked.

    READY TO MOVE FORWARDA ready first task, a review environment, and a clear communication process.

  4. Build in reviewable stages.

    We work through the agreed priorities and share progress at the review points. Your team sees the work while there is still time to shape the result.

    Your agency
    Answer open questions, supply any remaining assets, and keep priorities current. Flag client changes as soon as they arise.
    Our team
    Develop in the agreed environment, check the affected functionality, and share working previews. Raise blockers or scope changes with their impact.

    READY TO MOVE FORWARDA working stage of the project, with progress and open decisions visible.

  5. Review, refine, and approve.

    Compare the work with the brief and test the agreed journeys. Consolidated feedback gives both teams a clear list to work through.

    Your agency
    Review the preview, gather client feedback, and send one prioritized list. Confirm approval once the agreed work is ready.
    Our team
    Resolve issues against the scope and recheck the changes. Identify new requests separately and explain their effect on hours and timing.

    READY TO MOVE FORWARDReviewed work, recorded approval, and any follow-up items clearly identified.

  6. Hand over and coordinate launch.

    Make the work ready for your agency to deliver. We confirm what is being handed over and who is responsible for each release task.

    Your agency
    Approve the release, coordinate client communications, and confirm the host, launch contact, and timing where a deployment is involved.
    Our team
    Provide the agreed files, access, and editing guidance. Confirm deployment and recovery steps, then complete the live checks assigned to us.

    READY TO MOVE FORWARDA clear handover and, where included, a coordinated release with live verification.

Milestones are agreed after scoping. Timing depends on the work, available capacity, assets, access, and feedback.

KEEP REVIEWS EASY TO ACT ON

One feedback list.
Clear next actions.

Your agency gathers the feedback and confirms priorities. We turn that into a list of changes that can be checked against the agreed brief.

  • Name the page or feature and describe the expected result
  • Combine internal and client feedback before sending it
  • Identify who can resolve questions and approve the work

If feedback introduces a new requirement, we flag it and agree on the effect on scope, hours, and timing before proceeding.

WHAT DELIVERY LOOKS LIKE

The work is ready.
Your team is ready, too.

Handover covers the practical details your agency needs to present, release, and manage the work. We confirm the exact package in the scope.

The agreed deliverables.

Site files, custom code, templates, or configuration covered by the scope, with the final version and its location identified.

Access and ownership of tasks.

The accounts and permissions your team needs, who manages the hosting and licenses, and who is responsible for launch tasks.

Practical editing guidance.

How to update the agreed content areas, use custom controls, and find the settings your agency or client will manage.

Checks and follow-up items.

What was reviewed, any agreed limitations, and the remaining actions with their owners. Future work has a clear starting point.

And after delivery?

We agree on the next priorities, whether that means another build, a feature, or ongoing maintenance. Future changes use your agreed monthly capacity.

Explore ongoing care

WORKING TOGETHER

Before we
get started.

Have a specific workflow in mind?

Talk it through
Do we need everything ready before contacting you?

No. Start with the outcome you need, the type of work, and any dates you have in mind. We can identify missing requirements together. Approved designs, content, and access need to be ready for the stages that depend on them.

Will you speak directly with our clients?

Your agency manages the client relationship. We work with your team and deliver under your brand. If a project needs direct client involvement, we agree on the participants, branding, communication, and confidentiality arrangements beforehand.

Which tools will we use to work together?

We agree on the project tools during preparation. The important part is having one place for the current task list, files, questions, feedback, and approvals, with a clear contact on each team. Access details are shared through an agreed secure channel.

How do you agree on a delivery date?

We review scope, available monthly capacity, asset readiness, and dependencies before proposing milestones. The schedule also allows for your team’s reviews. If access, feedback, or requirements change, we discuss the impact and update the plan with you.

What happens if the client changes the brief?

Send the change with its priority and desired outcome. We compare it with the agreed scope and explain the effort and timing involved. Your agency can then decide whether to replace a queued task, move the request to a later stage, or agree on additional capacity before work starts.

Does delivery include launch and ongoing support?

Launch responsibilities are agreed in the scope. We can coordinate deployment and verification, or hand the work to your team for release. Ongoing updates, fixes, and new features use agreed development capacity and support coverage; they are planned separately from the handover.

LET’S TAKE THE FIRST STEP

What’s on your
agency’s to-do list?

Start with a few lines about the work and the outcome you need. We’ll help you work through the details.

Let’s talk about your project Compare monthly plans