Choose a pricing model that matches the uncertainty
Your agreement with the partner and your agreement with the client can use different models. If you sell a fixed-price build while buying open-ended hours, your agency carries the difference when the estimate slips.
| Model | Who carries risk | Best fit | Watch for |
|---|---|---|---|
| Fixed-scope project | Partner: scoped overruns; agency: extras | Defined build or repair | Acceptance and exclusions |
| Monthly retainer / care | Partner: included workload; agency: resale promises | Recurring support | Limits and emergency coverage |
| Hourly with a cap | Agency: hours; partner: cap discipline | Diagnosis or uncertain fixes | Stop point, not guaranteed completion |
| Task menu | Partner: standard task effort; agency: exceptions | Repeatable small requests | Eligibility and task boundaries |
| Reserved capacity | Agency: unused capacity; partner: availability | Predictable ticket pipeline | Queue, rollover and expiry |
Fer Marketing's white-label web and WordPress development starts from $250 per project or retainer, with a fixed written quote before any work starts. The starting price is not a quote for every site; review the published pricing and submit the actual scope.
↑ Back to topCalculate margin after counting your agency's work
Markup measures the increase over cost: (price - cost) / cost. Margin measures the share of selling price left after the counted costs: (price - cost) / price; multiplying either result by 100 expresses it as a percentage.
| Markup | Selling price | Amount left | Margin |
|---|---|---|---|
| 50% | $1,500 | $500 | 33.3% (rounded) |
| 100% | $2,000 | $1,000 | 50% |
| Cost item | Calculation | Cost |
|---|---|---|
| Partner's fixed quote | Hypothetical build | $1,000 |
| Project management | 4 hours x $40 internal cost | $160 |
| QA | 3 hours x $40 internal cost | $120 |
| Client calls | 2 hours x $40 internal cost | $80 |
| License | Project allocation | $100 |
| Hosting | Quoted project period | $40 |
| Total counted cost | $1,000 + $360 + $140 | $1,500 |
Example: a hypothetical 40% target margin gives $1,500 / (1 - 0.40) = $2,500. That leaves $1,000 after the counted delivery costs; simply doubling the $1,000 partner quote to $2,000 would leave $500, a 25% margin on the same full cost base.
EXAMPLE INPUTS BELOW ARE HYPOTHETICAL, NOT FER MARKETING RATES. P = partner's fixed quote: 1000 A = agency hours x internal cost: (4 + 3 + 2) x 40 = 360 T = pass-through costs you pay: license 100 + hosting 40 = 140 R = explicit allowance for defined delivery risks: 0 in this example C = P + A + T + R = 1500 m = target delivery margin as a decimal: 0.40 S = client price = C / (1 - m) = 2500 Check: (S - C) / S = 0.40; markup = (S - C) / C = 66.7% rounded Use 0 <= m < 1. Recalculate when scope, hours or recurring costs change. Actual margin = (actual revenue - actual counted costs) / actual revenue
Define the work before asking for a fixed quote
Attach evidence or a decision to each item
- Count pages and unique templates separately.Attach a page inventory and approved layouts. Ten pages using one layout differ from ten unique layouts; list reusable sections, languages and who enters each page's content.
- Verify content readiness.Name the owner and delivery date for copy, images, logos and translations. State whether copywriting, image sourcing, entry and formatting are included, and what happens to dates if assets arrive late.
- Specify integrations and forms.List each CRM, booking tool or API, required credentials, fields, routing, consent text supplied by the client, notifications and failure handling. Acceptance means a labeled submission reaches the intended inbox or system, not only a success message.
- Map ecommerce workflows.List products, variants, imports, payment methods, shipping, tax configuration supplied by the client, account flows and subscriptions where needed. Define sandbox checkout and confirmation tests and who approves the settings.
- Bound migrations.Inventory files, database, media and redirects, identify DNS access and state whether email moves too. Define the cutover window, handling of new live orders, rollback owner and tests after deployment.
- Write acceptance criteria and revision limits.Specify the function or layout to demonstrate, named approver and review deadline. Define a revision round as one consolidated feedback list against approved scope; new functionality needs a change order.
- Name browsers, devices and handoff items.Agree the browser versions and desktop, tablet and cellular test conditions at kickoff. List admin access, source files, training, documentation and launch checks; save the agreed test results with the acceptance record.
How to price a white-label WordPress job
- Step 1
Collect and confirm scope
Complete the scope checklist with the client and save the approved version. Resolve missing assets and acceptance tests before promising a fixed delivery date.
- Step 2
Get the partner's fixed written quote
Send the same scope to the partner and confirm deliverables, exclusions, revision rounds, QA and delivery conditions. Do not commit to a client price based on an unconfirmed starting price.
- Step 3
Add pass-through costs
List licenses, hosting, migration tools and other project purchases you will pay for, with their covered period and renewal owner. Exclude items the client buys directly and avoid duplicating costs already in the partner quote.
- Step 4
Estimate your own hours at internal cost
Count project management, QA, client calls, feedback consolidation and launch coordination. Multiply each role's hours by its internal cost and record the assumptions for later comparison.
- Step 5
Choose a target margin
Add any explicit delivery-risk allowance to the cost base and calculate price = cost / (1 - target margin). Treat the resulting delivery margin as an input to your profitability review, with overhead and fees also considered.
- Step 6
Check the price against your market
Compare the proposed deliverables, client budget, alternatives, urgency and value of the agreed outcome. If the price does not fit, reduce scope, phase delivery or decline rather than silently dropping QA.
- Step 7
Write the client quote
Include line items, assumptions, exclusions, acceptance tests, revision rounds and a change policy. Match each client promise to something the partner has agreed to deliver or your agency has explicitly costed.
- Step 8
Set payment terms and authorize work
Agree a deposit if appropriate, milestone invoices, due dates and what authorizes scheduling and launch. Check that client receipts can cover partner obligations, then obtain written approval before starting.
Use the cost calculation as a floor for a business decision
A partner's cost does not tell you what the client values or what your agency must provide. A client buying a booking workflow may need requirements gathering, staff training and coordinated launch support in addition to a working plugin.
Compare the same deliverables
Ask which alternatives the client is considering and compare scope, ownership, support and launch responsibilities. Record budget objections in your own quote history instead of treating an unrelated site's price as a benchmark.
Make value concrete
Describe a verifiable outcome, such as a booking request reaching the correct calendar. Use client-supplied business data for value discussions; do not promise revenue increases from a redesign.
Offer meaningful scope choices
Separate the required launch scope from optional integrations or later pages. Each option needs its own acceptance tests, cost and schedule so a smaller budget buys a clearly smaller commitment.
Keep acquisition and site delivery as separately scoped work when combining offers. Use the cold email guide for agencies to plan outreach or discuss client acquisition as a separate service; Fer Marketing quotes cold email after a short call.
↑ Back to topCharge for changes without charging twice for the original promise
An in-scope defect fails an agreed acceptance test; a change adds to or replaces the approved requirement. Correct defects under the agreed responsibility and warranty terms, and treat a new booking integration or a newly requested layout as a scope decision.
- Log
Compare the request with the approved scope
Save the requested behavior, scope version and affected acceptance test. Ask the partner to identify whether it is a defect, included revision or new work before quoting the client.
- Estimate
Cost the whole change
Get the partner's fixed change quote, then add agency coordination, retesting, licenses and any rework of already approved items. Apply your chosen margin formula and state dependencies and schedule impact.
- Approve
Get a written change order
Offer the added work, a scope swap or deferral. Record the new price and delivery conditions, and require approval of any extra charge before the changed work begins.
- Verify
Test and update the project record
Run the new acceptance test and the affected existing journeys. Update scope, invoices and delivery dates so the agency, client and partner use the same approved version.
Project / change ID / date / original scope version: [fill in] Request and reason: [new behavior or changed deliverable] Classification: [defect / included revision / extra work, with reason] Added work / removed work / unchanged deliverables: [list] Acceptance tests and reviewer: [observable result and owner] Internal costing, not client copy: [partner + agency time + purchases] Client price / applicable taxes / payment due: [agreed amounts] Schedule impact / dependencies / revised milestones: [fill in] Approval: [authorized client name, written acceptance and date] Partner authorization: [matching scope and written approval]
Write a quote the client and delivery team can both use
- Make line items testable.Separate discovery, build, integrations, migration, QA and launch where applicable. Describe what each includes, identify optional work and specify whether licenses and hosting are included, passed through or purchased directly.
- State assumptions, exclusions and dates.List supplied designs and content, access requirements, third-party dependencies and the quote validity date. Link the schedule to asset delivery and approval milestones, with a process for delays and rescheduling.
- Define acceptance and revisions.Name the approver, tests, review window and included revision rounds. Explain the change-order route for new scope and how unresolved defects are recorded before handoff.
- Make payment and ownership explicit.Agree deposit and milestone amounts, due dates, pause conditions and final handoff requirements. State who receives custom code and access, when rights transfer under the agreement, and which third-party license terms or renewals still apply.
- Define post-launch responsibility.Specify the bug warranty period with start and end dates, covered defects, reporting channel and exclusions. Assign hosting, backups, ongoing updates and renewals after launch, and distinguish warranty corrections from a paid maintenance agreement.
QUOTE: [project, client, agency, version, date, valid until] Outcome: [agreed visitor task and business purpose] Build: [pages, unique templates, content entry] | [amount] Integrations / forms / store: [bounded workflows] | [amount] Migration / QA / launch / handoff: [deliverables] | [amount] Licenses / hosting: [included period, payer, renewal owner] | [amount] Optional work: [separate items, excluded from base total] Total / currency / applicable taxes: [amounts and treatment] Assumptions: [approved designs, ready content, working access] Exclusions: [copywriting, email move, extra workflows, as applicable] Schedule: [milestones, asset deadlines, dependencies, delay policy] Acceptance: [tests, browsers/devices, approver, review window] Revisions: [number, definition of a round, submission channel] Changes: [written estimate and approval before extra work] Payment: [deposit, milestones, due dates, pause and launch conditions] Ownership: [custom code, access, transfer timing, license restrictions] Bug warranty: [start, end, covered defects, reporting and exclusions] After launch: [hosting owner, maintenance scope or separate agreement] Approval: [authorized name, signature or written acceptance, date]
Price ongoing care around the work and the promises
Fer Marketing's WordPress maintenance starts from $250 monthly per site, with agency volume pricing available, and can be resold under your brand. Site management starts from $250 for a monthly plan based on site size and expected request volume; confirm which ongoing content changes need that separate scope.
Write the included work
List updates, security, off-site backups, tested restores, uptime monitoring and the branded monthly report. Agree site-specific checks, frequency, access and exclusions with the partner; use the WordPress maintenance checklist as a starting point.
Cost account support
Add monthly client calls, report review, ticket triage, license renewals you fund and an explicit allowance for defined support risks to the partner cost. Calculate the resale price from that monthly total and revisit actual time by site.
Set service boundaries
Document support hours, emergency routing and response expectations separately from resolution. Confirm coverage for malware cleanup, compatibility work, content edits and out-of-hours incidents before making client promises.
Plan onboarding and exit
Audit the site before promising routine care and separately scope pre-existing faults if needed. Name the owners of hosting, licenses, credentials, backups and reports, with an agreed handoff and cancellation process.
Use the WordPress maintenance checklist to turn each included task into evidence the client can understand. Keep a monthly record of partner cost, agency hours, exceptions and billed revenue, then adjust future scope or renewal pricing through the agreed process.
↑ Back to topResell postcard campaigns with the same math
If you also sell client acquisition, the same formula applies. Fer Marketing's personalized postcards cost $10 per custom postcard, with a 50-card minimum ($500). For a first campaign, the intro pack is 100 custom postcards for $500 ($5 per card). Research, design, printing, USPS First-Class postage and the QR report page are included, under your agency's brand.
| Line | Calculation | Amount |
|---|---|---|
| Intro pack cost | 100 cards at $5 | $500 |
| Agency time | 3 hours x $40 internal cost (niche, list review, replies) | $120 |
| Counted cost | $500 + $120 | $620 |
| Price at a 40% margin | $620 / (1 - 0.40) | $1,033.33 |
Sell acquisition and website delivery as separate scopes, so a campaign that wins a client does not turn into unpriced build work. The postcard campaign guide explains the method end to end.
↑ Back to topWhat kills margin even when the partner quote stays fixed
Margin stays visible
- One approver sends consolidated feedback against the approved scope.
- Every page, integration and revision round has a written boundary.
- PM, QA, calls and launch coordination are costed and tracked.
- License renewals have a named payer and covered period.
- Extra work is approved before delivery; client receipts match obligations.
- Actual cost is compared with the estimate at handoff and renewal.
Margin disappears
- Feedback arrives in multiple channels and restarts approved work.
- A small fix becomes an unpriced redesign or integration.
- The owner's evenings and client calls are treated as free.
- Agency-owned licenses and hosting renew without a budget.
- The agency funds extra work while waiting for client payment.
- Only the partner invoice is reviewed, so overruns stay hidden.
Make the partner agreement support your client quote
Confirm these before the first ticket starts
- A fixed written quote and matching scope.Confirm price, delivery conditions, QA, acceptance tests, revisions, change pricing and responsibility for defects before any work starts. Compare these terms with your client quote and cost any gap your agency must cover.
- Staging on your domain and controlled approval.Agree staging under an agency-controlled domain, with protected access and test integrations. Check branding in notifications and reports, approve the work there, and name who authorizes production deployment.
- NDA and non-solicitation in writing.Fer Marketing offers these on request, so request and agree them before sharing client material. Specify confidentiality, permitted access and the rule that client communication stays through your agency unless you authorize otherwise.
- Ownership, access and handoff.Document access to source code, WordPress and hosting, license ownership, deployment records and the exit process. Confirm response expectations and who handles warranty defects after launch, rather than leaving support implied.
The white-label WordPress process explains tickets, staging and handoff. For white-label web development, Fer Marketing works under your brand and provides a fixed written quote before work starts, from $250 per project or retainer.
Send the page inventory, designs, integrations, content status and target launch date when you contact Fer Marketing. That makes the partner quote something you can cost, review and translate into a clear client commitment.
↑ Back to topFrequently asked questions
How much does white-label WordPress development cost at Fer Marketing?
White-label web and WordPress development starts from $250 per project or retainer. Fer Marketing provides a fixed written quote for the agreed scope before any work starts.
How should an agency price white-label web development?
Add the partner quote, project purchases and your own delivery hours at internal cost, then calculate price = cost / (1 - target margin). Check market fit and client value, and quote defined scope with a change policy and payment terms.
What is the difference between markup and margin?
Markup divides the amount left after cost by cost; margin divides it by selling price. A 50% markup yields a 33.3% margin rounded, while a 100% markup yields a 50% margin on the same cost base.
Is doubling the partner's quote enough?
It gives a 50% margin only if the partner quote is your entire counted cost. Agency project management, QA, calls, licenses and hosting reduce that margin unless you include them in the cost base.
What margin should my agency target?
Choose a target that supports your delivery work, overhead, risk and market position; there is no universal percentage. Check it against actual costs after each project and avoid treating delivery margin as net profit.
Should I use fixed-price or hourly white-label pricing?
Fixed pricing suits work with clear requirements and acceptance tests. For uncertain repairs, a capped investigation can establish scope before a fixed repair quote; define the stop point and require approval for further work.
How do I price a client change request?
First determine whether it is an in-scope defect, an included revision or extra work. For extras, add the partner's change quote, agency coordination, retesting and purchases, apply your pricing formula and obtain written approval of price and schedule impact before starting.
What should a white-label WordPress quote include?
Include deliverables, line items, assumptions, exclusions, timeline, acceptance tests, revision rounds, payment terms and the change process. State code and license ownership, hosting and maintenance responsibilities, and the bug warranty period and coverage.
Can I resell WordPress maintenance under my agency's brand?
Yes, Fer Marketing's maintenance starts from $250 monthly per site, with agency volume pricing available and white-label reporting. Add your client support costs before setting resale pricing, and confirm scope, coverage and exclusions in writing.
Can my agency resell postcard campaigns too?
Yes. Fer Marketing's personalized postcards are $10 per custom postcard with a 50-card minimum ($500), and the intro pack for a first campaign is 100 postcards for $500 ($5 per card), delivered under your brand. Apply the same cost-plus-margin math and recalculate after the first campaign.
Does a bug warranty include ongoing maintenance?
Only if the agreement explicitly includes that work. Define the warranty dates and covered defects separately from recurring updates, monitoring, backups and newly requested changes.
Can staging use my domain, with an NDA and non-solicitation?
Fer Marketing can work on staging under your domain and offers an NDA and non-solicitation on request. Agree those terms and client communication rules before sharing materials or starting work.
Who should own WordPress licenses and custom code?
Name the owner, renewal payer, access rights and handoff conditions in writing. Separate ownership of custom deliverables from third-party license terms, since not every plugin license can be transferred to a client.
Send your scope, content status and target launch date to [email protected]. We can confirm a fixed written partner quote so you can price the client work with clear costs and responsibilities.