Meridian turns scattered tasks, threads and spreadsheets into one living plan. Move a date and everything that waits on it moves too — so the next two weeks are never a surprise to anyone on the team.
Projects
Q3 Platform
Mobile 4.0
Data residency
Pricing page
Views
Critical path only
Planning the quarter at 11,400 teams — from twelve-person studios to platform groups of four hundred
One source of truth
Most teams keep a board for the work, a document for the plan and a chat thread for the reasons. Meridian keeps one record and draws it as a timeline, a workload and a log, so there is nothing to reconcile on Monday.
Timeline
Dependencies are declared once. After that a slipped milestone pushes everything waiting on it, and the critical path redraws itself.
+1 wkReview ran long, so Build and Launch moved with it — nobody had to redo the dates.
Workload
Hours against a stated week, with time off read from the calendar.
Decisions
Baselines
Weeks against the 1 July baseline
Weekly update
On trackPermissions, onboarding, audit export
MovedBilling +2 wks — backfill agreed on the 14th
NextParity checks start Monday
Guests
Finance, legal, the client and the board can read the live plan and leave review comments without taking a seat — on every plan, in any number.
14reviewers on this plan
$0added to the bill
What happens when a date moves
In most teams a slipped date travels by rumour. In Meridian it travels along the dependencies, in under a second, to exactly the people it touches.
Rita drags the billing migration two weeks right and writes one line about why.
Parity checks and the search cutover move with it. Permissions does not depend on billing, so it stays put.
Six owners of affected work get one message each. The other forty people in the workspace get nothing.
Friday's report already says what moved, by how much, and the reason Rita gave on Thursday.
11,400
Teams planning in Meridian
2.3m
Milestones tracked to date
38%
Fewer status meetings, on average
99.98%
Uptime across the last four quarters
Reporting
Every Friday at eight, Meridian drafts the weekly update from the plan itself: what moved, why, what is next and whether the quarter still fits. Leads edit a sentence or two and send it. Stakeholders who want more open the live plan instead of asking for a meeting.
MovedBilling migration +2 weeks. “Backfilling historic invoices now costs two weeks; doing it in Q4 costs a quarter.” — R. Adeyemi
AheadOnboarding v2 started a week early after permissions reached staging on the 8th.
NextParity checks begin Monday. The quarter still fits, with four days of float left.
Fits what you run
Meridian reads status from where the work happens and writes dates back, so nobody updates two systems.
In their words
Leads, engineers and the stakeholders who used to chase them — on what changed when the timeline became the thing everyone reads.
We cancelled two status meetings a week. The timeline answers the question those meetings existed to ask.
Hana Lindgren
Head of Product, Copperline
The first week was uncomfortable. The plan was suddenly honest about how much we had committed to.
Owen Achebe
Engineering Director, Northglass
When a client asks why a date moved, I paste the decision. It has a date, a name and the trade we made.
Priya Ramaswamy
Delivery Lead, Arcade Labs
4h → 45m
Weekly reporting at Fieldnote, once the update started drafting itself
Firmware and the app finally sat on one plan. We found a six-week collision a whole quarter early.
Anders Vik
Programme Manager, Northglass
I stopped writing the Sunday-night update. That alone paid for every seat we have.
Leo Marchetti
Founder, Fieldnote
Ten minutes from now
Import the spreadsheet you already keep. No credit card, no sales call, no onboarding webinar — and the free plan stays free.
Q4 · drafted from your import