A lot of financial models are built to impress investors—but few are built to run a business. At Nexa, we’ve reviewed hundreds of spreadsheets and seen a consistent pattern: founders either overcomplicate or oversimplify. What they really need is a model that helps them answer real questions: Can I hire? Can I scale? When do I run out of cash?So here’s how we help companies build models that don’t just look good—but actually work.
Week 1–2: Start With Questions, Not Tabs
We begin by asking three key questions:
- What do you need this model to answer?
- Who will use it—and how often?
- Where are your current blind spots?
In this early phase, we define the model’s primary purpose (fundraising, internal planning, scenario stress-testing, etc.), identify key assumptions, and build around the real decisions that drive the business—not just a nice-looking P&L.
“We didn’t get a spreadsheet. We got a sharper way to think about our business.”
Week 3–6: Build Around What Drives the Business
This is where we get into the build—and where most teams go wrong.
Instead of packing the model with every metric under the sun, we help clients focus on a lean driver-based model. That means mapping growth to 2–3 key levers (CAC, retention, ACV, etc.), not 200 line items. From there, we layer in flexible assumptions, simple toggles for scenario planning, and clear outputs.
We also help teams structure models to match their internal logic, so they’re not dependent on us or anyone else to run it.
Week 7–12: Pressure-Test With Real Use Cases
We don’t call a model done until it’s been battle-tested.
This phase includes real-time applications:
- Hiring scenario walkthroughs
- Board meeting prep
- “What if” funding gap conversations
- Burn rate recalibrations
We refine based on how the team actually uses the model—not how it looked in the kickoff deck.
“The model helped us make a hiring call with confidence. It’s not just for investors anymore.”
After 90 Days: The Model Becomes a Living Tool
The best models evolve. They don’t get shelved.
We help teams create habits and structures to maintain, update, and trust their models month over month. That means clear ownership, lightweight documentation, and version control best practices. Some teams keep us on in an advisory loop—others fully own it in-house.
Either way, the model isn’t just a spreadsheet. It becomes a strategic engine.
