Fixed quote after a free call

A dietary supplement claims review workflow your regulatory lead can trust

Supplement marketing goes out through product pages, ads, emails, Amazon listings and influencer briefs, and every one is a place where a claim can drift. We build a workflow that compares each draft with your approved claims library, highlights wording that is new, stronger than approved or missing a required qualifier, and routes it to your regulatory lead with the evidence file attached. It flags; a person decides. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why supplement claims drift between review and publishing

Most brands keep approved claims in a spreadsheet and review copy by email. Under deadline, a new hire rewrites a product benefit more strongly, an agency adds an implied claim through an image caption, or an old Amazon bullet survives after the claim was withdrawn. Nobody can show who approved what, or when.

The rules are different in each market. In the US, the FTC expects competent and reliable scientific evidence for health benefit claims and judges the net impression of an ad, and structure/function claims on labels need FDA notification within 30 days and the standard disclaimer. In Great Britain only authorised claims on the GB register may be used, and the EU has its own register under Regulation (EC) 1924/2006.

What we build

What our dietary supplement claims review workflow includes

Approved claims library

Each claim with its ID, market, approved wording, conditions of use, required qualifiers, evidence file and review date, in Airtable, Notion or a simple database.

Copy pre-check

Drafts from Google Docs, Shopify, Klaviyo or an upload are compared with the library; matching, close-but-different and unmatched statements are highlighted.

Market rules

The check knows which claims are approved for the US, the UK or the EU, so a claim cleared for one market is not reused in another.

Routing and sign-off

Flagged drafts go to the regulatory lead with the matched claims and evidence links; approval or changes are recorded against the draft.

Live content sweep

A scheduled scan of product pages and marketplace listings for wording that no longer matches the library.

Audit trail

Who submitted, what was flagged, who approved and what went live, exportable for a retailer, marketplace or regulator request.

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

    Draft submitted

    A product page, ad, email or brief is submitted to the workflow.

  2. 02 Automated

    Pre-check runs

    Statements are compared with the approved library for that market.

  3. 03 Automated

    Flags prepared

    New, stronger or unqualified wording is highlighted with the closest approved claim.

  4. 04 Team review

    Marketing revises

    The author fixes simple matches to the approved wording.

  5. 05 Regulatory lead or founder decides

    Regulatory sign-off

    The regulatory lead approves, changes or rejects every flagged claim.

How it behaves

How the claims pre-check behaves

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

What the author sees

  • Highlighted statements that do not match the approved library
  • The closest approved wording to use instead
  • A clear status: approved, needs changes or with the regulatory lead

What the regulatory lead sees

  • Only flagged claims, with evidence links and market
  • A one-click record of each decision
  • A weekly sweep report of live content that drifted

What the automation does

  • Compares drafts with the library for the right market
  • Never approves anything on its own
  • Logs every submission, flag and decision

Edge cases and fallbacks

Claim is implied by an image or product name
Authors tag images and names for review, since text matching cannot see them.
Claim approved in the US but not the UK
Flagged when used in UK content.
Library entry past its review date
Treated as unapproved until the regulatory lead renews it.
AI matching service is down
Drafts queue for manual review; nothing is auto-approved.

Architecture

A supplement claims review workflow at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Draft copy Pages, ads, emails n8n workflow Intake and routing Claims library By market Pre-check Match and flag Marketing Revise wording Regulatory lead Sign-off Audit trail Approvals
  • Input
  • Logic and services
  • Data
  • AI step
  • People

How it flows

  1. 1 Draft copy for a page, ad, email or brief is submitted from the tool the team already uses.
  2. 2 Each statement is compared with the approved claims library for the target market and flagged where it differs.
  3. 3 Marketing fixes simple matches, then flagged claims go to the regulatory lead with evidence links.
  4. 4 The regulatory lead decides, and every decision is kept in the audit trail.

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.

Claims pre-check & content approval workflow project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current claims records, review process, channels, markets and who signs off.

  2. 02

    Library build

    About 1 week

    Structure the approved claims with IDs, conditions, qualifiers and evidence links, with your regulatory lead.

  3. 03

    Build

    1 to 2 weeks

    Intake from docs and platforms, pre-check, routing, live sweep and audit log.

  4. 04

    Shadow run

    About 1 week

    Recent copy is run through the check and compared with the regulatory lead's own review.

  5. 05

    Launch

    1 to 2 days

    Switch on for new drafts and train the marketing team.

  6. 06

    Support

    Ongoing

    Library updates, new markets and tuning of what gets flagged.

What it runs on

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

n8n Airtable, Notion or a database for the claims library Google Docs and Drive Shopify Admin API Amazon Selling Partner API (Listings Items) Claude or OpenAI for statement matching

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 library design

    Claims structure, markets, qualifiers and evidence links.

    $250 – $450

  • Build

    Intake, statement matching, routing, live sweep and audit log.

    $450 – $1,250

  • Integrations

    Docs, Shopify, Amazon listings and the library tool.

    $150 – $400

  • Testing and shadow run

    Recent copy compared with the regulatory lead's own review.

    $100 – $250

  • Launch and training

    Team training and run book.

    $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. We build the workflow; we do not provide regulatory advice or substantiation. Library tools and AI usage are billed to you directly.

Monthly running costs you pay directly

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

  • Library tool: Your Airtable or Notion plan, or a small database on your server.
  • AI model usage: Billed by the provider per use; usually a small monthly amount at typical content volumes.
  • 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: FTC substantiation and net impression

FTC staff guidance says health claims generally need competent and reliable scientific evidence, implied claims count as well as express ones, and a disclaimer does not cure a deceptive claim.

Source: www.ftc.gov

US: structure/function claims on labels

Under 21 CFR 101.93, a firm must notify FDA within 30 days of first marketing a supplement with a structure/function claim, and the label must carry the standard two-sentence disclaimer.

Source: www.fda.gov

UK: GB nutrition and health claims register

Only authorised claims in the GB register may be used in Great Britain; CAP advice adds that evidence does not rescue a health claim that is not on the register.

Source: asa.org.uk

EU: authorised health claims

Regulation (EC) 1924/2006 prohibits health claims that are not authorised and listed, and sets up a register of authorised claims and their conditions.

Source: eur-lex.europa.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

Claims pre-check & content approval workflow questions, answered.

They describe how a nutrient or ingredient affects the normal structure or function of the body, as opposed to disease claims. In the US, FDA must be notified within 30 days of first marketing one, and the label must carry the standard disclaimer. Your regulatory adviser decides whether a given statement qualifies.

No. It compares wording with claims your regulatory lead has already approved and flags differences. Whether a claim is allowed and properly substantiated is a decision for a qualified person.

For structure/function claims, the label must state, prominently and in boldface, that the statement has not been evaluated by the Food and Drug Administration and that the product is not intended to diagnose, treat, cure or prevent any disease, as set out in 21 CFR 101.93.

Yes. Briefs go through the same check before they are sent, and submitted posts or scripts can be run through it before you approve them. The FTC holds advertisers responsible for claims made on their behalf.

Very much. A claim approved for the US may not be on the GB register. The library stores approvals by market, and the check uses the right set for each piece of content.

An exportable trail of every draft, flag, decision and published version, with the approved claim IDs used.

Free 20-minute call

Want this for your health & supplement brand?

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