Productivity & Workflows
Todoist Pro or Business? Decide Whether You Need Personal Upgrades or a Team Workspace
A fictional three-person team maps personal and shared work, compares Pro and Business seat costs, and records a six-task departure handoff without confusing guest access, personal entitlements, and billing.
Choose Todoist Pro when the missing capability belongs to your personal task system. Choose Business when the work needs a team-owned workspace, roles, shared project organization, and centralized billing. Business already includes personal Pro features for its members, so do not automatically budget a second Pro subscription for each person. Guests are a different relationship and do not inherit that entitlement.
This LandOffer.ai guide checks official documentation on October 27, 2026. The workspace map, budget, and departure record below are complete fictional examples. We did not access Todoist accounts, create projects, invite or remove people, move tasks, change subscriptions, or test permissions. Prices and documented behavior support a buying decision; they do not establish actual team productivity or account-specific charges.

Buy for the missing capability, not the word Business
The current Todoist pricing page lists Pro at US $7 monthly or $60 billed yearly, equivalent to $5 per month. Business is US $10 per user monthly, or $96 per user billed yearly, equivalent to $8 per month, plus local tax. Annual equivalents are not month-to-month payment options. Prices here exclude tax, promotions, proration, and any account-specific credit.
Pro's listed personal upgrades include more projects and filters, personal calendar layout, task duration, custom reminders, and fuller reporting history. Business adds a shared team workspace, team-project calendar layout, folders, roles, and consolidated billing. Those features answer different problems: a better personal planning view does not by itself establish a team-owned home for work.
Todoist also supports a free team option. Collaboration alone does not justify Business; identify the required limits and controls. Three personal Pro subscriptions do not supply the Business administration model.
A solo employee who wants personal calendar planning and has no shared-workspace requirement should normally evaluate Pro first. A group that needs recurring shared projects, accountable administration, and a central invoice has a stronger Business case. An employer's permission to store the work remains a separate requirement from either purchase.
Separate personal space, membership, and project access
Todoist's Business introduction, updated October 26, describes personal My Projects as separate from the team workspace. It also explains that team members receive Pro features in personal projects. That does not move private projects into the team or make the employer the owner of every task a person creates.
Treat that as a Todoist workspace distinction, not a promise about a managed device, shared login, or an employer's other systems. A personal project manually shared with colleagues is also a different situation from an unshared personal project. Decide what belongs in the team before moving anything; a combined task view is not evidence of shared ownership.
The roles documentation distinguishes admins, members, and guests. Admins manage billing and team settings. Members collaborate across the team without those high-level controls. Guests are outside collaborators invited to particular projects, are not billed as team members, and do not inherit Business's paid features. On a free team, invited team members are admins by default; the member role requires Business.
An internal colleague who needs the whole team's working context should not be labeled a guest merely to make a spreadsheet cheaper. An outside reviewer needing one bounded project should not be made a full member merely because the invitation button is easier to find. Map the relationship and access first, then calculate its cost.
A completed three-person workspace map
Lina, Ezra, and Bo are a fictional documentation team using Chrome on Windows 11 laptops and Todoist's mobile apps for review. They currently coordinate in separate task lists. Their employer has not approved the proposed workspace. Val is an external designer who needs to review one website project, not browse the team's other work.
The group has six ongoing work projects: Release Notes, Translation Intake, Website Refresh, Support Articles, Vendor Review, and Quarterly Planning. Their stated reasons for evaluating Business are a central team home, member roles, shared project organization, and a team calendar view. They are not assuming that paying for more software solves unclear responsibility.
Here is the completed proposed placement and access record. It is a design decision, not an observed Todoist configuration.
| Person or item | Proposed location and role | Included scope | Explicit exclusion or check |
|---|---|---|---|
| Lina | Team admin | Billing review, workspace settings, coordination of all six work projects | Personal Home and Language Study remain unshared in My Projects |
| Ezra | Team member | Release Notes, Translation Intake, and collaboration in the other work projects as appropriate | Personal Reading List stays outside the team; no billing authority |
| Bo | Team member | Support Articles, Website Refresh, and shared planning responsibilities | Personal Weekend Projects stays outside the team; no billing authority |
| Val | Guest on Website Refresh only | Review the agreed design tasks and comments in that project | No general team browsing, no assumed personal Pro entitlement, no other project access |
| Six work projects | Named team workspace: Editorial Operations | Work tasks and work context belong in the team record | Existing personal lists must be reviewed before any migration; nothing moved yet |
| Personal planning view | Each person's own account | Members' included personal Pro features where applicable | A combined view must not be mistaken for a shared project or permission setting |
The first draft of the map placed Translation Intake in Ezra's personal space “because he started it” and treated Val as a fourth paid member “because she needs one task.” The corrected map puts continuing team work in the team workspace and gives Val a project-scoped guest proposal. Lina keeps the employer's content-approval question open instead of sending an invitation.
This choice still requires a project-access review. Todoist documents team-visible and restricted project settings; the team name alone does not tell you which projects someone can see. Lina must verify the intended project audience and any default collaborator settings in an authorized setup. If Website Refresh contains material Val should not see, the solution is to separate approved review content before sharing, not assume a guest role hides individual tasks automatically.
The group selects Business for its three internal members, subject to employer approval and access checks. It does not include a separate Pro purchase for Lina, Ezra, or Bo. Val remains a Website Refresh guest candidate; her paid-feature needs are unconfirmed. This is a resolved scope choice with an unapproved rollout, not a completed deployment.
Calculate the bill from actual relationships
Using the current annual prices, three personal Pro subscriptions cost $180 per year. Three Business members cost $288 per year before tax, a $108 difference. On monthly billing, the comparison is $21 versus $30 each month, a $9 difference. These differences price the stated team capabilities; their productivity value remains unmeasured.
| Steady-state arrangement | Monthly billing before tax | Yearly billing before tax | Why it does or does not fit this case |
|---|---|---|---|
| Lina alone on Pro; Ezra and Bo on Beginner | $7 | $60 | Upgrades Lina's personal system but does not meet the stated team-role and administration requirements |
| Three separate Pro users | $21 | $180 | Personal upgrades for all three; not equivalent to the Business workspace model |
| Three Business members, Val a project guest | $30 | $288 | Matches the proposed team structure; personal Pro features already included for the members |
| Four Business members, including Val | $40 | $384 | Adds $10 monthly or $96 yearly for a relationship that currently needs only one project |
| Two Business members after Ezra leaves, Val still a guest | $20 | $192 | A future full-cycle baseline only; not a prediction of the next prorated invoice |
Do not add $180 of separate annual Pro subscriptions to the $288 Business budget and call $468 the required total. That would duplicate personal entitlements for the three members. However, included features do not mean an existing store subscription has been canceled or its unused value refunded.
The Business setup guide, updated October 15, distinguishes existing Pro payments from team billing. Beyond the stated refund window, remaining Pro time may become credit usable for future Pro website purchases, not the Business invoice. It also explains payment-channel differences and warns about store renewals. The team should reconcile the actual receipt and subscription channel rather than subtracting an invented credit from its first Business bill.
Lina's completed procurement note therefore records $288 as the unadjusted annual team budget, Val excluded as a guest, and all transition credits as unknown until verified. She selects monthly billing as the candidate evaluation arrangement at $30 per full month, because annual commitment is not yet approved. No trial or purchase is initiated. Once the team validates the workspace, it can compare the annual commitment separately instead of calling the evaluation price $24 monthly.
Complete the departure handoff before removing a member
Six weeks into the fictional planning scenario, Ezra is expected to leave the internal team. The group completes a paper handoff decision, while all account actions remain pending. This is where a team-owned workspace matters more than the number of personal filters a plan includes.
Todoist's member-management guidance says that removing someone from all team projects leaves their assigned tasks unassigned and visible to remaining people with access. It also describes retained task comments and says accounts should not be exchanged between people. Reassign unfinished work before removal; give a replacement their own authorized account.
The completed handoff record identifies six open work tasks and their accepted future owners:
| Work record or decision | Accepted disposition within the fictional discussion | Account-side verification still required |
|---|---|---|
| Release Notes: draft outline and collect source links | Bo accepts both tasks and their current context | Reassign the two tasks and confirm Bo can open the referenced material |
| Translation Intake: triage pending request and resolve glossary question | Lina accepts both tasks; the glossary answer is still pending | Preserve the unanswered question and source links; do not mark either task complete merely to clear Ezra's list |
| Quarterly Planning: prepare review note and inventory open dependencies | Bo accepts both tasks | Reassign the two tasks and retain the dependency status |
| Ezra's personal Reading List | Remains his personal project; no team migration approved | Confirm no work-only material was incorrectly left there, using the employer's approved process |
| Team membership | Lina will remove Ezra only after the work handoff is checked | Verify no open work remains unintentionally unassigned and inspect access after removal |
| Future bill and personal upgrade | Two-member full-cycle Business baseline is $20 monthly before tax | Inspect actual proration/credit and Ezra's separate personal entitlement; no refund amount promised |
Bo accepts four tasks and Lina accepts two, accounting for all six. That is an acceptance of responsibility in a fictional discussion; it is not evidence that six assignments were changed in Todoist. An updated assignee field does not verify Bo can open a required private link.
If Ezra later becomes a genuinely external reviewer, guest access requires a new project-specific decision. The role guide describes removing a member and then inviting them to selected projects as a guest, rather than directly flipping the membership into guest status. That would require authorization and review of what Ezra should retain access to; the article does not perform it.

Plan for personal features after team access ends
The cancellation guide, updated October 21, says someone leaving a Business team returns to Beginner rather than automatically regaining their old Pro plan. Future Pro use requires a new upgrade, with eligible credit applied through supported website payments. Personal data ownership, personal paid features, and the team's invoice are three separate questions.
Ezra's departure note therefore does not promise that his earlier Pro subscription restarts, nor that he can keep paid features merely because he once belonged to Business. It records a personal subscription decision for him after the team entitlement ends. Lina does not buy it on his behalf or treat his personal credit as team money.
Choose Pro if the work is fundamentally your own planning system and its personal upgrades justify the price. Choose Business when the continuing team record and administration requirements are real, and budget for the actual admins and members. Keep appropriate external collaborators project-scoped without pretending that a guest inherits every paid feature.
Before upgrading, complete a space-and-role map, a full-cycle budget, and an exit owner for unfinished work. Verify the subscription channel, included personal entitlement, and approved recipient access before committing. LandOffer.ai publishes this guide; no account, membership, task, billing, or permission changes were made for it.


