66. Startup Finance Basics

Startup finance is not about becoming a full-time accountant. It is about knowing enough to avoid fooling yourself. A founder who cannot see cash, burn, margin, collections, payroll, and taxes will eventually be managed by panic instead of judgment.

Finance becomes especially important in Indian startups because customers may pay late, statutory obligations arrive whether or not revenue arrived, fundraising timelines are uncertain, and many early teams operate with thin cash buffers. A useful finance system gives the founder time to act before the bank balance becomes the strategy.

The founder’s finance job

The founder’s finance job is to answer five questions every week:

• How much cash do we actually have?
• How much cash will leave before more cash comes in?
• Which revenue is collected, not merely invoiced?
• What commitments have we made to employees, vendors, government, lenders, and investors?
• What decision needs to change because of the numbers?

This is not the same as having perfect books. Clean accounting matters, but founder finance starts with operational clarity. You should know whether you can make payroll, whether a hiring plan is safe, whether sales collections are slipping, whether pricing covers delivery cost, and whether a funding plan is realistic.

Basic terms founders must know

Term	What it means for a founder
Revenue	Money earned from customers. Separate contracted, invoiced, and collected revenue.
Cash	Money available in bank accounts and wallets. Cash is what pays salaries and vendors.
Gross margin	Revenue left after direct cost of delivering the product or service. Low margin limits growth.
Gross burn	Total cash spent per month before counting cash inflows.
Net burn	Cash spent minus cash collected in the same period.
Runway	Months before cash runs out at the current or expected burn rate.
Receivables	Money customers owe you. It is not cash until collected.
Payables	Money you owe vendors, employees, government, or lenders.
Assets	Resources the company owns or controls.
Liabilities	Obligations the company must settle.

The most dangerous confusion is between revenue and cash. A startup can show strong invoiced revenue and still die because customers pay late, refunds rise, implementation costs are high, or statutory dues were not planned.

Cash view vs accounting view

Accounting tells the story of the business according to rules. Cash tells the story of survival.

Founders need both:

• Cash view: bank balance, expected inflows, expected outflows, runway, collections risk.
• Accounting view: revenue, expenses, profit and loss, balance sheet, statutory records, audit trail.

Early founders often live only in the cash view and ignore accounting until diligence, tax filing, or audit pressure arrives. Others look only at accounting reports and miss the fact that invoices are unpaid. The practical answer is a weekly cash review plus a monthly close with your CA/accountant.

Weekly cash review

Create a 30-minute weekly finance ritual. Do it even when the numbers are uncomfortable.

Track:

• Opening bank balance.
• Cash collected last week.
• Cash expected in the next 30 days.
• Payroll and contractor payments due.
• Vendor payments due.
• Tax, GST, TDS, PF/ESI, professional tax, or other statutory items that may apply.
• Loan, credit card, or founder repayment obligations.
• Current net burn.
• Conservative runway.
• Decisions needed this week.

The output should be a decision, not a spreadsheet. Examples: pause hiring, chase three receivables, renegotiate a vendor, move a founder salary, raise prices, cut an experiment, or start fundraising earlier.

Monthly founder finance pack

Every month, prepare a simple finance pack:

• Profit and loss summary.
• Cash movement summary.
• Revenue booked, invoiced, and collected.
• Customer-wise receivables ageing.
• Top expenses.
• Payroll and contractor cost.
• Gross margin by product, service, or customer segment.
• Runway under base and conservative scenarios.
• Statutory/compliance status.
• One paragraph explaining what changed.

This pack is useful even if you have no board. It forces the founder to see the company as a system instead of a set of anecdotes.

The founder finance stack

Think of finance in layers. Do not jump to complex models before the basic layers work.

Layer	Founder question	Minimum artifact
Cash visibility	How much money is available and what leaves next?	Weekly cash sheet
Collections	Which customer money is actually coming in?	Receivables tracker
Spend control	Which costs are fixed, variable, optional, or waste?	Expense review
Payroll safety	Can we pay people on time for the next few months?	Payroll forecast
Margin clarity	Are we making money on each customer, order, project, or account?	Gross margin view
Compliance rhythm	What filings, deductions, returns, and records need attention?	Compliance calendar
Scenario planning	What happens if revenue, collections, hiring, or funding slips?	Base/conservative/downside model

The stack is deliberately boring. Boring finance creates calm decisions.

Cash, profit, and growth are different

Founders often mix three ideas:

Idea	What it answers	Startup trap
Cash	Can we survive and meet obligations?	Assuming invoices or committed investment are already cash.
Profit	Does the business earn more than it spends over a period?	Ignoring timing, working capital, or founder salary.
Growth	Are revenue, usage, customers, or transactions increasing?	Growing a low-margin or cash-draining motion.

A startup can grow and still become financially weaker. A services company can show revenue but destroy founder time. A SaaS company can show ARR but carry weak collections. A marketplace can show GMV but keep little contribution margin.

Finance is how the founder sees the difference.

Stage-based finance focus

Stage	Finance focus	Dangerous blind spot
Idea/discovery	Personal runway, small experiment budget.	Spending like a funded company before proof.
MVP	Cost to build, manual delivery cost, founder salary reality.	Ignoring the cost of “manual for now” operations.
First customers	Invoicing, collections, gross margin, paid pilots.	Celebrating sales without cash collection.
Early revenue	Repeatable pricing, delivery cost, payroll plan.	Hiring ahead of revenue quality.
Fundraising	Runway, milestones, financial model, data room.	Starting the raise too late or using fantasy forecasts.
Scaling	Unit economics, working capital, controls, monthly close.	Scaling a leaky model because topline looks good.

The founder should not use the same finance dashboard at every stage. Early on, survival and learning matter. Later, margin, repeatability, and controls matter more.

Financial decision rules

Write decision rules before pressure rises.

Decision	Example rule
Hiring	We hire only if the role improves a named milestone and keeps conservative runway above X months.
Paid marketing	We scale spend only when activation, retention, and payback are within our target range.
Vendor spend	Any recurring tool above Rs. X/month needs an owner and review date.
Founder salary	Salary changes only during monthly cash review and applies fairly across co-founders.
Receivables	Any invoice older than X days gets founder-level escalation.
Fundraising	We begin investor outreach when conservative runway falls below X months or milestone evidence is ready.

Decision rules reduce the chance that fear, optimism, or one loud customer drives the company.

Finance habits that compound

Good startup finance is mostly habit:

• Keep company and personal money separate.
• Record every invoice, receipt, and vendor bill.
• Reconcile bank accounts monthly.
• Review receivables every week.
• Approve expenses deliberately.
• Plan payroll before hiring.
• Keep a compliance calendar with your CA/CS.
• Keep one source of truth for cash and runway.
• Do not count investment money until it is in the bank.
• Maintain clean data room finance folders from early on.

These habits look boring, but they are what keep fundraising, due diligence, tax work, and management decisions from becoming painful later.

India angle

Indian startup finance has a few common realities:

• B2B customers may pay after long approval cycles even when they like the product.
• Invoices may need GST, purchase orders, vendor onboarding, and correct billing details before payment moves.
• Founders often underestimate TDS, GST, payroll, and annual compliance coordination.
• Early CA/accountant quality varies widely; founders must define expectations clearly.
• Many customers negotiate hard on price but still expect high-touch service.
• Cash collection discipline matters as much as sales discipline.

Do not treat “revenue booked” as victory. In India, “cash collected with clean paperwork” is the safer operating signal.

Founder finance dashboard

Keep a simple dashboard that can be reviewed in 15 minutes.

Metric	Why it matters	Review rhythm
Cash in bank	Survival reality.	Weekly
Conservative runway	Time left under cautious assumptions.	Weekly/monthly
Monthly gross burn	Spending before collections.	Monthly
Monthly net burn	Actual cash consumption.	Monthly
Receivables ageing	Cash stuck with customers.	Weekly
Payroll committed	Fixed people cost.	Monthly
Gross margin	Quality of revenue.	Monthly
Top 5 expenses	Cost discipline.	Monthly
Compliance status	Avoidable risk.	Monthly
Next finance decision	Converts numbers into action.	Weekly/monthly

If a metric does not change a decision, remove it. If a decision is being made without a metric, add one.

Finance operating cadence

Finance becomes useful when it has rhythm. A founder should not wait for a crisis, a board meeting, or a CA reminder to look at money. Set a cadence that is light enough to sustain and serious enough to catch problems early.

Rhythm	What to review	Output
Daily, during tight periods	Bank balance, major expected inflows/outflows, urgent customer payments	No surprise cash movements
Weekly	Cash, collections, payroll risk, upcoming vendor/statutory payments, runway	One decision list for the week
Monthly	P&L, cash movement, receivables, payables, gross margin, top costs, compliance status	Monthly finance note
Quarterly	Pricing, hiring plan, fundraising plan, vendor commitments, tax/compliance risks, scenario model	Updated operating plan
Before major decisions	Hiring, fundraising, pricing, office, large vendor, new market, large customer deal	Runway and margin impact

This cadence is deliberately simple. The danger is not that founders lack advanced finance theory. The danger is that nobody looks at the obvious numbers until they become painful.

Revenue quality review

Revenue is not equally useful just because it has the same amount on an invoice. Each month, review revenue quality.

Question	Better signal	Warning signal
Is it collected?	Cash received on time	Invoice raised but payment uncertain
Is it repeatable?	Same customer type buys for the same reason	One-off relationship or custom project
Is it profitable?	Clear gross margin after delivery/support cost	High revenue with hidden manual effort
Is it strategic?	Teaches product, ICP, pricing, or distribution	Distracts team from the core customer
Is it renewable?	Customer uses and gets value repeatedly	Customer pays once and disappears
Is it expandable?	More seats, usage, departments, or workflows possible	No natural next purchase

For Indian founders, this matters because early revenue often comes from services, paid pilots, founder network, or custom enterprise work. That revenue can be excellent if it teaches the product and funds learning. It becomes dangerous when it tricks the founder into believing the startup has a repeatable business before repeatability exists.

Use four labels:

Label	Meaning	Founder response
Core revenue	ICP-fit, repeatable, profitable, strategically useful	Protect and study it
Learning revenue	Not yet repeatable, but teaches the product or market	Use consciously, limit distraction
Cash revenue	Helps runway but may not define the future business	Take carefully, avoid over-commitment
Distracting revenue	Low-margin, custom, politically difficult, or off-strategy	Decline, reprice, or contain

The best founders do not only ask, “How much revenue?” They ask, “What kind of revenue, from whom, at what cost, and what does it prove?”

Finance ownership map

Even a tiny startup needs clarity on who owns finance tasks. If ownership is vague, important work falls between founders, accountants, sales, and operations.

Use this ownership map:

Work	Primary owner	Founder check
Weekly cash view	Founder or finance owner	Is the runway number conservative and current?
Customer invoicing	Finance/ops owner, with sales input	Are billing details, PO, GST, and payment terms correct before invoice?
Collections	Sales owner for relationship, finance owner for tracker	Which overdue invoices need founder escalation this week?
Expense approval	Founder or budget owner	Is this spend tied to a current milestone?
Payroll planning	Founder plus accountant/payroll partner	Can payroll be paid on time under the conservative case?
Monthly close	CA/accountant	Are books closed, reconciled, and usable for decisions?
Compliance calendar	CA/CS plus founder	What is due in the next 30, 60, and 90 days?
Investor finance updates	Founder	What changed in cash, burn, revenue quality, and runway?

The founder should not do every finance task forever. But the founder must know whether the system is working. Delegating finance without visibility is how surprises become crises.

Payroll safety test

Payroll is the most important recurring promise a startup makes. Before hiring, fundraising, or increasing spend, run a payroll safety test.

Question	Healthy answer	Risk signal
How many payroll cycles are covered by cash in bank?	Enough cycles under conservative runway, not best-case collections.	Payroll depends on one uncertain customer payment or investment transfer.
Are statutory/payroll obligations planned?	Applicable deductions, filings, and records are included in the calendar.	Salary is modeled, but obligations and processing costs are not.
Are founder salaries explicit?	Founders have agreed salary, deferral, or no-salary rules.	Founders silently absorb stress and later resent it.
Are contractor payments visible?	Contractors are included in monthly cash planning.	Contractor costs are scattered across invoices and reimbursements.
What happens if a large receivable slips?	The company has a response plan.	Payroll becomes dependent on aggressive follow-up in the final week.

If payroll safety is weak, do not comfort yourself with revenue projections. Fix the cash plan, reduce commitments, collect faster, or change the hiring timeline.

Founder expense controls

Early teams do not need heavy bureaucracy, but they do need basic controls. A lightweight control system protects trust between co-founders, employees, investors, and advisors.

Set rules for:

• Who can approve recurring software, agencies, contractors, travel, events, devices, and reimbursements.
• What spend needs written approval before purchase.
• Which expenses are never paid from company accounts.
• How founder advances and reimbursements are recorded.
• When subscriptions are reviewed and cancelled.
• What happens when a customer request requires unplanned spend.

A simple rule works well: every recurring expense needs an owner, a purpose, a review date, and a cancellation condition.

Expense type	Control question
Software	Who uses it weekly and what work would break if removed?
Agency/consultant	What output is expected this month and who reviews quality?
Cloud/infra	Is usage tied to customers, experiments, or waste?
Travel/events	What pipeline, hiring, partnership, or customer result justifies it?
Discounts/refunds	Who approves margin impact and customer precedent?

Controls should make spending intentional, not slow. The right question is not “Can we afford this?” The better question is “What decision, learning, revenue, or risk reduction does this buy?”

Weekly finance meeting agenda

The weekly finance meeting should be short and decision-oriented. If it becomes a long accounting discussion, founders will stop doing it. Keep the meeting to 30 minutes and use the same agenda every week.

Minute	Question	Output
0-5	What is cash in bank and conservative runway today?	Current survival picture
5-10	What cash is expected in the next 30 days and how confident are we?	Collections priority list
10-15	What cash will leave in the next 30 days?	Payroll, vendor, tax, and one-time cost visibility
15-20	Which receivables need founder escalation?	Named owner and next action
20-25	Which spend decisions are pending?	Approve, delay, cut, or reprice
25-30	What changed in the business because of this review?	One decision logged

The meeting is successful only if it changes action. A good finance meeting might produce a founder call to a late-paying customer, a delayed hire, a pricing change, a vendor renegotiation, or an earlier fundraising start.

Do not let the meeting become a place where everyone reports numbers and nobody decides anything.

Revenue-to-cash checklist

Many Indian founders lose weeks because a customer has agreed commercially, but payment operations were not understood. Put this checklist inside the sales handoff.

Stage	Founder question
Before proposal	Who is the buying entity and who signs?
Before contract	Does the customer require vendor onboarding, PO, security review, or finance approval?
Before invoice	Do we have legal name, GST details where applicable, address, PO/reference, billing contact, and payment terms?
After invoice	Has the customer acknowledged receipt and confirmed the payment process?
Before due date	Has the relationship owner checked whether payment is still on track?
After due date	What is the blocker: paperwork, approval, dispute, budget, silence, or low priority?
Collection	Has cash been matched to invoice and recorded correctly?

For founder-led sales, the founder should own this until the company has a reliable finance or operations owner. Do not assume the customer’s finance team will move quickly just because the business sponsor likes you.

Finance red flags that need founder attention

Some finance signals should not wait for the next monthly review.

Signal	Why it matters	Founder response
Payroll depends on one incoming payment	People commitments are exposed to customer delay.	Create backup plan, escalate collection, pause discretionary spend.
60+ day receivables are growing	Revenue quality is weaker than sales suggests.	Review customer segment, terms, invoice process, and escalation.
Gross margin is unclear	The company may be selling work that loses money.	Calculate direct cost by customer, product, or project.
Founder reimbursements are informal	Trust and diligence risk increase.	Document advances, reimbursements, approvals, and business purpose.
Recurring tools have no owner	Spend is becoming invisible.	Assign owner, purpose, review date, and cancellation condition.
CA/accountant cannot produce monthly status	Finance hygiene is not operating.	Reset expectations, add a monthly close rhythm, or change support.
Investors ask for numbers the company cannot explain	Diligence readiness is weak.	Build a finance pack and reconcile source documents.

Red flags are not moral failures. They are early warnings. Treat them as prompts to improve the operating system before the numbers become a crisis.

Common mistakes

• Tracking invoices instead of cash: receivables do not pay salaries.
• Hiring ahead of proof: fixed payroll before repeatable revenue or funding can shorten runway brutally.
• Ignoring gross margin: high revenue with low margin can make growth more dangerous.
• No collections owner: everyone celebrates sales, nobody follows payment.
• Surprise taxes and filings: statutory obligations should be in the calendar before they are urgent.
• Overestimating fundraising certainty: investor interest is not cash.
• No monthly close: finance becomes memory and guesswork.

Practical process

1. Create a weekly cash sheet with bank balance, expected inflows, expected outflows, and runway.
2. Create a monthly finance pack with P&L, cash movement, receivables, expenses, margin, and compliance status.
3. Ask your CA/accountant for a recurring monthly close date.
4. Assign one owner for collections.
5. Review every new hire, vendor, and large expense against runway impact.
6. Keep a finance data room from day one: bank statements, invoices, tax filings, payroll records, contracts, and cap table.

Founder Finance Control Room

A founder does not need to become a full-time accountant. But the founder does need a control room where the business can be seen clearly every week.

Build one page with these sections:

Section	What to track	Founder decision it supports
Cash	Bank balance, expected inflows, expected outflows, minimum cash threshold	Can we operate normally this month?
Runway	Current runway, conservative runway, post-hiring runway	Do we hire, cut, raise, or wait?
Revenue	Booked revenue, collected revenue, recurring revenue, one-time revenue	Is revenue real cash or only invoices?
Receivables	Ageing by customer, owner, promised payment date	Who follows up and what risk exists?
Expenses	Payroll, tools, agencies, cloud, marketing, rent, founder reimbursements	Which costs are core, useful, optional, or waste?
Gross margin	Revenue minus delivery, support, infrastructure, and service cost	Is growth improving or damaging economics?
Compliance	Upcoming GST, TDS, payroll, ROC, audit, and advisor tasks	What can surprise us legally or financially?
Decisions	Hires, vendor renewals, pricing changes, discounts, funding needs	Which finance decision needs founder judgment now?

Review this page every Friday. The point is not financial sophistication. The point is to remove surprise. A founder who sees cash, collections, burn, and compliance early can make calm decisions. A founder who waits for the bank balance to become scary is already late.

Cash Decision Ladder

When cash is limited, every spending decision should climb a ladder. This keeps the founder from treating all expenses as equal.

Level	Spend type	Founder rule
1	Legal, statutory, payroll, customer-critical infrastructure	Protect unless the company is in survival mode.
2	Work that creates or protects revenue, retention, security, or core product reliability	Approve when owner, outcome, and review date are clear.
3	Learning spend: experiments, pilots, discovery, narrow GTM tests	Approve only with a success threshold and stop date.
4	Convenience spend: tools, agencies, subscriptions, travel, events	Review hard; cut if not tied to current bottleneck.
5	Status spend: office optics, vanity brand work, premature hiring, vague consultants	Avoid unless the business case is unusually clear.

Use this in the weekly finance meeting. The question is not whether a cost is “good.” Many costs are good in isolation. The question is whether this cost deserves cash before the company has proved the next constraint.

For Indian founders, the ladder is especially useful because cash can be trapped in receivables, GST/TDS timing, slow enterprise payments, or fundraising delays. A profitable-looking month can still create cash pressure if collections are weak.

Finance Truth Review

Once a month, run a finance truth review. The goal is to separate numbers that make the founder feel good from numbers that actually increase the company’s chance of survival.

Use this table:

Number	Feel-good version	Truth version	Founder question
Revenue	Invoices raised	Cash collected, recurring, retained, and margin-positive revenue	Which revenue can pay salaries and compound?
Pipeline	Total deal value discussed	Qualified deals with buyer, budget, pain, timeline, and next step	Which deals are real enough to plan around?
Runway	Bank balance divided by average burn	Conservative cash after taxes, payroll, collections delay, and planned commitments	How much decision time do we really have?
Burn	Last month’s expenses	Forward-looking burn after hires, tools, taxes, renewals, and known one-time costs	What burn have we already committed to?
Profitability	P&L profit	Cash profit after collections, taxes, founder dues, and delayed vendor payments	Is the business actually self-funding?
Margin	Revenue minus obvious costs	Revenue minus delivery, support, infra, AI, onboarding, refunds, and service load	Does growth improve economics?
Fundraising	Investor interest	Money in bank or signed documents with high confidence	What plan works if the round is delayed?

Ask these questions out loud:

1. Which number are we using to comfort ourselves?
2. Which number would a skeptical investor, acquirer, or lender adjust?
3. Which number would change our hiring or spending decision if we were honest?
4. Which number is still unknown because our finance system is weak?
5. Which customer, vendor, tax, or payroll item could surprise us in the next 30 days?

The founder should not weaponize finance against the team. But the founder must protect the company from narrative finance. If the real number is weaker than the story, adjust the story, the spend, or the operating plan.

Founder Cash War Room

When cash becomes tight, founders often oscillate between denial and panic. A cash war room creates a calm operating ritual. It should be used any time runway is under 12 months, collections are slipping, fundraising is uncertain, or hiring decisions depend on cash.

Build one shared view:

Section	Required detail	Owner
Bank cash	Current balance by bank account and payment gateway settlement balance.	Finance/founder
Confirmed inflows	Customer payments with amount, date promised, buyer contact, and confidence level.	Sales/customer owner
Required outflows	Payroll, taxes, statutory dues, cloud, rent, critical vendors, debt, refunds.	Finance/ops
Optional outflows	Tools, agencies, events, travel, experiments, hiring, consultants.	Functional owners
Receivables risk	Customers late by 0-30, 31-60, 61-90, 90+ days.	Founder/sales
Decision list	Payments to approve, defer, renegotiate, cancel, or escalate.	Founder

Run the meeting weekly in normal times and twice a week in tight times. Keep it factual. The goal is not to scare the team; the goal is to make cash visible early enough that the company still has choices.

Finance Roles By Stage

The finance function changes as the startup grows. Do not overbuild too early, but do not let founder memory remain the system.

Stage	Minimum finance owner	What must be true
Idea/discovery	Founder + CA/accountant	Business and personal money are separated; basic expenses are tracked.
MVP	Founder + monthly accounting support	Invoices, receipts, bank reconciliation, and tax obligations are visible.
First revenue	Founder + CA/accountant + collections owner	Cash collected, receivables, gross margin, and runway are reviewed weekly.
Repeatable revenue	Part-time finance/operator or strong internal owner	Monthly close, MIS, payroll, tax calendar, and investor reporting are reliable.
Funded scaling	Finance lead/controller	Budgeting, approvals, financial controls, board reporting, and audit readiness exist.

The founder should still understand the numbers even after hiring finance help. Delegation means someone else prepares the system. It does not mean the founder stops owning financial judgment.

Friday Finance Questions

Every Friday, answer these ten questions:

1. How much cash is in the bank today?
2. What cash must leave in the next 14 days?
3. Which customer payments are expected in the next 14 days, and how confident are we?
4. Which receivable needs founder escalation?
5. Did we approve any new recurring cost this week?
6. Did any vendor, tax, payroll, refund, or compliance item surprise us?
7. Did revenue quality improve or weaken?
8. Are we spending behind the current company constraint?
9. Has runway changed enough to affect hiring or fundraising decisions?
10. What finance decision are we avoiding?

This ritual is simple, but it compounds. Most startup finance problems are not caused by one bad spreadsheet. They are caused by many small surprises the founder saw too late.

Unit Economics Snapshot

A founder does not need a perfect finance department to understand unit economics. You need a clear view of whether each customer, order, transaction, account, or workflow becomes more or less attractive as volume grows.

Create a unit economics snapshot for your business model:

Model	Unit to inspect	Questions
SaaS	Account, seat, or workspace	What is gross margin after infra, support, onboarding, and payment costs?
Marketplace	Transaction or order	What remains after payment fees, refunds, logistics, incentives, support, and disputes?
Services-to-product	Customer project or workflow	Which work repeats and which work stays manual?
Consumer subscription	Active subscriber	What is CAC, payment failure, refund, support, and retention by cohort?
AI product	Successful task, account, or workflow	What do model calls, retries, human review, storage, and support cost?
Enterprise product	Account	What do sales cycle, onboarding, security, support, collections, and success cost?

The founder unit economics table

Start with a simple table:

Item	Amount
Price charged
Payment/platform fees
Direct delivery cost
Support cost estimate
Onboarding/setup cost estimate
Refund/credit/collection risk
Gross profit per unit
Time to collect cash
Repeat/retention likelihood

The exact math can improve later. The habit matters now. A founder should know whether growth is making the company stronger or simply increasing workload.

Warning signs

Watch for these:

• Revenue grows but gross margin falls.
• Each customer needs custom onboarding.
• Support tickets rise faster than active usage.
• Paid acquisition brings customers with worse retention.
• Enterprise contracts look large but collections are slow.
• Discounts hide low willingness to pay.
• Founder time is the real delivery engine.

If unit economics are unclear, do not scale spend blindly. First learn what a good customer costs to acquire, serve, retain, and collect from.

Minimum Viable Financial Controls

Early startups do not need corporate bureaucracy. But they do need a few controls so cash, trust, and records do not depend on memory.

Set minimum controls:

Control	Founder rule
Bank separation	Personal and company money stay separate.
Payment approval	Every material payment has owner, invoice/proof, and reason.
Recurring spend list	Subscriptions, tools, retainers, rent, and cloud are reviewed monthly.
Customer invoice trail	Every invoice links to customer, contract/order, GST details where relevant, and payment status.
Payroll safety	Payroll is protected before optional spend.
Tax/statutory reserve	Cash obligations are visible before money is treated as available.
Founder reimbursements	Reimbursements are documented and not guessed months later.
Access control	Bank, payroll, accounting, and payment tools have clear permissions.

Approval thresholds

Write thresholds before the team grows:

Under Rs ______: owner can approve within budget.
Rs ______ to Rs ______: founder approval required.
Above Rs ______: founder plus finance/advisor review.
New recurring cost: review runway impact before approval.
New hire or contractor: review runway, role scorecard, and proof of need.

The numbers can be small in an early company. The point is not the threshold; the point is that spending has ownership and context.

Finance control without fear

Controls should make good work easier, not make people afraid. Explain the principle:

We are not controlling spend because we distrust the team. We are controlling spend because runway is strategy, and every recurring rupee should buy learning, revenue, retention, or resilience.

This keeps finance from becoming a founder mood swing. The system decides what deserves review.

Finance Exception Review

Most finance risk enters through exceptions: a one-off customer promise, a delayed payment, a vendor asking for advance, a founder reimbursement without proof, a contractor hired quickly, a tax item nobody owns, or a discount that changes unit economics. Exceptions are normal. Untracked exceptions become hidden debt.

Create a weekly exception review.

Exception type	What to inspect	Founder decision
Customer payment delay	Amount, age, reason, owner, next follow-up	Escalate, pause work, adjust forecast, or accept risk
Discount or custom commercial term	Margin, support load, reference value, renewal impact	Approve, reject, or document exception expiry
New recurring expense	Monthly cost, owner, workflow, runway impact	Approve, delay, cancel, or require milestone
Large one-time expense	Purpose, alternatives, timing, cash impact	Approve now, defer, negotiate, or split
Missing invoice/receipt	Amount, vendor/customer, tax impact, owner	Recover proof or mark risk
Founder reimbursement	Business purpose, proof, approval, timing	Pay, defer, document, or reject
Tax/statutory uncertainty	Amount, deadline, advisor status	Reserve cash and escalate

Use a simple ledger:

Date	Exception	Amount	Owner	Decision	Review date

The point is not to make finance slow. The point is to make exceptions visible before they become normal. In early startups, almost everything can look like a reasonable exception. The founder’s job is to decide which exceptions buy learning, revenue, retention, or trust, and which ones quietly weaken the company.

Founder Finance Risk Register

Founders should maintain a short finance risk register. This is not a corporate risk document. It is a living list of money risks that can change decisions before they become emergencies.

Track:

Risk	What to record
Payroll risk	Months of payroll covered, next payroll date, funding source, owner.
Collections risk	Large receivables, age, reason, buyer contact, next escalation.
Revenue quality risk	Revenue that is discounted, custom, non-recurring, low-margin, or not activated.
Tax/statutory risk	Dues, filing dates, uncertain treatment, advisor status, reserve amount.
Vendor risk	Critical vendor payment, renewal, lock-in, data access, or service dependency.
Hiring risk	Offers made, joining dates, cash impact, milestone dependency.
Founder personal risk	Founder runway, salary needs, family obligations, reimbursement backlog.

Review weekly when runway is under 12 months and monthly when the company is stable. Use four statuses:

Status	Meaning
Watch	Visible but not urgent.
Act	Needs owner and next step this week.
Escalate	Needs founder/advisor/customer/investor attention now.
Closed	Resolved or deliberately accepted.

The register should force one question:

Which finance risk would surprise us least if it became a crisis next month?

That is the risk to act on first. Finance maturity is not having no risk. It is knowing which risks exist and making decisions before panic removes your options.

Thirteen-Week Cash Calendar

Every founder should maintain a 13-week cash calendar. A monthly runway number is useful, but it can hide short-term crunches: payroll week, GST/TDS dates, vendor renewals, delayed customer collections, card bills, cloud invoices, refunds, travel, or founder reimbursements.

Create a simple weekly view:

Week	Opening cash	Confirmed inflows	Likely inflows	Required outflows	Optional outflows	Closing cash	Decision
Week 1
Week 2
Week 3

Separate inflows:

Inflow type	Treat as
Cash already received	Real cash.
Customer confirmed payment date	Probable, but still watch.
Invoice raised but no payment commitment	Not cash.
Verbal investor interest	Not cash.
Signed term sheet but money not wired	Not cash.
Expected GST/refund/credit	Not cash until confirmed with advisor and received.

Use the calendar every Friday:

Which week creates pressure?
Which inflow is uncertain?
Which outflow can move without damaging trust?
Which customer payment needs founder escalation?
Which statutory or payroll item must be protected?

For Indian founders, this calendar is often more useful than a beautiful annual model. It catches the reality of enterprise payment delays, vendor onboarding, GST/TDS timing, UPI/payment gateway settlement delays, and payroll commitments. Finance becomes practical when the founder can see the next 13 weeks clearly.

Reader action

Open your bank account and write the current cash balance. Then list every expected cash outflow for the next 30 days and every expected cash inflow you are confident will be collected. If the answer surprises you, finance is already asking for founder attention.

Related links

• 67. Runway and Burn
• 68. Accounting and Tax
• 152. Finance Templates
• 155. Startup Calculators