The Agreement Is Won Ninety Days Before It Renews.
JaxSuite AI runs outbound for managed service providers on infrastructure you are able to audit: your own sending subdomain, dedicated IPs, automated warm-up, and sequences timed to renewal dates rather than to a campaign calendar.
This page reached you by email. Look up the SPF and DKIM on that message with the free checkers on this site, because that check is your day job.
One Provider Campaign, Start to Finish
Renewal Window Sequence · 90 Days Out
- Subdomain AuthenticatedSPF, DKIM and DMARC published and verifiedDone
- Warm-Up CompletedVolume ramped on the sending accountDone
- Account List FilteredEndpoint counts and regions you coverDone
- Delivered and AuthenticatedPassing the checks the receiving side runsDone
- Reply From the Operations DirectorAsking what a switch actually involvesIn Progress
- Technical Assessment BookedStraight onto the calendar from a link
Account created with the renewal date attached
Why Provider Pipelines Stall at the Size of the Referral Network
Managed services is a recurring revenue business, and recurring revenue makes prospecting feel optional right up to the quarter a large client is acquired, taken in house, or lost to a competitor. The pipeline that has to replace that contract was never built, because nothing forced anyone to build it.
How Most Providers Fill the Pipeline
- Referrals only, so growth is capped by the number of clients you already have
- A quarterly newsletter to a list assembled from business cards and old tickets
- Campaigns sent from the same domain that carries alerting and ticket notifications
- Cheap sending through a shared IP pool, alongside senders you cannot inspect
What That Produces
- Seat growth that tracks client goodwill rather than anything you control
- No visibility into who is near term, so timing is luck rather than a plan
- Alerting mail filtered because campaign volume damaged a shared reputation
- Technician hiring planned against revenue nobody can forecast
Where the Agreement Is Actually Decided
- 1The term date sits ninety days outThe window opens here, and it opens quietly
- 2An SLA gets missed, or the internal administrator resignsA sender already in the inbox gets the callJaxSuite AI
- 3They ask their peer network who to talk toA referral reaches them before you do
- 4Two providers are invited to quoteThe shortlist is closed and you are not on it
- 5The auto-renewal clause runs for another termThe next window is a year or three awayToo Late
The Trigger Is a Renewal or a Loss, Not a Campaign Idea
Nobody changes provider because a well-written email arrived on a Tuesday. They change when an agreement approaches term, when the one internal administrator resigns, when a cyber insurance questionnaire comes back with gaps, or when an incident makes the incumbent unforgivable. Outbound that works in this market is outbound aimed at those dates.
Ninety Days Before Term
Agreements run in one and three year terms with auto-renewal clauses, so the decision window is narrow and it opens long before anybody circulates a request for proposal. A sequence timed to that date reaches somebody who is already thinking about it.
Renewal window openTerm dates held on the account record, with sequences scheduled against them.
The Week After Something Broke
An outage, a failed restore, a ransomware scare or a resignation in the internal team turns a settled client into a shopping one. Being in the inbox already at that moment beats arriving after the peer recommendation has.
Incumbent just failedLong follow-up cadences that keep a dormant account warm for months on end.
Sending Infrastructure Built to Be Audited
You administer mail for other organisations, so this section is written in the vocabulary you already use rather than around it. Every item below is something you can verify from the outside.
SPF, DKIM and DMARC on Your Own Domain
- One include to add, kept well inside the ten DNS lookup limit that breaks SPF records
- DKIM signing and DMARC alignment on your sending domain, not on a vendor one
Dedicated IPs With Automated Warm-Up
- A dedicated sending IP, so the reputation belongs to you and not to a pool of strangers
- Warm-up ramps volume on every new account without anybody scheduling it
Keep Campaigns Off the Domain That Carries Alerting
- Send from a dedicated subdomain with its own records and its own reputation
- Ticket notifications, monitoring alerts and client mail keep the standing they already have
Filter by Endpoint Count and Service Area
- Narrow a database of over 300 million contacts to the sizes and regions you support profitably
- Reach whoever owns the vendor relationship rather than the help desk queue
Sequences Aimed at a Term Date
- Hold the incumbent, the endpoint count and the renewal date on the account in the built-in CRM
- Cadences that run for months, because the window you want is months out
Assessments Booked Without a Thread
- BookMe links against Google, Outlook and Zoom, so a technical assessment lands on a calendar
- JaxForms takes assessment requests from your own site into the same pipeline
- Account
- Term date
- Sequence
- Assessment
- Agreement
Do not take the authentication story on trust.
DNS records are public and you already know how to read them. Start with what alignment actually requires, then go and look ours up.
Read the DMARC ExplainerYou Are Going to Audit This, So Here Is the Short Version
Readers of this page look up the records before they look at the pricing, which is the correct order. So rather than adjectives, here is what a cheap sending tool does to your domain and what is set up here instead.
What Cheap Sending Does to Your Domain
- Routes your mail through an IP pool shared with senders you have no way to inspect
- Asks for an SPF include that pushes the record past the ten lookup limit and breaks it
- Signs with a vendor domain, so DMARC alignment fails on the domain you actually own
- Ramps a cold domain to full volume on day one and calls the deferrals normal
What Is Set Up Here Instead
- Dedicated IPs, with automated warm-up running on every sending account
- Google Workspace and Microsoft 365 sending, so signing stays on your own domain
- Inbox rotation on the Elite tier, so volume spreads instead of concentrating
- Fifty sending accounts on the free tier, which is enough to test the setup honestly
The Buyer Changes as the Practice Grows
A three person break and fix shop and a forty seat provider with a service desk are not the same customer. The difference is not budget, it is who has the time and the authority to run new business at all.
Owner Technicians
Two to five people, and you are still closing tickets at four in the afternoon. Outbound has to run unattended, which means sequences that keep going while you are on a client site.
Providers With a Dedicated Sales Lead
Past roughly fifteen staff there is one person who owns new business. They need term dates, incumbents and account owners in a shared pipeline rather than in a spreadsheet only they can read.
Co-Managed and Advisory Practices
You supplement an internal team rather than replace one. That is a different pitch and a different list: organisations that already employ IT staff and are short of capacity, not ones with nobody at all.
One Pipeline the Whole Practice Can See
Technician capacity is planned months ahead, so new business has to be visible before it arrives. Accounts, term dates, incumbents and sequence state sit in one workspace, so whoever is preparing a quote knows what was already sent and by whom.
- Term date and incumbent provider held on the account record
- Sequence state visible, so nobody contacts one prospect twice
- Roles for owners, new business staff and the service desk
- Slack notifications the moment an account replies
- Sequences
- Accounts
- Renewals
- Pipeline
Active Sequences (4)
- Renewal window, 90 days outLive
- Firms with no internal IT staffLive
- Co-managed, 50 to 200 endpointsWarming
- Post-incident follow-upPaused
Capacity Sized to the Volume, Not to the Payroll
A four person provider and a forty person one send comparable volumes, because the work spreads across accounts rather than across people. So capacity here is counted in sending accounts, rotation and reputation rather than in seats.
The people you are actually chasing are already on a list.
Directors of IT, the buyers who own the vendor relationship, with validation and the same sending infrastructure behind them.
See the IT Director ListA Setup Review From People Who Also Read Headers
The part genuinely worth a conversation is the sending setup: which domain, which subdomain, which records, and how fast volume ramps. Getting it wrong is more expensive for a provider than for anyone else, because the domain carrying your campaigns often carries client alerting as well.
- Domain and subdomain choice reviewed before the first campaign goes out
- Records checked against what the receiving side will actually test
- Warm-up schedule matched to the volume you intend to reach
- Free tier first, paid plans from $39 per month
How the Setup Goes
- Separate the SendingChoose a subdomain for campaigns, so alerting and ticket mail keep a reputation of their own.
- Publish the RecordsSPF, DKIM and DMARC on the sending domain, verified with the same checkers you point at client domains.
- Ramp the VolumeWarm-up runs per account, and volume rises only as far as the reputation supports.
Audit the Setup Before You Buy Anything
You own the tooling to check every claim on this page. Use it.
- 1Our own records, auditableRun the free SPF, DKIM and DMARC checkers on this site against the mail that brought you here
- 2Free workspace to test inFifty sending accounts on the Core tier, with no card and no call first
- 3Sending on a subdomainPublish the records, let warm-up finish, then send one small sequence
- 4Headers you can inspectCheck the authentication results on what lands, then decide
It works
Point it at every term date in your territory and plan technician capacity against the pipeline.
It does not work
The headers will tell you inside a week, and an afternoon is all it cost.
No card on the free tier. No certification is claimed on this page and no compliance posture is implied: read the records and judge the setup on what you find there.