Cap Table Software for Southeast Asian Startups: What a Singapore Holdco Doesn't Solve

You started the company in Jakarta, Ho Chi Minh City, or Manila. Then a seed investor's term sheet showed up with a structure attached: incorporate a Singapore Pte Ltd, make it the holding company, and turn the entity you actually built into an operating subsidiary underneath it.

This isn't unusual. A Singapore holdco is the default structure regional VCs ask for — it's investor-friendly corporate law, no capital gains tax on share disposals, and a jurisdiction every fund's counsel already knows. For a founder in Indonesia, Vietnam, or the Philippines, it's often the price of admission to institutional capital.

What nobody mentions in the same conversation is that you now have a cap table that lives in two places, a shareholder meeting requirement your incorporation lawyer didn't flag, and an ESOP pool that has to make sense across currencies. Search "cap table software" from Jakarta or Ho Chi Minh City and you'll land on Carta, Pulley, or Qapita — tools built for a single entity, a single share register, and usually a single legal system. None of them start from the structure you're actually running.

The holdco isn't a rebrand — it's two cap tables

When the Singapore Pte Ltd goes in above your existing company, the local entity doesn't disappear. It keeps the employees, the local contracts, the operating licenses, and — critically — often the original ESOP grants issued before the holdco existed. Meanwhile, new equity, new investor rounds, and usually the go-forward option pool sit at the Singapore level, because that's where investors want to hold their stake.

A few things break in that split, consistently:

• The exchange isn't 1:1 by default. Founders and early shareholders in the operating entity get issued shares in the Singapore holdco under a ratio set in the swap agreement, not automatically. Whoever was tracking ownership in a spreadsheet now has to recompute every stake, including anyone who converted a SAFE right before the swap.
• The operating entity has its own capital rules. If the local entity is an Indonesian PT PMA, it's the only vehicle a foreign shareholder can legally hold shares in directly, and it carries its own paid-up capital requirements tied to its business classification. That entity isn't a shell you can ignore once the holdco exists — it's still the thing regulators, banks, and local employees deal with.
• Old ESOP grants at the operating entity need a bridge. Options or phantom equity issued before the flip don't just migrate. Someone has to decide — and document — whether they convert into Singapore holdco instruments or stay local, and on what schedule.
• Multi-currency stops being a rounding error. You raise in USD or SGD, deploy into IDR, VND, or PHP at the operating entity, and pay local employees in local currency while granting equity denominated in Singapore dollars or US dollars. A cap table that only stores one currency per stakeholder silently gets this wrong the first time someone asks what a grant is worth in take-home terms.

None of this shows up in the incorporation paperwork. It shows up eight months later when an investor's associate asks for a consolidated ownership view and the honest answer is two spreadsheets and a Slack thread explaining the difference.

The shareholder meeting nobody scheduled

Here's the part that catches founders who came from a Delaware-only mental model completely off guard: your Indonesian operating entity has an annual general meeting of shareholders — RUPS — as a hard legal requirement, not a governance nicety.

Indonesia's Company Law (Law No. 40 of 2007) requires every PT, including a PT PMA, to hold an annual RUPS within six months of fiscal year-end. It's mandatory every year regardless of whether anything changed at the company. As of December 2025, the approval also has to be documented in a notarial deed and reported to the Ministry of Law through the SABH system within 30 days, and the meeting itself must be registered in AHU Online. Miss it, and the sanctions escalate from a written warning to suspended system access — which is a real operational problem when SABH is also where you file the routine paperwork that keeps the entity in good standing.

If there's a single shareholder, Indonesian law allows a circular resolution instead of a physical meeting — but every shareholder with voting rights has to sign it, which for a company with a Singapore holdco parent and minority local shareholders often isn't the case.

This is structurally the same problem Saudi founders hit with general assembly requirements: a shareholder-level governance obligation that Carta, Pulley, and most Delaware-first tools have no concept of, because it doesn't exist in US corporate law. The mechanics — quorum, shareholding-weighted voting, a recorded resolution — are the same shape whether the law calls it a general assembly or a RUPS. Most cap table tools stop at board resolutions and leave shareholder-level governance to whatever the company secretary does on paper.

Where the regional tools stop

Qapita is the closest thing Southeast Asia has to a category standard — it's Singapore-based, and it's built specifically around cap table and ESOP administration for the region. If your only need is tracking a cap table and running an option program, it's a reasonable, purpose-built choice.

Where it and comparable regional tools generally stop is everything around the cap table: a fundraising pipeline that tracks investor commitments and stage, a data room with per-investor tracked access, and a governance layer that handles the shareholder meeting, not just the board. Founders end up running the cap table in one tool, the raise in a spreadsheet or a generic CRM, and the data room in a shared Drive folder with no visibility into who actually opened what.

Carta's APAC presence is real but oriented around companies already comfortable in a Singapore-as-Delaware-equivalent mental model — clean for the holdco level, silent on the operating entity's local obligations.

Where Govy fits — and where it honestly doesn't yet

Govy runs on an event-sourced, append-only ledger: every change to the cap table — the swap ratio, a SAFE conversion, an option grant — is a logged event, not a cell edit that can be quietly overwritten. For a company running a Singapore holdco over a local operating entity, that matters because the two-cap-table problem doesn't get solved by discipline alone; it gets solved by a system where every number has a traceable origin.

The general assembly module — shareholding-weighted voting, quorum computation, recorded minutes — was built first for Saudi general assembly requirements, but the underlying mechanics are the same ones an Indonesian RUPS needs: who showed up, what percentage of shares they represent, what passed, and a permanent record of it. You can run that meeting inside the same login as the cap table instead of documenting it separately and hoping the two stay consistent.

The fundraising CRM tracks investor commitments, pipeline stage, and one-click SAFE-to-cap-table conversion — useful precisely at the moment a Singapore holdco round is being negotiated. The data room serves files on demand from your own Google Drive, with per-investor tracked visits, so materials shared with a Singapore-based fund don't sit in an unwatched folder link.

To be direct about the boundary: Govy doesn't yet generate jurisdiction-specific legal templates for Singapore, Indonesian, Vietnamese, or Philippine entities the way it does for US/Delaware and Saudi ESOP grants. If you need an auto-generated, legally reviewed RUPS resolution template or a Singapore-specific option agreement today, that's still a job for local counsel. What Govy replaces is the fragmented tracking underneath — the spreadsheet holding two entities' worth of ownership, the separate document where shareholder votes get recorded, the CRM nobody updates, and the data room with no read receipts. Governance and cap table tracking work across jurisdictions now; jurisdiction-specific document generation is currently shipped for US/Delaware and KSA only.

We wrote a related breakdown of the equivalent problem for African startups doing a Delaware flip — same underlying pattern of a cap table splitting across two entities, different jurisdiction: Your Cap Table Split in Two. And if the next step for your Singapore round is getting materials in front of investors cleanly, we've laid out what that data room actually needs in our data room checklist.

The structure is the easy part

Setting up the Singapore holdco takes your lawyers a few weeks and a filing fee. Running the cap table, the ESOP pool, and the shareholder governance underneath it correctly is the part that has to hold up for years — through the next round, the next hire, and the next RUPS deadline that arrives whether or not anyone remembered to put it on the calendar.

Govy is $24.99/month, everything included — cap table, ESOP, treasury, fundraising CRM, tracked data room, and shareholder governance, in one login. Start at govy.tech.