APAC base
Fractional CTO for Singapore Startups
Singapore is a small domestic market that companies use as a base for a much larger one, and that shapes almost every technical decision. Architecture that only ever considers Singapore tends to need rework the moment you expand into Indonesia, Vietnam, or Australia.
The timezone is effectively the same as mine, so this is the market where a fractional arrangement feels least remote. There is no handoff, no overnight lag, no waiting until tomorrow for an answer.
How this actually works
What is different about building in Singapore
Build for the region, not the island
Multi-currency, multi-language, and country-specific payment rails are far cheaper to design for than to retrofit. If the plan is Indonesia or Vietnam within two years, the schema should know that now. This is the single most common expensive mistake I see in Singapore-headquartered products.
PDPA has real engineering consequences
Consent, purpose limitation, retention, and mandatory breach notification within a fixed window. That last one is an engineering requirement, not a policy one: if you cannot determine what was accessed and by whom, you cannot notify accurately inside the deadline.
MAS expectations if you are anywhere near financial services
Technology risk management guidelines set concrete expectations on access control, change management, incident response, and vendor oversight. Whether they bind you or merely inform what partners ask for, they are the bar your architecture will be measured against.
Data residency across a fragmented region
Indonesia, Vietnam, and others have their own localisation rules. Assuming one region in one cloud will carry you across APAC is the assumption that forces a painful migration later. I design so region is a deployment decision rather than a rewrite.
A senior talent market that is small and expensive
Singapore engineering salaries are high and senior candidates are scarce, which is why so many teams there run distributed across the region. I will give you a straight read on what to hire locally, what to distribute, and how to keep a split team coherent.
How an engagement runs
Week one, month one, month three
Week 1
I find out what is actually true
Architecture review, codebase read, and honest conversations with every engineer you have. You get a written assessment at the end of it: what is solid, what is risky, what is going to break, and what it costs to fix each one. No slide deck, just a document you can act on.
Month 1
The bleeding stops and the roadmap becomes real
I fix or contain the things from week one that were actually urgent, and rebuild the technical roadmap so it has dates you can believe. If you are hiring, the role is written and the interview loop exists. If you are pre-launch, scope gets cut, usually by a lot.
Month 3
It runs without me in the room
Ship cadence is predictable, the team knows the standard, security and infrastructure are at the level your customers expect, and the decisions are documented. If the engagement is a bridge to a full-time CTO, this is where I start hiring my replacement.
Why me, for this specifically
Experience, not a capabilities deck
Plenty of people can advise on singapore startups. Fewer have shipped in it, been wrong in it, and had to fix it with their own name on the commit. Here's what I'm bringing.
- Full timezone overlap with Singapore working hours
- M.Tech in Cybersecurity, directly relevant to PDPA and MAS technology risk expectations
- Built products for multi-country markets across three continents
- Comfortable designing for regional expansion rather than a single market
Pricing
Priced at $100 an hour. Not counted at it.
I value my time at $100 an hour and the retainers are sized from that, but the hours are a floor I commit to rather than a cap I bill against. If a week needs more, it gets more. A full-time CTO in the US runs about $260,000 a year before equity; I'll do that job for $60,000 at 150% commitment. Three-month minimum, then month to month.
It does not all have to be cash. The split is negotiable, from a small equity component up to roughly half and half, depending on your stage and how long we expect to work together.
Technical Advisor
$1,500
per month
Minimum 15+ hours a month
A senior technical brain on call. For founders who mostly need the big decisions checked rather than someone in the codebase.
Fractional CTO
$5,000
per month
Minimum 50+ hours a month
Around 50 hours a month as your acting CTO, usually two days a week. I own technical direction, and the roadmap ships because someone senior is accountable for it.
Embedded CTO
$8,000
per month
Minimum 80+ hours a month
Around 80 hours a month, usually three days a week, hands on the keyboard. Everything above, plus I build the hard parts myself instead of delegating them.
Questions
Singapore startups, specifically
Do you understand MAS requirements?
I understand the technology risk expectations well enough to build to them, and I work with your compliance advisors on interpretation. What I own is making sure access control, change management, and incident response actually meet the bar rather than being described as if they do.
We plan to expand across Southeast Asia. Does that change anything?
It changes a great deal, and it is much cheaper to account for now. Currency, localisation, payment rails, and data residency all get designed in rather than bolted on. This is the conversation I most want to have before you build, not after.
Is the timezone a problem?
No. It is the closest overlap of any market I work in, so a Singapore engagement runs much like an in-house hire in terms of availability.
More general questions about cost, commitment, and how this compares to a full-time CTO are answered on the main fractional CTO page.
Earned, Not Claimed
What the founders and teams I build with say
I had the pleasure of working with Kunal while building out my MVP and I have to say that it was pleasure to both interact and work with him and his team. As a first time founder, I had a lot of self doubt and internal ruptures, however Kunal's calm, never-say-die and never-panic attitude often helped bring me back to center. I can't vouch for him enough.
Anand Tahiliani
Founder, Debaser Technologies
I had the pleasure of working closely with Kunal during my time as a Product Manager at DhunGuru. As our CTO, Kunal and his team at Panicle Tech worked closely with me across the entire product journey, from building and launching our mobile apps to developing and maintaining our web platforms. His technical expertise, ownership, and willingness to collaborate made a real difference, and I genuinely enjoyed working with him throughout the journey.
Anirudh Joshi
Product Manager, DhunGuru
Kunal helped us architect Mosler's core platform, connecting smart lock hardware, our cloud dashboard, and PMS integrations into one reliable system. The foundation he helped design in those early days still scales with us today.
Pranav Kapoor
Co-Founder, Mosler
Building in singapore startups? Let's talk.
Thirty minutes. Tell me what you're building and where it's stuck, and I'll give you a straight answer on whether I can help.
Book a 30-min callSend me a message