Built by a builder who got tired of the pile.

Before Projects existed, running one job looked like this: a construction cloud — the expensive one — for pay apps and change orders. Asana for project tasks and scope. Dropbox holding the plans, specs, and sub quotes. Word for the long proposals. QuickBooks for estimates, invoices, and chasing what clients owed. Monday for the schedule's Gantt. Todoist for everything that wasn't a job. And a Google Sheet, because of what comes next.

The details were worse than the count. We paid to link our clients and architects into the construction cloud — not one of them ever used it. Daily logs were so slow to write that the field crew hated filing them, and after all that they still had to be sent by hand. Assigning a sub a simple to-do took so many clicks that Asana existed mostly as an escape hatch — the place to throw a quick note or an attachment because filing it properly took forever.

The sub book was its own mess: phone numbers in contacts, trades from memory. A good sub and a bad one looked identical, and “who did we have on that job last spring?” had exactly one search engine — my head.

The schedule burned through more tools than anything else. Every Gantt app made charts that looked fine on my screen and poor in front of a client — printing and exporting lookaheads never came out right, and updating them was worse — so every one of them eventually lost to a boring Excel doc that was horrible to maintain.

And here's the part that finally did it: even paying for the construction cloud, seeing profit on a job meant so many buttons and clicks that the honest answer lived in a Google Sheet — a few quick columns of simple math, made by hand, every time the question came up. Am I making money on this job? The software that existed to answer that question was the reason it needed a spreadsheet.

That's seven apps and a spreadsheet to manage one project — and the pile billed like it. Autodesk ran us over $3,000 a year at the entry tier, and takeoff was extra. At today's list prices the rest stacks fast: QuickBooks at $140 a month for the tier that tracks jobs, Asana at $11 a seat, Microsoft 365 at $14, Dropbox at $12, Monday at $12 for the tier with the Gantt. Call it more than $400 a month — over $5,000 a year — for one person's seat. The spreadsheet was the only thing in the pile that was free. And none of them talked to each other — the only thing they shared was an invoice.

So we built the one app we wanted: tasks and brain-dumps, phases and scheduling, estimates and invoices and change orders and expenses — with the five-second answer to the money question on every job, no export required. Lookaheads you'd hand a client without apologizing. A sub book with ratings, notes, and which jobs they've been on. Spaces for the rest of the business — onboarding, marketing, the side quests — under the same roof. A real iPhone app for the site, a real web app for the office.

We run our own construction company on it — every vendor in our book, every active job, every dollar. Every screen in Projects exists because a real job needed it, and everything that exists only to justify an enterprise invoice was left out on purpose. The app is fast because of what it refuses to be.

That goes for the numbers too. You won't find a dashboard with forty stats that exist for the sake of looking like software. Sales, margins, profit — clean, current, and honest. That's the dashboard.

Procore is software you're trained on. Projects is software you just use.