Can density compound?
The venture tests whether qualified employer demand and dependable hotel supply can meet repeatedly in one operating district.
Portfolio · Platform venture
Parqo.
Space, put to work.
A B2B marketplace proposition connecting idle hotel parking with employers that need reliable employee parking in dense UAE business districts.
Private evidence snapshot · repository main at 79cd4aa · reviewed 11 July 2026
Executive view
A marketplace experiment designed to earn the next investment.
Parqo 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?
Acquisition wedge live
Separate demand and supply journeys now produce structured leads and commercial learning.
Not yet a marketplace
Contracts, access operations, payments and repeatable district economics remain outside the current proof.
Evidence before scale
The experiment sharpens marketplace strategy by tying each build decision to a commercial learning target.
District-level proof
Validate supply, employer willingness and operational reliability before funding broader platform surface area.
01
Why it exists
Parking scarcity and parking waste exist on the same street.
Employees struggle to find dependable parking while nearby hotel bays sit underused. Parqo tests whether these two fragmented markets can become a reliable, contracted capacity network—one district at a time.
Two invisible markets
Employers lack guaranteed capacity; hotels lack a simple route to monetise predictable idle inventory.
Qualify both sides
District pages, calculators and separate intake flows create structured demand and supply evidence.
Density before scale
One operating district must prove supply, access reliability and employer willingness before wider platform investment.
02
Current architecture
The live wedge is an evidence machine—not yet the full marketplace.
The production surface acquires and qualifies both sides of the market. Next.js route handlers validate submissions into separate Supabase tables; notifications, analytics and founder follow-up close the loop. The employer dashboard, hotel console, payments and access integrations remain intentionally outside this build.
DemandEmployersTeam size · district · readiness
SupplyHotelsCapacity · availability · access
AcquisitionNext.js websiteDistrict pages · calculators · forms
MeasurementPostHog EUMasked funnel events
IntakeLead API routesValidate · classify · notify
Operator loopResend + follow-upWhatsApp · Cal.com · founder review
System of recordSupabaseDemand + supply intake tables
IntelligenceNotion dashboard12 lead views · operator-run
03
Loom-informed delivery
Make the next investment conditional on real market evidence.
Parqo 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.
Research
Market evidence, competition, risks and district economics
Specify
PRD, v0.4 design, data model, contracts and decision gates
Handoff
A bounded Codex prompt and an ordered implementation backlog
Ship wedge
A production acquisition site with demand and supply intake
Validate
Conversion and lead-quality evidence before marketplace build-out
Technical build recordAI delivery · Technology · Quality posture+
04
AI build system
AI shortens the learning loop. It does not own the business decision.
The repo evidences Codex as an implementation partner and documents a broader AI-native operating model. It also makes a disciplined claim: generated code is not the moat. Distribution, contracts, reliable access operations and proprietary network data are.
Codex
The repository contains a first Codex build prompt, a Codex handoff package name and Codex-authored delivery history.
AI-native, human-authorised
AI can scaffold code, tests, research and documentation; founders and engineers retain commercial and production authority.
Deterministic operations
AI cannot activate capacity, alter access, set payouts, issue final finance documents or change privacy policy.
Still deliberately light
No repository MCP config, hooks, custom skills or CI workflow were found in the reviewed snapshot.
Claude guidance only
A Claude brand-voice guide is present, but it is context documentation rather than evidence of an autonomous build loop.
Supabase → Notion
A founder-run script converts lead data into a Notion page with 12 text-based demand and supply views.
Evidence→Codex-assisted build→Human review→Production wedge→Commercial gate
05
Technology
A deliberately small stack for a commercial validation problem.
TypeScriptNext.js 16 + React 19VercelSupabase PostgresNext.js route handlersResendPostHog EUCal.comWhatsAppVercel WAFNotion APINode.js
06
Quality posture
The live wedge has useful controls—and a visible hardening gap.
Validated intake
Separate hotel and employer endpoints check required fields before storage and notification.
Server-side storage
Supabase secret access stays on the server; anonymous direct reads of intake tables are not granted.
Masked analytics
PostHog is used for non-sensitive funnel events with session masking and an EU endpoint.
Abuse controls
The operations design specifies Vercel WAF rate limiting around the lead endpoints.
One source test
The reviewed repository contains one source-behaviour test and one database migration.
No CI workflow found
Automated CI, RLS tests and production-like vertical-slice checks belong before the operational pilot.
07
Development record
The next milestone is commercial proof, not more surface area.
Thesis + evidence
Complete
Approved v0.4 design
Complete
Acquisition wedge
Live
Lead validation
Current gate
Operational pilot
Next
Platform scale
Later
Known boundary
Parqo is not yet an operating parking marketplace. The live production asset validates acquisition; the approved v0.4 design describes the next product. Facility contracting, access provisioning, staff and employer portals, payments, provider adapters and the employee PWA remain future work gated by district-level demand and supply evidence.
08
Evidence register
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
R2Approved v0.4 specificationReviewed
R3Current acquisition website stackReviewed
R4AI-native delivery controlsReviewed
R5First Codex implementation promptReviewed
R6Ordered implementation backlogReviewed
R7Operations runbookReviewed
R8Notion leads dashboard automationReviewed
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.