A new product project in the CRM sends the brand owner a portal checklist for formula, specs, packaging drawings, artwork and the safety assessment. Missing items are chased automatically, files route to the right lead for sign-off, and the customer follows a live status page.
Typical results
≈4 hrs/wk
Project manager time no longer spent chasing files
Every 3 days
Reminder listing only the items still missing
100%
Launch files stored with an approval record
Figures reflect typical results for this kind of automation.
The challenge
Launching a new product for a brand owner depends on a dozen documents arriving from the customer: formula approval, ingredient specs, packaging drawings, label artwork and the safety assessment. They come by email in pieces, the project manager chases each one by hand, and a missing label proof can push the pilot batch back by weeks.
Before and after
Weeks to collect all launch documents
−40%Project manager hours per week on chase emails
−80%Weeks from project start to first production run
−14%The automation
Opening a new product project in the CRM sends the brand owner a portal checklist with an upload slot for each required item. Every 3 days, an email lists what is still missing. Received files are routed by type to the lab, purchasing or regulatory lead, who approves them or sends them back with a comment. The project moves from documents to pilot batch to first production run, and the customer sees each stage on a status page.
How it works
- 01
Project opened in the CRM
Sales opens a new product project in the CRM with the brand, product type and target launch date, which creates the checklist.
- 02
Portal checklist for the brand
The brand owner gets a portal link listing formula approval, ingredient specs, packaging drawings, label artwork and the safety assessment, each with an upload slot.
- 03
Reminders every 3 days
Every 3 days the brand owner gets an email listing only the items still missing, with a direct upload link.
- 04
Routed for sign-off
Each file goes to the lab, purchasing or regulatory lead, who approves it or sends it back with a comment the customer can see.
- 05
Stages and status page
Once every item is approved, the project moves to pilot batch and then first production run, and the customer's status page updates at each step.
Starts from
- New project in the CRM
- Brand owner uploads
Delivers
- Missing-item reminders
- Department sign-offs
- Customer status page
The impact
Document collection typically shrinks from about 5 weeks to 3, bringing the first production run roughly 2 weeks forward. The project manager stops writing chase emails, saving around 4 hours a week, and every approved file sits in one place, ready for the product safety file and the next reorder.
Questions about this automation
Can the checklist change by product type?
Yes. Each product type, such as a cream, a serum or a rinse-off product, has its own list of required items in the template, and sales picks the type when opening the project. Items that do not apply are left out, so the brand owner only sees what is needed for that launch.
What happens when a file is rejected?
The reviewer adds a short comment, the item reopens on the brand owner's checklist with that comment, and the next reminder email lists it again. The project cannot move to the pilot batch stage until every required item has an approval from its assigned lead.
What does the manufacturer need to start?
A CRM where new product projects are opened, a list of required documents per product type, and the reviewing role for each item. This is a multi-step build, usually rolled out in stages, starting with the checklist and reminders before the approval routing and the customer status page.