Capital allocation inside a company builder

In a single-company startup, capital allocation is mostly a question of how much to spend and on what. In a company builder there is a harder question on top: which company?

Every Oryvelon company competes for the same limited resources. A month of engineering time spent improving ZodiVela is a month not spent on MerchNivo. An afternoon the founders spend on a CastLyra partnership is an afternoon not spent on EduRelia schools. Getting these decisions right is, arguably, the most important thing a company builder does.

This note explains how we approach it.

Three kinds of capital

When people hear "capital allocation" they think of money. In a company builder, money is only one of three resources, and often not the scarcest.

Money pays for acquisition, infrastructure, AI usage, tools, freelancers and sometimes hires.

Build capacity — engineering, design and content time — determines how fast products improve.

Founder attention is the scarcest of all. Partnerships, key customer relationships, hiring, strategy, brand decisions and the hardest problems all need it, and there is only so much of it in a week.

We allocate all three deliberately. A company might receive a modest budget but a lot of founder attention during a critical partnership period, or the reverse once it runs smoothly.

Principle one: evidence over enthusiasm

Every founder has favourite ideas. The danger in a company builder is that favourites receive resources regardless of results, while less exciting companies with better numbers are starved.

Our protection against this is the continue, stop or scale process. Each company has KPIs written before launch and checkpoints at 30, 60 and 90 days. Allocation decisions are based on what those checkpoints show:

• Are the right customers arriving and activating?
• Are they coming back?
• Are they paying, and staying?
• Does each customer generate more than they cost to acquire and serve?
• Is the team learning faster than the problems grow?

Enthusiasm still matters — it keeps teams going through hard months — but it does not decide budgets.

Principle two: visible per-company economics

You cannot compare companies fairly if you cannot see their economics separately. A group invoice that bundles hosting, AI usage, tools and payroll across companies makes it impossible to say which company is healthy.

At Oryvelon, each company's costs are attributed to that company as far as practical:

• hosting and infrastructure;
• database and storage;
• AI usage, through separate AI projects and budgets;
• email and messaging;
• tools and subscriptions;
• a fair share of shared costs, allocated transparently.

Next to those costs sit revenue, gross margin and the key customer metrics. That view is what makes allocation decisions honest. See Unit economics per product in a shared-infrastructure group.

Principle three: staged commitments

We rarely make large, irreversible commitments early. Instead, investment grows in stages as evidence accumulates.

Each stage is a smaller bet than it would be for a standalone startup, because the foundation already exists. That lets us try more ideas at the early stages while being stricter about which ones advance.

Principle four: move resources away, not just towards

Allocating to winners is the easy half. The hard half is taking resources away from companies that are not working — or that are working but have reached a plateau where more investment will not change much.

We make that easier in three ways:

• Pre-agreed checkpoints mean reductions are expected, not personal.
• Clear definitions of "steady state" let a company that is healthy but not growing fast run efficiently on a smaller share of attention.
• Responsible stopping preserves value when a company or initiative ends — domains, content, code and learning stay in the group. See Continue, stop or scale.

A portfolio where every company always gets a little more is not being managed. It is being hoped for.

Principle five: protect the shared foundation

There is one allocation that is easy to neglect because it does not belong to any single company: the shared operating core. Domain and email security, deployment standards, the AI gateway, measurement, access reviews and cost tracking all need ongoing investment.

If the core is starved, every company slowly inherits problems: outdated standards, security gaps, tools that no longer fit. So a fixed, modest share of build capacity goes to the core every cycle, and improvements are prioritised by how many companies they help. See What is a digital company builder?.

How a typical allocation review works

We review allocation on a regular rhythm, aligned with the group's operating cadence. The review is short and follows the same structure every time.

1. Each company's snapshot. Key metrics against targets, economics, recent checkpoint decisions, and one paragraph from the company's owner on what they need most.
2. The core's snapshot. Open risks, planned improvements, and which companies would benefit.
3. Proposed changes. More, the same or less money, build capacity and founder attention for each company, with reasoning.
4. Decision and record. Changes are agreed and written down, with the date of the next review.

The written record is important. Months later, when a decision looks obviously right or wrong, we can see what we knew at the time and learn from it.

How it plays out across very different companies

The companies in the group have different natural rhythms, and allocation respects that.

• Commerce and services businesses such as Noveniq and WeAreMedia have established models. Allocation focuses on efficiency and steady improvement rather than exploration.
• Software and AI products such as MerchNivo and KeşifAtlası need concentrated build capacity in early stages and careful attention to AI unit economics as they grow.
• Marketplaces such as CastLyra often need founder attention more than money early on — relationships on both sides matter enormously before the network effect starts.
• Education in EduRelia follows the school calendar; allocation peaks before and at the start of terms.
• Consumer products such as ZodiVela benefit from rapid experimentation budgets once retention is proven.
• Service-and-education brands such as Sinem Keser Beauty Academy grow through reputation, content and repeat relationships, where brand investment and quality of delivery matter most.

Mistakes we try to avoid

A few allocation mistakes are common enough that we name them explicitly:

• Equal shares. Dividing budget evenly feels fair and avoids conflict. It also guarantees under-investment in the best opportunities.
• Newest-idea bias. New ideas are exciting; established companies are less so. Evidence should decide, not novelty.
• Scaling before retention. Acquisition spend on a product that does not retain users multiplies losses.
• Ignoring attention. A company with enough money but no founder attention can stall just as badly as one without money.
• Starving the core. Short-term savings on shared foundations become long-term costs everywhere.
• Decisions without records. Without written reasoning, the group cannot learn from its own allocation history.

What this means for partners and investors

If you are considering partnering with or investing in an Oryvelon company, the allocation discipline has two practical implications.

First, the numbers exist. Because each company's economics are tracked separately, there is a clear picture of revenue, costs and customer behaviour for that company alone.

Second, group support is deliberate. When a company receives more of the group's resources, it is because the evidence justified it — and the conditions for continuing that support are written down.

An illustrative allocation round

To make the process concrete, here is a simplified, illustrative round — the kind of reasoning that happens in a review, not a report of specific numbers.

Imagine three companies reaching checkpoints in the same month.

Company A has modest growth, but almost every customer who activated two months ago is still active, and several are paying for higher usage tiers. Its unit economics are positive. The owner asks for more acquisition budget and a small amount of engineering time for the features retained customers request most. The group agrees to a staged increase — a larger budget for one cycle, with a review date and a guardrail: retention must hold at current levels.

Company B had an excellent launch month but weak return behaviour. The owner proposes a bigger marketing push to "keep momentum". The group declines additional acquisition spend and instead moves engineering time to onboarding and the core experience, with a clear question for the next checkpoint: do the people who arrive now come back?

Company C is stable, profitable and growing slowly. It does not need more money; it needs less founder attention so that attention can go elsewhere. The group documents how it runs, sets a steady-state budget and moves its review to a lighter rhythm.

Nobody "won" or "lost" in that round. Each company received what the evidence suggested it could use well.

Signals that trigger an off-cycle review

Most allocation happens on the regular rhythm, but some events justify an immediate review:

• a sudden change in retention, positive or negative;
• AI or infrastructure costs rising faster than usage;
• a partnership or distribution opportunity that needs a quick answer;
• a security or data incident that requires resources to be redirected;
• a regulatory or platform change that affects a company's model;
• a company hitting a hard budget limit.

Off-cycle reviews are short and focused on one decision. They follow the same principle: evidence first, then a written decision.

Scheduling founder attention

Because founder attention is the scarcest resource, we treat it like a budget too. Each cycle, the founders decide roughly how their time will be split across companies and the core, based on where their involvement makes the biggest difference.

A few patterns help:

• Concentrate rather than spread. A company that needs founder attention usually needs a lot of it for a short period — a launch, a key partnership, a pricing change — rather than a little of it forever.
• Delegate steady state. Once a company runs smoothly, its day-to-day decisions should not wait for founders.
• Protect deep work on the core. Standards, security and architecture decisions need uninterrupted time; they get scheduled, not squeezed in.
• Say no explicitly. When attention goes to one company, it is worth being clear about what is not getting attention this cycle.

Allocation and risk

Allocation is also a risk decision. Concentrating resources in one company increases the group's dependence on it. Spreading them thinly reduces the chance that any company succeeds.

We try to keep a balance: established businesses with steady revenue provide stability, while newer products receive the focused investment they need to prove themselves. Because each company is designed to stand alone, a problem in one company does not threaten the others technically — the shared layer is infrastructure and standards, not a single platform that could fail for everyone.

Ten questions every allocation review answers

To keep reviews consistent, each one ends by answering the same ten questions in writing.

1. Which company has the strongest evidence of a recurring, paying customer base?
2. Which company is closest to a breakthrough if it receives more build capacity?
3. Which company needs founder attention most urgently, and for how long?
4. Which company can move to a lighter, steady-state rhythm?
5. Where are costs growing faster than value, and what is the fix?
6. Is any company being kept alive by hope rather than evidence?
7. What does the shared core need this cycle, and which companies benefit?
8. Which risks — security, regulatory, platform, concentration — need resources now?
9. What did the previous round get wrong, and what do we change because of it?
10. When is the next review, and what do we expect to see by then?

Answering all ten takes discipline, especially the sixth and ninth. They are the questions that make a company builder more than a collection of projects.

Worked example: when AI costs jump at one company

Here is an illustrative off-cycle review of the kind described above — a pattern, not a report.

Imagine a relevant visa rule changes in a destination many KeşifAtlası users are exploring. Interest rises, more people take the free eligibility test, and more existing report holders come back to check how the change affects them. AI usage climbs sharply in a few days, and the company approaches its monthly AI budget limit.

The easy responses are both wrong. Raising the budget without thought rewards a cost problem with more money. Switching off AI explanations hurts users exactly when the product is most useful.

Instead, the review asks three questions:

1. Is this demand we want? Yes — it is the product doing its job at a moment of real need.
2. Where is the cost going? Often the same explanation of the same rule is being generated many times. Eligibility itself comes from the verified rules engine; the model only explains the result, so identical explanations can be cached safely. See Latency and caching for AI.
3. Is the most capable model needed for every step? Simple rephrasing and classification can go to smaller, cheaper models, with the capable model kept for the harder explanations. See Model routing.

The decision might be a temporary budget increase with a fixed end date, alongside engineering time for caching and routing. The written record says what the extra money is for and when it stops. Allocation here is not a yes or no to spending; it is a choice about what kind of spending fixes the problem.

Allocating shared costs fairly

Shared costs are where per-company economics usually get distorted. If the group simply divides the core's costs equally, a small, early company looks unprofitable and a large one looks cheaper than it is. Both views lead to bad allocation.

We use a simple order of preference:

Whatever the method, it is written down and applied the same way every cycle. Changing the allocation formula to make a favoured company look better is exactly the kind of drift the process exists to prevent. When the formula itself seems unfair, we change it openly, for everyone, and note the date.

Cheap bets that pay twice

Some allocations produce value in more than one place, and we look for them deliberately.

Noveniq is the clearest case. It is a real store with its own customers and economics, and it has to stand on those. But running it also teaches the group what store operators face every day — the questions that make MerchNivo more useful. Time spent improving Noveniq's operations is judged first on Noveniq's own results; the learning for MerchNivo is a secondary return, not an excuse for weak numbers. See A real store as a testbed.

The same logic applies to shared standards. A privacy or security improvement built for EduRelia, where the bar for child data is highest, often becomes the default for other companies. Investment made where requirements are strictest tends to travel well.

A pre-review checklist for company owners

Before each allocation review, the owner of each company prepares:

• [ ] Current KPIs against the targets written at the last decision.
• [ ] Costs for the period, broken down, with anything unusual explained.
• [ ] One specific request — money, build capacity or founder attention — with what it would change.
• [ ] What the company would do if the answer were no.
• [ ] One thing the company should stop doing to free resources.

The fourth and fifth items matter most. An owner who has thought about the "no" case and found something to stop is making allocation easier for everyone, including their own company.

Summary

Capital allocation is where a company builder earns or loses its value. At Oryvelon we treat money, build capacity and founder attention as resources to be allocated deliberately; we let evidence rather than enthusiasm decide; we keep each company's economics visible; we stage commitments; we are willing to move resources away; and we protect the shared foundation that every company relies on. It is not glamorous work, but it determines which companies thrive.

Questions and answers

How does Oryvelon decide which company gets more investment?

By comparing evidence from each company's checkpoints — activation, retention, paying customers and cost to serve — using per-company economics rather than group totals.

Does every Oryvelon company get the same budget?

No. Spreading resources evenly avoids decisions. Resources move towards companies with the strongest evidence.

What counts as capital in a company builder?

Money, engineering and design time, and the founders' attention. All three are allocated deliberately.

Published by Oryvelon, a digital company builder · About the group · Our companies · More in Company Building

NextDesigning every company so it could stand alone →