The standard FP&A rollout is six to twelve months. Some are longer. Almost none are shorter. The reflex is to assume this is because the software is complex.
It isn't, mostly. The complexity is real, but it's not what's eating the calendar.
What's actually inside that timeline
If you sit with a few rollouts and add up where the months go, the same pattern shows up. A small slice of the time is genuine engineering: configuring the data model, wiring the integrations, building the custom reports. The rest is handoff tax.
Sales hands you to implementation. Implementation hands you to a third-party partner for the things implementation doesn't do. Your in-house team handles the parts neither of them will touch. Every transition is a re-explanation, a scoping doc, a follow-up meeting, a week of slack.
The reason rollouts take quarters is that there are usually three or four companies sitting between you and the person who can actually change something.
Each handoff is rational on its own. Together, they are most of the timeline.
What we cut
We collapsed those handoffs into one team. The people who built Novaplan are the same people who configure it for you. There is no implementation partner. There is no support tier. The person hearing your hierarchy question on Tuesday is the person shipping the change on Wednesday.
That sounds like a staffing decision. It's actually a tooling decision, which is the part most teams miss. The reason small teams couldn't operate this way historically is that the configuration work was slow. Custom modules, bespoke reports, integration changes - each was multi-week effort by hand.
That changed in the last 18 months. AI-assisted engineering is now fast enough that a single technical operator can ship custom configuration in days. We don't talk about it as "AI in the product" - we use it where it actually compounds, which is in how quickly we can shape the product to your team. It's the difference between renting consultant hours and owning a build pipeline.
The number we publish
From signed contract to live and configured.
Your GL, hierarchy, planning cycle, and the reports your CFO actually reviews. Most platforms still quote quarters.
That's not a marketing number. It's the operating constraint we hold ourselves to. If we can't get there in that window, the model is broken and we want to know it. So far the math has held.
If your team has been quoted "Q3" or "next year" by a vendor, the gap between that and 14 days isn't because they're being careful and we're being reckless. It's because the work they're describing is mostly the gap between three companies, and we removed it.