The work it takes to make software useful.

I tried to set up a CRM. We spent weeks on it, and the effort wasn’t productive.

That is the part I want to keep in view when comparing software: the work required before it helps with anything.

I’m not turning one unsuccessful implementation into a verdict on the product. I’m interested in the decision around it. How much setup work should we accept before we expect something useful?

For another attempt, I’d make the first test much smaller: one contact, one opportunity, one follow-up. I’d also agree on a point at which we decide to continue or change course.

Then I’d compare the subscription with the implementation effort, ongoing maintenance and the time someone needs to own it.

Sometimes more control is worth that work. Sometimes you just need a functioning CRM.

There isn’t one answer for every business. But I’d want to make that trade-off deliberately, rather than let a tool become another project competing for attention.

The question I’d ask earlier is simple: what has to happen before this actually helps us run the business?