Marketing automation, self-hosted

Because Stillpoint's marketing layer sits on the same database as the CRM and the WooCommerce order sync, segments can be built from real transactional and pipeline data rather than an imported mailing list with no context behind it. A segment can combine contact attributes, deal stage and value, order history and configurable RFM (recency/frequency/monetary) data into one dynamic definition that re-evaluates as records change.

"Customers in the At Risk RFM segment with no order in 90 days" or "contacts with an open deal over $5,000 in the Negotiation stage" are segment definitions you can actually build, because the fields they reference already exist on the contact and deal records — nothing needs to be exported and re-imported to define them.

Journeys are built visually as multi-step flows with wait steps and yes/no branching, so a sequence can pause for a set interval and then split based on a condition — whether a contact clicked, whether a deal is still open, whether an order was placed — rather than firing the same fixed sequence at everyone regardless of what they did.

The campaign composer includes an audience preview, so you can see roughly who a segment resolves to before committing, and a test send, so you can check rendering and content in your own inbox before it goes anywhere near the real audience.

Every contact's consent is recorded with a source and a timestamp — where the opt-in came from and when — so you have a defensible record rather than an assumption. The suppression list tracks unsubscribed, bounced and complained contacts, and it is enforced at the point of send: no journey, campaign or segment can reach a suppressed contact, with no override switch to bypass it.

Unsubscribing is RFC 8058 one-click — the List-Unsubscribe header mailbox providers use to offer a genuine one-click opt-out — paired with a preference centre where a contact can adjust what they receive instead of leaving entirely. Provider webhooks from your configured send adapter feed bounces and spam complaints straight back into suppression automatically, so a bounce doesn't have to be discovered manually before it stops future sends.

This is a deliberate architectural decision, not a missing feature. Stillpoint owns the audience, the consent records and the journey logic — the parts that determine who should receive what, and that you should never want locked inside a third-party sender's proprietary database. Delivery, the last mile of actually getting a message into an inbox, is handed to a send adapter: SendGrid, Mailgun, Postmark or Amazon SES over SMTP, capped direct SMTP for small lists, or a handoff to FluentCRM if you're already running it.

The reason is deliverability, not convenience. Mailbox providers increasingly require SPF, DKIM and DMARC alignment and expect a sending domain's spam complaint rate to stay under 0.3%, and meeting that bar reliably is what dedicated sending infrastructure is built for. A CRM plugin bolting on its own outbound mail server is how legitimate sends end up in spam folders. Stillpoint does not itself blast bulk email — it configures and hands the job to infrastructure built specifically to get it delivered.

If you already run FluentCRM, or want mature bulk-sending on the same install, the shipped bridge lets the two work alongside each other rather than one replacing the other. Stillpoint syncs contacts to FluentCRM and applies tags automatically when a deal is won or lost and when a contact's RFM segment changes — so FluentCRM's own automations can react to sales and purchase behaviour without you re-entering anything.

Engagement data flows back the other way: opens and clicks recorded in FluentCRM show up on the corresponding Stillpoint contact record, so a salesperson can see that a prospect opened the last three campaigns without leaving the CRM. This is a companion integration, not a migration path — FluentCRM keeps its own sending, list management and automation builder, and Stillpoint keeps owning pipeline, quotes, invoices and order data.

For the full connection details see the integrations page, and for how the two products compare as categories see Stillpoint vs FluentCRM.