For agencies
SendLint for agencies
Set up each client’s rules once. Every campaign then gets the same QA pass, a fix list for the developer, and proof the client can check for themselves.
The sample is a fictional campaign for a brand called Northwind. It shows a complete report, not a client’s data.
How an agency runs a campaign
- 01
Set up the client rulebook once
Create the client, import its brand guide PDF, and set each check to On, Warn or Off. Add brand voice samples. Every campaign for that client runs against the same rulebook.
- 02
Run round 1 in minutes
Paste the HTML, drop the .html or .eml file, or fetch a URL. Attach the copy deck and the creative as a PDF, PNG or JPG. Batch mode takes every language version in one run, and each email is rendered in real desktop Outlook, light and dark, next to the browser captures.
- 03
Hand the developer the variance log
Each finding lists the versions it affects, the fix in the developer's terms, and the evidence. Download it as a .docx, or share a dev brief link.
- 04
Round 2 verifies the fixes
Run the fixed files as the next round. Each finding moves to Verified fixed, stays Open, or comes back as a Regression. Nothing is re-read by hand.
- 05
The client signs off
Share the read-only portal so the client can follow round status without a login. Marking the round complete mints a SendLint Approved certificate with a public verify page.
Seats that match how agencies staff
One paid seat runs the work. Everyone who reviews, fixes or signs off joins for free. Pricing is on the pricing page.
Paid
Member
QA leads and account admins
- Run analyses
- Edit brand rules and check policies
- Sign off rounds
- Create share links and client portals
- Export the compliance PDF
- Manage seats and billing
The only seat that is billed.
Free, unlimited
Reviewer
Designers, developers, account managers
- View reports and the round matrix
- Comment on findings
- Update finding status
- Add a finding SendLint missed
- Import an existing bug log
- Grant approval under a two-party policy
Cannot run analyses, edit rules or send a round back.
Free, no login
Client viewer
Brand-side stakeholders
- Open a per-campaign portal link
- See a status pill per round
- See finding counts by status
- See the seal once a round is approved
- Open the public verify page
Never sees email source, snippets or internal notes. Revoke the link at any time.
One rulebook per client
A client in SendLint is a rulebook, not a folder. Each one holds:
- Brand rules. Palette, typography, logo variants, trademark treatment, CTA wording, template width and spacing.
- Check policies. Every check set to On, Warn or Off for that client. A standing false flag can be dismissed client-wide.
- Brand guide import. Upload the client’s brand guide PDF. SendLint proposes rules with the page and quoted text behind each one. Nothing saves until you review the list.
- Brand voice samples. Approved emails that show the client’s tone, used by the Brand Voice check.
- Notifications. The client’s own Slack channel for round and approval updates.
- Compliance policy. What a round must pass before it can be approved, and whether approval needs two people.
Starting a new client takes one click: copy the rules from an existing client, or fork a client to branch a variant. The full walkthrough is in the guide on turning a brand guide PDF into QA rules.
Where it fits
- Slack. Each client channel gets round notifications and approval pings. Add to Slack with one click, or paste a webhook.
- Real Outlook. Renders come from desktop Outlook on Windows, light and dark mode, produced by the real application rather than a browser imitation. Desktop, mobile and tablet captures sit beside them.
- REST API. Analyze, read reports and verify a hash from your own pipeline with a bearer key. The verify call blocks a send whose bytes changed after approval.
- Webhooks. Signed events for finished analyses, round status, approval requests, mentions and certificates, so findings land in Jira, Asana, ClickUp, Zapier or Make without copying.
- Existing bug log. Import the client’s current tracking sheet as CSV. SendLint matches rows to findings, shows a preview, and you confirm.
- Share links. Report links, client portals and dev briefs are separate links for separate audiences. They expire after 30 days by default and can be revoked.
- Your QA process stays the QA process. SendLint runs the checks and keeps the record. Your rounds, reviewers and sign-off happen inside it, not in a side spreadsheet.
Every setting is documented in the help centre, and the checks themselves are written up in the guides.
Frequently asked questions
- Can one workspace hold several clients?
- Yes. Every client has its own rulebook, campaigns, share links and Slack channel. Members and Reviewers in the workspace can work on any client. Add a client from the Clients page, copy the rules from an existing client, or fork a client to branch a variant.
- Who can approve a round?
- A Member marks a round complete. Approval is earned: the round must pass the client's compliance policy, or the Member overrides with a typed reason that goes on record. With two-party approval turned on, the Member's action becomes a request and a Reviewer grants it. The certificate records which mode was used.
- What does the client see?
- The client portal shows the campaign label, a status pill per round, finding counts by status, and when it was last updated. Once a round is approved it shows the SendLint Approved seal, linking to the public verify page. It never shows email source, finding snippets or internal notes.
- Which copy deck formats work?
- .docx, .pages and .pdf decks. A table with a section column and one or more language columns reads best, and a plain document with headings works too. Decks with Launch and Reminder version tables, or Email 1 and Email 2 headings, are read per version. Before you run, SendLint shows what it captured from the deck so you can correct it.
- Does SendLint render in real Outlook?
- Yes. Every run can render the email in desktop Outlook on Windows, in light and dark mode, using the real application on a machine SendLint operates. Desktop, mobile and tablet captures come from a browser engine alongside it, so a layout finding names the client it broke in.
- Which ESPs does SendLint support?
- Any. SendLint reads the built HTML, an .eml saved from the sending platform, or a hosted URL, and it recognises personalization tags from Salesforce Marketing Cloud, Mailchimp, Klaviyo, Braze, HubSpot, Marketo, Iterable, Customer.io and Campaign Monitor. The pre-send gate is one HTTPS call that checks a SHA-256 hash against the certificate, and the help centre includes a Salesforce Marketing Cloud recipe.
- Which languages are checked?
- English, French and Spanish. Multilingual campaigns are checked per language against the matching deck column, including language leaks, links that do not switch language, and the typography rules of French and Spanish.
- Is there a trial?
- Run one email through the free demo without an account, or open the sample campaign to see a full multi-round report. Accounts start on a paid plan with one Member seat; Reviewer seats and client links are free.
Start with one client.