What WERKR, Jobr and Tinrate taught us about building the supply side first, even when nobody wants to demo it.
We have now built three marketplaces: WERKR for on-demand staffing, Jobr for job matchmaking, and Tinrate for paid expert consultations. Different industries, different founders, same shape. Every one of them is two products wearing one brand. And in every one, the product that decides success is the one nobody wants to see in a demo.
When a founder pitches a marketplace, they pitch the demand side. The swipe-style job hunt in Jobr. The two-click booking of an expert on Tinrate. The company that gets a trained cleaning crew tomorrow through WERKR. That side is visual, emotional, easy to explain to investors.
The supply side is none of those things. It is worker onboarding, planning screens, payout logic, invoicing. On WERKR, the real product is the platform that matches hundreds of flexible workers to incoming requests without the back office growing at the same pace. On Tinrate, it is escrow that releases payment only after the call happens, and VAT-compliant invoicing so an expert in Belgium can actually accept money without a headache. On Jobr, it is the employer side that gets vacancies into the system in the first place.
None of this makes a nice screenshot. All of it decides whether the marketplace lives.
Here is the asymmetry we keep running into: a frustrated buyer complains, a frustrated supplier just leaves. A candidate who cannot find a job blames the market. A worker whose payout is late, or an expert whose invoice is wrong, blames you, once, quietly, and never comes back. You do not get a support ticket. You get a thinner marketplace three months later and no idea why.
That is why the unglamorous features earn their place. WERKR runs with 500+ active workers today, serving clients from local businesses to BMW, Volvo and Cardoen dealerships. That number holds because the worker app and the planning behind it treat workers as the primary user, not as inventory. Tinrate holds 2,000+ vetted experts for the same reason: an expert who gets paid correctly and on time comes back, and tells other experts.
We did not start out believing this. Early on we sequenced work the way the pitch deck was sequenced: demand-side polish first, supply-side tooling when we got to it. The result was predictable. Beautiful booking flows pointed at supply that was still managed half by hand. Every manual step on the supply side became our bottleneck, because the demand side was software and the supply side was somebody’s Tuesday afternoon.
The fix was a rule we now apply on every marketplace project: the supply side gets built to the same standard as the demand side, and usually first. If the founder pushes back, we show them the math. Demand you can buy with marketing spend. Supply you can only keep by being good to it.
When someone brings us a marketplace idea, we ask one question before anything else: what does the supplier’s worst week look like, and what does your product do about it? A late payout, a no-show client, a booking that changes last minute. If the answer is “support will handle it”, the product is not designed yet, only the demo is.
Two products, one brand. Budget for both, and build the boring one like it is the business. Because it is.
We build websites, software and companies. Tell us which one you need.