A few questions.
Clear answers.

We deliver under your agency’s brand, and your team manages the client relationship. Branding, communication, and confidentiality are agreed before work starts. If a project needs direct client involvement, we confirm the participants and approach with you first.

A few lines about the outcome, the type of work, and any dates you have in mind are enough to begin. Public site URLs, references, and your preferred WordPress setup help. You can bring a partial brief; we identify the decisions, designs, content, and access needed before each stage starts.

Yes. Start with one website, feature, or set of fixes. We review the work and recommend monthly capacity that fits its scope. A larger project can span several months, with milestones agreed before development begins.

Start by sharing the public URL and the work you need covered. Leave passwords and private access details out of the contact form. During preparation, we agree on the accounts and permissions needed and a secure channel for providing access.

Starter: $750 USD for 20 hours and 1 active request. Growth: $1,500 USD for 40 hours and 2 active requests. Agency: $3,000 USD for 80 hours and 4 active requests. These are monthly allowances shared across the agreed work. Starter covers WordPress builds, fixes, and maintenance; Growth adds WooCommerce and integrations; Agency adds custom plugins and complex functionality. The plans, prices, and limits shown are proposed and pending confirmation.

An active request is an agreed task or piece of work currently in progress. Your plan limits how many requests can move forward at once, and they all share the same monthly hours. More active requests do not multiply the hour allowance. We agree on how to divide larger projects and handle tasks awaiting feedback during onboarding.

No. Under the proposed plans, unused hours do not carry into the next month. We review priorities with your team so briefs, access, and approvals can be prepared around the available capacity.

You can agree on a queue across client sites within the plan’s scope, hours, and active-request limit. If the work exceeds that capacity, we review what to prioritize, move to a later cycle, or cover with a revised plan. Extra capacity, pricing, and timing are agreed before additional work starts.

Hosting, paid software licenses, and third-party subscriptions are separate. We review the tools the work depends on and confirm who provides and manages them. Design changes, copywriting, migrations, and other additional services need an agreed scope rather than being assumed as part of a build.

Prices are shown in USD per month. Billing dates, payment terms, applicable taxes, and the terms for pausing or cancelling are confirmed in the agreement before work starts. Choosing a plan on the site opens an enquiry and does not take a payment or create a subscription.

Yes. Tell us whether you use Elementor, Bricks, the block editor, or a custom theme. We agree on the WordPress setup before starting and review constraints in existing themes, plugins, and custom code. Editing requirements are part of that discussion.

Yes, after reviewing its current setup and condition. Share the URL, the changes needed, and any known issues. We check relevant themes, plugins, and custom code before confirming the work. Unsupported components or migration requirements may need attention in their own scope.

You can contact us with references or partial designs. Before building a stage, we identify the approved layouts, content, and behavior it needs. Missing design decisions are raised with your team. Copywriting, new design work, and changes to approved designs need to be scoped explicitly.

Yes, after defining the feature and its requirements. WooCommerce and integrations sit within Growth, while custom plugins and complex functionality sit within Agency under the current proposed plans. For integrations, we review API access, limits, testing options, and what should happen when a request fails before confirming scope.

Timing depends on scope, monthly capacity, design and content readiness, access, and dependencies. We estimate the work and agree on milestones after reviewing the brief, including time for your team’s feedback. If requirements or dependencies change, we discuss the impact and update the plan with you.

We agree on the project tools, contacts, and review points during preparation. Tasks, questions, files, feedback, and approvals need a shared home. Your agency sets priorities, and we share working previews and flag blockers. Review frequency follows the agreed plan and scope.

We check the agreed functionality and affected journeys in a review environment, using staging where available. Your team reviews the work against the brief and sends one prioritized list of internal and client feedback. We resolve in-scope issues and recheck changes before approval. If staging is unavailable, we agree on a suitable approach first.

Share the requested change, its priority, and the desired result. We compare it with the agreed scope and explain the effort and timing involved. Your agency can decide whether to replace a queued task, plan it for a later stage, or agree on more capacity before work begins.

The handover includes the agreed files or code, access, configuration details, editing guidance, and any follow-up items. Launch responsibilities are set in the scope: we can coordinate deployment and verification, or hand the work to your team for release. Your agency approves the release and manages client communication.

Yes. We agree on the sites, routine work, update frequency, support arrangements, and request process. Updates, troubleshooting, fixes, reviews, and reporting use your monthly capacity. A redesign, new integration, or substantial feature needs its own assessment and scope.

Support hours, response targets, and any out-of-hours arrangements are agreed before work starts. Around-the-clock emergency coverage is not included by default. For an urgent issue, share the affected URL, what changed, steps to reproduce it, and the business impact so we can assess it within the agreed coverage.

We review your existing backup setup and can coordinate with your hosting provider. Backup frequency, retention, restore testing, and responsibility for recovery are agreed per site. Paid backup services are separate. Before a restore, we account for newer orders, submissions, or content that could be affected.

We can assess performance issues, establish a baseline, and scope targeted improvements; a specific speed score is not guaranteed. Recovery from a compromised site needs its own assessment and scope. We explain the dependencies and estimated effort so your team can decide how to proceed.