Frequently asked questions about Macro WP.

Macro WP is a productized WordPress development service for agencies and teams with recurring WordPress work. You subscribe to ongoing development capacity instead of pricing every supported request as a separate project.

The subscription is designed for recurring needs. It gives you an ongoing workflow, predictable monthly cost, less repeated onboarding, and a development partner that can build context across your websites and requests.

If you only need one isolated task and do not expect more work afterward, a recurring subscription may not be the best fit.

[OPERATIONAL INPUT REQUIRED] Insert exact term and cancellation policy.

[OPERATIONAL INPUT REQUIRED] Insert finalized pause policy.

[OPERATIONAL INPUT REQUIRED] Insert upgrade/downgrade policy and effective date.

[OPERATIONAL INPUT REQUIRED] Confirm whether annual billing exists and whether it changes price or terms.

If Macro WP uses that phrase, it means you can keep adding requests to the backlog. It does not mean unlimited requests are developed simultaneously.

Your plan determines active development capacity. Additional requests wait in the queue until capacity becomes available.

[OPERATIONAL INPUT REQUIRED] Insert the capacity rule for each plan or link to Pricing if the number differs by plan.

A request should represent a clear development outcome that can be understood, worked on, and reviewed. Larger outcomes may be divided into smaller milestones when that makes delivery clearer or safer.

[OPERATIONAL INPUT REQUIRED] Add any formal request-size definition if the operating model requires one.

The queue is intended to reflect your current priorities. If priorities change, queued work can be reordered.

[OPERATIONAL INPUT REQUIRED] Define how work already in progress is handled when a client wants to switch immediately.

Large work can be divided into milestones or sequential requests and moved through the same capacity model. Size affects completion time; the subscription should not imply that a large project and every other queued task will all move simultaneously.

[OPERATIONAL INPUT REQUIRED] Answer once the capacity model is finalized.

Completion time depends on the size and complexity of the request, quality of the handoff, dependencies, feedback cycle, and your plan's active capacity. Macro WP should provide realistic expectations once a request is understood rather than applying one universal promise to every task.

[OPERATIONAL INPUT REQUIRED] Add plan-level turnaround ranges only if they can be consistently supported.

[OPERATIONAL INPUT REQUIRED] Publish an answer only after a clear urgent-request policy exists. Do not imply 24/7 or guaranteed same-day support unless genuinely offered.

You complete onboarding, provide the relevant website/access context, submit your first requests, and put them in priority order. Macro WP confirms anything needed before development begins and then moves active work according to your plan's capacity.

[OPERATIONAL INPUT REQUIRED] Insert the launch request method—client portal, PM system, form, email, or another approved workflow.

The intended workflow makes request status clear: received, waiting for information when applicable, active/in progress, ready for review, and complete. Exact channels and notification behavior depend on the launch request system.

Supported work can include custom development, themes, plugins, landing pages, page-builder implementation, PHP, ACF, features, fixes, integrations, existing-site development, maintenance-related work, and other development that reasonably falls within the WordPress ecosystem.

See WordPress Development for the full capability overview.

Yes, custom plugin development is within the intended scope when custom functionality is the right solution. Macro WP may recommend extending an existing reliable plugin instead when rebuilding the feature would add cost and maintenance without enough benefit.

Yes. Custom themes and custom template work can be handled when they fit the request and development environment.

These tools are part of the intended WordPress capability.

[OPERATIONAL INPUT REQUIRED] Confirm the final public supported-technology list before launch.

Yes. Existing-site development is a core use case. Macro WP may need to review the theme, plugins, custom code, hosting/staging setup, and overall condition of the site before making higher-risk changes.

WooCommerce-related development is within the intended capability where supported. The exact request still needs to fit Macro WP's technical scope and capacity model.

Yes, API and third-party integration work can fit the service when WordPress is part of the implementation and the external system provides an appropriate integration path. The specific API should be reviewed before scope is confirmed.

Macro WP is not intended for general IT, SEO fulfillment, unrelated software development, 24/7 emergency engineering unless explicitly offered, or unlimited simultaneous development. Some specialized WordPress-adjacent requests may also be declined if they require expertise or access Macro WP cannot responsibly support.

Yes. Agencies are the primary audience. The service is intended to support recurring client work, overflow capacity, design-to-development handoffs, multiple WordPress environments, and collaboration with existing agency teams.

The intended model supports discreet agency delivery without unnecessary Macro WP branding in client work.

[OPERATIONAL INPUT REQUIRED] Finalize NDA, communication, and other white-label boundaries before making broader promises.

[OPERATIONAL INPUT REQUIRED] Confirm NDA policy and any contract/process requirements.

Yes, the model is intended to support agencies working across multiple WordPress sites.

[OPERATIONAL INPUT REQUIRED] Insert plan-specific site limits or fair-use rules.

Yes. Macro WP can act as overflow, additional bandwidth, backup support, or WordPress-specific expertise without replacing your current developer.

Yes. Figma is a natural design handoff. Include the approved design, responsive expectations, assets, and any known site or builder constraints.

[OPERATIONAL INPUT REQUIRED] Finalize whether direct client communication is unavailable by default, available by agreement, or plan-dependent.

Macro WP should use a controlled credential workflow rather than asking clients to pass passwords around casually.

[OPERATIONAL INPUT REQUIRED] Insert the actual secure-sharing process once finalized.

Staging should be used when the risk and environment make it appropriate. High-impact changes should not be pushed directly into production simply for speed when a safer workflow is available.

Macro WP's brand principle is client ownership. The website, accounts, code, content, data, and credentials should remain under the appropriate client or agency control rather than being held through unnecessary lock-in.

[OPERATIONAL INPUT REQUIRED] Ensure the Service Terms use legally precise ownership language consistent with this principle.

A freelancer may be cheaper and perfectly appropriate for occasional work. Macro WP is designed for recurring development where you value an ongoing workflow, predictable cost, continuity, and dependable access to WordPress-focused capacity.

Then Macro WP may still be useful as overflow, backup, project acceleration, or specialist capacity. The service does not need to replace a good existing developer.

If your WordPress needs are truly occasional, a recurring subscription may not be the best fit. Macro WP should be positioned for teams that can make practical use of ongoing development capacity.

Choose based primarily on how much WordPress work you need moving, not on which technical feature you need. If your workload is hard to translate into a plan, book a consultation and bring examples of the work your team typically sends to development.