The intelligence engine scores properties on violations, permits, liens and market signals; saved searches alert on new matches.
◆ Solution 02 · Execution & collaboration
From a scored parcel to a delivered project
Execution Layer connects distressed and underused property to qualified local professionals, then runs the whole engagement in one place — project workspaces, tasks, threaded messaging, document version control, the permit lifecycle, inspections and recertification deadlines, with an audit trail behind every action.
Modules
Five systems that usually live in five tools
Marketplace, collaboration, permitting, intelligence and forms — sharing one data model and one audit trail.
🏘️
Marketplace
Interactive map search with property pins colour-coded by distress score, a professional directory with discipline filtering and service-area matching, lead generation, and ratings and reviews.
🗂️
Collaboration hub
Realtime project workspaces with role-based access, Kanban task boards with subtasks, threaded messaging with @mentions, document management with version control, and full activity logging.
✅
Permitting & compliance
Permit lifecycle workflow, inspection scheduling and recording, checklist templates that auto-instantiate, deadline monitoring with reminders, and an escalation engine with multi-level notification.
🎯
Intelligence engine
Distress scoring, professional matching on geography, discipline and capacity, saved searches with alerts, and violation and permit data integration feeding the marketplace.
📝
Forms module
Drag-and-drop builder with rich field types — text, number, date, select, rating, location, attachments and subforms — conditional logic, AI-assisted UI generation, and JSON-schema export.
💳
Wallet & orders
Service catalog, order flow for both sides of the marketplace, provider service management, and a wallet ledger — so the commercial relationship lives in the same audit trail as the work.
The workflow
How a lead becomes a closed permit
Five steps, one record, no re-keying between systems.
A lead is scored against the professional directory on geography, discipline and current capacity, then routed to the shortlist.
The lead becomes a workspace in one call — members, roles, tasks, documents and messaging provisioned together.
Permits move through explicit lifecycle transitions with checklist templates, scheduled inspections and monitored deadlines.
Sign-off, an immutable activity log, and recertification dates tracked forward with escalation before they lapse.
Walkthrough
The whole platform in one pass
A recorded run through dashboard, marketplace, professionals, leads, workspaces, chat, documents, forms, permits and recertification.
Recorded against a running instance — no mockups.
Screens
Every module, captured
Architecture & API SDK
A Rust backend with the API already written
Execution Layer runs on TrailBase — Rust, SQLite with STRICT tables, and WASM handlers — with a React and TypeScript frontend. Every table gets CRUD endpoints and a realtime subscription stream for free; domain logic lives in explicit custom endpoints.
| Component | Technology |
|---|---|
| Backend | TrailBase — Rust + SQLite + WASM |
| Database | SQLite with STRICT tables |
| Frontend | React + TypeScript + Vite |
| Maps | Mapbox GL JS |
| Styling | Tailwind CSS |
| Deployment | Docker Compose |
# Auto-generated CRUD for every table GET /api/records/v1/{table} GET /api/records/v1/{table}/{id} POST /api/records/v1/{table} PUT /api/records/v1/{table}/{id} DELETE /api/records/v1/{table}/{id} # Realtime — server-sent events GET /api/records/v1/{table}/subscribe/* # Domain endpoints POST /api/custom/v1/leads/match POST /api/custom/v1/distress/calculate POST /api/custom/v1/permits/transition POST /api/custom/v1/workspaces/convert-lead
properties # property records with geospatial data professionals # professional profiles + service areas leads # lead records and match state workspaces # project rooms with role-based access tasks # Kanban tasks and subtasks permits # permit lifecycle + inspections activity_logs # immutable audit trail form_definitions # form schemas and templates form_instances # submitted forms form_attachments # files attached to submissions
◆ Source-code SDK for every solution
Run your next project on it
Bring a real permit backlog or a live matching problem to the demo — that is where the platform earns the meeting.