Why I had multiple companies for products I eventually combined

If you look up my public business filings from a couple of years ago, you will find more than one corporate entity.

There was Shopmatey Pte. Ltd., incorporated in Singapore, alongside an entity associated with Omni.

When people see a solo founder or early-stage builder with multiple incorporated companies, they often jump to one of two conclusions:

1. They assume you are running an elaborate tax optimization strategy.
2. They assume you are an over-eager founder playing enterprise dress-up with an imaginary holding company.

The reality was far more mundane.

I did not incorporate separate entities because I wanted an empire on paper. I did it because early startup infrastructure is surprisingly fragmented.

At different points in my building journey, having separate corporate containers was the fastest way to solve practical, unglamorous problems:

• opening business bank accounts;
• accessing fintech payment tools;
• qualifying for startup cloud credits;
• keeping legal liabilities separated between an active commerce product and an experimental social app.

Looking back, those corporate structures served a purpose. But they also came with a steep administrative tax that eventually convinced me to streamline everything.

The banking hurdle for early builders

When you build your first software product in Singapore, one of the first walls you hit is traditional business banking.

Opening a corporate account at a traditional brick-and-mortar bank can be a frustrating process for an unbacked software startup:

• hefty initial deposit requirements;
• mandatory minimum monthly average balances;
• monthly maintenance fees if balances dip below five-figure thresholds;
• weeks of manual paperwork and in-person branch visits.

When you are bootstrapping a software idea with minimal capital, tying up thousands of dollars just to avoid monthly bank fees makes no sense.

That reality pushed me toward modern fintech alternatives like Aspire, Wise Business, and Revolut Business.

These platforms were built for digital-first businesses:

• instant multi-currency account creation;
• zero maintenance fees or low minimum balances;
• seamless virtual debit cards for developer tooling and server subscriptions;
• simple integrations with payment gateways like Stripe.

However, each entity you incorporate has to go through its own compliance onboarding, identity verification, and source-of-funds documentation.

When I started Shopmatey, having a dedicated Singapore private limited company allowed me to establish a clean financial container for merchant payment processing, e-commerce transactions, and local vendor agreements.

When Omni started growing as a distinct communication and social platform, spinning up a separate corporate identity initially felt like the cleanest way to keep its finances, vendor accounts, and payment rails completely isolated from Shopmatey.

The startup cloud credit ecosystem

Another major factor that influences early corporate decisions is the startup credit ecosystem.

Major technology providers offer generous credit programs to help early startups survive their first few years:

• Amazon Web Services (AWS Activate);
• Google Cloud for Startups;
• Stripe processing fee waivers;
• SaaS partner perks offered through platforms like Aspire and startup incubators.

These programs are lifesavers for bootstrapped builders. A credit package can easily cover thousands of dollars in cloud infrastructure, database hosting, object storage, and API costs while you are finding product-market fit.

The catch is that these credit allocations are tied to specific legal entities, verified domains, and business registration numbers.

When I was building Shopmatey, its infrastructure was powered by startup credits granted to its entity. When Omni emerged as a new product with its own server architecture and AI workloads, having a distinct corporate profile enabled it to apply for developer programs independently.

For a young startup, access to cloud credits is not a vanity metric; it is pure runway.

Merchant liability and legal separation

Beyond banking and cloud credits, there was also the practical issue of merchant risk.

Shopmatey was a commerce platform where independent creators sold products, processed digital payments, and managed customer orders. That meant dealing with:

• merchant terms of service;
• payment dispute resolutions;
• chargeback liability;
• customer refund policies.

Omni, on the other hand, was an experimental communication platform exploring real-time messaging, social graphs, and AI agents.

From a risk management standpoint, mixing customer payments and merchant transactions from an e-commerce platform with the experimental server infrastructure of a new social app felt messy. Keeping the legal entities separate provided a clear firewall: if a dispute occurred in the commerce layer, it had zero legal or operational bearing on the communication app.

For an early builder navigating multiple product categories, that separation provided peace of mind.

The hidden tax of multiple entities

While having separate companies solved immediate tactical problems, the administrative friction accumulated quickly.

What many first-time founders do not realize is that every private limited company in Singapore comes with fixed statutory and financial overhead, regardless of whether it generates ten dollars or ten million dollars:

The Overhead of Multiple Entities:
┌────────────────────────────────────────────────────────┐
│ Annual Corporate Secretarial Retainers                 │
├────────────────────────────────────────────────────────┤
│ Annual ACRA Annual Return Filings & Registered Address │
├────────────────────────────────────────────────────────┤
│ Bookkeeping, Financial Statements & Tax Returns        │
├────────────────────────────────────────────────────────┤
│ Multi-Account Reconciliation & Bank Verification KYC   │
└────────────────────────────────────────────────────────┘

For a solo founder, the financial cost is noticeable, but the mental cost is worse:

1. Corporate secretarial retainers: Singapore requires every private limited company to appoint a resident company secretary and maintain an official registered office address.
2. Statutory filings: Annual Returns must be lodged with ACRA via BizFile+, alongside director resolutions and annual general meeting documentation.
3. Accounting and corporate tax: Every company requires dedicated bookkeeping, annual unaudited financial statements, and corporate tax filings with IRAS (Form C-S).
4. KYC re-verification: Whenever a fintech platform or bank updates its compliance policies, you have to submit director declarations, proof of address, and business models for every single entity.

I reached a point where I was spending meaningful time every quarter acting as an administrative clerk for my own projects rather than writing code and talking to users.

The complexity had outgrown the benefit.

From fragmentation to consolidation

When I decided in early 2025 to consolidate Shopmatey into Omni, the decision was not just about merging codebases and user accounts.

It was also about consolidating the corporate and financial footprint.

Once Shopmatey became a core feature set inside Omni rather than an independent standalone product, maintaining separate legal entities and distinct bank accounts became entirely redundant.

Streamlining the structure allowed me to:

1. Unify financial operations: All developer subscriptions, server costs, and revenue streams flowed through a single, clean banking hub.
2. Eliminate duplicate compliance: Annual corporate secretarial retainers, ACRA filings, and tax preparations were cut in half.
3. Consolidate infrastructure billing: Server hosting, database clusters, and domain renewals were brought under one unified billing account.

The administrative burden vanished, leaving a clean, simple operational structure that matched the unified product.

What I would tell an early founder

If you are an indie developer or early founder thinking about how to set up your business, here are the lessons I took away from navigating this process:

1. Don't build an empire on paper before you build a product

It is tempting to design an elaborate multi-company structure with holding companies and operating subsidiaries. Resist that urge. Every entity you create is a recurring bill and a compliance burden. Start with the simplest legal container that allows you to open a bank account and accept payments.

2. Embrace fintech tools early

Traditional banks in many jurisdictions are not designed for early-stage software companies. Platforms like Aspire, Wise, and Revolut make opening digital multi-currency accounts accessible without trapping capital in minimum balance requirements.

3. Temporary structures are fine

It is completely acceptable for your corporate structure to reflect temporary constraints. If setting up an entity allows you to access essential banking rails or startup credits, do it. Just be prepared to clean up and consolidate the structure once the product landscape matures.

4. Optimize for focus, not theoretical perfection

The best corporate structure is the one that gets out of your way and lets you focus on building software that people want to use.

An incorporated company is just a legal tool.

Build the product first. The paperwork will follow.

Back to work.