Project Management for 100-Person Teams

The recurring meeting that exists to answer one question

Somewhere around a hundred people, most companies have a meeting whose entire purpose is a single sentence: "where's everything." Engineering gives a two-minute update, marketing gives a two-minute update, ops gives a two-minute update, and everyone leaves having spent forty-five minutes to learn four things they could have read in four sentences, if those four sentences had existed anywhere before the meeting started.

The meeting isn't the problem. Building the update the meeting runs on is. Someone on each team spends part of their week turning boards and Slack threads into a status paragraph, and that work gets redone from scratch every single week, because there's nowhere for it to accumulate. At 100 people, running several concurrent projects across several teams, that's not a minor tax. It's a standing weekly cost that scales with headcount and never gets cheaper.

ShipSprint's answer isn't a better meeting. It's removing the reason the meeting exists: a screen that already shows where everything is, so the meeting (if it still happens at all) starts from real numbers instead of building them live.

This is squarely Business-plan territory, not because of the headcount alone but because of what the headcount implies: several concurrent projects, several team leads each with their own status to report, and an owner or founder who's several layers removed from any single board. Team was never built to answer "where are we across everything." It was built to run one team's boards well, which it still does, but that's a narrower job than the one a hundred-person company running multiple projects actually needs done.

Replacing the standing meeting, specifically

The cross-team status meeting usually exists because there's no other reliable way to get a rollup. Once the command center and Monday digest exist, the meeting's actual job shrinks to the part that needs humans in a room: deciding what to do about a risk, not reporting that the risk exists. Some teams keep a shorter version of the meeting for exactly that; most find the meeting itself gets smaller once the status-gathering part is no longer happening live. Companies around a hundred people who make this switch often stop calling it "the status meeting" within a quarter. It just becomes the fifteen minutes where the two or three at-risk items actually get discussed.

The digest matters as much as the command center here. A screen that's always current is only useful if someone remembers to look at it; a digest that lands on its own on Monday morning removes that dependency. It shows up whether or not anyone had time to build a status update that week, which is usually the exact week it's most needed.

What "several teams" actually means operationally

A hundred people rarely means one team of a hundred. It usually means five or six teams of fifteen to twenty, each with its own lead, its own cadence, and its own definition of a good week. Engineering might run two-week sprints, marketing might run a monthly campaign calendar, and ops might run a queue with no sprint structure at all. A rollup that forces all of them into the same reporting format tends to distort at least two of the three.

That's why each team's forecast is computed from its own velocity rather than a blended company number: a two-week sprint team and a monthly-cadence team shouldn't be judged against the same curve. The command center is built to show both the aggregate view and the team-by-team detail underneath it, so nobody has to choose between "the big picture" and "the accurate picture."

What it costs

Business runs ₹599 per user per month. For a hundred people: 100 × ₹599 = ₹59,900 a month. On annual billing at ₹6,499 per user per year, that's 100 × ₹6,499 = ₹649,900 a year, roughly ₹54,158 a month.

• Business is the only plan that fits a hundred seats: Team's ceiling is 40 users
• Unlimited projects, so running several at once across teams doesn't hit a cap
• Billing is per seat in rupees with GST-compliant invoices, annual billing available
• A 14-day full-access trial runs on Business with a sample project loaded and no card required

Full detail is on the pricing page.

Where the digest actually goes on a Monday morning

At a hundred people, the person who wants the Monday digest usually isn't the same person building it. It's an owner, a founder, or a head of operations who needs the picture without spending their own morning assembling it from five separate team leads. The digest is built for that seat specifically: what shipped last week across every team, what's at risk, and where a team is running thin on capacity, delivered without anyone having to chase it down first. Founders who make the switch at this headcount usually describe the same relief: Monday morning stops being the morning they spend on other people's status updates instead of their own priorities.

It also solves a smaller but real problem: the weeks nobody has time to write a proper update are usually the weeks something is actually going wrong, which is exactly when a manually assembled status is least likely to exist. A digest that's generated from the underlying work, rather than typed up by a person, shows up the same way whether it was a calm week or a chaotic one.