Creator workspace
I built multi-tenant creator records that keep status, ownership, channels, campaign history, and operator context together.
Always currentProduction product / Creator operations
Influencer Army
A creator-operations platform for managing large-scale UGC programs, used by more than 200 active users.
Why I worked on it
One operating system for creator work that had outgrown spreadsheets.
I joined the build after seeing how quickly a large creator program fragments. Rosters sit in spreadsheets, briefs disappear into chats, contracts live elsewhere, and every report becomes a manual reconciliation job.
I helped turn those moving parts into one shared model for creators, campaigns, content, and decisions. My work covered the product workflows and the systems that keep those workflows scoped, current, and usable by more than 200 active users.
What shipped
The parts I had to make agree with each other.
Campaign execution
I connected briefs, announcements, deliverables, and approvals into a workflow the operations team could follow every day.
Always currentReport generation
I worked on the pipeline that turns campaign activity into ranked insights and readable monthly reports with traceable source data.
Always currentOperational history
I modeled the events and decisions behind each creator relationship so the next action starts with current context, not guesswork.
Decision ready
Decisions I made
Most of the work was deciding where state should live.
Keep one operational history
Reports and recommendations read from the same events as the product UI. I did not want a second analytics story that could quietly drift from what operators saw.
Scope every action to a tenant
Creator programs can share templates and tooling, but their people, contracts, content, and decisions must remain isolated at the data and workflow level.
Make AI return an action with evidence
A ranked recommendation is useful only when an operator can trace it back to the posts, contract state, or campaign activity that produced it.
Behind the interface
A multi-tenant workflow around creators, campaigns, and content.
I treated every creator interaction as part of a durable program record. The product surfaces share the same tenant-scoped model, so reports, automations, and operator actions all work from consistent state.
The harder engineering problem was keeping high-volume operations legible. Background integrations and AI analysis can accelerate the work, but each recommendation still needs source data and a clear human action.
- Creator intake
- Campaign operations
- Content tracking
- Reporting and action
What I actually did
Product and systems engineer
I worked across the product surface and the systems behind it, translating creator-program operations into reliable workflows, integrations, analytics, and production behavior.
Product engineeringMulti-tenant systemsAutomationAnalyticsAI reporting
- I translated the operations team's spreadsheet and chat-based process into tenant-scoped creator, campaign, content, and activity records.
- I built product workflows across creator intake, campaign execution, announcements, contracts, and the reporting path used by operators.
- I worked on the background integrations and AI-assisted reporting while keeping the source records and operator action visible.