He turned down the job because of the software

Let's go.

A commercial project manager on r/ConstructionManagers, in a thread about how many jobs one PM can carry, named the thing that would rule an employer out for him. The pay never came up. The software did.

"I just couldn't use CMIC again — no way."

Another PM in the same run of threads described what that felt like from inside the workday. "I literally have to sit there while it slowly loads each step." Entire days set aside to click through change orders, on jobs he was also supposed to be running.

Neither man was reviewing software. One was deciding where to work next. The other was explaining why he left. The tool surfaced on its own, unprompted, in a conversation about careers.

That is a different class of evidence than a review site. A review is a person grading a product. This is a person pricing a product into the rest of his life and declining.

Two things follow from that, and this category has published neither.

The first is that your buyer has a hiring problem you are allowed to talk about. Construction has been short on experienced project managers for a decade, and every principal reading you is trying to keep the ones he has while hiring two more. If the platform he runs is the reason a good PM crosses him off the list, that is not a software preference. It is a recruiting cost, and it lands on a line he already watches every month.

Almost every product page in this category sells upward: visibility, standardization, control. The person who opens the thing forty times a day appears in that copy as an adoption risk to be managed. He is also the person who decides whether the next hire says yes, and whether the last good one stays through the winter.

The second is that the reverse claim is sitting there unclaimed. If your product is one a project manager would take a job in order to use, that is the strongest sentence available about it, and it works precisely because a buyer can check it. It cannot be written by a marketing team. It has to come out of the mouths of PMs who picked an employer partly because of what was on the screen.

Here is why nobody writes it. Asking the question risks an answer you did not want. Put it to twenty PMs and some number of them will tell you your tool would count against a job, and they will be specific about which screen. That answer is worth considerably more than the page you were going to publish instead, because it is the only version of this that a superintendent, a PM, or an answer engine will treat as real.

Add one question to your next three customer calls.

"If you changed companies tomorrow, would the software they run factor into the decision?"

Then ask the follow-up that actually produces material: "Has it ever?"

You will get one of three answers. No, which means your product is neutral in this dimension and you have nothing to write yet. Yes, and here is the tool I would refuse, which tells you the real churn mechanism inside your competitor's accounts. Or yes, and I would stay somewhere for this one, which is a sentence you can put on a page and defend under questioning.

Ask five people this month. If two of them say something you would not have written yourself, you have the piece.

Source: r/ConstructionManagers, threads captured June 2026, HammerScript field library.

HammerScript. A content engine for construction SaaS companies.