Skip to content
PROOF48
All answers
automation

How customer segmentation actually decides who gets which offer

Segmentation decides who gets which offer through rules. Each customer record is checked against a few facts, such as what they bought and how long ago, and gets one label. Each label maps to one offer. Automating it means the labels update themselves. At PROOF48 that could be scoped as one of the two custom automations a month in AUTOMATE.

Founder, PROOF48Updated 2026-11-166 min read

01A segment is a rule, not a hunch

A segment is a group of customers who pass the same test. The test reads facts you already store: date of last purchase, number of orders, the service they booked, the town, how they first reached you. The result is one label on the customer record, for example new, regular or lapsed. Nothing about it is clever. It is useful because the test is written down, so two people applying it to the same customer reach the same label. Keep the labels few enough to hold in your head. We hold no benchmark for how many segments a small business needs, so begin with three or four. That is our working advice, not a measured figure.

  • Facts to test: last purchase date, order count, service booked, town, first contact route
  • One label per customer at a time, so nobody sits in two groups
  • Write the test in one sentence, for example: bought once, more than 90 days ago (an example, set your own limit)
  • Begin with three or four labels (our working advice, not a measured figure)

02From label to offer: one table decides

The software does not decide the offer. You decide it once, in a table with a row per label: the offer, the channel, the day it goes out and the rule that stops it. A lapsed customer might get a reminder and a small reason to return, a new customer a welcome and a nudge toward a second visit, a regular customer early access instead of a discount. Those are examples, and we hold no data on which offer works for which group. If a person fits two rows, a priority order breaks the tie, otherwise they get two offers in one week. Add a quiet period, so nobody hears from you more than once in the span you choose. If the offer is a price cut, our Black Friday post summarises the Romanian previous-price rule for announced reductions. We did not verify how it applies to an offer shown to one segment only, so ask ANPC or a lawyer.

  • One row per label: offer, channel, send day, stop rule
  • A priority order for when a customer fits two labels
  • A quiet period: at most one offer per person in the window you pick
  • A stop rule: the offer ends for a person once they buy or once the end date passes
  • A price cut for one segment? Check the previous-price rule with ANPC or a lawyer first

03What makes it automatic, and what keeps it honest

Done by hand, segmentation goes stale: someone labels the list in March, and by June half the labels are wrong. Automation fixes one thing, the upkeep. A rule runs when a record changes, a new order, a booking, a message, or once a night, and rewrites the label. The sender then reads the label, not a list someone exported last month. The same job should log each change, so you can answer why a person got an offer. It must also respect objections. GDPR Article 21(2) gives people the right to object to processing for direct marketing, which includes profiling related to it, and Article 21(3) says that once they object, their data is no longer processed for that purpose. So an objection has to remove the person from every offer, not just the last one sent. Whether you may email a given person at all is a consent question that this post does not settle.

  • Trigger: a record changes (order, booking, message), or a nightly check
  • The label is rewritten by the rule, never typed by hand
  • A log row for every change: who, which label, which rule, when
  • An objection or opt-out removes the person from every offer at once (GDPR Article 21(2) and 21(3))
  • Consent to receive marketing is a separate question, settle it before anything is sent

04Where PROOF48 is the wrong choice

If your email or booking tool already tags customers and sends by tag, use it and stop reading. Features differ by tool, so check yours. AUTOMATE costs 2,997 EUR a month and includes everything in GROWTH, which makes it the wrong purchase for a list you could sort by hand in an afternoon. What AUTOMATE lists is a CRM, a website chatbot that qualifies and books, DM and email auto-responders, booking automation and 2 custom automations a month. It does not list segmentation or offer sending, and we do not claim it runs newsletters. So a tagging rule on your CRM records would be scoped first, and the bulk send would stay in your own email tool. It covers neither WhatsApp nor phone. A store with checkout is a separate build at 2,500 to 4,500 EUR, and a larger custom system is quoted separately and may need a deposit, as our terms say.

  • Your email or booking tool already segments: switch it on, pay nothing extra
  • A short list you can sort by hand: AUTOMATE at 2,997 EUR a month is the wrong buy
  • Customer records with no purchase date or contact route: fix the data before any rule
  • Customers reach you by WhatsApp or phone: outside AUTOMATE
  • A store with cart and checkout: separate build, 2,500 to 4,500 EUR, not the 48-hour offer
  • A larger custom system: quoted separately, may need a deposit per our terms
From a build we shipped

A marketplace that tells nearby customers, and what we have not measured

FreshBatch is a food marketplace PROOF48 built, live at freshbatch.app with more than 19 businesses publishing batches. Its shipped list includes customer notifications when a batch lands nearby and a campaign system for producers to run offers. That is the closest thing in our work to a rule deciding who hears about what. The case study does not record how those audiences are chosen or what any offer returned, and we publish no transaction volume. So this article explains the mechanism, not a result we measured.

See the build: FreshBatch

Questions, answered

How many segments does a small business need?

We hold no benchmark. Begin with three or four labels that each lead to a different offer, and add one only when you can say what that group would be sent.

Does segmentation need a CRM?

It needs one place where customer facts are stored and a label can be written back. That can be a CRM, a booking tool or an email platform. AUTOMATE includes a CRM, so check whether the tool you already pay for does the same.

Can PROOF48 send the offers to each segment?

Not as a listed feature. AUTOMATE lists DM and email auto-responders, which reply to incoming messages, and we do not claim it runs newsletters or bulk sends. A segmentation rule could be one of its two custom automations a month, scoped before we build. The bulk send would stay in your own email tool.

Do I need consent before I segment people?

Sending marketing to a person is a consent question, and objecting to profiling for direct marketing is a right under GDPR Article 21. This post is not legal advice. Ask a lawyer or your national data protection authority about your case.

Where PROOF48 fits

Segmentation is a written rule that gives each customer one label, plus a table that gives each label one offer, a priority order and a stop rule. Automating it keeps the labels current and logged, and an objection removes a person from every offer. PROOF48's AUTOMATE, 2,997 EUR a month, lists a CRM and two custom automations a month, not offer sending, and we say plainly when your own email tool already does the job.

· Founder, PROOF48

Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.

Related articles

automation

How the automatic birthday message actually gets sent, and what triggers it

An automatic birthday message needs four things: a stored birth date, a daily check that compares it with today's date, permission to email the person, and a channel, usually email. PROOF48's plans list email auto-responders and a CRM but no birthday feature, so a sender would be a custom automation.

Read it
marketing

How to actually choose an email marketing platform for a small business

Choose an email platform by five things, not by feature lists: the size of your list and how many emails you send, whether it records how each person signed up and offers one-click unsubscribe, the automations you need, the cost when your list grows, and whether you can export everything. PROOF48 does not resell any platform.

Read it
marketing

How to actually build a customer persona for a five-employee business

To build a customer persona for a small business, talk to five recent customers, then read your reviews and messages for the words they actually use. Write one page per customer type: the situation that made them look for you, what almost stopped them, and how they decided.

Read it
automation

What "two custom automations a month" actually means

Two custom automations a month, the line inside PROOF48's AUTOMATE plan, means two workflows built specifically around how a business already operates, not two generic templates picked from a menu: connecting a booking system to a spreadsheet nobody wants to update by hand, or routing a specific kind of lead differently than the rest. AUTOMATE costs 2,997 EUR a month and bundles that allowance alongside a website chatbot, DM and email auto-responders, booking automation and a CRM.

Read it