Moosewave is in private early access and not yet generally available. Join the waitlist for an invitation.
Email marketing, measured after send
Most email tools tell you a message was delivered. That only means a server accepted it — not that a person saw it.
Moosewave measures where mail actually lands, and builds everything else on top of that.
Guided with synthetic data. Nothing is sent and no account is required.
A receiving server can accept a campaign and still route it somewhere a person will never notice. The sending response proves transport; it does not prove inbox placement.
Seedlist testing closes that gap by observing the same campaign across controlled mailboxes. It turns a vague delivery status into evidence you can inspect before the next send.
Delivery means a server accepted your message. It does not mean anyone could see it. Moosewave runs campaigns against a seedlist panel so you know where mail actually landed per provider, and checks your SPF, DKIM, DMARC, and BIMI records against live DNS — because alignment failures are the most common cause of bulk rejection and the hardest to spot from inside a sending tool.
Most automation fails quietly. A flow that enrols each subscriber once forever looks healthy while serving a shrinking population, and a branch reading 'if opened' has been unreliable since Apple began pre-fetching tracking pixels. Moosewave makes re-enrolment and exit conditions explicit per flow, so a cart reminder can run every time a cart is abandoned and stops the moment the order completes.
Segments are live definitions that re-evaluate, not snapshots someone has to remember to rebuild. Suppression sits above every segment: one unsubscribe, hard bounce, or complaint removes a person from every campaign and every automation, and no segment definition can override it. Imports cannot quietly reintroduce someone who already left.
Opens are labelled directional rather than authoritative, and are not the default basis for engagement segmentation — a metric inflated by automated pre-fetching should not silently decide who receives your next campaign. Metrics break down by segment, because a list-wide average is a blend that hides the group actually worth acting on.
Operating model / evidence lineage
Permission, eligibility, and live state converge at execution time. The selected channel applies its own boundary. What comes back—placement, response, or opt-out—is only useful when it changes a named control.
The model below separates facts the system reads from decisions it owns, so a transport result cannot quietly become evidence of human attention.
The send control path
CoveragePermission & eligibility · Decision & action · Transport & placement · Observation
What is true before an action is evaluated
What did this person agree to?
BoundarySubmitted and confirmed are different states.
Forms field guideIs this person eligible for this send now?
BoundarySuppression overrides every segment.
Audiences field guideIs the event that started this message still actionable?
BoundaryA completed order makes its cart reminder obsolete.
Commerce field guideEntry noteA scheduled campaign can enter at eligibility; a lifecycle message enters through a qualifying event.
Automation reads the records; it does not replace them
Automations / flow logic
Did a qualifying event occur?
Is the recipient still permitted and unsuppressed?
Has an exit condition made the message obsolete?
Has the delay elapsed, and is this route allowed now?
Possible resultDecision vocabulary, not live status
BoundaryAn event can start a flow. Current state decides whether it should continue.
Email and SMS do not share one permission or one delivery path
Email / delivery evidence
Authenticate before send; observe a controlled panel after.
BoundarySeed mailboxes indicate provider behaviour. They do not predict placement for every recipient.
Deliverability field guideSMS / channel policy
Check permission, time, and payload before the phone buzzes.
BoundaryEmail permission never authorises SMS.
SMS field guideThe next decision changes only when the signal deserves it
Analytics / signal quality
Click · reply · unsubscribe · complaint · store-side purchase
Server acceptance · bounce · seed placement by provider
Opens are directional · attribution depends on its model and window
BoundaryAn open is a proxy, not a human action. Attribution is a model, not causation.
Return path / named consequences
Returned evidence can change the next eligibility or branch decision. It never rewrites permission.
Our security page says what is in place, what is not, and how to report a vulnerability. The boundary is part of the product story, not fine print hidden after the promise.
The software is built. What is not open yet is availability. Join the waitlist and we will send an invitation when a place opens — and tell you about pricing before it goes on the website.
Questions about early access can also be sent to info@moosewave.com.
