Before You Build
Web AppShut Down

Design Inc.

Design Inc. was a marketplace that connected companies with freelance designers for high-quality design work.

View original story

Product snapshot

What it was

Design Inc. connected companies and individuals with freelance designers through several marketplace models.

Who it was for

companies seeking design workstartup teams needing product designfreelance designerscreative professionals

Problem / value

Reduced friction in finding designers and gave designers access to paid project opportunities.

Core workflow

  • post design projects
  • let designers propose to relevant client work
  • match companies with designers
  • create paid lead flow for freelance designers

Core dependency

Revenue capture, repeat project flow, growth channels, and protection against off-platform transactions.

Product form

web marketplacedesigner lead marketplacepay-to-propose workflow

Pricing model

The founder describes early transaction-fee models and a later pay-to-propose model where designers paid roughly $5 to $35 to send proposals.

What happened

Summary

Design Inc. shut down after creating marketplace value but failing to capture enough revenue and growth.

Outcome

The company closed the platform, returned remaining funds to investors, dissolved the team, and reimbursed designers.

Demand signal

The founder wrote that Design Inc. created real value and helped more than 900 companies complete over $4 million in design projects, but early models captured too little revenue and later growth work only slightly improved revenue.

Distribution issue

The marketplace had to attract both quality design demand and designer supply, while competing with referrals, freelance networks, and direct off-platform transactions after introductions.

Timeline

  • Launched in 2016
  • Built four major product versions
  • VentureBeat reported shutdown of the self-service platform in May 2017
  • Founder retrospective published in August 2017

Before you build

Why it matters

If participants can transact directly after an introduction, the platform needs ongoing workflow value or a monetization model both sides accept.

Primary check

Prove value capture before scaling a marketplace: if buyers and sellers can route around you, matching quality alone will not pay the bills.

Checklist

  • Track repeat projects by client and designer.
  • Measure take rate acceptance and off-platform leakage.
  • Judge growth experiments by revenue lift, not signups or project posts.
  • What ongoing value keeps both sides on platform after the first match?
  • Which side pays, how often, and at what price?
  • Can growth channels produce revenue before runway gets tight?

Relevant if

  • You are building a services marketplace, lead marketplace, or freelancer platform.
  • Your product introduces buyers and sellers who could continue off platform.

Less relevant if

  • Your product is a single-vendor SaaS with no two-sided transaction or lead-routing dynamic.

Pre-build tests

  • Run a paid lead or transaction model manually before building marketplace tooling.
  • Test whether buyers and sellers accept the fee after a successful match.

Transferable lessons

  • Validate who pays and why they keep paying before scaling supply.
  • Test disintermediation risk early.
  • Measure whether growth experiments improve revenue, not just activity.

If you build this today

Validate the paid wedge first: who pays, how often they repeat, why they cannot bypass the platform, and what ongoing workflow value keeps both sides active after the first match.