← Shannon Lunsford
MARKETPLACE · 0→1 · WE ARE ROSIE

Launching a community marketplace portal — web + mobile

Replacing repetitive forms, insecure access, and manual matchmaking with one personalized portal for talent and clients — designed mobile-first and built to scale to 20,000 members.

Role
Product owner — concept to launch
Company
We Are Rosie
Platform
Web + mobile (mobile-first)
Users
Rosie · Admin
5,000+
members in the first year
SSO
one centralized profile — no more re-keying
Web+app
parity across desktop and mobile
20K
members the architecture was built to support
// context

An on-demand community of marketing experts

We Are Rosie is a community of independent marketing experts — "Rosies" — available on demand to augment, backfill, and accelerate the in-house teams of Fortune 500 brands and agencies. The product question: how do thousands of independent experts and the companies who need them find each other, apply, and get matched without the whole thing running on manual admin work?

[ SCREENSHOT ] Hero / landing — the portal entry point where a visitor chooses Rosie or Company. Replace with a Figma export (PNG @2x).
Portal entry & role selection
// the problem

Repetitive data entry, insecure access, and manual matchmaking

// goals

What the product had to do

For Rosies

A personalized home

SSO and a centralized profile, a space to manage their data, browse and apply to open opportunities, and track application status.

For the community

Members only

Make the community hub an exclusive, authenticated experience — accessible only to people who'd actually joined.

For the business

Less manual work

Replace re-keyed data, manual posting, and offline scheduling with self-serve flows and system-driven coordination.

// process

From user flows to a tested, responsive product

I ran the product from discovery through launch: mapping user flows for each role, building wireframes for mobile and desktop, then testing a low-fidelity prototype with real users across several sessions to catch gaps before visual design. From there: UI guidelines, a high-fidelity responsive prototype, and a scoped MVP spanning the Rosie portal, a back-office admin, and a companion mobile app with full parity — all built mobile-first.

Under the hood, the portal had to sit on top of the existing operational stack: I scoped integrations for single sign-on, the applicant-tracking system, CRM, calendar, time tracking, support, and notifications, plus migration of existing profile and opportunity data from the legacy systems.

[ SCREENSHOT ] Registration / onboarding flow — social login + profile setup (bio, skills, roles, rates).
[ SCREENSHOT ] Rosie profile — skills, industry expertise, portfolio uploads, availability toggle.
Onboarding & profile (replace with Figma exports)
// the solution

One system, three experiences

Rosie portal

Profile, apply, track

Social login; a rich profile (bio, roles, skills, industry, education, hourly rates, portfolio uploads); easy-apply with share & refer-a-friend; an availability calendar; and a dashboard with application tracking, profile-completion, and time tracking.

Admin back office

Manage & match

Tools to manage member accounts and coordinate interview scheduling across calendars — replacing the email-and-phone runaround.

Mobile app

Full parity, on the go

A dedicated mobile app mirroring the web portal — same credentials, same core flows — for Rosies who live on their phones.

[ SCREENSHOT ] Opportunities list + detailed view with easy-apply.
[ SCREENSHOT ] Rosie dashboard — applications, profile completion, time tracking.
Opportunities & dashboard (replace with Figma exports)
[ SCREENSHOT — wide ] Mobile app screens, or the company-side applicant tracker. Good spot for a 2–3 frame Figma export.
Mobile & company experience
// results

A community marketplace that scaled

← All case studies Get in touch →