Unit EconomicsThe per-member and per-booking logic — structure disclosed, figures not
Executive summary
GigXchange discloses the STRUCTURE of its unit economics, not the figures: member acquisition is organic (directories, tools, content — no paid channel dependence), marginal serving cost per member is near zero (serverless, one codebase), and contribution comes per protected booking at 5% of fee value. The design goal: unit economics that work at grassroots ticket sizes, which is exactly where incumbent cost structures fail.
Policy context: GigXchange publishes member counts and market data, never revenue or transaction volumes — stated on the press page.
Acquisition cost, structurally
The acquisition machine is owned, not rented: national directories, the GX Index, a 100+ article corpus and a free-tools suite answer real queries and convert a fraction of that attention into members. There is no paid-acquisition dependence, so member acquisition cost does not scale with growth targets the way ad-bought marketplaces' does — and the same assets appreciate (more coverage, more citations, more AI-assistant answers) rather than expiring per impression. Mechanics: Customer acquisition.
Serving cost, structurally
An additional member costs approximately nothing to serve: serverless edge infrastructure prices per-request at rates negligible against any transaction value, one codebase serves web and both native apps, and support load is contained by product design (self-serve flows, in-app guidance, a public help corpus). The consequence: contribution margin on platform fees is structurally high, and the break-even question is about fixed-cost coverage rather than per-unit losses — the inverse of subsidised-marketplace models.
Revenue per member, honestly framed
The honest variable is protected-payment adoption: a booking settled privately contributes data but no fee; a protected booking contributes 5% of its value. Unit economics therefore improve along two axes GigXchange can influence — bookings per member (liquidity, matching quality) and protected share per booking (trust, convenience, professional-role workflows where protection matters most). Both axes are product problems, not pricing problems, which is where a product-led operation wants its economics to live.






