BA

Bear and Breakfast Financial Model

Bear & Breakfast is a sim/management adventure game with a focus on narrative and exploration.

Core loop: Build your cabin → manage guests and their cash → explore surroundings for rewards → repeat.

Two gameplay pillars:

1. Sim / Management - attract guests, manage stay quality vs. capacity, earn money, upgrade the cabin.
2. Adventure / Exploration - progress story of three characters (Hank, Gwen, Will) through quests, puzzles, and world areas around "Timberfall." Each unlocked area improves the cabin.

References cited as comparable titles: Stardew Valley, Night in the Woods, Theme Hospital.

Target audience: "Chill players" who prefer relaxed, funny, content-rich games with familiar themes and beautiful aesthetics.

• Primary: Premium game sale on PC (Steam implied) and at least 1 first-party console platform.
• Post-launch (stated in roadmap): Free content updates + Premium DLC.
• No price point, sales volume projections, platform revenue-share terms, or projected unit sales disclosed in the deck.

The only quantitative development stat is redacted by OCR artifact: "The prototype has been developed over roughly 0 months, by a team of 0 people, working part-time" - these are placeholder/redacted fields, not real zeroes.

No direct competitive analysis slide. Implied differentiation: combination of management sim depth (Theme Hospital-like), cozy narrative (Night in the Woods), and life/farming sim feel (Stardew Valley) - occupying a gap in "narrative simulation" games.

Moat described qualitatively: unique IP, strong visual identity, compelling pun-driven humor brand. No quantitative moat metrics.

• Team: Rares (Rick) Cinteza - Owner / Pun Designer (Gummy Cat Studio).. No team size or other members named publicly; prototype built by redacted headcount.
• Use of funds structure (categories disclosed, no figures):
• Development: Art, Programming, Design, Sound, Overhead
• Marketing: PR Support, Events, Online Advertising, Trailers
• Estimated over "XX months" (redacted). Cost breakdown available on request.
• Release target: REDACTED.
• Development timeline: MMYYYY placeholders for all six phases (Concept → Pre-Prod → Production → Pre-Launch → Launch → Support). Currently at Pre-Prod / Funding stage.

• Archetype + why: Indie video game project P&L / production budget model. This is a pre-revenue, pre-launch game seeking a one-time development grant or publishing advance. The right model is a *production budget + revenue waterfall*, not an operating forecast. It should track: total development spend by category, recoupment against projected unit sales, and post-launch DLC tail. Not a SaaS, marketplace, or recurring-revenue model. Not M&A.

• Forecast horizon & granularity:
• Pre-launch: Monthly cash spend by category from funding date through launch (unknown duration; assume 24–36 months typical for an indie of this scope).
• Post-launch: Annual for 3–5 years (launch year + support tail with DLC).

• Key drivers & assumptions:
• Development budget total: - redacted; must be provided by team. $300K–$700K range typical for 2–5 person indie over 2–3 years in Romania (lower cost base).
• Marketing budget: - redacted. 15–25% of development budget, consistent with mid-tier indie.
• Development duration: - redacted ("XX months"). 24 months from funding to launch.
• Launch platforms: PC + 1 console (simultaneous). Steam (PC) + Nintendo Switch or Xbox (console).
• Platform revenue share: 70/30 (Steam standard) for PC; 70/30 for console.
• Unit price: $14.99–$19.99 (Stardew Valley/cozy genre comparable).
• Unit sales - Year 1: 50K–200K units across all platforms (wide range given no wishlist/traction data).
• Unit sales - long tail: 20–30% of Y1 in Y2, 10–15% in Y3 (typical indie decay curve).
• DLC revenue: Premium DLC planned post-launch. 1–2 paid DLC packs at $4.99–$7.99; attach rate 15–25% of base owners.
• COGS / royalties: minimal direct COGS (digital); platform fee is primary cost of sale.
• Team headcount ramp: - redacted. 3–6 people (art-heavy indie; art is typically largest line item).
• Overhead: listed as a line item; office/tools/SaaS ~10–15% of total dev cost.
• Localization: mentioned as pre-launch and post-launch milestone. 3–5 languages at $5K–$15K each.
• Porting: listed. $30K–$60K per additional console port.
• Publisher advance (if applicable): model should accommodate a publishing deal where advance is recouped from revenue split, as an alternative to pure grant funding.

• Scenarios (Base / Bull / Bear - which variables flex):
• Base: 100K units Y1 @ $17.99, 24-month dev, $500K total budget.
• Bull: 250K units Y1 (breakout success, Stardew-like word-of-mouth), 1 DLC at 25% attach rate.
• Bear: 30K units Y1 (soft launch, niche), DLC revenue minimal, longer recoupment tail or write-off.
• Flex variables: unit sales volume, launch price, DLC attach rate, development duration (cost overrun), platform mix.

• Required sheets / outputs:

1. Production Budget - monthly spend by category (Art, Programming, Design, Sound, Overhead, Marketing sub-lines), total cash required, funding timeline.
2. Revenue Waterfall - gross unit sales × price → platform fee → net revenue → recoupment of advance/grant → developer share.
3. P&L Summary - per year: net revenue, COGS (platform fees), gross profit, operating costs (post-launch support team), EBITDA.
4. Cash Flow - monthly during development (burn rate, funding draw-down), quarterly post-launch.
5. Sensitivity Table - unit sales × price matrix showing breakeven and ROI at each scenario.
6. DLC Model - owner base × attach rate × DLC price → incremental revenue by title.