Claims-passport software that turns beauty and wellness formulas into country-specific label, claims, and launch approvals.

1. Seed financing into this category shows compliance automation for beauty and CPG has crossed the threshold from bespoke service to venture-backed software category.
2. The reported need to check formulas, ingredients, labels, claims, and market-entry rules across more than 70 countries makes manual workflows increasingly untenable for expanding brands.
3. Source-cited AI checks and traceable reasoning make automation newly credible in a workflow where legal defensibility matters as much as speed.
4. Reviews falling from days to minutes create a concrete ROI story tied directly to launch velocity and retailer deadlines, not vague AI productivity claims.
5. Reported adoption by major cosmetics, personal care, nutrition, and food groups suggests the beachhead can expand into a broader enterprise compliance network over time.

Catalyst. Certo's funding and reported traction show cross-border beauty and CPG compliance has moved from back-office pain to an urgent launch-timeline bottleneck.

The product ingests formulas, ingredient documentation, packaging copy, shelf-life assumptions, and target markets, then creates a claims passport for every SKU-market combination. It flags which claims are unsupported, which label elements must change, and which importer or market-entry documents are still missing, all with cited reasoning. When a brand reformulates a product or changes a supplier, the system reruns only the affected checks and updates downstream approval packets instead of restarting the whole review. External partners such as contract manufacturers, consultants, and distributors can review the same evidence trail rather than working from stale attachments.

What's different. Most compliance tools either act like broad regulatory databases or expensive consulting workflows. This wedge is the shared claims passport that persists across brand, manufacturer, distributor, and retailer handoffs, so every product change updates a reusable approval object instead of spawning another bespoke review project. Over time, the company can build defensibility from accepted claim patterns, rejection reasons, and supplier-document normalization at the SKU-market level.

Jobs to be done

flowchart LR
  Buyer[Regulatory Lead] --> Pain[Manual multi-country reviews]
  Pain --> Product[Claims Passport]
  Product --> Outcome[Faster compliant launches]

Executive takeaways

• The wedge is real because each cross-border launch forces brands to reconcile formula, claims, labels, notifications, and importer paperwork across multiple rulebooks; the work is repeated whenever formulas, suppliers, or packaging change.
• The best incumbents either monitor regulations or manage internal product data, but few center the shared SKU-market approval packet that external partners can trust without emailing revised spreadsheets and PDFs.
• European beauty is already a large, export-oriented market, and GCC plus ASEAN expansion adds enough local registration and labeling friction to make launch-timeline compression a board-level operations issue.
• Trust will hinge on auditable citations and human sign-off: buyers can accept automation, but not a black-box recommendation that creates claim or labeling liability.

Market definition

Workflow software for beauty and ingestible-wellness brands that converts one formula-plus-claims set into cited, market-specific approval packets for each SKU-market pair, then keeps those packets current as formulas, suppliers, or packaging copy change.

Customer and buyer

Primary users are regulatory affairs, quality, and launch-operations teams at beauty and ingestible-wellness brands and contract manufacturers. The economic buyer is typically the VP Regulatory, COO, or Head of Quality who owns launch timing, external partner coordination, and the cost of non-compliant rework.

Buying triggers

• A new country launch or distributor deadline turns compliance into a critical path task because labels, claims, notifications, and importer documents must all line up before product can ship. [14][18][19][23][24][25][35][37]
• Reformulations, supplier changes, and updated packaging copy trigger repeated ingredient and claims review work across every affected market. [13][15][33][39][54][59]
• Marketplace and channel onboarding can add another documentation layer beyond baseline regulation, raising the cost of inconsistent compliance packets. [34][56][58]

Willingness to pay

Public pricing is mostly hidden, which itself is informative: the main substitutes are enterprise PLM and regulatory-intelligence vendors sold via demos plus consultant-heavy market-access work. That points to an existing spend envelope funded from launch acceleration, avoided consultant hours, and lower risk of relabeling or listing suspension rather than from a small self-serve software budget. [39][40][42][43][45][46][47][59]

Category dynamics

Growth signal 7% global beauty sales growth in 2024 (current terms)

Validation signals

• Certo's seed financing is a direct market signal that beauty and CPG compliance automation is now venture-backable.
• Europe's beauty market reached €104bn in 2024 with strong export orientation, which supports a meaningful base of cross-border launch activity.
• Bain and Coresight both frame CPG operators as under pressure to digitize workflows and use AI or technology to handle operational complexity.
• A dense incumbent set already sells regulatory-intelligence and PLM tools into this budget, confirming existing buyer spend even if the exact wedge is open.
• Marketplace compliance guides show channel partners can require extra documentation and suspend listings, increasing the ROI of reusable approval packets.

Regulatory & technical constraints

• EU cosmetics require responsible-person oversight and prior CPNP notification before market placement.
• EU supplement marketing is constrained by authorized nutrition and health claims, with misleading claims prohibited.
• GCC entry for supplements and cosmetics layers regional standards with local SFDA and other national requirements, often including labeling and conformity documents.
• Singapore and ASEAN-aligned markets still impose notification and packaging-detail rules that make one global label or claim set insufficient.

Competition breaks into four classes: AI regulatory-intelligence platforms, broad PLM/compliance suites, niche cosmetics R&D/PLM tools, and consultant-led market-access providers. The proposed startup is strongest when it sits above source data and below consulting, owning the shared approval object that moves across brand, CMO, distributor, and retailer handoffs.

Why incumbents do not win by default

• Regulatory intelligence platforms. RegASK, Compliance & Risks, and Freyr prove that buyers will pay for global rule monitoring and expert summaries, but those products primarily help teams know what changed rather than maintain a reusable approval packet for each SKU-market pair.
• Broad PLM and specification suites. Trace One, Aptean, Centric, and Specright already manage product, supplier, and specification data, yet their center of gravity is enterprise PLM transformation, not a lightweight external-facing claims passport shared with distributors and importers.
• Niche cosmetics development software. Coptis sits closer to formulators and already automates alerts and dossier outputs, but it is still anchored in lab and formulation workflows rather than multi-party launch approvals across geographies.
• Consultants and local-market specialists. Artixio, Intertek, and similar providers can solve country entry one market at a time, but the delivery model is still service-heavy and therefore weaker at keeping every downstream approval packet synchronized after each product change.

Cross-border Claims Passport should launch as a human-in-the-loop compliance workflow product for European skincare and personal-care brands expanding into Saudi Arabia, the UAE, and Singapore, with ingestible wellness added only after the trust model is proven. The first customer is a €30 million to €200 million brand with 20-200 active SKUs, outsourced manufacturing, and 5-20 new or reformulated launches per quarter, where regulatory and quality teams repeatedly rebuild country-specific packets from spreadsheets, consultant emails, and stale PDFs. The acute buying trigger is an upcoming market launch, reformulation, or retailer deadline that makes compliance review the critical path to shipping inventory. The product should create a cited SKU-market approval packet, rerun only affected checks when formulas or claims change, and keep brand, CMO, distributor, and importer stakeholders on the same evidence trail. The go-to-market motion should start with founder-led paid pilots tied to one launch program, then expand into annual contracts priced by active SKU-market pairs and collaborator usage. The company wins only if it sits above incumbent PLM systems and below consultants, proving it can reduce review cycle time without asking customers to trust black-box automation. Research supports a meaningful wedge with an estimated $95.2M beachhead SAM and $6.0M year-3 SOM, but public pricing benchmarks remain opaque and the true ACV must be validated in paid pilots before scale hiring. The biggest disconfirming risk is that country-specific exceptions and messy source data keep the business too services-heavy to reach software margins.

Problem

• Cross-border beauty launches still require teams to rebuild formula, claims, label, notification, and importer evidence for each SKU-market pair whenever formulas, suppliers, or artwork change.
• Because brands, CMOs, distributors, and local-market agents work from spreadsheets, email threads, and PDFs, launch deadlines slip and rejected labels or claims can strand inventory and force relabeling.

Solution

• Generate a cited approval packet for each SKU-market pair that shows allowed claims, required label changes, missing market-entry documents, and explicit reviewer sign-off.
• Maintain that packet as a shared workflow object across brand teams and outside partners, rerunning only the impacted checks after reformulations, supplier changes, or packaging edits.

Why we win

• The product owns the partner-facing approval object that regulatory-intelligence tools monitor around and PLM systems store data beneath, which is a narrower and faster-to-value wedge than replacing either system.
• Source-cited outputs plus mandatory human sign-off fit the liability posture buyers already expect in claims and labeling workflows.
• A cosmetics-first launch into GCC and Singapore creates repeated, high-friction workflows where accepted-claim history, exception patterns, and normalized supplier data can compound into a real moat.

Milestones

flowchart LR
  Wedge[EU beauty launch wedge] --> MVP[Cited claims passport MVP]
  MVP --> Proof[Cycle-time and trust proof]
  Proof --> Expansion[More markets and product classes]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least half of qualified beachhead brands launch enough SKU-market pairs each year to support €50k+ recurring software spend.
• The first 3 pilots reduce median review cycle time by at least 50% while maintaining complete citation coverage and human sign-off.
• A standalone passport layer with spreadsheet and PDF ingestion is adoptable before full PLM integration.
• Consultant or local-market partners will work inside the shared packet instead of reverting to email attachments and side documents.
• Country-specific exceptions in Saudi Arabia, the UAE, and Singapore are limited enough that gross margin can trend toward 70% rather than staying services-like.

Open diligence questions

• How many launches, reformulations, and SKU-market pairs does the target customer actually process each quarter?
• Which Saudi, UAE, and Singapore workflow steps still require local human judgment even when source data is clean?
• What systems own formulas, specifications, and artwork today, and how much integration work will the first buyer require?
• What liability language, reviewer controls, and audit evidence does procurement or legal require before approving deployment?
• Why will the customer buy this layer instead of adding more consultant hours or extending an existing PLM or regulatory-intelligence tool?

Model sanity

• Revenue engine. Base-case revenue comes from growing active paid launch and production programs from 13 at Q4Y2 to 84 at Q4Y3 while upselling extra markets and collaborator modules.
• Must go right. The company must hold pilot-to-production conversion near the plan and use partner-assisted onboarding so headcount does not scale one-for-one with every new program.
• Model breaks if. If sales cycles stretch toward nine months and gross margin stalls below 69%, downside cash falls toward roughly $150K before the next round proof is established.
• Next-round proof. The next financing is justified by exiting Y2 with 6-8 production accounts, two live connectors, gross margin near 70%, and a repeatable consultant-assisted expansion motion.

Scenarios

Sensitivity

flowchart LR
  FounderOutbound --> PaidPilots
  PartnerReferrals --> PaidPilots
  PaidPilots --> ProductionPrograms
  ProductionPrograms --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: customersEop models paid programs, not purely distinct logos, because pilots and expansion programs are monetized before every account becomes a full annual production customer. · The base case still depends on add-on market coverage and collaborator upsells pushing blended ARPU above the initial core subscription range by Y3. · Y2 burn is intentionally heavy relative to revenue, so a slower partner channel or weaker pilot conversion would likely force an earlier raise even with the modeled buffer. · The model reaches equivalent Y3 production revenue but still lands slightly below the business-plan headline of about 90 paying customers, so execution must stay strong to close that gap.

• Regulatory liability. A wrong recommendation or stale rule could cause a non-compliant launch and destroy trust early. Mitigation: Require human sign-off, keep every output source-cited, and start with decision support plus audited market coverage before automating filings.
• Messy source data. Many brands and contract manufacturers store formulas, claims, and supplier documents in inconsistent spreadsheets and PDFs. Mitigation: Start with concierge onboarding for one SKU-market workflow and build lightweight ingestion around the systems customers already use.
• Incumbent squeeze. Broad compliance platforms or consulting firms could copy the category once the ROI story is obvious. Mitigation: Own the partner handoff workflow and build reusable approval objects plus integrations that are harder to replicate than a rules database alone.