Founder finance guide

Multi-project finance tracking: know which bet is earning, burning, or consuming runway

A practical, project-aware system for founders managing several products, experiments, or client engagements from the same pool of time and cash.

Multi-project finance tracking means assigning every revenue, expense, and capital event to a specific product, client project, or business bet. It lets a founder understand each project’s operating result while preserving a portfolio-wide view of cash, burn, and runway.

Track your first projectUse the five-step method

The underlying problem

One bank balance can hide several different businesses

A founder running multiple products often pays for hosting, APIs, domains, advertising, contractors, and software from one account. Revenue may arrive through several processors or client invoices. The company total can look healthy even when one project is quietly subsidizing another.

The failure is not usually a missing spreadsheet formula. It is missing ownership. When a transaction is recorded without a project, the founder cannot answer the decision that matters: which bet created this result?

Why cash visibility matters

QuickBooks’ 2026 late-payments research found that 51% of surveyed businesses with overdue invoices described cash flow as a problem, compared with 36% without overdue invoices. The research concerns small businesses generally, not Piveth users, but it illustrates why earned revenue and usable cash cannot be treated as the same thing.

Read the QuickBooks methodology and findings

Four questions company-wide totals cannot answer reliably

  • Which product generated this month’s revenue?
  • Which project caused the increase in hosting or contractor spend?
  • Is a project profitable on its own, or funded by another project?
  • If spending continues, which bet shortens portfolio runway the most?

The operating method

How to track finances across multiple projects

Use one consistent ledger with a required project dimension. Avoid creating disconnected workbooks that drift apart; the goal is a comparable view of every bet using the same definitions.

  1. Define stable project boundaries

    Create a project for each product, client engagement, or experiment you may fund, pause, or evaluate separately. Do not create a project for every vendor or category.

  2. Record the starting financial state

    Enter available founder capital or declare the business bootstrapped. Treat capital as financing—not customer revenue—so it does not inflate operating performance.

  3. Assign direct transactions at capture

    When an expense or receipt occurs, attach its type, amount, date, project, and category. Capturing project ownership immediately is more reliable than reconstructing it at month end.

  4. Choose a rule for shared costs

    For infrastructure or subscriptions serving several products, document a repeatable allocation rule such as usage, seats, revenue share, or an equal split. Use the project profitability calculator to test the effect. Piveth does not yet automate split transactions, so shared costs currently require separate project entries or an explicit portfolio-level treatment.

  5. Run a weekly decision review

    Correct unclear entries, verify the ledger is current, compare project revenue and operating costs, inspect burn and runway, and record the action you will take next.

Comparable definitions

The five numbers each project needs

Definitions matter more than decorative dashboards. Piveth uses the following operating model so capital cannot masquerade as customer demand.

Operating revenue

customer cash inflows

Money earned from the project’s customers during the selected period.

Gross burn

operating cash expenses

Total operating cash spent during the period, before subtracting revenue.

Operating net

revenue − expenses

A positive number indicates an operating surplus; a negative number indicates an operating deficit.

Net burn

max(expenses − revenue, 0)

The rate at which operations consume cash after revenue. It is zero when revenue covers expenses.

Estimated runway

available capital ÷ net burn

An estimate based on the selected period’s net burn, not a guarantee or forecast.

Capital

financing inflow ≠ revenue

Founder contributions or investment can increase available funds without improving operating profit.

These gross/net burn distinctions are consistent with Stripe’s published startup burn-rate definitions. Review Stripe’s definitions.

Worked example

From one sentence to a reviewable project result

“I spent ₹3,000 on hosting for VClar.”
1Parse

Expense · ₹3,000 · VClar · Hosting

2Verify

Compare the structured fields with the founder’s original words.

3Calculate

Gross burn: ₹0 → ₹3,000
Operating net: ₹0 → −₹3,000

4Control

Edit or undo the entry if any field is wrong.

This example deliberately does not infer tax treatment, accounting entries, or business advice. It shows the narrower job a founder finance layer can perform reliably: capture an operating event, assign its project, update defined metrics, and expose the result for review.

Choose the right layer

Spreadsheet, accounting system, or project finance command center?

ToolBest atCommon limitation for a multi-project founder
SpreadsheetFlexible custom analysis and one-off planningCapture is manual, definitions drift, and separate sheets become stale
Accounting softwareBooks, reconciliation, compliance workflows, and accountant collaborationMay be too account- or company-centric for daily product-bet decisions
Project-management toolTasks, owners, time, and deliveryUsually lacks a project financial ledger and founder runway model
PivethConversational capture and reviewable project-level operating signalsDoes not replace accounting, tax, bank reconciliation, or professional advice

The useful pattern is often complementary: Piveth for frequent founder decisions, accounting software and qualified professionals for formal books and compliance, and a spreadsheet for bespoke models.

How Piveth fits

A project-aware capture and decision loop

Piveth is built around the repeated moment when a founder knows something financial happened but has not yet placed it in a structured ledger. The product accepts manual, text, and voice-origin entries, then returns a receipt showing the original input, parsed fields, and metric impact.

Capture

Record expenses, revenue, or capital against the project involved.

Review

Inspect the structured result and correct or undo it when needed.

Understand

See project revenue, gross burn, operating net, net burn, and estimated runway using explicit definitions.

Return

Add new activity and run a short weekly project-finance review.

Product boundary

Piveth is not bookkeeping, tax filing, statutory accounting, bank reconciliation, or financial advice. Its job is to help founders maintain and inspect a project-level operating view.

Direct answers

Multi-project finance tracking questions

What is multi-project finance tracking?

It assigns revenue, expenses, and capital events to a specific product, client project, or business bet so you can evaluate each project without losing the portfolio-wide cash picture.

How do I track expenses across multiple projects?

Maintain a stable project list, tag direct expenses when they happen, document a repeatable allocation rule for shared costs, and review the classifications every week.

Should founder capital count as project revenue?

No. Capital is a financing event. It may increase available cash, but it should not improve operating revenue, operating net, or project profit.

What is the difference between gross burn and net burn?

Gross burn is total operating cash expenses for a period. Net burn subtracts operating revenue from those expenses and cannot fall below zero under Piveth’s displayed definition.

Does this replace accounting software?

No. Project finance tracking supports management decisions. Formal books, tax, payroll, reconciliation, and compliance may still require accounting software and qualified professionals.

How often should I review project finances?

Capture transactions when they occur and conduct a short weekly review. The useful cadence is frequent enough to correct stale classifications before they shape a decision.

Put the method into practice

Give the next transaction a project.

Start with one project, a capital or bootstrapped state, and three real entries. Review every result before using it.

Start freeCalculate project profitCalculate runway