Budgeting and FinOps for Start-ups ================================== Slide 1: Budgeting and FinOps for Start-ups Narration Anna: [upbeat] Welcome to our deep dive into budgeting and FinOps for Sarah's start-up. Greg: We're here to prove that disciplined cost management can coexist with ambitious product roadmaps. Anna: Think of this session as a playbook for stretching every credit without throttling innovation. Greg: And we promise to keep it tactical—no enterprise finance jargon required. On-screen text Budgeting and FinOps for Start-ups Stretch every credit while protecting runway Slide 2: Session objectives Narration Anna: [curious] First, let's anchor what participants should walk away with. Greg: They need a FinOps mindset sized for fewer than 50 people, not a Fortune 500 bureaucracy. Anna: We also connect tooling spend directly to runway conversations so finance, product and investors see the same numbers. Greg: Finally, everyone practices spotting optimisation levers before renewals lock in waste. On-screen text Session objectives - Understand FinOps principles tailored to sub-50 person teams. - Translate infrastructure and tooling spend into runway scenarios. - Build a cadence for monitoring usage and renegotiating credits. Slide 3: FinOps mindset in the first 24 months Narration Anna: [thoughtful] A FinOps mindset in year one starts with acknowledging cash is your scarcest resource. Greg: Exactly—so we lay out guardrails before Sarah automates every workflow or signs annual commits. Anna: Documenting cost taxonomy sounds dull, but it stops engineering and finance from arguing over which budget a new tool hits. Greg: And those living forecasts? They're the proof investors need that the team is steering spend deliberately. On-screen text FinOps mindset in the first 24 months - Cash is the constraint; design guardrails before scaling automation. - Align product, finance and engineering on a single cost taxonomy. - Document who owns pricing decisions for each platform or vendor. - Treat forecasts as living artefacts reviewed with investor updates. Slide 4: Mapping cash runway with tooling Narration Anna: [analytical] When we map runway, we anchor on a simple burn formula that everybody can recite. Greg: Then we separate must-have spend from experiment budgets so product bets don't quietly cannibalise payroll. Anna: Calling out contractual cliffs keeps Sarah from being surprised by auto-renewals or seat minimums. Greg: And the shared dashboard keeps stakeholders aligned on which customers and features actually drive the bill. On-screen text Mapping cash runway with tooling - Start with burn formula: (opening cash - committed spend) ÷ monthly burn. - Categorise costs into keep-the-lights-on vs. experiment budgets. - Highlight contractual cliffs: annual renewals, seat minimums, auto-renewals. - Use a shared dashboard to show spend per customer or feature flag. Slide 5: Making cloud credits last Narration Anna: [energised] Credits can feel like free money, but the expiry dates creep up fast. Greg: That's why we inventory every cloud provider perk and match workloads carefully. Anna: Low-risk environments soak up those credits first while we tune rightsizing and scheduling tactics. Greg: Budget alerts at 60, 80 and 100 percent stop panic fire drills by catching drift early. On-screen text Making cloud credits last - Catalogue every provider credit, expiry date and eligible workloads. - Deploy credits to low-risk environments first (sandbox, QA). - Set budget alerts at 60/80/100% of expected usage to course-correct. - Pair credits with optimisation tactics: rightsizing, scheduling shutdowns, spot usage. Slide 6: Tooling usage monitoring toolkit Narration Anna: [practical] Monitoring usage is the boring hero work that keeps costs tame. Greg: Centralising billing exports means Sarah stops copy-pasting invoices at midnight. Anna: Tags and labels turn raw bills into insight—suddenly you know the growth team triggered last month's spike. Greg: Weekly digests and variance triggers create a rhythm so nobody is surprised by the finance meeting. On-screen text Tooling usage monitoring toolkit - Centralise billing exports in a warehouse or spreadsheet. - Instrument services with tags/labels for team, feature and environment. - Automate weekly cost digests to Slack/email for accountable owners. - Trigger lightweight reviews when variances exceed 15% week-on-week. Slide 7: Monthly stack spend drill Narration Anna: [engaging] Here's the concrete spend drill we run in workshops. Greg: Learners see how credits offset AWS bills, while cash still flows to collaboration, monitoring and support tools. Anna: The contingency line normalises setting aside 10 percent for surprises instead of hoping they never happen. Greg: We deliberately show the total cash outlay so teams link the numbers back to runway, not just accrual accounting. On-screen text Monthly stack spend drill Tool / ServiceSeat or usage assumptionMonthly cost (AUD) Google Workspace Business Standard12 seats @ $11$132 AWS compute & storageForecast 450 credits, 70% burn$0 (credit drawdown) Datadog monitoring3 engineer seats @ $27$81 Customer support platform6 agents @ $20$120 Contingency / experiment buffer10% of baseline$33 Total cash outlay$366 (credits cover $150 value) Slide 8: Workshop instructions Narration Anna: [directive] During the exercise, we ask each team to clone the drill with their own stack assumptions. Greg: As they tweak seat counts and usage, the guardrails force trade-offs—keep the SOC tool or hire a contractor? Anna: The optimisation lever per tool becomes an action list for the next quarter. Greg: It also builds muscle memory for renegotiating or automating before the finance team has to step in. On-screen text Workshop instructions - Duplicate the drill with your own stack and contract terms. - Adjust assumptions until your cash outlay stays within guardrails. - Identify one optimisation lever per tool (renegotiate, downgrade, automate). Slide 9: Guardrails & red flags Narration Anna: [cautionary] We also spotlight the red flags Sarah will meet in real life. Greg: Multi-year deals feel flattering, but at pre-Series A they usually mortgage optionality. Anna: Auto-renewals are sneaky, so we model calendar holds as part of the FinOps ritual. Greg: And when founders ignore chargeback data, they lose credibility fast with both finance leads and investors. On-screen text Guardrails & red flags - Vendor pushes multi-year deal before product-market fit—counter with quarterly. - Usage spikes without revenue signal? Pause automation rollouts immediately. - Silent auto-renewals: set calendar holds 60 days prior to renewal dates. - Founders ignoring chargeback data erodes trust with finance and investors. Slide 10: Linking to investor conversations Narration Anna: [confident] All this work feeds directly into investor conversations. Greg: Monthly scorecards show spend versus forecast and how many credits remain, signalling control. Anna: When Sarah can say "rightsizing bought us two extra months of runway," the room pays attention. Greg: Inviting observers to FinOps reviews turns a potential grilling into a collaboration ahead of the next raise. On-screen text Linking to investor conversations - Share FinOps scorecard in monthly updates: spend vs. forecast, credits remaining. - Demonstrate how optimisations extended runway (e.g., +2 months from rightsizing). - Use variance explanations to reinforce control over GTM and product strategy. - Invite observers to quarterly FinOps reviews to build confidence pre-Series A. Slide 11: Action plan for Sarah Narration Anna: [motivating] We close with an action plan Sarah can run immediately. Greg: Weekly cost reviews with engineering and finance build the drumbeat. Anna: The central ledger for credits, renewals and owners stops information from living in someone's inbox. Greg: Revisiting guardrails at each funding milestone keeps FinOps aligned with the pace of growth instead of blocking it. On-screen text Action plan for Sarah - Stand up a weekly cost review ritual with engineering and finance partners. - Build a central ledger for credits, renewals and owner accountability. - Pilot the monthly spend drill with leadership, then cascade to team leads. - Revisit guardrails each funding milestone to stay aligned with growth.