Built by a builder who got tired of the pile.

Before Projects existed, running one job looked like this: a task app for the brain-dumps and quick notes between site visits. A project management tool for phases, scheduling, and assigning the crew. A construction cloud — the expensive one — for pay apps, change orders, and expenses.

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.

Add a doc for writing proposals and an accounting tool for sending invoices, and that's five apps and a spreadsheet to manage one project. None of them talking to each other. All of them billing monthly.

So we built the one app we wanted: tasks and brain-dumps, phases and scheduling, budgets and change orders and expenses — with the five-second answer to the money question on every job, no export required. 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.

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