Delivery as operational records
Portfolios, plans, resources, progress, and cost control on the same engines as Finance and Materials — budgets measured against real commitments, not spreadsheet hope.
Active project
Harbor Expansion — Phase 2
Budget
$4.2M
Committed
$3.96M
Variance
−6%
Work packages
Seat-based PM pricing was designed for the vendor. Projects prices the module.
Most PM tools charge you more every time you add a planner, controller, or sponsor. Projects charges for the delivery system — not a tax on every person who needs visibility.
Monthly cost vs active users
Their bill climbs. Yours steps with complexity.
At 120 users
$1640/mo
Typical seat PM
At 120 users
$299/mo
Fyboard Projects (Growth)
Visibility for sponsors should not multiply your software tax.
See pricingEight capabilities. One delivery record.
Everything in the Products mega-menu — Delivery, Organization, Control, and Evaluate — wired to the same projects, permissions, and audit trail.
Delivery
Plans and progress against the live schedule
Organization
Portfolios and the people who deliver them
Control
Cost against commitments, evidence on the record
Evaluate
Compare and price the module
Propose to close. One record.
Every stage reads and writes the same project — so planning, progress, cost, and documents never drift into parallel truths.
Plan
Schedule with a baseline
Publish versions, lock a baseline, and keep variance readable — planning lives on the same packages you will execute.
- Work packages & activities
- Schedule versions
- Baseline freeze
- Calendar & cockpit
Schedule · Baseline v3
Three surfaces that stay on one record.
Planning, progress, and cost — the trio most teams reconcile in three tools. Projects keeps them wired together.
Planning
Schedule versions and baseline variance on the same packages you execute — not a sidecar Gantt file.
- Baseline freeze with history
- Package-level variance
- Calendar & activity cockpit
Why project tools lose the plot
Standalone PM software is great at charts. It is weak at being the system of record your finance and ops teams already trust — so delivery stays a reconciliation job.
The spreadsheet plan
Schedules live in one file, budgets in another, and status in a slide deck. None of them agree by Friday — and nobody can say which one is authoritative.
Cost without commitments
PM tools track estimates. Finance tracks invoices. Materials tracks POs. The gap between them is where overruns hide until it is too late to course-correct.
Delivery as a silo
People, materials, and contracts sit elsewhere. Project “truth” is reconstructed in meetings instead of read from the same operational records the org already trusts.
Status as performance
When progress is a narrative, sponsors get the version that fits the room. Exceptions surface late. Audit asks for evidence that was never attached to the work.
Cost control against real commitments
Most PM tools stop at estimates. Projects reads the commitments your org already booked — so delivery and finance argue about one number.
Explore cost control- Budget versions that survive reforecasts
- Commitments from Finance and Materials — not copy-pasted estimates
- Variance that operators and controllers can both trust
- Same permissions and audit trail as the rest of Fyboard
Not another PM island.
Projects runs on Fyboard’s shared engines — permissions, audit, documents — and reads the modules delivery already depends on.
Built for every altitude.
PMO, delivery, finance, and sponsors — reading different views of the same operational records.
PMO lead
Running a portfolio of 40+ initiatives
- Portfolio and program rollups from live project state
- Baseline variance across the book of work
- Exception surfacing before the quarterly review
- Consistent governance without a second PPM stack
- Evidence attached where the work already lives
The boring parts we obsess over.
Delivery data sits next to money and people. Projects inherits the same permission and audit posture as the rest of Fyboard — not a lighter sidecar.
RBAC
Granular roles — PMO, delivery, finance, sponsors — scoped to the projects they own.
Audit trail
Every budget change, status update, and baseline freeze. Who, when, why — immutable.
Shared engines
Permissions, Workflow, FyDrive, and FlexField — the same platform under every module.
Encryption
AES-256 at rest, TLS 1.3 in transit — project records treated like the rest of Fyboard.
Row scoping
Operators only see the portfolios and projects their grants allow. No drive-wide leaks.
SOC 2 track
Active SOC 2 readiness with the same controls that protect contracts and people data.
Price the module, not the seat tax.
Starter for day-to-day delivery. Growth when sponsors need rollups and finance needs commitments. Enterprise when scale demands it.
Starter
Core projects, planning, and progress
- Projects & work packages
- Planning & baselines
- Progress tracking
- Documents on the record
Growth
Portfolios, resources, and cost control
- Everything in Starter
- Portfolios & programs
- Resource capacity & bookings
- Cost vs commitments
Enterprise
Custom limits, SSO, dedicated support
- Everything in Growth
- SSO & advanced grants
- Custom limits
- Dedicated support
Questions teams ask first.
Records, cost, and how Projects sits with the rest of Fyboard — the answers sponsors and controllers usually need before a pilot.
Projects is Fyboard's delivery and cost-control module. Portfolios, plans, resources, progress, budgets, and documents are operational records on the same engines as Finance, Materials, and People — not a standalone PM silo.
Cost control measures budgets against real commitments that Finance and Materials already know — not spreadsheet estimates that drift from the ledger.
It can. Many teams start with planning and progress, then pull cost and documents onto the same project records so sponsors, ops, and finance stop reconciling three systems.
Projects shares permissions, audit, documents, and people with the platform. Cost and materials link into Finance and Materials when those modules are live for your org.
We price the module by complexity — Starter for core delivery, Growth for portfolios/resources/cost control, Enterprise for SSO and custom limits — not a per-seat tax every time a sponsor needs visibility.
Visibility is permissioned on shared engines. Unlike seat-based PM tools, opening the record for a sponsor or controller is not designed to multiply your bill with every viewer.
Artifacts and transmittals attach to the project record, with lineage into FyDrive and AlphaCore when a canonical contract or file home is required.
Projects is in development on the Fyboard platform. Join the waitlist for early access, or sign in on non-production environments when your org has module access.
Run delivery on records, not decks
Portfolios, plans, resources, and cost control — one module, shared with the rest of Fyboard.
- Records-first delivery
- Cost vs commitments
- Shared platform engines