A 30-Day UGC Operating System for a Team of One
A week-by-week plan for running a UGC programme solo: what to collect in week one, what to clear and publish in week two, what to measure by week four. No agency, no new headcount.
Most UGC advice assumes a team: someone to collect, someone to clear rights, someone to publish, someone to measure. Most stores have one person doing all four between other jobs. This is the version built for that person: four weeks, roughly an hour a day, no new hires.
In this article
A UGC operating system is a repeatable weekly routine for collecting, clearing, publishing and measuring customer content, sized for one person working roughly an hour a day rather than a dedicated team. It's built around four one-week phases, and it's designed to be run again every month, not as a one-off project.
The four-week cycle
- 01
Week 1: Collect
Search your brand hashtag and tags for existing content, then turn on a post-purchase photo/video request email.
~1 hr/day
- 02
Week 2: Clear rights
Send a consent DM or email within 24 hours of finding a post. Speed matters more than the wording.
38% avg. yes-rate
- 03
Week 3: Publish
Tag cleared content to the specific product and place it on the PDP itself, not only a social feed.
+22% median CR lift
- 04
Week 4: Measure
Check which pieces actually got engagement or add-to-cart clicks, drop the rest, set next month’s targets.
Repeat monthly
Week 1: collect
Start with content that already exists. Search your brand name, hashtag and any product tags across Instagram and TikTok for the last 90 days; most stores have more usable content sitting unrequested than they expect. In parallel, turn on a single automated email, sent 5–7 days after delivery, asking for a photo or short video. One well-timed ask beats a complicated multi-touch sequence for a solo operator; the goal this week is volume, not perfection.
Week 2: clear rights
Every piece found in week one needs explicit consent before it goes anywhere near the store. Send the request within 24 hours of finding the post: yes-rate roughly halves after seven days and drops 80% after thirty, so speed matters more than a polished template. A short, specific DM ("we’d love to feature this on our product page, would you say yes?") with a one-tap consent link outperforms a longer, more formal ask. Keep a simple log, spreadsheet is fine at this stage, of who said yes, to what, and when.
Week 3: publish
This is the week most solo programmes quietly skip, cleared content sits in a folder because publishing it feels like a bigger job than it is. It doesn't need to be: tag each cleared piece to the specific product it shows, and place it directly on that product's page, not only a general social feed or a "customers say" landing page. Placement matters more than volume at this stage; five pieces live on your three best-selling PDPs will outperform thirty pieces sitting on a page nobody visits.
Week 4: measure and repeat
Check which published pieces are actually getting looked at or clicked, most platforms and widget tools show this per-piece. Drop anything with genuinely no engagement after a few weeks rather than leaving it up out of inertia, and note which product pages still have no UGC at all, that's next month's week-one search list. The system compounds: month two starts with a shorter collection list because month one's request email is still running in the background.
When a week gets skipped
Some months, one phase won't happen: a launch eats week three, a holiday eats week one. Don't try to cram the missed phase into the next week on top of its own workload, that's how the whole system quietly stops. Instead, carry the missed phase's backlog into the following month's version of that same phase (a skipped week-one search just means a bigger week-one list next time) and keep the cycle on its normal rhythm. A system that survives being interrupted is more valuable long-term than one that only works when nothing else is competing for the same hour.
The 15-minute version, for the days the hour isn't there
Collection week: reply to one customer comment or tag with a request to feature their content. Rights week: send one consent DM to the single best piece found that day, not a batch. Publishing week: get one cleared piece live on one product page, rather than waiting for a batch to publish together. Measurement week: check one metric (clicks on the newest gallery addition) rather than a full report. None of these fifteen-minute actions replace the full hour, but they keep the cycle moving on the weeks it genuinely can't get the full time, which matters more than any single week being perfect.
How to get rights to repost customer UGC has the exact templates for week two; how to legally collect UGC from Instagram and TikTok covers the sourcing side of week one in more depth.
FAQ
How much time does this actually take per week?
Roughly an hour a day, so about five to seven hours across the week, once the post-purchase request email is set up and running. Week one (initial search) is the heaviest; the cycle gets lighter each month after that.
What if I only have time for one phase, which matters most?
Publishing (week three). Plenty of stores collect and even clear rights on content that never actually reaches a product page. If time is short, prioritise getting already-cleared content live over collecting more.
Do I need software to run this, or can I do it manually?
It can be run manually with email and a spreadsheet at small volume. Past roughly 50 pieces of UGC a month, manual tracking of rights and placement starts to break down, and a dedicated collection/rights/publishing tool earns its cost.
Sources
- 1Idukki: How to get rights to repost customer UGC
- 2Idukki: How to legally collect UGC from Instagram and TikTok
- 3Idukki cohort, 2024–26 · Median PDP conversion-rate uplift from an on-page UGC gallery
- 4Idukki: build your 90-day rollout plan
More from Rohin Aggarwal
- Strategy
PDP before and after UGC: what actually changes on the page
Add verified customer photos, video and reviews to the middle scroll of a brand-only PDP and conversion lifts. Here is what moves, scroll by scroll.
- Strategy
A kitchen table in Egham, why I built Idukki
Day job: SAP architect on UK government software. Night job: founder of a UGC platform. The Venn diagram of those two communities is roughly one person.
- Strategy
The Death of Impression-Based Pricing: A Finance Director's Case
Impression-based pricing made sense while impressions tracked funnel impact. They stopped. A finance director's argument for outcome-based commercial models in the agentic era.