August 17, 2026 — BuildVera
I built BuildVera because I couldn't answer one question
Nobody asked me to build job costing software. I just couldn't tell the owner which jobs actually made money — and nothing I looked at was built for how a small crew really works.
What I built
BuildVera is job costing for construction — cost tracked by crew, by equipment, by category, tied to the actual job. I didn't start with a tech stack or a market size. I started with the spreadsheet I was already keeping at the crane company, and the questions I kept not being able to answer from it.
Why
I run the back office of a crane and steel-erection company. At the end of any month I could tell you what came in and what went out. I could not tell you which jobs were worth doing again. The software I looked at was built for general contractors with an office full of admin staff — not for a crew where the same person does dispatch, invoicing and payroll. So it never fit how the work actually happens, and everyone quietly went back to the spreadsheet.
What changed
BuildVera only tracks what someone in a small construction office can realistically enter between phone calls. Every part of it exists because I needed it on a real job first, not because it demoed well. When I add something now, the test is whether I would have used it at 6pm on a Friday with payroll still to run.