The Mobile App Studio P&L That Investors Never See

Every app studio has two P&Ls. The one in your pitch deck shows 15% operating margins — healthy, sustainable, fundable. The one in your bank account shows you're borrowing from next month to pay this month's bills.

This isn't hyperbole. It's an accounting fact rooted in how revenue recognition works for app store businesses. Accrual accounting — the standard under both UK GAAP and IFRS 15 — records revenue when it's earned, meaning the moment a user completes an in-app purchase. Cash-basis accounting records revenue when money arrives in your bank account. For most businesses, the gap between these two is days, maybe a week. For app studios receiving payouts through Apple's fiscal calendar and Google Play's monthly cycles, that gap stretches to 33–63 days. And that gap changes everything about how your studio's financial health actually looks.

This matters if you're a founder preparing a board deck. It matters if you're a CFO trying to explain to investors why a profitable company needs external financing. It matters if you're making any financial decision based on a P&L that only tells half the story.

The accrual P&L: what investors see

Here's a monthly P&L for a mid-size app studio — call it "GameFlow." Eight people, a portfolio of casual games generating roughly £115,000 in gross revenue per month, mostly through iOS IAP and subscriptions. After Apple's 30% commission, net payout lands around £80,500 per month.

Monthly P&L (Accrual Basis) — Studio "GameFlow" (illustrative)

Gross Revenue (in-app purchases + subs)    £115,000
  Less: Apple/Google commission (30%)      -£34,500
Net Revenue (payout equivalent)             £80,500

Operating Expenses:
  Payroll (8 FTEs)                         -£36,000
  UA / Marketing                           -£22,000
  Server & Infrastructure                   -£4,500
  Tools & Services (MMP, analytics, etc.)   -£3,500
  Office & Admin                            -£2,000
Total Operating Expenses                   -£68,000

Operating Profit                            £12,500
Operating Margin                              15.5%

On paper, this looks strong. 15.5% operating margin. Profitable. Sustainable. Growing. This is the P&L that goes into the investor deck, the board report, the annual tax filing. Every line item is real. Every number is accurate. And every number is misleading.

The £80,500 in net revenue? Earned this month. Arriving in your account 33–63 days from now. The £68,000 in expenses? Due this month. Payroll hits on the 1st. Servers bill on the 1st. UA invoices are net-7 or net-14. The P&L records them in the same period. Your bank account does not.

The cash-basis reality: what your bank account knows

Same studio. Same month. Same numbers. But mapped to when cash actually moves.

Week-by-Week Cash Reality — GameFlow, March 2026

Week 1 (1–7 March):
  Cash IN:   £0 (Apple payout from January period expected ~15th)
  Cash OUT:  -£36,000 (payroll, due 1st)
             -£4,500 (servers, monthly billing cycle)
             -£2,000 (office, admin, insurance)
  Net:       -£42,500
  Running balance: Starting £25,000 → -£17,500

Week 2 (8–14 March):
  Cash IN:   £0 (still waiting)
  Cash OUT:  -£5,500 (UA — cut from £11,000 target; cash too low)
             -£3,500 (tools — MMP annual billing, split monthly)
  Net:       -£9,000
  Running balance: -£26,500

Week 3 (15–21 March):
  Cash IN:   +£80,500 (Apple payout arrives)
  Cash OUT:  -£16,500 (UA — ramping back to full budget)
  Net:       +£64,000
  Running balance: +£37,500

Week 4 (22–31 March):
  Cash IN:   £0 (Google payout may arrive late month)
  Cash OUT:  -£12,000 (remaining UA + miscellaneous)
  Net:       -£12,000
  Running balance: +£25,500

The accrual P&L said +£12,500 profit, 15.5% margin. The bank account said: two full weeks in negative territory, credit card carrying £26,500, UA budget cut by 50% during the highest-intent acquisition window, and the founder wondering if payroll will clear.

The studio is profitable. The studio is also cash-negative 50% of the time.

This isn't mismanagement. It's the mathematical consequence of expenses following a standard calendar — payroll on the 1st, billing cycles on the 1st and 15th — while revenue follows Apple's fiscal calendar, with payouts arriving around the 15th of the following month. The expense timeline and the revenue timeline are structurally misaligned, and no amount of operational discipline fixes that.

Revenue recognition: the gap that accounting hides

For the finance-oriented reader, here's the technical mechanism behind this disconnect.

Under accrual accounting, revenue is recognised when the performance obligation is satisfied — for app studios, that's when the user completes a purchase or when a subscription period elapses. Cash receipt is irrelevant to recognition timing. A user buying a £4.99 item on March 3rd generates recognised revenue on March 3rd, even though Apple won't release that cash until late April or early May.

For subscription apps, this creates a continuous stream of daily accrued revenue. For IAP-heavy games, it creates lumpy recognition that follows user behaviour. In both cases, cash receipt lags by 33–63 days depending on where the transaction falls within Apple's fiscal period.

The result: at any given point, your studio holds 4–8 weeks of confirmed, recognised, already-in-your-P&L revenue that hasn't yet converted to cash. You can calculate the exact amount frozen in transit:

Frozen Working Capital = Monthly Net Payout × (Average Delay Days ÷ 30)

For GameFlow: £80,500 × (45 ÷ 30) = £120,750 permanently frozen in the payout pipeline. That's £120k of earned revenue that exists on the P&L but not in the bank. At any moment. Every month.

We calculated the exact cost of this delay for three studio sizes →

The hidden costs that never appear in the P&L

The frozen capital isn't just an accounting abstraction. It generates real costs that compound over time — costs that never show up on the accrual P&L because they're consequences of timing, not operations.

Credit card interest. GameFlow uses a business credit card to cover Weeks 1–2, carrying an average balance of £30,000 for roughly 15 days each month. At a typical UK business card APR of 24%:

£30,000 × 24% × (15 ÷ 365) = £296 per month = £3,552 per year

This is a direct, recurring cost of the cash timing gap. It reduces effective operating margin from 15.5% to roughly 15.1%. Small — but real, and cumulative.

Suppressed UA spend. In Week 2 of the cash flow example, GameFlow cut UA from the planned £11,000 to £5,500. That's £5,500 in foregone spend during a single week. At a conservative 2x D180 ROAS (return on ad spend measured at 180 days), that £5,500 would have generated £11,000 in future revenue.

Over 12 months, these weekly UA gaps add up to roughly £66,000 in suppressed spend, representing approximately £132,000 in unrealised future revenue. That's before compounding effects — the installs you didn't acquire don't generate the organic uplift, the improved app store rankings, or the word-of-mouth referrals that paying users produce.

Opportunity cost of intermittent UA. Platform algorithms — Apple Search Ads, Meta, Google UAC — optimise delivery based on spend continuity. Pausing and restarting campaigns weekly forces the algorithm to re-enter learning phases, degrading targeting efficiency. Studios running continuous UA at steady budgets typically see 15–25% higher efficiency (lower CPI, better ROAS) compared to studios running the same total budget in start-stop patterns. Over 12 months, this translates to a meaningful install base gap.

Management overhead. The founder or CFO spends 3–5 days per month managing the cash gap — juggling credit card balances, prioritising vendor payments, renegotiating terms, manually throttling UA. That's time not spent on product development, partnerships, or strategic planning.

The accrual P&L says 15.5% margin. After credit card interest, suppressed UA, algorithm inefficiency, and management overhead, the real effective margin is closer to 8–10%. Nobody reports it this way because accrual accounting isn't designed to capture timing costs.

The full anatomy of this cash trap and why it hits harder the faster you grow →

What this means for fundraising

If you're building an investor deck, you've almost certainly presented the accrual P&L. It's correct, it's standard, and it tells a story of a healthy business. The problem arises when investors — especially those unfamiliar with app store payout mechanics — draw conclusions about capital needs from that P&L.

"If you're profitable at 15% margin, why do you need financing?" is a question every app studio founder has heard. The answer is structural: you need financing not because the business is failing, but because the market's payout mechanics create a permanent gap between when you earn and when you receive.

This isn't a weakness unique to your studio. It's an industry-wide structural feature that affects every developer on the App Store and Google Play. The studios that handle it well aren't necessarily more profitable — they've simply found a way to bridge the timing gap without destroying UA continuity or loading up on expensive credit.

The credible move: present both P&Ls in your board deck. Show the accrual view for performance, and the cash-basis view for capital planning. Investors who understand the difference will respect the transparency. Those who don't will learn something about the industry they're investing in.

Closing

The P&L that investors see and the cash flow reality your bank account knows are two different financial stories about the same business. The gap between them isn't a signal of poor management — it's a structural feature of app store economics, created by the 33–63 day delay between earning revenue and receiving it.

The studios that thrive long-term aren't necessarily the most profitable on paper. They're the ones that manage the cash timing gap without sacrificing growth. Whether that means building reserves, securing credit, or bridging with factoring — the approach matters less than the awareness that the gap exists and is costing you more than you think.

We built a financial model specifically for app studios — 6 tabs, 12-month projection, 3 scenarios side by side. Download it free → App Studio Financial Model

This is the problem Amps33 was built to solve. One advance, one fee, your account. See how it works →