Software team size calculator
Enter the hours of work and the weeks you have, and see the smallest team that fits, allowing for coordination.
Free, runs in your browser, no sign-up. Updated 2026-10-25.
Result
3,000 hours in 16 weeks needs 7 people (about 15.2 weeks at that size, 21 communication channels).
- Without coordination losses
- 6 people
- Communication channels
- 21
- Hours per person per week
- 32
- Loss per extra person
- 2%
| People | Effective hours a week | Weeks | Channels |
|---|---|---|---|
| 1 | 32 | 93.8 | 0 |
| 2 | 63 | 47.8 | 1 |
| 3 | 92 | 32.6 | 3 |
| 4 | 120 | 24.9 | 6 |
| 5 | 147 | 20.4 | 10 |
| 6 | 173 | 17.4 | 15 |
| 7 | 197 | 15.2 | 21 |
| 8 | 220 | 13.6 | 28 |
| 9 | 242 | 12.4 | 36 |
| 10 | 262 | 11.4 | 45 |
Adding people to a late project can slow it further: each new person needs onboarding and adds channels.
Assumptions
Every number the result depends on, and where it comes from. Change any value and the result updates.
| Assumption | Value | Source |
|---|---|---|
| Productive hours per person per week | hours | OceanLab assumption. 40 paid hours minus meetings and review. Planning assumption.Reviewed 2026-10-25 |
| Time lost to coordination per extra person | % | OceanLab assumption. Each person added costs everyone a little time in hand-offs and meetings. Planning assumption, no primary source.Reviewed 2026-10-25 |
Send this to OceanLab
Opens an email to OceanLab with this result and a link to your inputs. Nothing is sent until you press send, and there is no sign-up.
How this is calculated
Each person adds productive hours per week, but each extra person also costs everyone a little time in coordination: effective hours = people × hours per week × (1 − loss × (people − 1)).
The team size is the smallest team whose effective hours finish the work within the weeks, up to 20 people.
Communication channels = n(n − 1) ÷ 2, which is why coordination grows faster than headcount.
Hours per week and the loss per extra person are planning assumptions. Edit them in the assumptions panel.
Questions about this tool
Why not just divide hours by weeks?
Every person added needs onboarding and adds conversations. The table shows how the gain from each extra person shrinks.
Where do the total hours come from?
From an estimate. The software development cost calculator shows total hours across roles.
What if no team size fits?
Cut scope, move the date, or both. Adding people beyond the point where gains flatten rarely helps.
Is anything I enter sent anywhere?
No. The tool runs in your browser and there is no sign-up. Nothing leaves the page unless you choose to email your result to OceanLab.
Other free tools
OceanLab product builds like this
Products OceanLab designed and built. Each case study covers the screens, the scope and the rules it was built for.
Building Pylon - AI-Native Insurance Operations from Prototype to Production
Replaced fragmented policy spreadsheets and disconnected claims tools with a unified AI-driven workspace, designed and shipped in 8 weeks via clickable AI prototype.
Clinica - Multi-Department Clinic Operations Console with AI Assistant
Built a multi-department clinic operations console with appointment management, department load tracking, staff performance, resource utilisation and an AI assistant for staff queries - shipped from clickable AI prototype to production in 14 weeks.
Qafila - Order Management System for Omnichannel Beauty Retail
Designed and built a clickable order management system for an Amman beauty retailer selling through 60 stores, two distribution centres, its own website and app, and Amazon, Noon and a fashion marketplace across Jordan and the GCC: every order in one place, sourcing that explains itself, and one dashboard for every stuck order.
Kleidi - SaaS Admin Console with Consented Support Access and a Full Audit Trail
Designed and built a clickable internal admin console for an Athens SaaS company that sells housekeeping software to EU hotels: find any tenant and see everything about it on one page, enter a customer's workspace only with their consent, work GDPR data requests on the clock, and give staff elevated rights only for a limited window with someone else's approval.
