Built by a contractor,
for contractors
A former project manager and tradesman got tired of writing the day up in the truck once the gate was shut. What follows is why CrewLog exists, how it’s built, what it refuses to do, and who it isn’t for.
Built and run from Ontario, Canada
Everyone else writes it down at a desk
Construction asks the people furthest from one.
Almost every record a business keeps is made by somebody sitting down. The shop closes out the till. The office logs the hours it billed. The dispatcher closes the run. In every one of those, the person keeping the record is already at the desk where the record gets kept.
Construction is the exception. The people who know exactly what happened — who showed up, what got installed, what the inspector said, what changed — spend the day on their feet, outdoors, hands full. The record is asked of them afterwards, somewhere else, on their own time.
That gap is where the money goes. Not in the building; the building gets built. It goes in the backcharge nobody can answer, the change order nobody wrote down, and the week spent rebuilding a month out of memory and a camera roll.
Software has been sold into that gap for decades, and most of it made the day longer. It asked the job site to behave like an office: log in, open the form, fill the required fields, save. That works when the person filling it in is already sitting at a desk. On a job, nobody is.
So CrewLog starts from the other end. You already say what happened — on the phone, in the truck, to the guy on the next job. The record should come off that. It should be a by-product of the day, not a second job after it.
I built the tool I
wished I had on site
I spent years as a project manager and out on the tools. The building was never the hard part. The hard part was everything around it. Who showed up, what actually got done, the photos, the delivery that never turned up, the change the client asked for on Tuesday that nobody wrote down. A site throws a hundred little things at you every day, and they all sit in your head until one of them comes back to bite you.
By the time you’ve locked up, you’re done in. Sitting in the truck to write the whole day up is the last thing you’ve got left in you. So it gets rushed, or it just doesn’t happen. And it was never that anyone was lazy. Everyone’s going flat out from the first coffee to the last load. There’s nothing in the tank for paperwork once the gate’s shut.
But the second any of it slips, it lands back on you. A dispute comes up and there’s no record. An invoice gets questioned and you can’t prove a thing. The client’s on the phone about last week and you’re sat there trying to remember what happened three Tuesdays ago. I got caught out by that more times than I’d like to admit.
Everyone knew it mattered. We just needed a way to do it that didn’t cost us the last hour of the night, every night.
So I built it myself.
You talk it through on the drive home, or type a couple lines between jobs, or just chuck your photos at it. CrewLog keeps every job, photo, task and safety talk in one place, writes your daily reports for you off the back of it, and holds onto the stuff you’d normally forget. Got a code question or a safety question on site? Ask it right there and you get a straight answer.
Solo, or running crews across five sites, I built this so the job is the thing you’re thinking about, not the paperwork following you home. That’s the whole reason it’s here. If it hands you back even one evening with your family, it’s done exactly what I made it for.
Sean Wemple
Founder of CrewLog · former PM & tradesman
CrewLog is built and run from Ontario, Canada
The rest of this page is what that turned into — and what I’ve refused to let it do. I’d rather you knew both before you paid for any of it.
Decisions the job site
made for us
None of these started life as product decisions. Each one is a fact about how the work actually runs, and the software had to bend to it rather than the other way round. Every one of them is checkable on the trial, without asking us.
The day gets logged where the day happened
You talk it through on the drive home, type two lines between jobs, or just send the photos up. The report is written off the back of that. Nobody has to sit down at the end of a ten-hour day and start from a blank form. That blank form is the step the record always died at.
It has to work with no bars
Basements, rural builds, the back of a site. The report is written and held on the phone with its photos and the raw voice recording, and it sends itself the moment you have signal. Nothing waits on a connection, and nothing is thrown away while it waits — not if your session expired, not if your access changed.
Half the crew doesn’t work in English
A foreman logs the day in Spanish and the owner reads it in English, off the same record. Reports, notes, safety talks, tasks and photo captions all carry across English, French and Spanish, set per person rather than per company. It is one record read in each reader’s language, not one company forced to pick a language.
Safety is not a tier
The incident and near-miss register — with corrective actions that carry an owner and a due date — is on every plan, Solo included. So are all 32 toolbox-talk topics. A crew’s safety record is not something we are willing to sell back to you at the next price point, and a company that cannot afford Pro this month still has crews on site this morning.
It stops where the job stops
No estimating, no takeoff, no invoicing, no payroll. CrewLog starts the morning after you win the job and ends when the record is written. Software that claims the whole business tends to be mediocre at all of it, and the field is the part we would rather be excellent at.
It writes things down.
It doesn’t decide anything.
That is the whole of CrewLog’s position on AI. It can organize a day you described; it cannot report a day you didn’t, sign for anyone, price anything, or decide on your behalf what is worth keeping. Everything below is that one sentence, spelled out — and every line of it cost us something: a feature we didn’t ship, a shortcut we didn’t take, a default we could have set in our own favour and didn’t.
None of the above is a promise about the future. Each one is how the software behaves today, and every one of them is something you can go and check yourself on the trial, without asking us. (On AI providers: Anthropic and OpenAI both state, in the standard commercial API terms we use them under, that they do not train on data sent through the API — their commitment rather than ours, which is why it lives down here.)
Who it’s for. And who it isn’t.
CrewLog is a field-record tool. It is very good at what happened on site, who was there, what it cost you and what you can prove. It is not the back office, and we would rather you found that out on this page than on day five of a seven-day trial.
The record is the point. Not the app.
A day that used to cost an hour to write up now costs a couple of minutes to say out loud, and a year of those is a record nobody can argue with. Everything we build from here has to make that record easier to make, or harder to dispute. If it does neither, it doesn’t ship.
Everything on the job,
everyone in the loop
Log the day, track your jobs, and keep your whole crew on the same page, with a clean, documented record behind every job. Your first one takes two minutes to set up.
7 days free on Pro, then the plan you pick · Card required, $0 today · Cancel anytime