TurnFlow Home

One calm record for every home repair: capture it, share just that job, prove the work, keep the history.

What it is

Homeowners who manage their own repairs live in text threads, camera rolls and receipt drawers. TurnFlow Home gives each property one shared record. You log an issue with photos, compare quotes, invite a vendor or trusted helper to that one request only, and get before/after proof, a decision history and a cost record that stays with the house.

It is intentionally homeowner-first: not property-management dispatch software, and not a payment processor.

How it works

flowchart LR
  O([Owner]) -->|creates| R[Repair request<br/>photos, urgency, access]
  R -->|invites one person| V([Vendor])
  R -->|invites one person| H([Helper])
  V -->|bid| Q[Owner approves quote]
  Q --> W[Work sessions<br/>before and after proof]
  W --> C[Closeout]
  C -->|owner approves| D[Complete + billing record]
  D --> Hist[(Property history<br/>PDF, CSV, backup)]
  H -->|updates| R

Key steps (status changes, invites, quote and closeout decisions) write an entry to a decision log, and helpers only ever see the request shared with them.

Guided intake	Request detail	Vendor portal	Maintenance calendar

Status

• Built: owner, vendor and collaborator workflows end to end, with 36 unit-test files (342 tests) and 7 browser smoke loops. CI runs lint, typecheck, tests, audit, schema-drift check and build.
• Hardened on 2026-09-28: private file access, strict status rules, login limits, and a private demo password (what changed).
• New on 2026-10-25: invited vendors and helpers create their account straight from the invite link, so a real person can run the full loop (what changed).
• Next: password reset, transactional writes, and moderated homeowner testing (roadmap).

Read more

I want to…	Go to
Start with the visual and narrative system guide	PROJECT_SYSTEM_GUIDE.md
Understand the project in 10 minutes	docs/README.md → Problem → System map
See how each feature works (algorithm, pseudocode, flowchart)	docs/04-algorithms/
Find a file	Code map
Read the latest review (PDF)	docs/review/
Deploy or operate it	Deployment · P0 rollout runbook
See the history of changes	Build log
Read the previous (long) README	docs/history/README-2026-09-18.md

Quickstart

npm install
cp .env.local.example .env.local   # fill in DATABASE_URL, BLOB_READ_WRITE_TOKEN, AUTH_SECRET, SEED_PASSWORD...
npm run db:migrate
npm run db:seed                    # demo accounts; needs SEED_PASSWORD unless the DB is on localhost (see docs/DEPLOYMENT.md)
npm run dev

Before deploying:

npm run poc:ready   # checks env values, including private file storage
npm run verify      # lint, typecheck, tests, audit, schema drift, build

The curated investor demo (npm run db:seed:investor) needs INVESTOR_DEMO_PASSWORD set. The password is shared privately and never committed.

Tech stack

Next.js 16 (App Router, Server Actions, TypeScript) · Neon Postgres + Drizzle ORM · Auth.js v5 · Vercel Blob · Resend · Vercel Cron · Tailwind CSS v4 · Vitest · Playwright.

This is the fourth iteration. It was rebuilt from a static Firebase MVP onto a real server boundary with relational data and server-side authorization (why it was rebuilt).