Project Management for Mid-Market Companies
Somewhere between 40 and 200 people, a company stops being one flat team and gets department heads instead, and the owner stops being able to answer "where are we" by walking around.
The company that no longer fits in one weekly meeting
There's a specific moment in a growing company's life that has nothing to do with revenue or funding. It's the moment an engineering lead, an HR head, a marketing lead and an ops manager each start running their own priorities, their own version of "on track," and their own private sense of what's actually urgent. Before that moment, one person could hold the whole picture in their head. After it, nobody can. Not because anyone got worse at their job, but because there are now genuinely separate things happening at once.
This is also, not coincidentally, close to where a company crosses the 40-user ceiling on ShipSprint's Team plan. That's not a marketing coincidence. Team was built for a single group working one way, and the ceiling sits roughly where "single group" stops describing most mid-market companies anyway. Once there's a department head who needs a rollup rather than a walkthrough, the plan built for a flat team runs out of room at almost exactly the same time the flat-team model itself does.
ShipSprint doesn't ask departments to converge on one workflow to get there. Engineering keeps sprints and story points, HR keeps a candidate pipeline, marketing keeps a content calendar: each department runs in its own vocabulary. What changes is that someone above all of them finally gets one screen instead of four separate check-ins.
What a company gets once every department has its own head
None of this requires departments to agree on a process. It requires one subscription that gives each of them their own.
Each department's board carries its own per-column WIP limits, so a quietly overloaded queue shows up structurally instead of at the next fire drill. New requests land in a triage inbox rather than in a department head's inbox, whichever department they're aimed at.
Logging a day's work takes about five seconds and sits next to the task someone just closed. A missing day pings the person who missed it, not their department head, so the nudge doesn't turn into one more thing on a manager's plate.
Each team's delivery forecast is built from that team's own measured pace, so a marketing launch running behind and an engineering release running behind both surface on their own timeline, weeks before either would have been obvious in a status meeting.
Everyone (engineer, recruiter, campaign manager) opens to the same kind of "my day" screen: today's items, a one-tap log, one tap to flag "I'm blocked" and pull in the right person with context already attached.
Decisions live next to the work they affect, with history, in the same workspace regardless of which department made them. Any sentence on a page can turn into a task, which is usually where a decision and the work meant to follow it quietly part ways.
The owner command center rolls every department into a single "where are we" view, and a digest lands Monday morning already built: the rollup a company this size actually needs, not one department's status dressed up as the whole picture.
Why the 40-user line matters more than the number suggests
Team tops out at 40 users. That's a hard ceiling, not a soft recommendation. The 41st person on the roster simply can't be added without moving to Business. Most companies with real department heads have already outgrown 25 or 30 seats before anyone frames it that way, so by the time the ceiling actually bites, the structural shift that made it bite has usually already happened.
Take a company running ShipSprint at 65 people, spread across engineering, HR, marketing and ops. Business runs ₹599 per user per month: 65 × ₹599 = ₹38,935 a month, or ₹6,499 a year per user for ₹422,435 annually. Compare that against what the company would have paid at Team's own ceiling: 40 seats × ₹299 = ₹11,960 a month, a plan it has already outgrown by 25 people, with no way to add a 41st seat to it regardless of price. The comparison that matters isn't Team-versus-Business on cost per seat; it's that Team simply stops being an option at exactly the headcount most mid-market companies are living at.
That's also where forecasts and the command center stop being a nice screen to look at and start being the thing that replaces a status meeting. A ten-person team's owner can ask "how's it going" in the hallway and get an honest answer. A department head three layers removed from the actual board cannot, and doesn't have the time to try.
What a mid-market rollout actually looks like
Mid-market adoption almost never happens as one project. It happens the way the departments themselves formed: one function goes first, usually whichever one is feeling the most delivery pressure that quarter, and the others follow once the first board is visibly working. A 65-person company might start with engineering running sprints on their own board for a month before HR moves their candidate pipeline over, and marketing joins a few weeks after that.
That staggered rollout works because the subscription doesn't care which departments have joined yet. A company paying for 65 seats can activate them across three departments this month and a fourth next quarter without a second purchase order or a renegotiated contract. That's a real, practical relief for a mid-market company: the rollout follows how the org actually adopts new tools, department by department, instead of forcing a single big-bang launch date everyone has to hit at once. The pricing scales with people added, not with departments turned on, so there's no penalty for going one function at a time.
What tends to force the pace isn't the software, it's the department head who's currently building their own status update by hand and would rather stop. That's usually the department that goes first, and it's usually also the department whose head becomes the strongest internal case for the next one to follow.
What it costs at this size
| Plan | Price | Fit for a mid-market company |
|---|---|---|
| Team | ₹299/user/month or ₹2,899/user/year | Up to 40 users; workable pre-department-heads, a hard wall past them |
| Business | ₹599/user/month or ₹6,499/user/year | Unlimited projects, forecasts, SSO, priority support, owner command center |
Billing runs per seat in rupees with GST-compliant invoices, and annual billing is available. Every paid plan opens with a 14-day full-access trial on Business, a sample project already loaded, no card required: enough time to see whether the command center actually replaces the status round-up your department heads currently do by hand. Full detail sits on the pricing page.
Common questions
Not purely on headcount. If there's still one person who can honestly answer "how's everything going" without checking with anyone else, Team may still fit. The better signal is whether you already have department heads each running their own priorities. That structural shift tends to arrive before the 40th seat does, and it's the shift, not the number, that makes forecasts and the command center worth having.
No. One workspace runs on one plan, shared across every department in it. What varies by department is the template and vocabulary each team uses on their boards, not the underlying subscription.
It replaces the part where someone assembles a status update from four separate sources before a meeting can happen. It doesn't replace the judgment calls: whether to move budget between departments, whether a slipping launch needs to bump a release date. Those conversations still need people in a room; they just start from real numbers instead of from memory.
The whole workspace exports as JSON at any time, on any paid plan: every department's boards, history and time logs included. Each workspace is an isolated tenant, two-factor authentication is available to everyone, and admin actions are written to an audit log. Details are on the security page.
No. Most mid-market companies start with a single department, usually whichever one is under the most delivery pressure, and add the rest once that first board is running. Because the subscription scales with seats rather than departments, adding a second function later is a template choice, not a new contract.
Related pages
See it on your own work.
A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.
14-day full-access trial · sample project included · no card required