Ask a room of consultants why their project plan is never quite current and you'll hear the same answers: no time, too many meetings, the client went quiet. All true. But there's a cause underneath all of those that nobody names, and it's sitting in your software's pricing.
Say you're a small shop: a project manager and a couple of consultants, three of you, running one engagement for a client whose own team runs to fifteen people who all ought to see where things stand. That's eighteen people who could be on the project. On most per-seat tools, the fifteen on the client side aren't free. They come in as "guests," and guests are where the fine print lives. Guest models tend to bill around four to one, so every four guests quietly becomes a paid seat. Minimums kick in. Read-only access, the least demanding thing a person can do in your software, turns into a line item.
Put real numbers on it. Eighteen people with real access on a typical per-seat tool runs somewhere between about $1,100 and $5,400 a year, depending on the tool. On monday.com it lands around $1,900 to $4,100; on Asana, $2,400 to $5,400. Pick something heavier like MS Project and you're up near $11,900. (List prices, per seat, full access, before whatever discount a salesperson eventually offers.) Scale that client team up and the gap only widens: their number climbs with every person you add. A flat price doesn't move at all.
So you run the math, and the math tells you to keep people out. The cheapest fix to a per-seat bill is to leave the client off the platform. And that's the real reason the plan drifts. The people who keep it updated are the ones you priced out. They can't log a change themselves, so they email you the update instead, or send it in a DM, or mention it on a call. Keeping the plan current now means tracking all of that down, aggregating it, comparing one person's version against another's, and typing it in yourself. The single source of truth quietly becomes your inbox.
You end up paying for software and still doing the work the software was supposed to do.
It's backwards. The people most affected by a project are the first ones cut from the license. The client is the reason the engagement exists. They sign off on scope, answer the open question, and need to know whether things are on track. Pricing them out as an afterthought "guest" gets the whole thing upside down.
We built Groundskeeper without that math. There's no per-seat tax, and no line between an internal user and a guest. There's a project and there are the people on it. What you pay tracks the AI work Willie does, not how many people you let in, so keeping everyone on the same current plan costs you nothing extra, whether the client team is five people or fifty.
Run the numbers on whatever you're using now. Count the people you'd put on the plan if it were free, then look at what putting them there actually costs. That gap is why your plan is out of date. There's a live version of this comparison on our pricing page if you want to plug in your own team.