How grant-dependent is your runway—and what would you do in the next 90 days if support stopped?

Updated Jun 2026, the “zombie startup” debate has landed in Singapore as a finance problem, not a moral one: too many teams can show activity, pitch decks, and even revenue—but can’t show customer-funded runway. Jeremy Foo’s near-shutdown story resonated because it reflects a common pattern: late pivots, Enterprise Singapore support, and peer help can keep a company alive, but they don’t automatically make it resilient. If you want Singapore startup resilience going into a tighter 2027 climate, the practical question is how much of your survival is funded by customers versus subsidies—and what breaks first when timing, conditions, or reimbursements shift. This guide gives founders a 60–90 minute resilience audit to quantify dependency, stress-test cashflow, and commit to a clear 30/60/90-day plan.

What does a “zombie startup” look like in numbers (without the moral judgement)?

The whisper-network label tends to be emotional: “grant-chasing”, “overhyped”, “not real”. It’s more useful to define it operationally.

A company becomes zombie-like when it can stay busy but cannot self-fund progress. You see it in these numbers:

• Runway composition is mostly non-customer sources (grants, founder loans, one-off windfalls).
• Revenue exists but doesn’t extend runway (low gross margin after delivery costs, heavy discounting, high churn).
• Cashflow timing is fragile (reimbursements, milestone-based payments, slow collections).
• Decision-making is delayed because the next tranche/claim is “around the corner”.

A practical definition you can use internally

Use a two-part threshold (choose your own numbers, but be consistent):

1. Customer-funded runway %: how many months of runway are funded by recurring/repeatable customer gross profit (not bookings, not invoices) versus subsidies and one-offs.
2. Cash conversion realism: whether your cash cycle (collections, inventory, payment terms) is stable enough that planned runway is actually usable.

This framing avoids grant-bashing. Grants can be a sensible accelerator in Singapore, especially for capability building. The risk is treating non-recurring financing as if it is recurring operating income.

If Jeremy Foo’s story felt familiar, it’s likely because the near-shutdown moment usually comes from timing and conditions: reimbursement delays, claims disallowed, milestone slips, or a customer pushing payment out by 30–60 days. Those are solvable—if you measure them early.

Can you run a 60–90 minute resilience audit of your runway composition?

Yes—if you keep it narrow. Your goal is not a perfect model; it’s a decision-grade snapshot.

Step 1 (15 minutes): Build a simple “runway sources” table

In a spreadsheet, list the last 6 months and next 6 months (or next 9 if you can). Create these columns:

• Cash in bank (opening)
• Customer cash-in (collections, not invoices)
• Customer cash-out (COGS, delivery, fulfilment costs tied to revenue)
• Operating expenses (payroll, rent, tools)
• Debt servicing (if any)
• Grant cash-in (by programme)
• “Other cash-in” (equity, founder loans, one-off rebates)
• Cash in bank (closing)

Keep it cash-based. If you only have P&L, use bank statements to approximate collections.

Step 2 (20 minutes): Classify every grant like a financing instrument

Treat grants as non-recurring financing with conditions.

Create a mini-register with:

• Grant/programme name
• Purpose: capex (equipment, systems) vs opex (wages, consultancy)
• Disbursement: reimbursement vs upfront/milestone-based
• Claim frequency and typical processing time (based on your experience)
• End date / final claim date (if applicable)
• Conditions that can reduce payout (scope changes, documentation gaps, vendor eligibility)

Why this matters: reimbursement-type grants create a hidden working-capital requirement. The “support” only arrives after you’ve already paid suppliers/staff.

Step 3 (15 minutes): Calculate your “runway composition” metric

Define two runway figures:

• Total runway (months) = cash balance / net monthly burn (include realistic timing)
• Customer-funded runway (months) = cash + expected collections-funded net operating cashflow excluding grants / burn

Then compute:

• Customer-funded runway % = customer-funded runway months / total runway months

A company can have 12 months total runway and still be fragile if only 2–3 months are customer-funded.

Step 4 (10 minutes): Set a target glidepath (not a purity test)

A practical goal is not “zero grants”. It is a glidepath to majority customer-funded runway.

Example targets founders use:

• Next 90 days: move from 20% to 35% customer-funded runway
• By mid-2027: sustain 60%+ customer-funded runway for 2 consecutive quarters

Your targets should reflect your sector. Deeptech and regulated industries may reasonably use longer support runways—but still need explicit dependency tracking.

Step 5 (10 minutes): Decide what the audit changes this quarter

If the metric doesn’t change any decisions, it’s just reporting. The audit should force one of these:

• Reduce burn (cost actions)
• Improve cash conversion (collections/terms actions)
• Increase gross profit (pricing, delivery cost, product mix)
• Secure financing (planned, not reactive)
• Re-scope grant usage (capability building vs payroll survival)

This is where stories like Jeremy Foo’s become useful: near-shutdowns usually happen when teams postpone the decision until after the next claim or next pitch. The audit’s purpose is to decide earlier.

How should you model Enterprise Singapore grants so they don’t distort runway?

Enterprise Singapore support (and other public support) can be a strong tool—but only if you model it with the same discipline you apply to customer contracts.

Treat grants as “conditional cash”, not revenue

In management reporting, separate:

• Operating performance: customer gross profit and operating expenses
• Financing: grants, equity, loans

Even if accounting standards may present some grants differently depending on facts, your management view should keep the operating engine visible.

Build two runway views: “with grants” and “without grants”

Use three forecast cases:

1. Base case (with grants as scheduled)
2. Delay case: shift grant cash-in 60–90 days later
3. Downside case: assume 20–40% of expected grant cash-in does not arrive (disallowed costs, scope change, missed milestone)

You’re not predicting failure; you’re pricing the operational risk of conditions and paperwork.

Put end-dates and conditions into your calendar

Common execution failures are operational:

• Claim documentation compiled too late
• Vendor invoices missing required details
• Staff time allocation not evidenced (where required)
• Scope drift that makes costs ineligible

Create a simple owner-and-deadline sheet:

• Claim owner (one person)
• Monthly evidence checklist (invoices, timesheets, deliverables)
• Internal cut-off date (e.g., 10 working days before submission)
• “Funding impact” if missed (months of runway at risk)

If you want this to be lightweight, assign it to your finance lead/outsourced accountant with a monthly 30-minute review. Paul Hype Page & Co. often supports founders by turning grant cashflows into a forecast that management can actually run weekly—without drowning teams in admin.

Avoid the hidden trap: using grants to carry recurring payroll without an exit plan

Using support to hire can be rational—until the grant ends and the headcount becomes “permanent burn”.

A practical control is to tag each grant-funded hire or cost line with:

• Funding end month
• Replacement plan: customer gross profit, price increase, role redesign, or planned redundancy (with lead time)

This keeps people decisions humane and planned, rather than last-minute.

What cashflow disciplines prevent a “near-shutdown week” in Singapore?

In Singapore, many early-stage companies fail not on annual profitability but on timing: GST timing, reimbursement timing, B2B payment terms, and customer concentration.

A weekly cash forecast that a founder will actually use

You need a 13-week cash forecast (rolling), updated weekly. Keep it simple:

• Starting cash
• Expected collections by week (top 10 customers individually)
• Payroll dates (including CPF)
• Rent/major fixed costs
• Supplier payments (top 10)
• Tax/GST instalments where relevant (don’t guess—use your accountant’s schedule)
• Grant-related payments and expected receipts (separate)

Rules that make it useful:

• No “lump sums”: if you can’t name the customer and invoice, it doesn’t go in.
• Collections probability: tag as 90% / 50% / 10%.
• Red flag line: minimum cash buffer (e.g., 6–8 weeks of payroll).

Use two operating metrics: burn multiple and cash buffer

• Burn multiple (practical version): net cash burn / net new gross profit (or net new ARR gross margin). If you’re burning $4 to add $1 of gross profit, you may be scaling a leak.
• Cash buffer (weeks): cash / weekly fixed outflows (payroll + rent + core tools). This prevents the “we thought we had runway” surprise.

Fix collections before you chase growth

For many Singapore B2B companies, the biggest lever is not marketing—it’s payment terms and collections.

Actions that work in practice:

• Move from net-60 to net-30 for new customers; trade discounts for faster payment only if it’s cheaper than your financing cost.
• Bill monthly in advance where service allows.
• Add milestone billing that matches your delivery cost curve.
• Put a senior owner on the top 10 receivables call list weekly.

If you sell to larger enterprises, slow payment can be “normal”. Your resilience plan should assume it continues—and price your contracts accordingly.

Don’t confuse invoicing with cash

Founders often feel safer after a strong invoicing month. The bank balance doesn’t. In a tightening funding climate, liquidity is strategy.

How do you run a unit economics truth test that cuts through revenue vanity?

When founders say “we have revenue”, the next question is: does that revenue fund survival?

The minimum gross margin test (fully loaded)

Compute gross margin after fully loaded delivery costs, not just direct costs.

包括：

• Direct labour to deliver (including founders if they are doing delivery)
• Contractor costs
• Hosting/usage costs tied to customers
• Customer support time
• Implementation/onboarding costs

For productised services, many teams undercount delivery time, especially when grants subsidise capability building. The result is “revenue” that doesn’t extend runway.

Build a contribution margin view per product/customer segment

Create a simple table:

• Average price per month / per project
• Fully loaded delivery cost
• Contribution margin
• Cash timing (days to collect)
• Churn / repeat rate

Then ask:

• Which segment funds the company?
• Which segment consumes cash but looks good in a pitch?

Pricing and scope are resilience tools

If you discover weak contribution margins, the fix is rarely “sell more”. Common practical moves:

• Scope boundaries in proposals (what’s included vs billed)
• Standardised packages to reduce delivery variation
• Minimum contract term to recover onboarding costs
• Price increases tied to measurable value (not inflation excuses)

If your story resembles Jeremy Foo’s—late nights, rapid changes—this is often the missing link: hard decisions on what you will no longer deliver at old prices.

A quick “customer-funded runway” shortcut

If you’re short on time, compute:

• Monthly gross profit (after fully loaded delivery costs)
• Monthly fixed costs

If gross profit doesn’t cover fixed costs, then customers are not yet funding runway—even if revenue is growing. That’s the uncomfortable but actionable truth test.

Which stress-tests should you run before 2027 forces them on you?

Stress-testing is not pessimism; it’s pre-committing to actions while you still have time.

Run these four tests using your 13-week cash forecast and your runway composition table.

Stress-test 1: Remove grants completely

Assume no grant cash-in from next month.

• What week does cash go below your buffer line?
• Which expense line causes the cliff?

Pre-commit actions:

• Immediate: freeze non-essential spend; stop hiring
• 30 days: renegotiate supplier terms; reduce discretionary tools
• 60 days: restructure delivery to protect gross margin; reduce payroll if needed

Stress-test 2: Delay receivables by 30–60 days

Assume your top 5 customers pay late.

Pre-commit actions:

• Tighten invoicing cadence; send invoices earlier
• Put collections calls on calendar with named owners
• Introduce partial upfront payments for new contracts

Stress-test 3: Lose your top customer

If one customer is >20–30% of revenue, you have concentration risk.

Pre-commit actions:

• Within 30 days: pipeline plan targeted at 2–3 adjacent segments
• Within 60 days: redesign offering to reduce bespoke dependency
• Within 90 days: revise credit policy and contract terms for new deals

Stress-test 4: CAC increases and conversion drops

Assume ads cost more, or partner referrals slow.

Pre-commit actions:

• Shift effort to retention/upsell where contribution margin is proven
• Reduce channel spend unless payback is within your customer-funded runway window
• Improve onboarding to reduce churn and support load

A note on “pivoting” versus “stabilising”

A pivot is not a badge of honour; it is a cost. If you pivot without understanding unit economics and cash timing, you may just be changing the shape of the problem.

The goal of stress-tests is to choose whether you:

• Cut (reduce burn)
• Pause (stop loss-making acquisition/segments)
• Raise (only if milestones and cash plan are credible)
• Reprice / Rescope (protect contribution margin)
• Pivot (if your customer-funded path is structurally blocked)

Do the decision-making while you still have 2–3 quarters of options, not 2–3 weeks.

What should your 30/60/90-day plan look like after the audit?

The audit is only useful if it converts into owners, deadlines, and measurable outcomes. Here is a practical structure that fits most Singapore startups and SMEs.

Day 0–30: Stop the cash leaks and make runway “real”

Objectives: tighten visibility and protect liquidity.

• Implement the weekly 13-week cash forecast (owner: Finance lead; reviewer: Founder)
• Separate reporting: operating performance vs financing (owner: Finance)
• Collections sprint: top 10 receivables weekly; renegotiate payment terms for renewals (owner: Sales/Founder)
• Delivery cost mapping for top 3 offers; identify unpriced scope (owner: Ops)

Metrics:

• Cash buffer weeks increases or stabilises
• Customer-funded runway % baseline established
• Aged receivables trend improves

Day 31–60: Rebuild margin and reduce dependence

Objectives: improve contribution margin and reduce subsidy reliance.

• Reprice or re-scope the worst-margin offering
• Standardise onboarding/delivery to reduce labour per customer
• Tag grant-funded costs with end-dates and replacement plans
• Reallocate spend from low-payback acquisition to retention/upsell

Metrics:

• Gross margin after fully loaded delivery costs improves
• Burn multiple improves (or at least stops worsening)
• Customer-funded runway % moves toward target

Day 61–90: Lock in the next 2 quarters of survivability

Objectives: make the business fundable and self-funding.

• Concentration reduction plan: add customers that reduce top-customer share
• Decide financing strategy (if needed): equity/debt/convertible—based on cash plan, not hope
• Document a “grant discipline” playbook: claim calendar, evidence checklist, owner responsibilities
• Prepare a board/advisory review pack: runway composition, stress-test results, actions taken

Metrics:

• Customer-funded runway % hits the quarter target
• Stress-test triggers are documented with actions
• The business can articulate a path to majority customer-funded runway by mid-2027

This is the level of operational clarity investors and ecosystem partners can work with—without needing a heroic narrative.

How can grants and ecosystem support be used as tools without becoming the model?

Singapore’s ecosystem is a genuine advantage when used correctly: capability grants, market access programmes, and peer networks can compress learning cycles. The risk is building an operating model that assumes support will always bridge the gap.

Use grants for capability, not to hide weak unit economics

A helpful internal rule:

• Use grants to build assets (systems, product capability, compliance readiness, training) that increase gross margin or reduce delivery cost.
• Be cautious using grants to fund recurring payroll unless you have a clear conversion plan to customer-funded roles.

Build a “two-track plan”: operating engine + support engine

• Operating engine: pricing, delivery efficiency, retention, collections.
• Support engine: grants as time-limited financing with conditions, scheduled claims, and defined outcomes.

When both are explicit, you can use Enterprise Singapore grants as intended—without blurring the line between operating performance and financing.

Use peer networks as execution infrastructure

Near-shutdown stories often include a quiet truth: founders survive because they had someone to call.

Practical ways to make this operational (not sentimental):

• Monthly peer review of cash forecast and runway composition (accountability)
• A “pre-mortem” session each quarter: what could break cashflow?
• A decision buddy for hard calls (pricing, headcount, stopping a product line)

Mental health support: keep it bounded and practical

Cash discipline is harder when you’re exhausted or isolated. It’s reasonable to:

• Set non-negotiable operating rhythms (weekly cash review, weekly collections)
• Use peer groups to reduce decision fatigue
• Seek professional help if stress becomes unmanageable (without treating it as business advice)

Resilience is not just money; it is the ability to make clear decisions repeatedly under pressure. Support systems should strengthen that discipline, not replace it.

What are the warning signs you’re drifting into “grant dependence” even with growth?

Some of the most fragile companies look “busy” on the surface. Watch for these signals:

Finance signals

• Runway improves mainly when grant cash-in arrives
• You forecast based on invoices, not collections
• Your gross margin looks fine until delivery labour is included
• You can’t explain cash movements without “timing issues” every month

Operating signals

• Sales celebrates bookings, ops complains about unscoped delivery
• Customer success is overloaded, churn is rationalised as “early days”
• The team is building features tied to grant milestones rather than customer retention

Governance signals

• No owner for claim evidence and deadlines
• Board/advisors see P&L, but not a weekly cash view
• Decisions are postponed until “after the next claim/pitch/event”

What to do if you see these signs

Pick one lever per week for 8 weeks:

1. Collections and payment terms
2. Delivery cost reduction via standardisation
3. Pricing and scope discipline
4. Stop-loss on loss-making segments

If you try to “transform everything” you’ll change nothing. The audit is about narrowing to the highest cash impact actions.

When should you bring in an external finance partner—and what should you ask them to build?

External support is useful when founders are making decisions with incomplete or delayed numbers. The goal is not to outsource thinking; it’s to upgrade the operating system.

Situations where outside help pays for itself

• You have grants with multiple claims, conditions, or evidence requirements
• Cash swings are frequent and hard to explain
• You’re planning a raise and need decision-grade forecasting
• You need to reset pricing and delivery economics with credible cost data

What to ask for (practical deliverables)

Whether you work with an internal hire, outsourced finance, or an advisory firm, ask for:

• A 13-week rolling cash forecast template used weekly
• A runway composition metric and glidepath targets
• A grant cashflow model with delay/downside scenarios
• A unit economics model with fully loaded delivery costs
• A monthly management pack that separates operating vs financing

Paul Hype Page & Co. typically supports founders by implementing these as lightweight routines—forecasting, reporting, and claims discipline—so management can spend time on pricing, delivery, and customer outcomes rather than reactive firefighting.

The best outcome is not “more reporting”. It’s fewer surprises and faster, calmer decisions.

结论

The useful lesson from Jeremy Foo’s near-shutdown isn’t that grants are good or bad—it’s that timing, conditions, and weak unit economics can turn support into a false sense of runway. If you want Singapore startup resilience going into 2027, run the 60–90 minute audit: classify grants as conditional financing, calculate customer-funded runway versus subsidy-funded runway, and stress-test the next 13 weeks for delays and shocks. Then commit to a 30/60/90-day plan that prioritises collections, margin, and cash visibility—so your company’s survival is funded increasingly by customers, not by hope or the next tranche.