Any
TBD
20
Mar 14, 2026
UGC Creator Portal – Airtable + Softr Build for Growth Agency
About Us
We run a UGC growth agency working with consumer tech brands. We manage multiple creators producing content daily for different clients. We're currently managing workflows manually and need a streamlined creator portal to scale our operations efficiently.
What We Need Built
The Problem We're Solving
Right now, our content submission, approval, and performance tracking processes are scattered across Discord,
Creators can see available jobs and submit content in one organized place
Our team can approve/deny submissions with clear feedback loops
Content automatically organizes into client-specific folders
We can track creator performance without manual data entry
What You'll Build
Creator-Facing Portal (Softr):
Secure login system (each creator has their own account)
Job board showing available campaigns with details (client, requirements, pay, deadline)
Content upload interface where creators submit videos with metadata (campaign name, concept, TikTok/IG links)
Submission history view (pending, approved, denied status)
Basic earnings/stats dashboard
Admin Portal (Softr):
Separate admin login for our team
Job posting interface (create new campaigns, assign to creators)
Content review queue (approve/deny with feedback notes)
Dashboard showing: pending submissions, approval rates, turnaround times by creator
Client overview (see all content by client)
Backend Database (Airtable):
Creators table (contact info, social handles, performance metrics, payment details)
Jobs/Campaigns table (client name, requirements, budget, deadline, status)
Content Submissions table (linked to creators and jobs, approval status, video URLs, view counts)
Clients table (contact info, active campaigns, content library)
Properly linked relational database structure
Automations (Zapier or Make.com):
When content is approved ? save video link to Google Drive in correct client folder
When content is uploaded ? notify assigned account manager
When content is denied ? notify creator with feedback
Weekly digest
Must-Have Features
Mobile-responsive (creators will access from phones)
Clean, professional UI (represents our brand to creators)
Role-based permissions (creators see only their stuff, admins see everything)
File organization system that mirrors our Google Drive structure
Notification system
Nice-to-Have Features
Bulk upload capability for multiple videos at once
Filtering/search functionality (by client, by creator, by date, by status)
Basic analytics dashboard (submission volume over time, top performers)
Integration with payment tracking (so we can log what we've paid creators)
What We're Looking For
Required Experience:
Proven experience building Airtable databases with relational structures
Experience building client portals or login systems using Softr
Comfortable with Zapier or Make.com for workflow automation
Strong understanding of user experience (this needs to be intuitive for non-technical users)
Portfolio showing similar projects you've completed
Bonus Points:
Experience working with content creators or agencies
Understanding of Google Drive API integration
Experience with performance tracking dashboards
Knowledge of TikTok/Instagram API for pulling view counts (optional future phase)
Deliverables
Fully configured Airtable base with all tables, fields, views, and relationships
Softr portal (creator-facing + admin-facing) connected to Airtable
Zapier/Make automations set up and tested
Documentation explaining how to use the system (for our team)
Simple video walkthrough showing how to add jobs, review content, onboard new creators
30 days of post-launch support for bugs or adjustments
Timeline
Initial setup call to review requirements: Week 1
Build and testing: Weeks 2-3
Training and handoff: Week 4
We're ready to start immediately with the right person.
To Apply
Please include:
Links to 2-3 similar projects you've built (Airtable + Softr portals, login systems, or creator/client management tools)
Brief description of your approach to building this (tools you'd use, how you'd structure the database)
Estimated timeline for delivery
Your availability (hours per week you can commit)
Any clarifying questions you have about the scope
Note: We're looking for someone who can think through workflows and suggest improvements, not just follow instructions. If you see a better way to structure something, we want to hear it.