Pricing
Priced by the number of departments you plan.
A genuinely free tier for three departments, flat annual bands above it, and no implementation fee on any tier but Enterprise.
Licence bands
You pay for the licence, not the plumbing.
There is no integration project to fund, because there is nothing to stand up. PlanFoundry installs into the Salesforce org you already run.
| Band | Departments | Annual licence | Implementation |
|---|---|---|---|
| Free | 3 | $0 | $0 (self-implementation) |
| Starter | 10 | $9,500 | $0 (self-implementation) |
| Starter, upper band | 25 | $18,000 | $0 (self-implementation) |
| Premium | 50 | $32,000 | $0 (self-implementation) |
| Premium, upper band | 100 | $48,000 | $0 (self-implementation) |
| Premium, unlimited | Unlimited | $62,000 | $0 (self-implementation) |
| Enterprise | Bespoke, multi-campus | Contact us | $50,000 implementation |
Enterprise is for multi-campus systems and very large institutions, roughly 50,000 students and up, on bespoke terms. No figure is published because there isn't a fixed one.
Every tier keeps unlimited academic years of plan history, including Free. Field history beyond the Salesforce default depends on your own Shield purchase rather than on PlanFoundry, so it passes through unchanged at every tier.
A plan's approved cost is captured permanently at submit, at approval and at finalization — every tier, including Free, with no way to purge it. That is the plain answer when procurement asks about records retention.
Free
- 3 plans per department, per year
- 3 renamable approval steps
- Unlimited plan history
Starter
- 5 plans per department, per year
- 5 scenarios per plan
- 5-step renamable, reorderable route
- Portfolio & Budget Report
- Bulk approval, rate-card backfill
- Guideline evaluation (per-department caps)
Premium
- Unlimited plans & scenarios
- Approval route up to 10 steps
- Legacy plan import
- Self-service rate-card and bargaining-agreement import
- Overnight instructor-board precompute
- Portfolio scenario comparison across departments
Enterprise
- Same software as Premium
- Bespoke commercial terms
- $50,000 implementation
- Contact us →
Positioning
A scheduling platform tells you what's being taught. PlanFoundry tells you what it costs.
Scheduling and curriculum-management suites are a real category, and PlanFoundry is not a cheaper way into it. It answers a different question, for a different office, from different data.
Questions about what is taught
- Which sections run, in which rooms, at which times
- Whether a proposed course or program change clears curriculum review
- What the student-facing catalog should publish
- Whether a section is under- or over-enrolled against forecast
- How a faculty member's workload sits against release-time rules
- None of these has a dollar answer.
Questions about what it costs
- What each staffing line costs against your own dated rate cards, with benefit load and tuition remission included
- Whether external funding reduces a department's ask, as institutional policy rather than a spreadsheet formula
- Whether a plan is over its cap in dollars at submission, rather than in workload units
- Who has signed off on a costed staffing plan, through the dean, budget office and provost chain
- What exactly was approved, frozen as a snapshot that any live plan can be checked against
Most of the time, what PlanFoundry replaces isn't a competing product. It is the spreadsheet a department already keeps, and the hand reconciliation that follows it.
What the licence covers
The hard parts are already built, and staying current is included.
A licence buys a finished system, and keeps it current on a platform that does not stop moving.
A real permission and sharing model, an approval router you configure, and a snapshot layer any live plan can be reconciled against. These are the parts that take years rather than quarters, and they ship in the box.
Salesforce ships three platform releases a year, forever. Keeping up with them is part of the subscription, so a release never becomes a project on your side.
Where the product is headed.
Nothing below can be shown or dated today.
Phase 2: after a real institution is using this daily
- Self-service onboarding, so a new campus could set itself up without an engineer
Phase 3: connected to the rest of campus
- Real course and enrollment data from the student information system
- Real salaries and appointments from HR/payroll
- Checking what was planned against what was actually paid
- A feed to the general ledger, multi-year forecasting, and a supported public API