Skip to content
← All work

Field service SaaS · Valve

Valve: field service software, built from zero

Co-founding field service software for trades businesses, and building most of it myself: web, mobile, payments and AI.

Problem

Small trades businesses run on paper, texts and spreadsheets. Quotes get lost and invoices go out late. Most field service software is built for much bigger companies.

Role

I'm co-founding Valve as a side venture. I own product direction and architecture, and I write much of the code.

Solution

  • Next.js and TypeScript on Vercel for the web app, and React Native for crews in the field.
  • Supabase for Postgres, auth and row-level security, so each business sees only its own data.
  • Stripe Connect, so each business is paid directly by its customers.
  • A Claude-powered assistant, plus an MCP server that gives AI tools permissioned access to each business's data.
A Valve job from signed quote to paid invoice, with a review request sent automatically.

One job, start to paid

Asking Piper, Valve's assistant, which invoices are overdue.

Piper, the AI assistant

A job moves from quote to paid in one place. Piper answers questions about the business in plain English.

Outcome

Next.js web app and React Native field app
Web + mobile
Next.js web app and React Native field app
Paying customers so far
0
Paying customers so far

The core product is built across web, mobile and payments, with no paying customers yet.

Telemetry

This tab only. Nothing here leaves your browser.

Core Web Vitals

LCP
…
waiting
INP
…
waiting
CLS
…
waiting
FCP
…
waiting
TTFB
…
waiting

Measured in this browser with the web-vitals library. INP appears after you interact.

Query engine

Engine
Not started
Start-up
–
Data downloaded
–
Tables loaded
–
Queries run
0
Errors
0
p50 latency
–
p95 latency
–