The house is already winning

Let's go.

I interviewed a painter on the Central Coast in July. Years ago he was crew at a 25-person painting contractor when the owner rolled out a phone-based time-punch app. Arrive, depart, a notes field.

He was careful about the owner's motive, and offered it as a guess rather than as something he'd been told: "The owner wanted to make sure that people weren't taking advantage, you know, I guess was the idea." Guys writing hours down later. Hours that might not match the hours worked.

The arithmetic on the ground looked different.

"If I went to three jobs in a day, I had to like pull it up six times," he said. "For when you're arriving and when you're leaving."

Six interruptions is a small number or a large one entirely depending on what the day already costs you. At this shop it was large, because the estimator who bid tight had already spent the slack. A job came down as one hundred hours with a note attached: "Oh, if you really move, you can do it in this." A second estimator at the same company gave you more room in the bid. You didn't get to pick which one priced your day.

"And so you had to just move, move, move," he said. "And so then they bring in this thing now. Now you've got to do all that, you also have to find time to stop everything you're doing and punch in to your phone and scroll down here and answer all these confusing things."

His argument back to the owner was about brushes. Most of the crew took theirs home at night and cleaned them on their own time, then showed up the next morning with them ready.

"The house is already winning. That's what I told him. You don't need to worry about these people stealing from you a minute here, a minute there. They're already doing this on their own."

The same usage data reads two ways, and you only get to write for one of them. It reads as accountability from the seat that bought it and as an accusation from the seat that generates it. There is no neutral version. Whichever reader your homepage was written for, the other one reads it too, and at a 25-person shop the other one is standing in the room when the announcement gets made.

Recovered minutes is a fragile place to put your ROI story. Time-tracking products are almost always sold on it. The claim carries an assumption underneath: that the loss is where the buyer is looking. At this shop it wasn't. The margin problem was upstream, in a bid priced with no room in it, which is also the thing that made six punches a day unaffordable. Content that names where the money actually goes will outperform content that quantifies the leak your buyer already suspects, because buyers suspect the wrong one about as often as not.

Then there's what didn't happen. There's no scene where he refused, and no scene where he came around. He complied the entire time. He never converted. Every login-based metric would have scored that rollout green, because he punched in six times a day exactly as instructed. What he actually reported was quieter: it made it less fun to work there.

Compliance without conversion is the failure mode adoption reporting is worst at detecting, and that's what this was, from a guy who was already giving the company unpaid labor at home every night.

Take the page you send to buyers and read it twice.

Read it once as the person who signs. Then read it again as the person who is going to stop what he's doing and punch into your product six times on a day that was priced with no room in it. If the second read turns up a sentence that sounds like an accusation, that's the sentence that gets quoted in the van on the way to the job.

He put the whole adoption thesis in one line himself: "The technology can be helpful if it doesn't impede your day."

The people who rolled that app out were solving a theft problem they didn't have, and they paid for it in painters who stopped enjoying the work. Nobody logged that. There's no field for it.

HammerScript Field Notes. A content engine for construction SaaS companies. If your content isn't landing with contractors, let's talk. hammerscript.io