Case Study 02 — crowdSPRING

Built the standard, hired the team, rode off into the sunset.

A creative marketplace startup with no fraud-response protocol and no documented standards. I built both.

crowdSPRING in October 2010, captured by Internet Archive
Internet Archive capture, October 2010.
Year
2009 — 2012
Role
CSA → Director of Operations
Company
crowdSPRING
Location
Chicago, IL
A marketplace runs on trust. Trust runs on consistent rules.

01The situation

crowdSPRING was an early creative marketplace. Tens of thousands of designers and writers around the world bidding on briefs from small businesses, startups, and the occasional Fortune 500.

It had a platform. It had press coverage. It had momentum.

What it didn't have was the operational layer underneath any of it.

Without documented standards, every dispute became a one-off negotiation. Every one-off negotiation took twice as long as it should have.

When a buyer or a creative ran into a problem, they hit a wall — or they hit me, the entire customer service team of one.

crowdSPRING customer metrics: 110 entries per project, 100% satisfaction, 96% recommend, 74,953 designers, 97% questions answered within an hour
The 97% response time is what it looked like with no SOPs and one person going full bore.

02The complication

A creative marketplace is a magnet for fraud in both directions.

Designers stealing other designers' work and submitting it as their own. Buyers running projects with no intention of awarding, then quietly using submitted concepts without paying.

The platform was a haven for scammers.

The premium tier of projects was private by design. A paying buyer could request that no other creatives see the entries. The feature was meant to protect proprietary work. It also made the private projects invisible to everyone except the buyer, the creatives bidding, and me.

I was the only person positioned to spot the patterns across the entire marketplace.

03The work I built

Four pieces of operational infrastructure that the platform needed and didn't have when I got there.

The fraud-response protocol

Documented procedures for the three most common patterns: design theft (creative submits another creative's work), buyer fraud (buyer doesn't award, uses submitted concepts anyway), and identity fraud (single user operating multiple accounts to game the platform). Each pattern had a documented investigation path, an evidence standard, and a remedy.

The help center

The FAQ existed. It just didn't work. I rebuilt it. Two hundred-plus articles covering every dispute pattern I'd watched come through the marketplace. Buyers and creatives could self-serve answers to the questions that used to require a one-off email exchange with me. The queue for questions that didn't get answered self-service had documented response standards.

The editorial program

A weekly editorial program targeted at small-business buyers — the segment driving most of the platform's revenue. Design fundamentals, branding case studies, how-to content. Built it from zero.

The team

Hired and trained the customer-service operation that replaced me. Three full-time agents working under documented standards I'd written. The team picked up exactly where I'd handed off.

04What changed

Resolution time on disputes went from days to hours.

The platform ran more efficiently. Creatives were happier. Buyers were happier. It became a place people felt comfortable doing business on — because the rules were consistent, and because the people enforcing the rules had creative experience and could provide insight beyond the documentation.

The personal touch still mattered. The documentation handled the patterns. The phone calls handled the exceptions.

05Educating the buyer

Part of the editorial program was teaching small-business buyers to recognize what generic, fraud-adjacent design actually looks like.

Once you see the patterns, you can't unsee them.

The post below is the kind of content I built into the editorial program. "Buyer Beware: Generic Logo Design."

Buyer Beware: Generic Logo Design — published article on crowdspring
Educating buyers, one swooshy-person logo at a time.

The post catalogs the visual tropes scammers leaned on to fast-track fraudulent submissions. Swooshy people. Geometric shapes. Clip-art icons. The kind of work that looks close enough to a real logo to fool a buyer who doesn't know what to look for.

Overused, overdone logo concepts: 20 examples of generic stock-logo design tropes
You've absolutely seen these "logos."

Once you've seen the patterns the post catalogs, you'll start spotting them everywhere in your daily life. Storefronts. Business cards. Restaurant menus.

The visual residue of the same problem we were solving on the platform: buyers who didn't know what good looked like, and the people happy to take their money to give them not-good.

Pattern recognition is a real skill. Teaching it scales.

The closing

I started at crowdSPRING as a customer-service agent. I left as Director of Operations.

The arc isn't the promotion. The arc is that I built a stronger marketplace, authored the brand voice that supported it externally, educated buyers on how to spot generic design, and trained the team that took over when I left.

Build it so the work doesn't depend on you.

That's the philosophy.

Next case study
Mess Marketing — What it takes to build a 24/7 anything from scratch