Fixed quote after a free call

A beauty CRM that knows when each customer will run out

Beauty customers reorder when a product runs out, and a 30 ml serum runs out on a different schedule from a 200 ml cleanser. We connect your store, subscription app, reviews and help desk into one customer profile in Klaviyo or HubSpot, build replenishment reminders timed to each product size, add shade and skin-concern preferences the customer gave you, and pause marketing whenever a customer has reported a reaction or complaint. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why generic restock emails miss beauty customers

Most beauty brands send the same "time to restock?" email thirty days after every order, whatever was bought. Customers who bought a three-month moisturiser get nagged; customers who use a mascara up fast hear nothing and buy elsewhere.

Meanwhile the data that would fix it is split across Shopify orders, Recharge subscriptions, Okendo or Yotpo reviews with shade and skin-type answers, and help desk tickets. A customer who reported irritation can still receive a cheerful cross-sell for the same product line.

What we build

What our beauty CRM and replenishment email flow includes

Unified customer profile

Orders, subscriptions, review answers and tickets joined into one profile with consent recorded.

Usage-based replenishment

Reminders timed per product and size from your own usage estimates and real reorder intervals.

Shade and concern preferences

Shade, undertone, hair type or skin concern captured from quizzes and reviews (with consent) to personalise recommendations.

Subscription save flows

Skip, swap or delay offered before cancellation, through the subscription app's API.

Safety-aware suppression

Any open complaint or reported reaction pauses marketing for that customer until the case closes.

Retention reporting

A weekly email with replenishment conversion, subscription churn and repeat rate by hero product.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Order or event lands

    A purchase, subscription change, review or ticket updates the profile.

  2. 02 Automated

    Run-out date estimated

    Product size and usage rules set the next replenishment date.

  3. 03 Automated

    Flow starts or pauses

    Replenishment or cross-sell starts; any open complaint pauses marketing.

  4. 04 Team review

    Retention lead reviews

    The CRM lead checks segment changes, failed syncs and save-flow exceptions.

  5. 05 Founder or regulatory lead decides

    Offers and positioning

    Discount levels, bundles and which products are recommended together are decided by the founder.

How it behaves

How the cosmetics CRM behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A reminder shortly before their product runs out
  • Recommendations that match the shade or concern they shared
  • Skip, swap or delay options on subscriptions
  • No promotions while a complaint is open

What the team sees

  • One profile per customer with orders, subscriptions and reviews
  • Exceptions and failed syncs flagged
  • A weekly retention report by hero product

What the automation does

  • Estimates run-out dates per product and size
  • Starts, pauses and stops flows by rule
  • Logs every sync and send

Edge cases and fallbacks

Customer buys two sizes of the same product
The run-out estimate uses combined volume.
Gift purchase for someone else
Marked by order notes or gift options and excluded from replenishment.
Quiz answers without marketing consent
Used only for on-site recommendations, not email.
Subscription or CRM API outage
Events queue and retry in order, and the retention lead is alerted.

Architecture

A beauty CRM and replenishment flow at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Store orders Shopify Subscriptions Recharge Reviews and quiz Shade, skin type n8n Join and estimate Customer profile Klaviyo or HubSpot Replenish flows By size and usage Retention lead Exceptions Weekly report Repeat and churn
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Orders, subscription changes, reviews and quiz answers arrive by webhook.
  2. 2 n8n joins them to one profile and estimates when each product will run out.
  3. 3 Replenishment and cross-sell flows start on time, and pause if a complaint or reaction is open.
  4. 4 A weekly report shows replenishment conversion, churn and repeat rate by hero product.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Beauty CRM & replenishment flow automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current flows, product sizes and usage estimates, subscription setup, review questions and consent records.

  2. 02

    Design

    2 to 3 days

    Replenishment rules per product, segments, suppression rules and report layout.

  3. 03

    Build

    1 to 2 weeks

    Profile sync, run-out estimates, flows, save offers and reporting.

  4. 04

    Shadow run

    About 1 week

    Flows send to an internal list while we compare timing with real reorders.

  5. 05

    Launch

    1 to 2 days

    Switch flows to customers and walk the team through the dashboard.

  6. 06

    Support

    Ongoing

    New products, seasonal flows and sync monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Shopify Admin GraphQL API and webhooks Recharge API (subscriptions, charges, webhooks) Klaviyo API Okendo Merchant REST API Gorgias API

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Usage rules, segments, flow map and reporting.

    $200 – $400

  • Build

    Profile sync, run-out estimates, flows and suppression.

    $500 – $1,300

  • Integrations

    Store, subscriptions, reviews and help desk.

    $150 – $400

  • Testing and shadow run

    Internal sends compared with real reorders.

    $100 – $250

  • Launch and training

    Switch-over and retention lead walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Klaviyo, Recharge, reviews and n8n plans are billed to you directly. Retail or wholesale accounts in the same CRM may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Marketing platform and subscriptions: Your Klaviyo, HubSpot and Recharge plans.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: commercial email

CAN-SPAM requires a physical postal address in marketing email and opt-outs honoured within 10 business days.

Source: www.ftc.gov

UK: electronic marketing

PECR requires consent, or the soft opt-in for existing customers, for marketing email and texts, with an easy way to refuse in every message.

Source: www.legislation.gov.uk

Gmail bulk sender rules

Brands sending 5,000 or more messages a day to Gmail need SPF, DKIM and DMARC, one-click unsubscribe and a spam rate below 0.30%.

Source: support.google.com

EU and UK: skin concerns can be health data

Answers about skin conditions may count as health data under Article 9 GDPR, so we collect only what personalisation needs, with explicit consent.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Beauty CRM & replenishment flow automation questions, answered.

For a beauty brand, a CRM is the customer profile that holds purchases, subscriptions, shade and skin preferences and engagement, and drives flows from it. It is usually a marketing platform such as Klaviyo or a CRM such as HubSpot connected to your store.

Each product gets a usage estimate by size, set by your team and refined from real reorder data. The flow sends a reminder shortly before the customer is likely to run out and stops as soon as they reorder or subscribe.

Yes. We connect Recharge through its API so subscribers get skip, swap and delay options instead of a cancellation page, and one-time buyers get an invitation to subscribe at the right moment.

With consent, yes. Shade, undertone, hair type and skin concern answers set which products a customer hears about. We avoid storing sensitive health details that personalisation does not need.

Marketing pauses for that customer immediately and the case goes to your safety inbox. Flows resume only when the case is closed by a person.

Replenishment conversion per product, time to second order, subscription churn and saves, repeat rate by hero product, and unsubscribe and spam complaint rates.

Free 20-minute call

Want this for your beauty & cosmetic?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call