If you have shopped for FP&A software in the last two years, you have felt the market pull you in two directions at once. One set of tools wants you to keep your spreadsheets and add intelligence onto them. The other wants you to leave spreadsheets behind for a real planning platform. Both pitches are honest, both are incomplete, and the gap between them is exactly where most mid-market teams live.
Tier one: the Excel-adjacent tools
Datarails, Cube, and Vena start from a true observation: your team already knows Excel, and the model already exists. So they keep the spreadsheet as the working surface and put a database, version control, and automation behind it. Adoption is genuinely easy, because nobody has to learn a new modeling paradigm on a deadline. The catch is that you inherit the spreadsheet's ceiling along with its comfort. The logic still lives in cells, and once the model gets complex enough, the same fragility you were trying to escape comes back, now with a sync layer on top. These tools buy a lean team real time. They do not change what the model fundamentally is.
Tier two: the planning platforms
Anaplan, Workday Adaptive Planning, Pigment, and Planful sit on the other side. They replace the spreadsheet with a purpose-built environment where the logic lives in a model, not in cells. The structure scales, the audit trail is real, and the ceiling is much higher. The cost is the one every buyer underestimates: getting the platform to reflect your business is a project, not a setup step. The model has to be built from your GL and your hierarchy up, and the configuration tends to live either in the vendor's templates or in a specialist you hire to speak the platform's language. You trade the spreadsheet's ceiling for an implementation and a standing dependency.
Mid-market teams do not want the spreadsheet's ceiling or the platform's implementation tax. They want the depth without the project.
The gap in the middle
Here is the position almost no vendor sells to directly. A company doing fifty to five hundred million in revenue usually has genuinely platform-shaped needs: multi-entity structure, headcount that drives most of the cost, a board that wants real scenarios. What it does not have is a spare quarter for implementation or a modeler to keep on staff. So it ends up choosing between a tool it will outgrow and a platform it cannot fully operate, and most teams pick the one whose pain arrives later.
What actually closes the gap
The gap closes when the configuration work moves off your team without moving to a consultant. That is the idea behind the Service-as-Software model, and it is how Novaplan is built: the same team that writes the platform configures it to your GL, hierarchy, and planning cycle, and ships that in days or weeks rather than quarters. You get platform-grade depth, and the fit work stays with the people who built the thing. The point is not that the other two tiers are wrong. It is that the mid-market gap between them was never a tooling problem. It was a question of who does the work.
If your shortlist currently forces that trade-off, it is worth seeing what the middle looks like on your own numbers.