WordPress development plans & pricing.

The same broad WordPress development capability, with different levels of active capacity and service.

Choose the plan that fits how much work your team needs moving—not which technology you need access to.

Pick your development capacity

Same WordPress capability. Choose the amount of development capacity your team needs.

[PLAN NAME A]

[One sentence describing the recurring workload this plan fits.]

$[PRICE] /month

Active capacity
[TBD]
Websites
[TBD]
Turnaround
[TBD]
  • [Active development capacity]
  • [Submitted/queued request policy]
  • [Website/client-site allowance]
  • [Typical turnaround language]
  • [White-label availability]
  • [Communication method]
  • [Meeting/planning access, if any]
  • [Maintenance-related work inclusion]
  • [Any plan-specific priority/service-level difference]

[PLAN NAME B]

[One sentence describing the recurring workload this plan fits.]

$[PRICE] /month

Active capacity
[TBD]
Websites
[TBD]
Turnaround
[TBD]
  • [Active development capacity]
  • [Submitted/queued request policy]
  • [Website/client-site allowance]
  • [Typical turnaround language]
  • [White-label availability]
  • [Communication method]
  • [Meeting/planning access, if any]
  • [Maintenance-related work inclusion]
  • [Any plan-specific priority/service-level difference]

[PLAN NAME C]

[One sentence describing the recurring workload this plan fits.]

$[PRICE] /month

Active capacity
[TBD]
Websites
[TBD]
Turnaround
[TBD]
  • [Active development capacity]
  • [Submitted/queued request policy]
  • [Website/client-site allowance]
  • [Typical turnaround language]
  • [White-label availability]
  • [Communication method]
  • [Meeting/planning access, if any]
  • [Maintenance-related work inclusion]
  • [Any plan-specific priority/service-level difference]

[OPERATIONAL INPUT REQUIRED] Final plan count, names, prices, active capacity, website allowance, turnaround wording, and communication level. No checkout exists yet, so every plan CTA currently routes to the consultation page.

Need help deciding? Book a Consultation .

What every plan should include

WordPress-focused development

Use your plan for supported work across new and existing WordPress sites.

One organized request workflow

Submit work, keep priorities visible, and understand what is active versus queued.

Practical development standards

Maintainability, safe workflows, testing appropriate to the change, and clear ownership principles.

Ongoing context

Keep working with one development partner that becomes more familiar with your websites and recurring needs over time.

Clear communication

Questions, blockers, risks, and review status should not disappear inside a black box.

Client ownership

Your sites, accounts, code, content, and data remain under the appropriate client or agency ownership.

[OPERATIONAL INPUT REQUIRED] Confirm which of these items are genuinely universal before presenting them as "every plan includes."

How capacity works

Submitted requests
The work you add to your backlog.
Active capacity
How much development your plan allows Macro WP to work on at the same time or within the defined capacity model.
Queue
Submitted requests that are waiting for active capacity.
Priority
The order that determines what should move next.

Completion time depends on the size, complexity, clarity, dependencies, and review cycle of each request. Any plan-specific turnaround estimate should be stated as an expectation—not a guarantee—unless Macro WP is operationally prepared to guarantee it.

Sending ten requests does not mean ten requests are developed simultaneously. Your plan determines how much work moves at once.

Which plan fits your team?

Choose lower active capacity when…

Your WordPress work is recurring but usually sequential. You want one dependable place to send changes, fixes, pages, and enhancements without maintaining constant parallel development.

Choose more active capacity when…

Your agency or team regularly has multiple meaningful requests that cannot wait for one another, or your delivery schedule requires work to cycle through the queue faster.

Talk to Macro WP when…

Your workload is unusually high, involves many client sites, has specialized collaboration requirements, or does not fit the published plan structure cleanly.

Book a Consultation

Subscription flexibility

[OPERATIONAL INPUT REQUIRED] Insert exact client-facing copy for month-to-month commitment, cancellation timing, pause policy, plan changes, annual billing, renewal behavior, and any minimum term. Recommended tone once finalized: literal, short, and reassuring. Pricing is not the place for clever ambiguity.

What about large website builds or bigger features?

Large work can potentially fit inside a development subscription, but "included" does not mean "instant."

Substantial requests may be divided into phases or milestones and worked through according to the active capacity of your plan.

Before starting unusually large work, Macro WP should confirm:

  • the desired outcome
  • major dependencies
  • what can be sequenced
  • what needs client/agency review
  • whether the selected plan provides enough capacity for the expected timeline

For a fixed, isolated project with no recurring need after delivery, a subscription may not always be the best commercial fit. Macro WP should be willing to say that.

What is not included by default

The final service terms should define exact exclusions. At a high level, Macro WP is not positioned as:

  • unlimited simultaneous development
  • 24/7 emergency support unless explicitly purchased/offered
  • general IT support
  • SEO fulfillment
  • unrelated non-WordPress software development
  • an entire embedded product engineering organization
  • guaranteed completion of arbitrarily large work within a fixed short window

[OPERATIONAL INPUT REQUIRED] Add plan-specific or commercial exclusions only after they are finalized.

Pricing questions

Is there a contract?

[OPERATIONAL INPUT REQUIRED] Insert exact minimum-term and cancellation language.

Can I cancel or pause?

[OPERATIONAL INPUT REQUIRED] Insert exact policy. Do not use "anytime" unless billing mechanics genuinely support it.

Can I change plans?

[OPERATIONAL INPUT REQUIRED] Insert upgrade/downgrade process and when changes take effect.

Do unused hours or capacity roll over?

[OPERATIONAL INPUT REQUIRED] Answer based on the final capacity model.

Are there setup fees?

[OPERATIONAL INPUT REQUIRED] Confirm before publication.

Are larger website builds included?

They can potentially be handled through the subscription when they fit the supported WordPress scope, but larger builds may be broken into milestones and will move according to your plan's capacity. If the expected timeline and selected capacity do not align, Macro WP should make that clear before work begins.

Is white-label work included?

The service is designed for agency-ready delivery. [OPERATIONAL INPUT REQUIRED] Confirm whether white-label work is universal or plan-dependent and whether NDAs/client-facing participation have separate rules.

Are there hidden charges?

The intended pricing position is transparent monthly capacity. [OPERATIONAL INPUT REQUIRED] Finalize any pass-through costs, premium add-ons, third-party licenses, rush work, or other potential charges so this answer can be absolute and accurate.

Know the plan you need?

Choose your subscription and move into onboarding. If you are comparing workloads, client-site volume, or collaboration requirements, book a consultation first.