PNW RENOVATION MARKETPLACE

A multi-surface platform — ops portal, subcontractor field portal, and customer-facing sites — on one secure backend.

4

User Roles

Multi-Surface

Ops + Field + Web

Role-Secured

Data Partitioning

Rapid

Build to Deploy

The Problem

The business was coordinating homeowner requests, subcontractor availability, job status, scheduling, materials, and payouts across disconnected surfaces. Leads came in through customer-facing channels, operations needed a central view of every job, and subcontractors needed a field portal that exposed only the work assigned to them.

The real challenge was not another website. It was turning a multi-sided service workflow into one reliable system: capture demand, route the right work, keep each participant in their lane, and preserve a clean operational record from intake through completion.


What We Built

We built a full operations platform for the renovation marketplace: an internal ops portal, a subcontractor field portal, customer-facing marketing surfaces, and a shared backend that keeps the entire job lifecycle in one place.

Operations Portal

The ops portal centralizes leads, jobs, subcontractors, materials, scheduling, and the financial ledger. The team can see what came in, who owns the work, what stage each job is in, and what needs attention next without stitching updates together manually.

Subcontractor Field Portal

Subcontractors get a role-secured portal for assigned jobs, field updates, scheduling context, and job-specific materials. The portal keeps execution close to the people doing the work while limiting visibility to the scope each user is supposed to see.

Customer-Facing Sites

The platform includes customer-facing web surfaces for lead capture and service presentation. Homeowner demand flows directly into the operational system instead of landing in a disconnected inbox that has to be re-entered later.


Architecture Decisions

The platform runs on one Supabase backend with row-level security and strict role-based data partitioning, so owners, operations staff, subcontractors, and customer-facing flows each operate inside their intended scope. The security model is enforced at the data layer rather than hidden in interface logic.

We used a monorepo with shared primitives so the ops portal, field portal, and web surfaces could reuse the same domain logic without duplicating fragile code. Automated tests guard the access rules that matter most, especially around role boundaries and job visibility.

That combination made the platform fast to build without treating it like a disposable demo. The important pieces — auth, data ownership, deployment, and access control — were designed for production from the start.


Tech Stack

Frontend / Platform

Next.js 15TypeScriptTailwind CSS v4TurborepoVitest

Backend / Infrastructure

Supabase PostgresSupabase AuthSupabase StorageSupabase RLSVercel

My Role

Co-founder / technical partner. Architecture, full-stack build, security model, and deployment.

STOP RUNNING YOUR BUSINESS ON SPREADSHEETS.

Book a paid workflow audit before you commit to a custom build.

Book a Workflow Audit