SoftwareGlimpse
Project Management & Productivity Software

Microsoft Project Plans: Seats, Guests, and Qualifying Tiers

Choose your Microsoft Project plan by mapping must-haves to qualifying tiers — seats, guests, views, and add-ons — not homepage “from” tiles.

By Lee M.Updated Aug 18, 20268 min readFact-checked

Quick answer

Choose a Microsoft Project plan by mapping must-haves for schedule-driven PMO planning to a qualifying tier — seats, guests, views, and add-ons included — not by comparing homepage “from” tiles. Confirm workload and resources (Planner Plan 1+) and AI assistance (Planner Plan 1+) are on the package you will actually buy. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/microsoft-project/.

  • 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

Microsoft Project packaging rules

  • Tiles are the bottom layer — Researched plans: Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5.
  • Gates change the bill — Plan-gated in research: workload and resources (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5); AI assistance (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5).
  • Prove on the package you will buy — Our snapshot flags a trial on Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5 without a published length — confirm the window on the Microsoft Project pricing page.
  • Job cluster first — Must-haves should match build one schedule with predecessors, resource names, and a baseline a sponsor can read. Do not pay for hubs that serve a lightweight kanban or a docs wiki.

Microsoft Project plan path

  1. 1Day one
  2. 2Qualifying tier
  3. 3Seats/guests
  4. 4In writing

Microsoft Project plan anatomy

Microsoft Project plan anatomy: seats, gates, add-ons.
Read Microsoft Project pricing from must-have gates upward; confirm numbers on the pricing page.

What actually shapes a Microsoft Project bill

We do not invent list prices here. Use this anatomy, then confirm live numbers on the Microsoft Project 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: workload and resources (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5); AI assistance (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5).

  • Add-ons and AI

    Research lists AI assistant, AI summaries, AI automation, and AI recommendations for Microsoft Project. Research places AI assistance on Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5.

  • Implementation time

    Internal owner hours plus any vendor onboarding — get fees in writing; do not invent them.

Open Microsoft Project pricing →

Who Microsoft Project packaging usually fits

  1. 01

    Small crew (about 5–15 weekly users)

    Fits when schedule-driven PMO planning 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
  2. 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
  3. 03

    Portfolio / multi-team

    Fits only if Microsoft Project is still schedule-driven PMO planning at that scale — not if you actually needed a lightweight kanban or a docs wiki.

    • Written qualifying configuration
    • Guest vs seat rules
    • Adoption review before more hubs

Microsoft Project must vs nice

Must-have
  • Core loop on the qualifying plan
  • Seats for weekly users
  • task boards, timeline / Gantt, workload and resources, and automations and workflows
Nice-to-have
  • AI / extra hubs

1. List day-one must-haves for this job cluster

Microsoft Project plans diagram 1.
Start Microsoft Project packaging from the schedule-driven PMO planning loop — not from a “from” tile.

  • Honest musts

    Five jobs, all used weekly.

  • Wishlist

    Twelve musts including unused AI — cut to five.

  • Wrong job

    If musts describe a lightweight kanban or a docs wiki, this product’s packaging will not save you.

Must-haves should match build one schedule with predecessors, resource names, and a baseline a sponsor can read. Research-supported features include task boards, timeline / Gantt, workload and resources, and automations and workflows. 1. Write five things the team must do in week one.

  1. Mark each must vs nice.
  2. Drop anything that is actually a lightweight kanban or a docs wiki. Worked example: Harbor PMO (construction-style schedule owners) drops a cheaper tile when the must-have workflow unlocks only on a higher hub.

2. Map must-haves to a researched qualifying plan

Microsoft Project plans diagram 2.
Map Microsoft Project must-haves upward until every day-one job unlocks.

  • 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: Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5. 1. For each must-have, write the lowest researched Microsoft Project plan that includes it. Plan-gated in research: workload and resources (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5); AI assistance (Planner Plan 1, Planner and Project Plan 3, Planner and Project Plan 5).

  1. The highest plan on that list is the qualifying tier — not the homepage starter tile.
  2. Check guests and view-only seats separately. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/microsoft-project/. Worked example: Harbor PMO (construction-style schedule owners) 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

Microsoft Project plans diagram 3.
Trial Microsoft Project on the qualifying package — not the demo’s extra hubs.

  • 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 snapshot flags a trial on Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5 without a published length — confirm the window on the Microsoft Project pricing page. 1. Run a planner updates percent-complete and a sponsor sees the shifted finish date on the qualifying hub — not a demo enterprise workspace.

  1. Confirm guest/viewer behaviour if clients or execs must see status.
  2. Write the configuration: seats, hubs, add-ons, billing term. Worked example: Harbor PMO (construction-style schedule owners) 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

Microsoft Project plans diagram 4.
Buy Microsoft Project from a written configuration — never from a homepage tile.

  • 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.

  1. Seats (weekly users only).
  2. Guests/viewers.
  3. Hubs and add-ons the trial proved.
  4. Implementation or onboarding fees if any — do not invent them.
  5. Annual vs monthly only after the configuration is frozen. Worked example: Harbor PMO (construction-style schedule owners) will not sign until the qualifying hub and guest rules are in an email they can attach to the buy decision.

Microsoft Project 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 Microsoft Project plan count?

    Our snapshot flags a trial on Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5 without a published length — confirm the window on the Microsoft Project pricing page.

  • 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/microsoft-project/.

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.