TWZNBooking Q4 2026
Practice01 / 04
01Platforms

Forge

Complete platforms, built from first principles.

End-to-end platforms, from concept to production.

  • Data model & API
  • Admin & customer apps
  • Payments, auth, deploys
01Thesis

One Team. One Codebase. A Whole Business on Top.

Off-the-shelf software gets a business to its first ceiling. Forge is what we do when a business needs to go through it. We design and build complete platforms — the data model, the transaction engine, the dashboards, the payments, the admin — as one coherent system owned end to end by one team. We build backwards from the operational decision the platform exists to serve, not forwards from a feature list. The result is software that fits the business exactly, and keeps fitting as it grows.

02Capability
01 / 03

Two-Sided by Design

Marketplaces fail in the middle — where two different kinds of users must share one transaction. Forge platforms are architected for both sides from day one. On EVÖQ, creators run a full business suite — listings, portfolios, earnings, payouts — while clients get discovery, booking, and messaging. Both sides meet in a unified booking and payment layer, so neither experience is a bolt-on.

Payments and payouts run on rails built by Keel

Fig.Two-sided marketplace
Shared layerAudience app
App
Creators
portfolio, services, earnings
Portfolio Services Earnings Bookings
Shared layer
Messaging + notifications
supabase realtime
push in ~120 ms
One schema
row-level security per user
App
Clients
discover, book, pay, review
Discovery Booking Reviews
Stripe Connect
pay in, payout out
5 events · play, or hover a node to trace its path
Distinct experiences sharing a unified booking, messaging, and notification layer.
Dual-sided marketplace architecture — EVÖQView case study
03Capability
02 / 03

The Transaction Is the Product

Every platform has one transaction that matters — the booking, the order, the entry. We treat its lifecycle as the core product. EVÖQ bookings move through request, review, payment, completion, and dispute as enforced states — with invalid states made impossible at the database level, not politely discouraged in the UI. Pricing modes are CHECK-constrained; expiry is automated; every edge has a defined path.

Fig.Booking lifecycle
Happy pathRejectDispute
01
Request
client submits
02
Accept
creator reviews
03
Payment
stripe processes
04
Complete
service delivered
05
Review
one per booking
Reject
creator declines
Dispute
any stage after acceptance
6 events · play, or hover a node to trace its path
Every transition is checked in the database — a booking can't skip a state or be reviewed twice.
Booking lifecycle engine — EVÖQView case study
04Capability
03 / 03

Trust You Can Verify

When a platform's credibility is the product, we engineer proof instead of promises. PM Competitions runs its prize draws inside PostgreSQL with pgcrypto: a 256-bit hardware-seeded value, SHA-256 hashed with the competition ID and timestamp, selecting the winner — with the full cryptographic proof stored and a public endpoint that lets anyone re-derive the result. No login. No trust required. Just maths.

Fig.Provably fair draw
In the databaseVerified
Trigger
Admin
one action in the dashboard
Seed
256-bit hardware entropy
SHA-256
seed + competition + time
Winner
hash → ticket index
Proof stored
seed, hash, index
Anyone, no login
Public verification
re-derive the hash, confirm the winner
6 events · play, or hover a node to trace its path
The entire draw process runs inside the database — the application layer never touches it.
Provably fair draw system — PM CompetitionsView case study
05Also in scope

Before the build, and after

  • 01Technical Consulting

    Advice from engineers who build.

    Architecture reviews, build-vs-buy calls, and technical strategy — grounded in systems we've shipped, not slideware. Consulting with us usually ends in a plan you could hand to any team. Sometimes that team is us.

  • 02Product Development

    From zero to launch.

    For new products, Forge covers the whole arc — scoping the MVP around the one transaction that matters, shipping it, then iterating against real usage. LOCKD went from first principles to live at lockd.zip on exactly this path.

06By the numbers
  • sides, 1 booking engine
  • payment states audited
  • of draws publicly verifiable
  • off-the-shelf cores
08Engagement
Options02

Ways to start

Every engagement starts with a conversation. Fixed-price entry points, then work scoped to the system it has to carry.
  • 01Start here

    Discovery Sprint

    £2,000fixed · two weeks

    Two weeks to a plan you could hand to any team. Architecture, build-vs-buy calls, the data model, and a scoped build plan — the consulting engagement, productised. Sometimes the team you hand it to is us.

  • 02The full engagement

    Platform Build

    Scoped per project

    One team, one codebase, concept to production. Every platform is priced against its own scope — the Discovery Sprint is where that number comes from.

Not sure where you fit? Tell us about the system and we'll point you at the right start.

Talk to us
09Other practices
Practices04
10Contact
London--:--:--

Building a platform for a specialist industry?

If the software your business needs doesn't exist off the shelf, that's exactly the work we take on. Tell us about the transaction that matters.

  • Platforms
  • Marketplaces
  • Product Development
  • Consulting

What happens next

  1. 01ReplyWe reply within 48 hours
  2. 02CallA 30-minute call to understand the problem
  3. 03ProposalA written proposal with scope and price