How Much Should a Small Team Pay for Project Management?

Somewhere in the first year of running a small company, someone does the math out loud: we have five people on the tool, the contractor needs to see two tasks, and adding her is another seat. So she doesn't get added. She gets forwarded a screenshot instead.

That decision gets made quietly, at almost every small company, almost every month. It is not laziness. It is arithmetic. Per-seat pricing means every person you let in has a monthly cost attached to their name, forever, whether they open the tool once a day or once a quarter.

This post is the arithmetic. Figures below are current as of publication — April 2025 — and you should re-check them before you commit budget, because pricing pages change without much warning.

What five, eight and twelve people actually cost

Per-seat pricing has a simple shape: a monthly or yearly rate, multiplied by the number of people who need a login. The rate varies by vendor and tier, but the shape doesn't. It's linear. Adding your ninth person costs the same as adding your third.

Take a plan priced at $10 per user per month, a common enough figure in this category, and run it against three real headcounts:

• 5 people: $50/month, $600/year
• 8 people: $80/month, $960/year
• 12 people: $120/month, $1,440/year

Nothing surprising there. The number that matters isn't the total — it's the marginal cost of the next person. At $10/seat, adding one contractor for a two-week project costs the same as adding them for the whole year, because most seat-based plans don't prorate cleanly for short stretches. So the question a founder actually asks isn't "can we afford this tool." It's "is this particular person worth a permanent line item."

That question has an obvious wrong answer, and small teams give it constantly.

Team and Tricks' own numbers, for comparison

We can only speak reliably to our own pricing, so here it is, current as of this post. Free costs $0 and includes 3 users; it can add up to 5 more people at $3 each, capping out at 8 people total. Pro is $30/month or $288/year and includes 8 users, with additional seats at $3/month or $28/year and no cap.

Run the same three headcounts against Pro:

• 5 people: fits inside Free's 3-plus-add-on structure, or inside Pro's included 8 — no extra seats needed either way
• 8 people: exactly the number Pro includes, no add-ons
• 12 people: Pro's $30/month base plus 4 extra seats at $3 each, $12/month, for $42/month total

The difference from the generic $10/seat example isn't that our number is smaller — it's that the included headcount absorbs the early growth. Going from 5 to 8 people costs nothing extra on Pro. Going from 5 to 8 on a pure per-seat plan costs three more full seats, every month, forever.

The people who get rationed off

Here is the part that doesn't show up in a pricing calculator. Once a tool charges per head, someone in the company starts running an invisible cost-benefit test on every person who might need access. That test is rarely generous to the people who most need visibility.

Three groups lose this test consistently:

• Clients who want to see progress on their own project but aren't going to log in daily
• Contractors and freelancers who need two weeks of access, not a year
• Part-time or occasional staff — a bookkeeper, an advisor, a fractional operator — whose involvement is real but light

None of these people are unimportant. They're just infrequent enough that a $10/month seat feels hard to justify next to five people who use the tool eight hours a day. So they get left out, and the company falls back on the workaround it was trying to avoid in the first place: a forwarded screenshot, a status email, a phone call asking "where are we on this."

The tool was bought to stop that exact behavior. Per-seat pricing quietly brings it back for anyone outside the core headcount.

Guests are a different math problem

Some tools solve part of this by pricing external collaborators differently from internal teammates, since a client checking on their own project is a different relationship than an employee doing the work. In Team and Tricks, this shows up as guests: people outside the team who can see whatever's been granted to them — a project, a task — without taking a paid seat. Free includes 25 guests; Pro includes unlimited guests. A guest can raise a request back to the team, but they don't appear in the Members list and they're never assigned work.

That distinction matters for the rationing problem specifically. If the client, the occasional contractor, and the advisor can see the relevant work without becoming a $10-a-month line item, the decision to include them stops being a budget decision. It becomes what it should have been from the start: does this person need to see this, yes or no.

That's the useful question to ask about any tool you're pricing out, not just ours. Not "what does it cost for our five, eight or twelve employees," but "what does it cost to let in the six people around the edges who aren't employees but still need eyes on the work." If the answer is "another full seat each," you should expect those six people to stay off the tool, no matter how good the tool is.

The number that should drive the decision

Total monthly cost at your current headcount is the number vendors want you to compare. It's the wrong number to anchor on. The number that predicts whether the tool still reflects reality in six months is the marginal cost of the next person — especially the next person who isn't full-time internal staff.

If that marginal cost is a full seat every time, budget for the fact that some people simply won't be added, and plan for the screenshots and status emails that will keep happening around them. If it's near zero for the people outside your core team, you've bought yourself the option to include everyone who actually touches the work — not just the ones on payroll.