Your Unit Economics Look Fine in Aggregate. Per Customer, They're a Disaster.

01 /The Concept

Unit economics can look fine at the aggregate level and be a disaster at the customer level. Bilanc tracks them per individual customer – making the delta visible.

The classic definition of unit economics is simple: revenue and costs per unit sold. Bilanc takes a broader view. Its platform calculates the actual profit generated by each specific customer – accounting for revenue received from them alongside the costs incurred not just in delivering the service but in all the surrounding support and overhead. That profit can be measured over any time period or over the customer's full lifetime (LTV).

The target audience is B2B SaaS companies, where understanding per-customer economics can drive smarter pricing and more efficient operations.

Analysis can be run at the individual customer level or across customer cohorts. For example: compare profitability across geographic markets to inform regional pricing. Or compare the LTV of customers acquired through different marketing channels – cut the underperformers, double down on the ones that drive profitable customers.

Revenue data flows into the platform automatically from connected accounting systems. Cost data requires a bit more instrumentation: developers insert Bilanc API calls at the relevant points in the product and in internal systems. Each call logs that a specific customer performed a specific action.

That action might involve a product feature that costs money to operate – a call to a third-party AI model, a storage write, or anything else that generates variable expense tied to usage.

Or it might be a support interaction: a call to the help desk, an email exchange. These are real costs too – someone's time. So the relevant API call gets added to tools like Zendesk or Intercom as well, capturing the event "this customer contacted support."

Separately, a cost table in the platform maps every event type to a dollar value. That price can be fixed or computed dynamically based on parameters passed with the event – for example, how many tokens were sent to and received from an AI model, or how many gigabytes of data were written.

From there, the logic is straightforward. The platform takes all logged events for a customer, prices them using the cost table, adds the total to the revenue figure from the accounting system, and presents the net margin per customer over any selected period – as a table or a chart.

Drilling deeper, you can identify which specific events were the biggest cost drivers for a given customer. Sometimes the culprit isn't the customer at all – it's a process that needs to be optimized regardless of who's triggering it.

Bilanc is currently going through Y Combinator, which provided the initial $500K. The first version of the platform launched just a few days ago.

02 /Why It Matters

Bilanc is clearly at a very early stage, and several aspects of comprehensive unit economics tracking are still missing from the platform.

Employee time allocation is one obvious gap. Many business types – accounting firms, for instance – have labor as their dominant cost, and that labor isn't yet trackable at the per-customer level in Bilanc. The platform will need to either build this capability or integrate with dedicated time-tracking tools.

On that note, Rize, [covered recently](/review/mnogo-ili-jeffektivno), is a platform that does exactly this – tracking knowledge workers' time across different tasks and projects, while nudging them toward better focus habits. A natural integration candidate.

The underlying problem Bilanc addresses is an old one. Early-stage businesses often set prices too low to land first customers, and unconsciously exclude certain costs from their mental model of what the service actually costs to deliver. Eventually – sometimes too late – they realize they've been operating at a loss.

So why is a platform for this worth building now?

First reason: the economic environment has tightened. Companies have been forced to care about costs in a way they didn't when cheap capital was abundant. Startups in particular can no longer just show revenue growth – they need to demonstrate healthy unit economics. Which means they need a quick, reliable, ongoing way to calculate them. That's what Bilanc provides.

Second reason: AI costs are now a real line item for most software companies. Adding AI features means calling external model APIs – OpenAI, Gemini, Mistral, or others – and paying per call, based on the volume of tokens transferred. Every one of those calls is a cost that must be tracked to ensure unit economics stay positive. It's easy to tip into the red: give customers unlimited access to an AI assistant inside your product, and the developer pays for every single response.

Real usage patterns are more complex than that example, of course – which makes the accounting more complex too. At that point, manual tracking isn't realistic. You need automation.

Someone might build a narrow tool just for tracking AI API costs – and a few startups have already started doing that. But if customers are already motivated to understand their AI costs, it's a short step to convince them to adopt a full unit economics platform that delivers far more insight. Bilanc can ride that specific entry point into a much broader product relationship.

03 /Opportunities

More broadly, financial analytics platforms for companies are becoming relevant again as economic conditions push founders and operators to prioritize profitability over growth at all costs.

A [related review](/review/vnezapno-aktualnaja-tema) from last year covered Puzzle, which built a "modern financial management platform" aimed specifically at startup founders who need to understand their numbers – not just for accounting and taxes, but for building sustainable businesses and raising funding in a climate where investors now demand financial discipline. Since that review, Puzzle raised another $30M, bringing total funding above $45M.

Accurate financial management requires solid unit economics. So the opportunity to build platforms for calculating per-customer unit economics fits squarely into the broader trend of founders prioritizing financial rigor.

The direction worth pursuing: unit economics platforms purpose-built for B2B software developers. Starting point: take what Bilanc is doing today – a raw but promising concept – and build it into a genuinely complete product that handles the edge cases, the nuances, and the variety of real-world usage scenarios.