Tactical insights for first-time founders to outsmart the burn, the churn & the breakdown.

Hey Founder,

It’s budget season. You’re weighing a sales hire, a second product, an AI rollout, and a profitability target. Each sounds reasonable, and the numbers almost fit.

But which one gets the spotlight?

In a film, people share the frame, but the lead character carries the scene. Your budget needs that distinction too.

You can keep the business healthy, improve what’s working, and test promising ideas. You just can’t treat every part of the company as if 2027 is its transformation year.

This issue is about choosing the problem you’re paying to change in 2027, and making sure your money, people, and forecast support that choice.

Let’s dive in.

You can probably name the biggest problem in your business in one sentence. Yet budget season turns it into seven: sales capacity, retention, enterprise readiness, a second product, a new market, AI, and profitability.

Every request sounds reasonable. Approved separately, they fund several ambitions without choosing which one will drive the year.

You’re deciding which useful work gets enough money, people, and attention to make a difference.

That choice belongs on both sides of the budget. If growth depends on sales, the forecast needs the pipeline, capacity, and ramp time you’re funding. If it depends on retention, show what keeping customers contributes and what improving retention requires.

The budget explains how the business earns its results, not just what it spends.

Atlassian made that visible. Its early model let customers discover, try, and buy online rather than relying on a field-sales team. In fiscal 2015, about 44% of revenue was spent on R&D versus 21% on sales and marketing, supporting its product-led approach. 

When strategy changes, allocation should too.

At Salesforce, the shift was toward profitability. In January 2023, it announced restructuring to reduce costs and improve margins. In fiscal 2024, sales and marketing spending fell from $13.53 billion to $12.88 billion even as revenue grew 11%. The new target had a different spending plan.

Now say retention is your 2027 priority. Sales wants two reps, your CTO wants a second-product team, a prospect needs security work, and a board member asks about AI. Each gets funded.

But onboarding needs those engineers. By May they’re spread thin; by Q3 churn hasn’t improved. Nobody forgot retention. It just never got the people.

Meanwhile, your forecast still assumes retention improves, even after its capacity went elsewhere. You’ve funded one set of activities while forecasting the benefits of another. 

Your priority needn’t be the largest expense; much of the budget keeps today’s business running. But it must change who gets assigned, what gets funded, and what waits. 

As a CFO, I’ve seen startup budgets become contests over who makes the strongest case for their department. Leaders have targets to hit, so naturally they defend their resources. But trimming individual plans until the total fits is negotiating spending, not deciding what the business needs most.

Equal cuts don’t have equal consequences. Delay one hire and the revenue plan might barely move. Delay an implementation hire and signed customers could wait to launch, pushing billing and cash collection into the next quarter. The payroll saving is immediate; the cash delay shows up elsewhere.

Instead of ranking departments, ask which constraint each request removes.

What will it unlock, what will it cost, which teams does it depend on, and what work loses capacity if you fund it? What happens if it waits three months?

Revenue, savings, reliability, or reduced risk can all justify spending, but each has to outweigh what it displaces. 

Your stage should guide, not dictate, spending. A second product, enterprise sales, and international expansion might each have a strong case. But if you still can’t reliably win and retain current customers, funding all three adds complexity before the core can support it.

The opportunities can be good and the timing still wrong.

Your budget should fund the next stage of the business, not several stages at once. 

You can hit growth targets and end up with a harder business to run.

More customers may mean more custom onboarding, higher revenue may leave margins unchanged, and a bigger team may still depend on you for every important decision.

That’s why fixing onboarding, reducing rework, or removing founder dependencies can deserve budget ahead of another sales hire, even without a revenue target attached.

When deciding where to spend in 2027, don’t stop at “How much revenue will this add?”

Ask: “If this works, what becomes easier, more profitable, or more repeatable?”
A good budget makes the year after easier to grow. 

Choose one result your budget needs to deliver, not every improvement you’d like to make. For example: “Increase annual customer retention from 80% to 90% by December 2027.”

Define the baseline, target, period, and owner, then explain why this comes first: does it remove the constraint on growth, improve the economics, or unlock the next stage?

Use that to test each spending request. 

Review customers who left. Were they slow to launch, inactive after onboarding, or poorly matched to your product?

If onboarding repeatedly shows up, make the investment specific: “Assign one implementation specialist and six weeks of engineering time to fix setup steps delaying launches.”

Specify the owner, timing, and expected improvement. “Invest more in customer success” isn’t a fundable plan. 

Budget recruitment, salaries, tools, and external support when you’ll pay. Then model when improvements can affect customers and renewals.

If onboarding improves in September, which customers benefit, how much revenue is at stake, and when can you collect it?

Don’t forecast a full year of retention gains from a September fix or treat an assumption as a guarantee. Make the lag visible 

If onboarding and a second product need the same engineers, decide which comes first. Write it down: “The second-product pilot moves to Q4. These engineers stay on onboarding through June.”

Update spending and expected revenue together. Delaying work while keeping its benefits makes the forecast fiction.

Before approval, complete four lines:

Review these commitments quarterly, not just whether departments hit their budgets.

A founder asked in my onboarding survey:

I’d target 50–60% gross margin. 70–80% could be a longer-term ambition if delivery becomes repeatable, but AI doesn’t guarantee software-like economics.

A client count should be a checkpoint only:

Include implementation, testing, support, contractors, software, and AI usage in delivery costs. Track setup and recurring-service margins separately; a profitable build can hide underpriced support.

Compare each client’s price with actual delivery and support cost. Fix the biggest recurring gap first.

More clients should repeat the profit, not multiply the costs, especially overtime.  

Send it my way, just hit reply.

A few great reads this week:

Before you go…

Most 2027 plans will have a good strategy deck. Fewer will have a budget that pays for it.

Choose your main character while changing course is still a spreadsheet edit. Give it the people and money, keep the core healthy, and test the rest within limits. Tell your team what you’ve chosen.

Your budget should reflect your strategy.

That’s your real moat.

See you next Thursday,

— Mariya

Hit reply and let me know. I read every single one (for real).

1. Early stage? Start with one of my practical finance guides.
2. Stuck on something specific? Book a 1:1 and we’ll work through it together.
3. Past $2M ARR? Work with me and the team at FounderFirst to run your CFO function.

Hey, I’m Mariya, a startup CFO and founder of FounderFirst. After 10 years working alongside founders at early and growth-stage startups, I know how tough it is to make the right calls when resources are tight and the stakes are high. I started this newsletter to share the practical playbook I wish every founder had from day one, packed with lessons I’ve learned (and mistakes I’ve made) helping teams scale.

Mariya Valeva

Find me on LinkedIn