A Trustless
Marketplace on ICP
A fully on-chain freelancing platform that takes 2 to 5 percent where Upwork and Fiverr take 20 to 30.
"The Web2 freelancing platforms didn't get rich on innovation. They got rich on the take rate. Workbudd was built around the bet that on-chain settlement and DAO arbitration could ship a serious marketplace at a fraction of the fee."
The number that wins the conversation
2–5%
Workbudd platform fee
20–30%
Upwork and Fiverr
01 — The Context
The freelance economy is on a trajectory toward 12 trillion dollars by 2030, with 1.5 billion freelancers worldwide. Upwork, Fiverr, Freelancer.com, and Braintrust together extract 20 to 30 percent of every transaction. They control disputes, hold reputation hostage to their platform, and decide who gets access to global clients based on opaque rules.
The Web3 freelancing category had tried to disrupt this for years. Most attempts failed for the same reason most early Web3 products fail: the on-chain pieces work, the product experience around them feels like a beta. Workbudd came with a focused thesis. Deliver full Web2 feature parity, charge 2 to 5 percent, and treat reputation, escrow, and dispute resolution as first-class on-chain primitives. ICP's reverse gas — the canister pays for compute, not the user — is what made the UX viable.
Protocol
Internet Computer Protocol
Escrow
Canister-managed, milestone-gated
Reputation
On-chain, portable, freelancer-owned
Disputes
DAO-arbitrated, on-chain record
02 — The Bet
Marketplace parity from day one,
or it was just another beta with a token.
— 01
Full surface area from launch
Web3 marketplaces usually ship at half the surface area of their Web2 competitors and pitch the missing features as 'coming in v2.' We bet the opposite. Eleven modules, all working, all coherent, all feeling native to a freelancer's working day.
— 02
ICP as the enabling decision
ICP's reverse gas is not a marketing line. It is what makes a freelancing UX possible without asking the user to approve a transaction every time they message a client, update a milestone, or check their earnings. Every other design decision sits on top of that architectural choice.
03 — My Role
Product Director and Design Lead
Product Surface
Owned the information architecture for all eleven modules and the design system that holds the marketplace together.
Escrow & Milestone Flow
The on-chain trust artifact at the centre of every transaction — scope, gating logic, release conditions, and edge-case handling.
On-Chain Reputation
Designed the reputation surface so freelancers own their track record, not the platform.
DAO Dispute Resolution
The UX that treats disputes as a normal part of a healthy marketplace, not a failure state. Evidence submission, voting, on-chain ruling.
Freelancer Onboarding
Full journey from cold visit to first proposal sent — designed to get to value fast without losing the trust of a new user.
Client Onboarding
Full journey from cold visit to first contract escrowed. Different goals, different friction points, different flow.
Design & Frontend Team
Ran the design and frontend team through delivery and shaped the integration model between canister logic and the UI.
Caffeine AI Positioning
Defined how AI was embedded in the product — as a junior teammate in the freelancer's voice, not a chatbot bolted on the side.
04 — The Build
Eleven modules. One product surface.
Every module had to feel native to the same working environment. Nothing could look like a bolted-on Web3 feature.
Dashboard
Marketplace home base. Earnings, project completion rate, active contracts, skills distribution, and Caffeine AI performance insights — all genuinely useful, not decorative.
Workers
Client-facing freelancer discovery. Filtering by skill, tier, availability, and on-chain reputation. The talent browse that makes the supply side legible.
Browse Projects
Freelancer-facing job feed with category, skill, and budget filters. The demand-side surface that lets freelancers find work worth taking.
Bounties
Fixed-reward, short-cycle task layer. Fast turnaround, fixed prize, no milestone negotiation. A different commit pattern from a full contract.
My Projects
Contract management, milestone tracking, and delivery visibility for both parties. The operational core of every active engagement.
Messages
Canister-backed on-chain chat. Conversations are live artifacts that sit inside the dispute record if things go wrong. Designed to feel like a normal modern chat.
Hackathons
Collaborative project and competition layer for builders. Structured around teams, deliverables, and judging criteria.
Pay & Loans
Escrow state across active contracts plus an optional credit layer. Freelancers can access funds against secured milestones. Designed so "loans" never reads as predatory.
Analytics
Self-coaching layer. Earnings over time, category breakdown, client feedback themes. The point is to make a freelancer better, not just to log their history.
Workbudd Swap
In-product token swap for ICP, ETH, stablecoins, and platform tokens without leaving the marketplace. Intentionally boring — this is value movement, not entertainment.
Caffeine AI
A junior teammate for proposal drafting, project scoping, and client replies. Positioned as an assistant in your voice, not a chatbot.
The Escrow and Milestone Flow
Every contract is structured around milestones. The escrow is the trust artifact at the centre of the entire marketplace.
Contract Created
Client and freelancer agree on scope, milestones, and total value.
Funds Locked
Full contract value deposited into canister-managed smart escrow.
Milestone Delivered
Freelancer marks milestone complete, submits deliverable for review.
Approval or Dispute
Client approves or raises a dispute — both paths have a clear UX.
Automatic Release
Approval triggers on-chain release. No third-party custodian.
Evidence Submitted
Both parties upload proof of work, communication, and deliverables.
Voting Period Opens
DAO token holders review and vote. Transparent, time-bounded.
Ruling Issued
Outcome lands as an on-chain record. Funds released or returned.
DAO Dispute Resolution
Disputes treated as a normal part of a healthy marketplace.
Not a failure state. Not a support ticket. Disputes route to a DAO-arbitrated layer. Both parties get a clean way to submit evidence, a transparent voting period, and a resolution that lands as an on-chain record. The interface had to feel both serious and fast without becoming a blockchain explorer.
"Reputation lives on chain and is portable. A freelancer's track record is theirs, not the platform's."
"ICP's reverse gas is not a marketing line. It is what makes a freelancing UX possible without asking the user to approve a transaction every time they message a client or accept a milestone."
05 — Tech & Stack
06 — The Result
2–5%
Platform fee — vs 20–30% on Upwork
11
Marketplace modules shipped at parity
$1M
Seed raise structure confirmed
$5M
FDV target
1.5B
Global freelancers as addressable supply
3–5%
Market share target
Production engagement metrics — active users, GMV, completed contracts — to be confirmed by the Workbudd team before publishing. The platform is live at workbudd.com. The structural result is a marketplace that competes on take rate, product depth, and on-chain trust simultaneously — a combination the existing category hasn't delivered.
07 — What It Unlocked
Workbudd is the project that proved an on-chain marketplace can ship at full Web2 feature parity if the underlying protocol is chosen correctly.
The work also clarified our position on Web3 marketplaces in general. The opportunity is not to disrupt Upwork by adding a token. It is to rebuild the marketplace with on-chain primitives in the places where Web2 architecture forces a 25 percent take rate.
11-Module Reference Architecture
The eleven-module structure became our reference model for any Web3 marketplace build. Information architecture, shared chrome, per-module commit patterns.
DAO Dispute UX Pattern
The dispute resolution surface has been adapted for subsequent projects. The principle: treat conflict as a product feature, not a failure mode.
Caffeine AI Integration Model
Positioning AI as a junior teammate inside a working surface — in the user's voice, not a chatbot — is now a default pattern for any AI-augmented product we ship.
"Web3 marketplaces usually ship at half the surface area of their Web2 competitors and pitch the missing features as coming in v2. We bet the opposite."
"Reputation lives on chain and is portable. A freelancer's track record is theirs, not the platform's."
Start a Project
Want to build with intent?
Let's talk about your product — the real constraints, the real goals, and the cleanest path between them.
Start a Conversation