MiddleLeap
Menu

Portfolio · Platform venture

Setbay.
Your space, set.

Setbay™ is a UAE marketplace proposition that turns underused premium parking—starting with idle weekday hotel bays—into reserved monthly spaces for companies and their employees. Formerly the working codename Parqo.

Private evidence snapshot · repository main at b32a45b · reviewed 4 October 2026

Executive view

A marketplace experiment designed to earn the next investment.

Setbay is not presented as regulated-platform proof. It tests a transferable platform question: can fragmented demand and idle supply become reliable contracted capacity in one dense district?

01 / Question

Can density compound?

The venture tests whether qualified employer demand and dependable hotel supply can meet repeatedly in one operating district.

02 / Evidence

Acquisition platform live

Employer, hotel and employee journeys across five district pages feed one operator console with enrichment, follow-up and retention built in.

03 / Boundary

Not yet a marketplace

No facility is contracted and no employer is paying. Subscriptions, allocation, access and payments remain specified, not built.

04 / Practice value

Evidence before scale

The experiment sharpens marketplace strategy by tying each build decision to a commercial learning target.

05 / Next gate

A first contracted district

Sign supply, convert one employer and prove access reliability before funding broader platform surface area.

Parking scarcity and parking waste exist on the same street.

Employees in dense districts struggle to find dependable parking while nearby hotel bays sit empty on weekdays. Setbay tests whether these two fragmented markets can become a reliable, contracted capacity network—one district at a time.

Problem

Two invisible markets

Employers lack reserved capacity; hotels lack a simple route to monetise predictable idle inventory without giving up guest priority.

Wedge

Qualify every side

District pages, calculators and separate employer, hotel and employee intakes create structured demand and supply evidence.

Thesis

Density before scale

One operating district must prove supply, access reliability and employer willingness before wider platform investment.

The live platform is an evidence machine—not yet the full marketplace.

The production surface acquires, enriches and qualifies all three sides of the market. Next.js route handlers validate submissions into Supabase; a database-backed queue drives notifications and opt-in follow-up; a private staff console runs the operator loop. The employer dashboard, employee app, subscriptions, access provisioning and payments remain intentionally outside this build.

DemandEmployers + employeesTeam needs · district · individual interest
SupplyHotelsCapacity · permits · access method
Acquisitionsetbay.aeFive district pages · calculators · three intakes
EnrichmentCompany lookupPlaces · public business registries
IntakeLead API + queueValidate · enrich · notify · follow up
Operator loopStaff consoleNext actions · activity log · Cal.com · WhatsApp
System of recordSupabase + RLSIntake tables · 12-month anonymisation
MeasurementPostHog EU + SentryFunnel events · error tracking

Make the next investment conditional on real market evidence.

Setbay applies the Loom's evidence, specification and human-authority principles to venture building. This is disciplined use of the method's ideas—not a claim of full regulated-harness adoption.

01

Research

Market evidence, competition, risks and district economics

02

Specify

PRD, v0.4 design, data model, contracts and decision gates

03

Ship wedge

A production acquisition site with demand and supply intake

04

Brand + harden

Codename retired, Setbay brand system, CI and an operator console

05

Validate

Lead quality and signed supply before marketplace build-out

Technical build recordAI delivery · Technology · Quality posture

AI shortens the learning loop. It does not own the business decision.

AI is used to build Setbay, not inside the product. The repository evidences Claude Code as the implementation partner under founder review, and makes a disciplined claim: generated code is not the moat. Distribution, contracts, reliable access operations and proprietary network data are.

Build agent

Claude Code

Delivery since the July snapshot is Claude Code-assisted, with co-authored commits merged through pull requests.

Delivery model

AI-native, human-authorised

AI can scaffold code, tests, research and documentation; founders retain commercial and production authority.

Prohibited actions

Deterministic operations

AI cannot activate capacity, alter access, set payouts, issue final finance documents or change privacy policy.

Brand context

A repository brand skill

Naming, claims and tone rules live beside the code, so generated copy says “reserved” until supply is signed.

Runtime AI

None, deliberately

The enquiry concierge is a form and is not presented as an assistant. Nothing customer-facing depends on a model.

Operating intelligence

Staff console

Leads, next actions, an activity log and an outreach link builder live in a private, authenticated console.

EvidenceClaude Code-assisted buildCI gatesHuman reviewCommercial gate

A deliberately small stack for a commercial validation problem.

TypeScriptNext.js 16 + React 19Vercel + CronSupabase Postgres + RLSSupabase AuthResendPostHog EUSentry EUCal.comWhatsAppGoogle PlacesVitest + PlaywrightpgTAPGitHub Actions

The hardening gap from the first snapshot is closed for the live surface.

CI

Gated merges

Lint, types, unit tests, build and a browser smoke test run on every change, with a separate database job.

Database

RLS under test

Migrations are replayed and pgTAP suites exercise intake, operator and row-level security policies.

Input

Validated intake

Separate employer, hotel and employee endpoints validate before storage, enrichment and notification.

Privacy

Retention by default

Idle leads are anonymised after twelve months; follow-up is opt-in with one-click unsubscribe.

Edge

Abuse controls

Lead endpoints are rate-limited, bot-screened and idempotent; the booking webhook is signature-verified.

Next hardening

Marketplace surfaces

Subscriptions, capacity allocation and access provisioning need their own tests before an operational pilot.

The next milestone is commercial proof, not more surface area.

P0

Thesis + evidence

Complete

P1

Approved v0.4 design

Complete

P2

Acquisition wedge

Complete

P3

Setbay platform

Live

P4

District pilot

Current gate

P5

Platform scale

Later

3Intake pathways: employer, hotel and employee
5Dubai district pages collecting demand
35Unit test files, plus three pgTAP suites
17Supabase migrations in the reviewed repository
Known boundary

Setbay is not yet an operating parking marketplace. The live production asset acquires and qualifies demand and supply; no facility is contracted and no employer is paying. The approved v0.4 design describes the next product: employer dashboard, employee app, subscriptions, capacity allocation, access handoff and billing remain future work gated by district-level evidence.

Claims are grounded in a reviewed private build record.

The repository is not publicly accessible. This register names the material reviewed; detailed source access can be considered during appropriate diligence.

R1Repository overview and shipped scopeReviewed
R2Setbay brand systemReviewed
R3Approved v0.4 specificationReviewed
R4Conversion planReviewed
R5AI-native delivery controlsReviewed
R6Continuous-integration workflowReviewed
R7Operations runbookReviewed
R8Risk registerReviewed

What this venture proves

Platform strategy gets sharper when every build step has a commercial learning target.

Bring the marketplace, district-density and AI-native delivery learning into your platform mandate.