# Client onboarding in 48 hours: feeds, rights-first, one widget
Agencies win 2027 UGC retainers by shipping a shoppable widget in two days—not a strategy deck—with feeds connected and permissions logged.
By Rohin Aggarwal · 2026-03-10
The prospect signed Friday. Monday standup expects a live homepage module. Your strategist is still in discovery. The fastest credible path is not a 40-slide roadmap—it is 48-hour onboarding: connect feeds, stand up a rights log, publish one shoppable widget, and schedule the week-two review. We make Idukki; this is the playbook our agency partners use to reduce time-to-first-proof without skipping compliance. It pairs with how we think about 2027 UGC retainer scope and reporting.
**Quick answer**
- Shopify staff access (or theme collaborator)
- Instagram / TikTok business connections
- List of 10 hero SKUs and their variant rules
## Hour 0–4: access and scope lock
Collect before any pixel goes live:
- Shopify staff access (or theme collaborator)
- Instagram / TikTok business connections
- List of **10 hero SKUs** and their variant rules
- Named approver for rights (client-side, not agency intern)
Out of scope for hour one: paid ads, email redesign, replatforming reviews. Those are week three-plus.
Send the client our one-pager mindset: [no UGC strategy without a rights log](https://idukki.io/blog/no-ugc-strategy-without-rights-log). If they push back on paperwork, shrink widget surface (single collection) until the log exists.
## Hour 4–16: feeds first, not creative first
Install and connect in this order:
1. **Social sources** — Hashtags, handles, tagged content; cap initial ingest to 90 days to avoid moderation debt.
2. **Review-with-photo feeds** if licensed—pull into moderation, not auto-publish.
3. **Manual uploads** for creator contracts already signed.
Document credentials in the agency vault; mirror connection steps from [Idukki docs](https://idukki.io/docs). For a budget-conscious stack list including Idukki, see [free Shopify stack: eleven installs](https://idukki.io/blog/free-shopify-stack-2027-eleven-installs-idukki).
Do not enable auto-publish. Every agency horror story starts with “we thought the app would filter NSFW.”
## Hour 16–28: rights pass on a shortlist
Goal: **12–20 approved posts** mapped to hero SKUs, not 200 “maybe” tiles.
| Field | Why it matters |
| --- | --- |
| Platform post ID | Audit trail |
| Creator / customer handle | Re-contact |
| Permission type (DM, form, T&C) | Channel eligibility |
| SKU / collection | Shoppable target |
| Expiry or campaign tag | Auto sunset |
Use client-provided DM templates; store screenshots in the shared drive the legal approver can search. [Help center articles on permissions](https://idukki.io/help) align with FTC/UK expectations—link them in the client Notion.
## Hour 28–40: one widget, one placement
Pick a single high-traffic surface:
- Homepage “Community” row below hero, or
- Collection page for the client’s highest-margin line
Configure lazy loading and fixed aspect ratio to protect CWV—same principles as [lightweight UGC under 79KB targets](https://idukki.io/blog/lightweight-ugc-79kb-no-cls-peak-traffic). Mobile preview is mandatory; most B2C traffic is still phone-first.
Label the module honestly (“From our community”) and avoid star-language unless the review app owns it—see [multi-source reviews and Google markup](https://idukki.io/blog/multi-source-reviews-without-breaking-google-markup).
## Hour 40–48: QA, analytics baseline, handoff deck
**QA checklist**
- Each visible tile opens correct PDP variant
- Out-of-stock SKUs hide or fallback per client rule
- No unapproved faces in jurisdictions with stricter rules
- Theme dark mode / RTL spot check if applicable
**Analytics baseline**
- Document sessions, baseline CR for affected templates (Shopify analytics or client BI)
- Gallery click events firing (verify in tag assistant)
**Handoff deck (5 slides max)**
1. What shipped
2. Rights backlog count and owner
3. Week-two plan (PDP expansion or email block)
4. Risks (missing TikTok connection, etc.)
5. Reporting cadence tied to retainer KPIs
Case study framing for QBRs—without inventing numbers—lives on [Idukki resources](https://idukki.io/resources).
## What not to promise in 48 hours
- Full PDP coverage on 2,000 SKUs
- Creator net-new production (that is a separate SOW)
- Incrementality proof (needs holdouts; see [UGC holdout tests](https://idukki.io/blog/holdout-tests-ugc-incrementality-without-lying))
- Bazaarvoice migration (30-day plan is different: [Bazaarvoice to Idukki Q1](https://idukki.io/blog/bazaarvoice-idukki-30-day-plan-q1-2027))
## Week two expansion menu
Present three priced options:
1. **PDP pilot** — Top 20 SKUs, mirrored rights fields
2. **Email block** — Static export of approved tiles for Klaviyo
3. **Capture sprint** — Easter or spring event; tie to [21-day proof sprint](https://idukki.io/blog/easter-2027-proof-sprint-21-day-capture-plan)
## Internal agency roles
| Role | 48h responsibility |
| --- | --- |
| Strategist | Scope lock, client comms |
| Implementer | Shopify + Idukki config |
| Moderator | Rights pass |
| Analytics | Baseline + event QA |
Rotate moderators weekly so one person does not become a bottleneck.
## Commercial packaging (what to put in the SOW)
Fixed fee for 48-hour launch should include:
- Up to two social sources and one manual upload bucket
- Twelve to twenty approved posts at go-live
- One widget, one template customization pass
- Baseline analytics screenshot and event verification
Exclude: PDP-wide rollout, paid whitelisting setup, review app migrations, and creator sourcing. Those are change orders with their own timelines—especially [Q1 replatform parallel runs](https://idukki.io/blog/q1-replatforming-reviews-ugc-parallel-run-30-day) when BV or Okendo is in flux.
## Client communication cadence
| Touchpoint | Audience | Content |
| --- | --- | --- |
| Hour 4 | Marketing lead | Scope lock + access gaps |
| Hour 24 | Legal/compliance | Rights process + sample DM |
| Hour 40 | Ecommerce | Preview link + SKU map |
| Hour 48 | Exec sponsor | 5-slide handoff |
Link [social proof roadmap one-pager](https://idukki.io/blog/2027-social-proof-roadmap-one-page-board) as the week-two planning artifact so the sprint connects to board-level narrative.
## Failure recovery
If hour 36 hits zero approvals, switch to **creator uploads** already under contract or pause go-live 24 hours. Shipping an empty widget damages trust more than missing Monday—reference [live shopping with UGC you already have](https://idukki.io/blog/live-shopping-shopify-2027-ugc-you-already-have) only if the client has usable archive footage with rights on file.
## Bottom line
Agencies that onboard in 48 hours win trust because **something shoppable is live** while competitors still workshop messaging. Feeds first, rights before publish, one widget with honest labels—that is the retainer foundation everything else stacks on.
### FAQs
**Q: Who is this guide for?**
A: Heads of ecommerce, CMOs and campaign leads preparing holiday and 2027 peak-season proof.
**Q: Does this require a new UGC tool?**
A: No. The checklist works with any collection workflow; Idukki is one option for tagged, shoppable galleries.
**Q: Where should I start?**
A: Read the quick answer, then work the first section of Client onboarding in 48 hours: feeds, rights-first, one widget on your top revenue SKUs.
### References
- [Idukki help centre](/help)
- [Engagement and analytics docs](/docs/engagement-analytics)
- [UGC resources and playbooks](/resources)
- [Related: agencies-sell-2027-ugc-retainers-scope-reporting](/blog/agencies-sell-2027-ugc-retainers-scope-reporting)
- [Related: free-shopify-stack-2027-eleven-installs-idukki](/blog/free-shopify-stack-2027-eleven-installs-idukki)
- [Related: no-ugc-strategy-without-rights-log](/blog/no-ugc-strategy-without-rights-log)
---
Canonical: https://idukki.io/blog/client-onboarding-48-hours-feeds-rights-first-widget-agency
Tags: agency, onboarding, shopify, ugc