Marketing automation for SMEs and growing companies

Marketing automation is a set of rules that sends a message or creates a task when a customer does something: fills in a form, goes silent after a quote, orders for the first time, or stops buying. For an SME with a small marketing team, it replaces exported lists and follow-ups that depend on someone remembering. Sensaria maps the journeys, connects the data sources (website, CRM, shop, ERP), builds the automation in your platform or as a custom service, and monitors it after launch. It pays off when you already have leads and customers but lose them between systems.

When does marketing automation pay off?

It pays off when the same moment repeats often enough that people can’t handle it reliably by hand. Typical signs: inquiries wait a day or more for a first reply, every contact gets the same newsletter, sales keep their own spreadsheets, and nobody can say which campaign brought in a customer. If you send five quotes a month, a clean CRM and a calendar reminder are enough. Automation earns back its setup through volume and repetition.

What does a working journey look like?

Here is a demo-request journey for a B2B company that sells in more than one language region:

1. The website form posts to the CRM. It creates or updates the contact, opens a deal and stores the source, UTM campaign and language.
2. The deal is assigned to an owner by language region, with a fallback owner when that person is away.
3. The visitor gets a confirmation email in their language within a minute, with a booking link.
4. No booking after three days: a second email with a relevant case or answer to a common question. No booking after seven days: a task for the owner, not a third automated email.
5. Once the demo is booked, marketing sequences pause for that contact.
6. A won deal moves the contact into onboarding. A lost deal moves them into a quarterly newsletter segment, but only if marketing consent is on record.

Each step writes an event to the contact’s timeline, so sales can see what the person has already received.

Platform workflows or a custom build?

Use the workflows of the CRM or email platform you already pay for, as long as the data they need lives there. Add connectors when important data sits in another system. Build a custom service when the rules depend on your own data model, when volume makes per-contact pricing expensive, or when data must stay on infrastructure you control.

Option	Fits when	Watch for
Native workflows (HubSpot, Brevo, ActiveCampaign, Zoho and similar)	The data is in the platform and marketing wants to edit content itself	Contact-based pricing tiers; dozens of undocumented workflows
Platform plus custom connectors	Orders, bookings or contracts live in a shop, ERP or booking system	Sync direction and field ownership must be agreed first
Custom automation service	Rules follow your own data model, volume is high, or hosting is constrained	You own the code and its maintenance

For most SMEs the middle row is the realistic answer.

How we build it

• Event and data map first. Which system emits which event, and which field is the source of truth for email address, language, owner and consent.
• Consent stored as data. Every contact carries consent status per channel, source, timestamp and the wording shown. Swiss law requires prior consent for mass advertising by email or SMS, with a narrow exception for existing customers, plus a correct sender and a free opt-out (UCA Art. 3 para. 1 let. o); EU rules are similar. The details are on our email and SMS automation page.
• Suppression at send time. Unsubscribes, hard bounces and contacts with an open support case are excluded when a message is about to go out, not when a list was built last week.
• Stop rules. Any reply ends the sequence. Our startup outreach platform tracks replies and bounces over IMAP and stops a sequence on the first reply. Its instances share one suppression list, so an opt-out recorded by one is honored by all of them.
• Dry runs before real sends. New journeys run against real data in a mode that only logs what would be sent and why. The affiliate reactivation system works this way: a shortlist with a reason for each pick comes before any message.
• Monitoring. Daily volume per journey, sync errors, contacts stuck in a step, bounce and unsubscribe rates. An alert fires when a journey sends nothing, or far more than usual.

Data quality decides the result

Automation multiplies whatever is in the CRM. A duplicate contact gets two welcome emails; a missing language field sends German copy to an Italian-speaking client. We deduplicate on email address and normalized company domain, make language and consent required fields, and flag incomplete records instead of guessing. In the reactivation system, missing activity dates are never filled in by assumption, and every profile carries a data-quality grade.

What drives cost and timeline

Driver	Why it matters
Number of journeys and branches	Each branch needs content, tests and a stop rule
Connected systems	A system without a usable API needs a workaround or a scheduled export
Data cleanup	Merging duplicates and fixing fields often takes longer than building workflows
Languages	Every template exists in each language you write to
Consent history	Contacts without proof of consent stay out of marketing until they opt in again
Platform or custom	Configuration is quicker to start; a custom service costs more upfront and less per contact

After a short discovery we send a fixed-price or phased proposal. One journey on data already in the CRM takes weeks; a multi-system setup with cleanup takes longer.

How it connects to the rest of your system

Journeys depend on the CRM behind them (CRM and sales automation), on messages that arrive (email and SMS automation) and on data from other systems (API integrations). A chatbot can start a journey too. For the path from first click to signed deal, see lead generation, or start with our guide to marketing automation for SMEs.

Why Sensaria

We have built sequencing engines ourselves, with warm-up limits, reply detection, shared suppression lists and approval queues, so we know where configured platforms stop. Sensaria AG is a Swiss company based in Lugano, working in English, Italian, German and French. Each journey is handed over with its trigger, audience, exit rules and owner written down, so your team can change it without us.