Suped

How to price DMARC remediation separately from monitoring

Published 9 Jul 2026
Updated 11 Nov 2026
12 min read
Summarize with
DMARC remediation pricing separated from monitoring for MSP service delivery.
Updated on 11 Nov 2026: We clarified how to calculate remediation fees and define completion before handing work back to monitoring.
Price DMARC remediation separately from monitoring when the work changes DNS, sender configuration, mail routing, client processes, or third-party platform settings. Monitoring is a recurring service that tells you what is happening. Remediation is project or change work that fixes what monitoring finds. Price them separately because the labor and change risk differ.
For MSPs, the cleanest model is a recurring DMARC monitoring subscription plus separately scoped remediation work orders. The monitoring subscription covers collection, reporting, alerting, source review, and recurring client communication. The remediation work order covers investigation, sender validation, DNS changes, vendor coordination, DKIM setup, SPF cleanup, policy staging, and enforcement planning.
Pricing rule
Do not sell remediation as an unlimited promise inside a low-cost monitoring line item. Price named deliverables with clear assumptions, exclusions, acceptance criteria, and a change path when the client has hidden senders or delayed vendor access.
  1. Recurring monitoring covers DMARC reports, source tracking, alerts, scheduled summaries, and ongoing posture review.
  2. Remediation projects cover scoped DNS edits, SPF restructuring, DKIM enablement, vendor follow-up, and DMARC policy changes.
  3. Urgent enforcement deadlines, acquisition cleanup, and extensive sender discovery need separate approval when outside the agreed scope.

Why remediation needs its own price

DMARC monitoring has a predictable rhythm once the domain is reporting. Remediation does not. One client has a single Microsoft 365 tenant and two approved senders. Another has legacy marketing tools, a billing platform, a recruitment system, a copier sending through an ISP relay, and a former agency still using the domain. Both domains can generate the same monthly DMARC report volume, but the remediation effort is completely different.
Monitoring line item
  1. Collect aggregate DMARC reports and track authentication results by source and volume.
  2. Run continuous report collection with scheduled reviews and alerts for unusual authentication changes.
  3. Provide reporting evidence and a queue of issues that need decisions.
Remediation work order
  1. Update DNS, platform settings, DKIM keys, SPF includes, and DMARC policy values.
  2. Require admin access, sender owners, vendor support, change windows, and client approval.
  3. Produce verified authentication results and documented decisions before enforcement.
A common MSP packaging mistake is treating remediation like a small add-on because the visible DNS record looks short. The record is rarely the hard part. The hard part is proving which systems are legitimate, getting each sender to authenticate correctly, and moving policy without breaking business mail.
Remediation price signal bands
Use effort signals instead of public price lists. The band depends on ownership, sender count, and change risk.
Low effort
Fixed pack
Few known senders, direct DNS control, and no unknown business platforms.
Medium effort
Scoped project
Several senders, some vendor coordination, and staged policy movement.
High effort
Custom scope
Many unknown senders, acquisitions, shared DNS, or strict deadline pressure.
Ongoing effort
Managed change
New sender onboarding, policy governance, and quarterly domain reviews.

Define the boundary before you quote

For a broader service model, use the DMARC for MSPs framing: sell visibility, remediation, and governance as related services, but keep the labor boundaries visible. A client can understand a recurring monitoring fee. They also understand a separate project when it has named deliverables.
Before pricing remediation, document the assumptions. This keeps the work from turning into an open-ended hunt through every system that ever sent mail for the domain. The written scope definition matters more than the rate card because it tells the client what is included and what becomes a change request.
  1. List every included domain and subdomain, and distinguish sending domains from parked domains.
  2. Classify approved platforms, unknown sources, retired systems, and suspicious traffic. Cap the sending-service configurations included rather than counting source IPs.
  3. State who controls DNS, mail tenant settings, vendor portals, and change approvals.
  4. Name the agreed policy state and the staged path by domain or subdomain.
  5. Define the DNS evidence and per-sender DMARC results needed for client sign-off.
  6. Set the review cadence and retest limit. Define response targets separately from resolution deadlines, and pause delivery milestones while waiting for client access or vendor action.

Work item

Monitoring

Remediation

DMARC report review
Included
Included for validation
Sender classification
Light review
Deep validation
DNS record changes
Excluded
Included by scope
Vendor coordination
Excluded
Included by scope
Policy enforcement
Advisory
Change project
Keep the monitoring and remediation boundaries visible in the proposal.

Build bands around work, not message volume

Message volume is useful for monitoring capacity, but it is a poor remediation pricing anchor. A small nonprofit can have five messy senders and no DNS access. A larger client can have high volume through one well-managed mail platform. Price remediation around the work required to change the authentication outcome.

Work type

What determines the estimate

Add DMARC reporting
Confirm DNS control and report destination setup.
Enable DKIM for one known sender
Confirm platform support and access to publish selector records.
Clean up SPF includes
Check approved senders and lookup use before removing entries.
Validate unknown senders
Identify a business owner and determine whether configuration work is needed.
Clean up legacy sender configurations
Identify owners and sequence changes across affected platforms.
Estimate each work type from the client environment rather than an assumed effort score.
Create a small number of internal remediation bands. The client does not need a long menu of technical tasks. They need a clear quote that says what gets fixed, what access is required, and what happens when new sources appear after the project starts.
Flowchart for turning DMARC monitoring findings into scoped remediation work.
Flowchart for turning DMARC monitoring findings into scoped remediation work.
Do not hide change risk
If a client asks for a single flat monitoring fee that includes all fixes, narrow the language. Include advisory review and issue identification in monitoring, then state that implementation work is quoted separately.
  1. DNS or vendor access delays can consume more time than the technical fix.
  2. Some senders need owner approval before they are retired, changed, or blocked.
  3. Moving too fast to enforcement can disrupt legitimate mail that lacks authentication.

Calculate the remediation price floor

Convert the effort band into a quote by estimating the full delivery cost, then applying the MSP's target gross margin. Use loaded labor cost, not technician wages alone. Include payroll burden and allocated delivery overhead once, then estimate all technical work and coordination hours.

Cost input

Include

Technical labor
Discovery, sender fixes, DNS changes, testing, and documentation hours
Coordination
Client meetings, approvals, vendor tickets, and follow-up hours
Project overhead
Scoping, scheduling, quality review, and administration, counted once in delivery hours or the loaded rate
Project-only costs
Vendor fees or temporary software costs not already covered by monitoring
Contingency
Normal uncertainty that remains inside the written scope
Cost inputs for a remediation quote. Count labor and overhead once.
Remediation pricing formula
Loaded labor = all scoped delivery hours x loaded hourly cost Estimated delivery cost = loaded labor + project-only costs + contingency Price floor = estimated delivery cost / (1 - target gross margin)
For example, a delivery cost of 1,000 in your billing currency and a 50% target gross margin gives a price floor of 2,000. A 50% markup gives a price of 1,500 and only a 33.3% gross margin. These are illustrative inputs, not suggested market rates. Set a minimum project fee to cover discovery, administration, quality review, and closeout even when the technical change looks small. Use a fixed fee when the domains, senders, access, and acceptance criteria are known. Use time and materials, or a capped discovery phase, when sender ownership or vendor effort remains unknown.

Use phases so clients can approve the work

The safest commercial structure is phased. Sell monitoring first, then quote remediation based on what the data shows. If the client already has a DMARC record and enough report history, quote faster. If the domain has no useful data, start with paid discovery before committing to a fixed remediation price.
  1. Turn on reporting, inventory senders, and classify known, unknown, and unwanted sources.
  2. Fix obvious SPF, DKIM, and DNS issues for approved core systems first.
  3. Work with marketing, finance, HR, CRM, and platform owners to fix each legitimate sender.
  4. Stage changes by domain or subdomain after validating senders. Use t=y only with the legacy-receiver risk understood; the pct tag is historic.
  5. Move to the agreed enforcement state only after approved mail is passing.
Hosted policy management reduces repeated DNS tickets during staged changes. After the DNS owner delegates policy control, Suped's Hosted DMARC lets the MSP manage policy changes from the dashboard. Budget the initial setup and approved policy changes as delivery work even when the software reduces DNS administration.
Sequential DMARC changes, one TXT record at a timedns
; Publish one version at a time, replacing the previous version. ; Stage 1: monitor the sending subdomain _dmarc.mail.client.example. 3600 IN TXT ( "v=DMARC1; p=none; rua=mailto:dmarc@client.example" ) ; Stage 2: optional test mode after sender validation ; Older receivers can ignore t=y and apply p=quarantine. _dmarc.mail.client.example. 3600 IN TXT ( "v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc@client.example" ) ; Stage 3: approved quarantine policy _dmarc.mail.client.example. 3600 IN TXT ( "v=DMARC1; p=quarantine; rua=mailto:dmarc@client.example" )
Under RFC 9989, t=y requests handling one policy level lower: quarantine becomes none, and reject becomes quarantine. It is not a percentage rollout. Older receivers can ignore t=y and apply the published policy, so approve that risk before testing. RFC 9989 advises against p=reject for general-purpose email domains. Choose the endpoint for the domain's mail flows, and budget testing for forwarding and mailing lists before quoting a stricter policy.
A PSA ticket separates DMARC remediation work from recurring monitoring.
A PSA ticket separates DMARC remediation work from recurring monitoring.

Agree acceptance criteria and rework limits

Tie completion to evidence for the scoped senders and the agreed policy. A domain-wide 100% DMARC pass rate is a poor completion target because unwanted traffic still fails.
  1. Verify DMARC passes for each approved sending service, including the required domain match for SPF or DKIM against the visible From domain. Keep test-message headers with the results.
  2. Agree an observation window that covers the client's actual sending cycle. Test monthly or seasonal senders before sign-off rather than relying on a quiet reporting period.
  3. Record remaining exceptions and the client's decision for each. Keep the prior DNS values and a rollback owner with the approved change.
  4. Set a defined correction period for defects in the MSP's scoped work. Quote client configuration changes and newly added senders separately.
Specify the monitoring start date and project billing milestones so report review during delivery is counted once. State when final sign-off and payment are due. Authentication acceptance does not guarantee inbox placement.

Package monitoring and remediation without confusion

Use a proposal structure with one recurring line and one or more change lines. The recurring line is DMARC monitoring. The change lines are remediation packs, sender cleanup projects, enforcement projects, or emergency response work. This keeps margins easier to protect and makes account reviews less awkward.

Offer

Best fit

Commercial model

Monitoring only
Visibility
Recurring
Starter remediation
Known senders
Fixed scope
Sender cleanup
Mixed sources
Work order
Enforcement project
Policy change
Project
Ongoing governance
Frequent change
Managed change
Example packaging language without public MSP pricing numbers.
Before quoting remediation, review the current DMARC and SPF records and DKIM records for known selectors. Use report history and the sender inventory to decide whether a starter remediation pack fits or paid discovery is needed.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

The health check gives sales and technical teams a DNS starting point. It cannot establish sender ownership or test every sending service; report evidence and client input are still needed to size remediation.
Once the client accepts the need for remediation, the operational question becomes who owns each fix. That is where issue queues, source status, and clear steps matter. The MSP needs a repeatable way to convert findings into tickets that technicians can complete and account managers can explain.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Suped supports this service model by tying monitoring findings to concrete issues and steps to fix. MSP teams can use Suped's multi-tenant workflow to review authentication results across clients. Record approvals, work assignments, and completed implementation in the MSP's service tickets.

Set billing controls before remediation starts

The billing control is simple: monitoring identifies and tracks issues, remediation fixes approved issues, and anything outside the approved scope gets quoted before work continues. Write this into the statement of work (SOW) and the internal ticket template so sales, account management, and technical staff use the same language. Check the existing managed services agreement (MSA) first. If it already includes the fix, honor that scope and agree any revised service boundary before charging separately.
MSP delivery controls
A controlled remediation project has a client-approved endpoint and a visible path to reach it. Without those controls, the MSP absorbs vendor delays, client indecision, and legacy system cleanup.
  1. Attach screenshots, DNS records, vendor notes, and before-and-after DMARC results by sender.
  2. Require client sign-off before policy changes that affect delivery.
  3. Define when a new sender, new domain, extended vendor coordination, or client-caused rework creates added scope.
  4. Close the project with source status, final policy, and ongoing monitoring notes.
State how after-hours or accelerated remediation is priced and approved. A compliance deadline or insurer request does not automatically make routine work an emergency. The monitoring subscription provides the evidence and alerts; an approved emergency work order funds extra coordination and change control.
Clean proposal language
Monthly monitoring includes DMARC report ingestion, source review, alerts, and status reporting. Remediation work is quoted separately after issue review and client approval.
Risky proposal language
Monthly monitoring includes all DMARC fixes, sender cleanup, DNS updates, vendor coordination, policy changes, and enforcement work with no scope limit.

Separate software cost from MSP service pricing

On the offer sheet, list monitoring, starter remediation, sender cleanup, enforcement, and ongoing governance as separate selectable lines. Use discovery to size each account. For teams mapping Suped's software cost to the recurring service, use Suped's pricing page for public plans or the agreed MSP partner quote as the software input, then add the MSP's own labor and overhead without counting either twice.

Frequently asked questions

Light advisory work can sit inside monitoring, such as identifying issues and recommending next steps. If fixes are included, define an eligible task list and a monthly hour allowance. Work beyond that allowance needs a separate quote and approval.

A starter remediation pack for one domain with known senders is the easiest offer. Cap the included sending-service configurations and specify sender classification, core DNS review, DKIM setup guidance, SPF cleanup, and a written enforcement plan.

Treat unknown senders as discovery findings first. Complete validation within the agreed allowance when it is included. If a legitimate sender needs work beyond that allowance, approve a change order before implementation. Document unwanted sources without authenticating them.

Policy enforcement can be a separate milestone within a remediation project or its own work order. Define client approval, testing, rollback responsibility, and acceptance evidence. Choose the final policy for the domain's mail flows rather than promising p=reject for every client.

Suped supports the recurring monitoring layer and the remediation workflow. MSPs can use it to monitor DMARC, SPF, and DKIM, detect issues, follow steps to fix, manage hosted policy options, set alerts, and run multiple client domains from one dashboard.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing