I help businesses define and build the software they need for their next stage of growth.
The work usually starts before the code: where the business is trying to go, what is getting in the way, and what kind of system would actually help it move.
Sometimes that means building a product from zero. Sometimes it means turning messy operations into software. Sometimes it means helping a founder shape the technical path before the first serious build.
See selected work ↓What this usually looks like
Growth exposes the systems a business does not have yet.
The work often starts before the code. The first question is not which stack to use. It is what kind of system the business needs in order to move.
A new product has to become real
A founder sees the opportunity, but the first serious version still needs to be shaped, scoped, architected, and built.
Operations have outgrown the workaround
The business runs on spreadsheets, WhatsApp, manual checks, duplicated effort, and knowledge that lives in people’s heads.
A platform needs technical direction
The idea is bigger than a simple website. It needs a backend, data model, workflows, integrations, and decisions that will hold up later.
The business needs a technical partner
Not just someone to take tickets, but someone who can understand the business, make tradeoffs, and stay close to the outcome.
The short version
I started as an engineer, then spent a decade as the person responsible for turning ideas into working systems.
Over time, I moved from writing code to leading technical work, helping scale a company from a small team of around 10 people to about 100. That experience shaped how I see software.
Good software is not just clean code. It is a system that fits the business, the people, the timing, the constraints, and the next stage of growth.
Today I run Tiny Edges. I work with founders and SMEs to shape and build the software their business needs next.
Sometimes it is a straightforward build. Sometimes, when the opportunity is strong and the fit is right, I work closer to the outcome through a stake, revenue share, or longer-term partnership.
What system does this business need in order to grow?
Selected work
As of May 2026
A few examples of growth needs turned into working systems, from founder-led products to platforms and internal tools.
The kind of work I take a stake in: shape the product, architect the platform, build the MVP, and stay close enough for the outcome to matter.
Built with EC Pixels Asia for Malaysia’s running and community events. Participants browse, reserve a spot, pay, and get a QR confirmation in seconds.
I leave it here on purpose. It became part of the lens I use to read every business I build with today.
How the work happens
The same loop, adjusted to the business.
The process is deliberately simple. Understand the growth problem, shape the system, build the smallest serious version, and keep learning from real use.
Listen
Understand where the business wants to grow, what is blocking it, and what cannot be ignored.
Shape
Turn the ambition into a clear product, workflow, platform, or system design.
Build
Create the smallest serious version that can be used, tested, and improved.
Stay close
Ship, learn, adjust. Where I share in the upside, I stay close to the outcome.
When it makes sense to talk
You have a real growth problem, and the system matters.
I am especially interested in founder-led businesses, SMEs, and early ventures where the opportunity is practical, the constraints are real, and the technical work has to connect back to the business.
See if it's a fit, what to expect, and FAQ → Contact