Basecamp Plans: Seats, Guests, and Qualifying Tiers
Choose your Basecamp plan by mapping must-haves to qualifying tiers — seats, guests, views, and add-ons — not homepage “from” tiles.
Quick answer
Choose a Basecamp plan by mapping must-haves for lightweight project communication hub to a qualifying tier — seats, guests, views, and add-ons included — not by comparing homepage “from” tiles. Confirm time tracking (Free+) is on the package you will actually buy. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/basecamp/.
- List day-one must-haves for the job cluster
- Map each to a researched qualifying plan
- Price guests / viewers separately from full seats
- Confirm trial or free proving ground
- Get the qualifying configuration in writing
- Never invent a spreadsheet total in this guide
Basecamp packaging rules
- Tiles are the bottom layer — Researched plans: Free, Pro, Pro Unlimited.
- Gates change the bill — Plan-gated in research: time tracking (Free, Pro, Pro Unlimited).
- Prove on the package you will buy — Our pricing snapshot records a 30-day trial on Pro and Pro Unlimited — confirm current terms on the Basecamp pricing page before you build a schedule around it.
- Job cluster first — Must-haves should match open one project, post a message, assign to-dos, and prove the team stopped using a parallel Slack thread for that project. Do not pay for hubs that serve an engineering tracker or a spreadsheet PMO.
Basecamp plan path
Basecamp plan anatomy
What actually shapes a Basecamp bill
We do not invent list prices here. Use this anatomy, then confirm live numbers on the Basecamp pricing page.
- Seats61%
- Add-ons18%
- Implementation12%
- Training5%
- Other4%
Full seats
People who create and update work weekly — not everyone in Slack.
Guests / viewers
Clients and execs often need a cheaper or free viewer path. Confirm whether they count as seats.
Feature gates / hubs
Plan-gated in research: time tracking (Free, Pro, Pro Unlimited).
Add-ons and AI
Our research does not list AI capabilities for Basecamp, so plan the rollout on the core lightweight project communication hub loop rather than assistance features.
Implementation time
Internal owner hours plus any vendor onboarding — get fees in writing; do not invent them.
Who Basecamp packaging usually fits
- 01
Small crew (about 5–15 weekly users)
Fits when lightweight project communication hub is the job and you can live without enterprise portfolio controls.
- One workspace owner
- One live board or project
- Guests only if the plan allows
- 02
Cross-functional team (about 15–50)
Fits when managers need a second view and you will admin the tool weekly.
- Named admin hours
- Intake or automations on a qualifying hub
- Stop shadow spreadsheets
- 03
Portfolio / multi-team
Fits only if Basecamp is still lightweight project communication hub at that scale — not if you actually needed an engineering tracker or a spreadsheet PMO.
- Written qualifying configuration
- Guest vs seat rules
- Adoption review before more hubs
Basecamp must vs nice
- Core loop on the qualifying plan
- Seats for weekly users
- task boards, timeline / Gantt, time tracking, and docs and collaboration
- AI / extra hubs
1. List day-one must-haves for this job cluster
Honest musts
Five jobs, all used weekly.
Wishlist
Twelve musts including unused AI — cut to five.
Wrong job
If musts describe an engineering tracker or a spreadsheet PMO, this product’s packaging will not save you.
Must-haves should match open one project, post a message, assign to-dos, and prove the team stopped using a parallel Slack thread for that project. Research-supported features include task boards, timeline / Gantt, time tracking, and docs and collaboration. 1. Write five things the team must do in week one.
- Mark each must vs nice.
- Drop anything that is actually an engineering tracker or a spreadsheet PMO. Worked example: Harbor Studio (a calm client-delivery crew) drops a cheaper tile when the must-have workflow unlocks only on a higher hub.
2. Map must-haves to a researched qualifying plan
Mapped
Every must-have has a researched plan name.
Tile shopping
You compared “from” prices across vendors — restart from must-haves.
Quote-only
If there is no public matrix, get the configuration in writing before you call it cheap.
Researched plans: Free, Pro, Pro Unlimited. 1. For each must-have, write the lowest researched Basecamp plan that includes it. Plan-gated in research: time tracking (Free, Pro, Pro Unlimited).
- The highest plan on that list is the qualifying tier — not the homepage starter tile.
- Check guests and view-only seats separately. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/basecamp/. Worked example: Harbor Studio (a calm client-delivery crew) discovers timeline or automations force a higher hub than the tile they screenshotted, so they re-qualify before a trial.
3. Prove the loop on the package you will buy
Honest trial
Loop works on the hub you will pay for.
Inflated trial
Ask the vendor which package the tenant is on, in writing.
Free-plan trap
Free is a proving ground only if must-haves actually live there.
Our pricing snapshot records a 30-day trial on Pro and Pro Unlimited — confirm current terms on the Basecamp pricing page before you build a schedule around it. 1. Run a contributor checks off a to-do and a lead sees it on the project hill without an owner login on the qualifying hub — not a demo enterprise workspace.
- Confirm guest/viewer behaviour if clients or execs must see status.
- Write the configuration: seats, hubs, add-ons, billing term. Worked example: Harbor Studio (a calm client-delivery crew) fails the gate when the trial ran Pro features they will not purchase. They restart the trial on the written package.
4. Get the qualifying configuration in writing
Written
Seats, guests, hubs, term — attached to the decision.
Verbal extra
If a feature was “included in the demo,” it is not included until it is written.
Walk
If packaging stays vague, keep looking via how to choose project management software.
- Seats (weekly users only).
- Guests/viewers.
- Hubs and add-ons the trial proved.
- Implementation or onboarding fees if any — do not invent them.
- Annual vs monthly only after the configuration is frozen. Worked example: Harbor Studio (a calm client-delivery crew) will not sign until the qualifying hub and guest rules are in an email they can attach to the buy decision.
Basecamp checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1List day-one must-havesFeatures that must ship without an unused enterprise tier.
- 2Map to a qualifying planUse researched plan names — not marketing starting tiles.
- 3Get the qualifying quote in writingSeats, guests, add-ons, and implementation fees.
Frequently asked questions
Does a free Basecamp plan count?
Our pricing snapshot records a 30-day trial on Pro and Pro Unlimited — confirm current terms on the Basecamp pricing page before you build a schedule around it.
Should we pay annually?
Only after the qualifying configuration is written. Annual discounts do not fix the wrong hub.
How do we treat guests?
Count people who must log in weekly as seats. Confirm whether clients and execs are guests, viewers, or billable users on the pricing page.
Can we compare “from” prices across tools?
Not usefully. Compare qualifying configurations for the same must-haves. Tiles omit gates.
Where are the actual numbers?
Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/basecamp/.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.