Why our cannabis emails reach the inbox
Twice the Gmail open rate of Alpine IQ, measured head-to-head on the same store, same 30-day window, distinct recipients: 40.1% vs 19.7%. Deliverability is not a trick or a setting. It is a mail server made for your store, a sending IP nobody else uses, and someone watching the neighborhood around it every day. That someone is us.
Methodology note: figures measured on one store sending through both platforms in the same window. Your numbers depend on your list and your history.
Your dedicated IP · warm-up send cap
Day 14 · 16,000 sends/day
One mail server instance built for your store, one sending IP nobody else uses. We run the warm-up, the volume ramp and the complaint and bounce thresholds on it.
Your store's own sending IP, warmed by us. Daily caps step up on their own, engaged recipients go first, and the ramp pauses automatically if complaints or bounces cross the safety line. Nobody at the store has to watch a dial.
Monthly sending bill
Your sending bill
Legacy per-contact platform, shared IP pool
$650-750/mo (typical)
Your own mail server + dedicated IP
$250/mo
~64%
less · ~$450/mo back in your pocket
The band we see most often on invoices at this list size.
You are not buying a seat on a shared platform. We stand up a mail server instance for your store and give it a dedicated sending IP that only your store uses, then we run the whole IP neighborhood around it: warm-up, volume ramp, complaint and bounce thresholds, blocklist monitoring, reverse DNS, SPF, DKIM and DMARC alignment. That is why the number below is a price rather than a margin on somebody else's platform.
Typical for legacy per-contact platforms; check your own invoice. Not a quote from any named vendor. Firm monthly price for sending at that volume. No per-contact ladder.
Attributed revenue
Payday Flash
$4,310
from 96 POS tickets
7-day window · completed tickets only
Open rate
MeasuredOur sending
40%
Their old platform
20%
Same list, same store, after migration.
Click rate
IllustrativeOur sending
5.4%
Their old platform
2.1%
Clicks reported as totals, never "unique".
Simulated product UI · revenue matched from POS tickets, not clicks · our sending prices are firm; "their bill" figures are typical ranges, not any vendor's quote
The real reason dispensary email lands in spam
Legacy cannabis platforms put hundreds of dispensaries on the same shared IP pools. Your store's reputation is welded to senders you have never met: their purchased lists, their complaint rates, their mistakes. When a mailbox provider penalizes the shared range, your perfectly clean campaign goes to spam with everyone else's. Then you pay per contact for the privilege, so the invoice grows every time your list does.
General-purpose ESPs add a second problem: policy risk. Cannabis is either quietly tolerated or outright restricted, which means your account can be flagged or suspended mid-campaign with no appeal path. The fix for both problems is the same. Your store gets its own mail server instance and its own sending IP, run by a platform that declared cannabis up front and got approved anyway. That is what we built, and it is the backbone of our dispensary email marketing platform.
The stack, in plain English
No black boxes. This is what we stand up for every store on our platform, on day one, at every price tier.
Your own mail server instance
We stand up a mail server for your store. It is not a seat on a shared platform: your sending configuration, your warm-up state and your reputation live on an instance built for you, on a mail transfer agent we operate ourselves.
A sending IP that is yours alone
Two dedicated IPs per store, one for marketing and one for transactional mail. When another brand's list generates spam complaints, it happens on their IP. Nothing about their sending touches your reputation.
Authentication configured for you
SPF, DKIM signing, DMARC alignment and matching reverse DNS are set up per store and re-checked automatically, so mailbox providers can verify that your mail really comes from you.
Per-provider routing
Gmail, Yahoo, and Microsoft each police mail differently. We route per mailbox provider, so sending strategy for one provider never jeopardizes standing with another.
Engagement-first sending
New volume goes to your most engaged recipients first, building positive signals with mailbox providers before colder addresses enter the rotation.
Governed backup lane
A separate, approved sending lane stands by as spillover and failover with a one-click switch, so a network-level issue never silently stops your campaigns.
The warm-up governor
Fresh IPs have no reputation, and mailbox providers distrust sudden volume. So the platform ramps automatically: daily send caps that grow on a fixed schedule, from a careful first day up to tens of thousands per day, with your most engaged recipients mailed first at every step.
The governor also has brakes. If complaints exceed 0.1% or bounces exceed 5%, sending pauses automatically, before a mailbox provider has to intervene. Temporary failures trigger throttling instead of blind retries. The system protects your domain from your own enthusiasm, which is exactly what you want from the thing that carries your revenue. If you are moving from another platform, this same ramp powers the 2-hour switch from Alpine IQ: sending on day one, full engagement-first cutover in about two weeks.
The IP neighborhood, managed by us
A dedicated IP is only worth having if somebody keeps the neighborhood around it clean. That is our job, not yours. From the day your instance goes live we own the warm-up schedule, the volume ramp, the complaint and bounce thresholds, the automatic pause when something spikes, the blocklist checks, and every authentication record your mail depends on. Nobody at your store has to learn what a DMARC policy is, open a DNS panel, or decide how many emails today is too many.
The practical difference: on a shared pool, someone else's bad send is your problem and you find out about it when your revenue drops. On your own IP, the only sending that can affect your reputation is your own, and when it wobbles we see it in hours and act before a mailbox provider has to.
Warm-up schedule
A fixed ramp on your new IP, starting small and stepping up daily. You do not set it, approve it, or wait on it. Sending starts on day one while the ramp runs underneath.
Volume ramp
Daily send caps grow as the IP earns trust, with your most engaged recipients mailed first at every step so the early signals mailbox providers see are good ones.
Complaint threshold
Spam complaints are tracked per campaign and per provider against a 0.1% line, which is the level mailbox providers themselves treat as trouble.
Bounce threshold
Hard bounces are watched against a 5% line, and every bouncing address is suppressed at send time so it cannot be mailed again through a later import.
Auto pause on spikes
If complaints or bounces cross the line, sending on that IP pauses by itself and we investigate. Temporary failures throttle instead of retrying blindly.
Blocklist monitoring
Your IP and sending domain are checked against the major public blocklists on a schedule, plus reputation feedback from the providers that publish it.
Reverse DNS
Your IP resolves back to a hostname that matches the mail it sends. Mismatched reverse DNS is a quiet, common reason ordinary mail gets filtered.
SPF, DKIM and DMARC alignment
Records are prepared for your domain, DKIM signs every message, and we verify that SPF and DKIM stay aligned with DMARC as your setup changes.
All of it is included at every tier, because it is not an add-on. It is the product. The same instance and the same dedicated IP carry your automated campaigns and your wallet card notifications, so one reputation covers everything you send.
Approved, cannabis-disclosed sending
Our backup sending lane was approved with full cannabis disclosure. We told the provider exactly what our customers sell, and got production approval anyway. That matters more than it sounds: it means no gray-area sending, no borrowed reputation, and no surprise shutoff the week of your biggest promo.
Compliance hygiene is enforced by the software, not by a checklist:
- Signed, per-recipient one-click unsubscribe with RFC 8058 headers, the standard Gmail and Yahoo now require of bulk senders.
- Suppression enforced at send time: unsubscribed and bounced addresses are blocked at the moment of sending, not just filtered at import.
- Consent records kept for every signup: IP, user agent, and timestamp.
- Two-way opt-out sync with Alpine IQ for stores running both platforms, so compliance never drifts between systems.
Behind it all sits monitoring: reputation checks, blocklist monitoring, and a twice-daily watchdog that verifies complaint, bounce, and infrastructure health so problems are caught in hours, not billing cycles.
vs Alpine IQ: a shared pool vs your own mail server
Credit where due: Alpine IQ's deliverability dashboard is one of the better screens in their product, and if you need SMS today, they offer a channel we deliberately do not. But their email rides shared platform infrastructure, their model reportedly includes per-message components (we computed roughly $2.47 per 1,000 emails from real invoices), and we have observed campaigns leaving their internal queue about 15 minutes after the scheduled time.
Read their own email feature page and the silence is the tell: as of our August 2026 review it markets the drag-and-drop builder, templates, A/B testing, and abandoned-cart emails, and never mentions IPs, warm-up, or authentication once. AIQ's serious delivery engineering (automatic 10DLC registration, message vetting, quiet-hour enforcement) lives on the SMS side, where carriers force the issue. SpringBig's homepage claims the "highest deliverability for regulated industries" while its communications page describes email as "customizable templates," a claim with no published numbers behind it. We publish the measurement and the methodology.
The head-to-head result is the point: on the same store, in the same 30-day window, Gmail opens ran 40.1% through our dedicated-IP infrastructure against 19.7% through Alpine IQ. Same customers, same brand. Different infrastructure. The full breakdown, including where Alpine IQ is still the right choice, is on our Alpine IQ alternative comparison.
vs Klaviyo and Mailchimp: the general-ESP problem
Klaviyo and Mailchimp are excellent products for mainstream retail. That is not the issue. The issue is policy and pooling. Klaviyo tolerates cannabis email but explicitly bans cannabis SMS; Mailchimp's acceptable-use history has repeatedly caught cannabis businesses in suspensions. Either way you are one policy review away from losing your list access, and on their standard plans you share IP pools with thousands of senders whose behavior you cannot see.
They also know nothing about your store. No POS connection means no purchase-based segments, no inventory-driven campaigns, and no register-verified results. Those are the things that make dispensary email actually work, covered under campaign-to-POS attribution. A cannabis-declared platform on dedicated IPs gives you the deliverability without the policy roulette.
What your own mail server costs
Here is the part people expect to be expensive. One store's real invoices: $1,240 for a month of sending on Alpine IQ, then $12 the following month with us, same store, same sending pattern. Your own instance, your own IP and the managed neighborhood around it are not a luxury line item. Modern sending is radically cheaper to run than legacy per-contact pricing, and that gap has been funding platform margins rather than your inbox placement. See how it flows through on our public pricing page.
Frequently asked questions
Watch your own domain hit the inbox
Book a 20-minute demo. We'll walk through the dedicated-IP setup, the warm-up plan for your list, and the head-to-head numbers behind it.