Solutions · growing portfolios

Scale the portfolio,
not the overhead.

Add brands, teammates, and automations without a sales call.

Permission first. Every brand distinct.
The problem

Growth should not trigger a procurement cycle.

The moment a portfolio outgrows a newsletter tool, the next step up is usually an enterprise suite: a demo, a quote, an annual commitment, and an onboarding project. The capability is real, but so is the standstill while you buy it.

SendNectar is self-serve at every size. Add a brand, invite a teammate, publish another workflow, connect another provider — the ceiling moves with your plan, not with a contract negotiation. Usage alerts warn you at 70%, 85%, and 100% so capacity is a decision, not a surprise.

What you get

Growing portfolios, specifically.

01

Add brands on demand

A new brand is a workspace, not an implementation. Create it, attach a legal entity, verify a domain, connect a sender — and it is live and isolated.

02

Real journeys at scale

Workflows support up to 500 nodes, 1,000 edges, and 50 triggers per definition, so a mature lifecycle program fits in one flow instead of five stitched together.

03

Predictable, published pricing

Four tiers, priced on brands, contacts, active workflows, and processed events. Annual billing costs ten months, not twelve. No quote, no seat negotiation.

04

Warnings before walls

Usage alerts fire at 70%, 85%, and 100%. Hit a limit and we preserve your data and running journeys, restrict only net-new usage, and give you a seven-day grace period.

05

Multi-provider routing

Weighted routing with priority and a designated fallback per message class means growth in volume becomes a routing decision, not an outage.

06

Governance that scales with you

Region-aware retention policies, legal holds, and risk events keep a hundred brands as defensible as three.

In the product

The ceilings, stated up front.

Nothing here is gated behind a conversation. These are the actual structural limits in the product.

Workflow size
Up to 500 nodes, 1,000 edges, and 50 triggers per definition
Step types
17, from trigger and condition through split test, goal, rate limit, and exit
Routing
Priority + weight per sender profile and message class, with fallback routes
Rate limits
Hourly, daily, and monthly caps plus max concurrency, per provider connection
Frequency caps
Layered and prioritized per brand, topic, and message class
Retention
Region-aware policies that delete, anonymize, or archive on schedule

Bring your provider.
Keep your brands distinct.
Start today.

Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.