QTO House
Construction takeoff & estimation platform.
Problem
Takeoff services traditionally run on email threads and spreadsheets. With 300+ clients and 2,500+ projects moving through a manual pipeline, prospects couldn't see sample work before committing, quote requests got buried in inboxes, and clients had no visibility into where their estimates stood.
Solution
I turned the whole funnel into product: a public sample-takeoff library that does the selling, a structured quote-request pipeline that replaces email intake, and an authenticated dashboard where clients follow projects from submission to estimate delivery. Django and PostgreSQL run the pipeline; a React frontend on Cloudflare Workers serves it.
Stack
Key Features
What I Learned
Contractors want status, not features — designing for a non-technical audience forced me to cut cleverness and surface state. Owning schema, API, and interface end to end also made every tradeoff mine to see, not someone else's problem.