Project Management for Small Businesses

You outgrew the spreadsheet years ago, not last quarter

A lot of project management writing assumes you're either brand new or growing twenty percent a month. Most small businesses are neither. You're a design studio that's held steady at eighteen people for six years. A facilities contractor running four crews. A small manufacturer's back office coordinating orders, vendors and a production floor. The company isn't chasing anything. It just needs to stop running on a shared spreadsheet that three people are scared to touch, and a group chat where the client somehow ended up in the thread too.

The spreadsheet didn't fail because it's a spreadsheet. It failed because nobody owns updating it, so it's accurate the day it's built and increasingly fictional every week after. The group chat works fine until someone's on leave and the message about a deadline gets read by the wrong three people, or the right one two days late.

What a business like this actually needs isn't more process, since there's nobody free to run a process. It's a system where status is a side effect of doing the work, because there's no ops hire whose job is chasing it out of people. This is exactly the gap ShipSprint's boards are built to close for a team this size: WIP limits and a triage inbox do the noticing, so nobody has to be assigned the job of noticing.

It's also worth saying what this isn't: it isn't a growth story. Nobody at an eighteen-person accounting firm is trying to hit 40 people next year, and a tool sold on the promise of "scaling with you" is solving a problem this business doesn't have. What's needed instead is something that fits well right now, stays affordable at this size indefinitely, and doesn't demand a re-evaluation every time a new feature ships that only matters to much bigger teams.

The kind of small business this is actually written for

Picture the businesses that quietly make up most of the small-business category: a regional accounting firm with eighteen staff and three offices. A print and signage shop that's been on the same high street for a decade. A boutique HR consultancy with twelve consultants, most of whom have been there since the beginning. None of them are trying to become the next big thing. They're trying to keep doing good work at roughly the size they already are, without losing a week every quarter to "wait, who was supposed to follow up with that supplier."

That's a different set of needs from a startup burning through its free-plan seats in month four. A steady small business doesn't need a system that scales gracefully to two hundred people. It needs one that works well at eighteen, doesn't demand an administrator, and doesn't ask the owner to become a part-time software evaluator every eighteen months when the old tool gets acquired and re-priced.

The Team plan, priced for a business that already knows its headcount

You're not modelling growth curves. You know roughly how many people are on payroll, because it hasn't moved much lately. Team is ₹299 per user per month, or ₹2,899 per user per year if you'd rather pay once and stop thinking about it. Twenty people comes to ₹5,980 a month on the monthly rate, or around ₹4,830 a month billed annually. Either way, it's a rounding error against what a bad week of "wait, did anyone follow up with the vendor" actually costs you.

If the business genuinely spans more than 40 people, or runs as several departments each with their own budget, the ../../pricing.html page covers the Business plan and when that jump is worth making.

What a steady small business actually notices

• A "my day" screen means a new office hire knows what's theirs on day one, without someone walking them through a shared drive.
• WIP limits on the board stop a project from silently piling up behind someone's desk while they're heads-down on something louder.
• The reminder for a missed time entry goes to the person who missed it, not to their manager: nobody enjoys being copied on a colleague's forgetfulness.
• No screenshots, no activity tracking. Trust runs both directions in a business this size, and everyone already knows who's actually working.
• Every workspace is an isolated tenant with two-factor login available, which starts to matter once client data is involved.

Who ends up owning this, in practice

In a business this size, there's usually no ops manager whose full-time job is running internal tools. It's the office manager, the founder's longtime deputy, or whoever's naturally organized enough that things gravitated toward them over the years: the same person who currently maintains the spreadsheet nobody else fully trusts. That's who ends up as the de facto admin, on top of their actual job, so anything that requires ongoing care and feeding is a cost to them specifically, not an abstract "IT overhead" line.

That's the practical argument for something that mostly runs itself: reminders that go to the person who missed a time entry rather than needing a manager to notice and chase; a triage inbox that catches new requests without someone manually routing them; boards that surface a stuck project on their own instead of requiring a weekly manual audit. None of it needs daily attention from whoever's nominally in charge of "the system," which matters when that person also has a real job to do. For a business this size, that's usually the biggest practical win: the de facto admin gets their afternoons back instead of trading one manual system for another.