I help businesses shape 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 carry it forward.
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 build that really matters.
New revenue, better operations, a product idea, a platform, or a market opportunity that is starting to become real.
The work is still manual, scattered, unclear, or technically fragile. The ambition exists, but the operating shape does not.
A product, platform, portal, internal tool, workflow, or technical foundation designed around how the business actually works.
Selected work
a few examples of business needs being shaped into working systems.

I lead the platform architecture and technical direction, while the Tiny Edges team handles implementation. Longer-term partnership with a share in the outcome.

Build partner on a fee-based engagement. I advise on the technical approach and architecture, and work alongside their internal team on delivery. The Tiny Edges team handles implementation.

Technical partner with a stake in the venture, involved in the product direction, technical decisions, business-model validation, and path towards market fit.
I usually work through a fee-based project or retainer. When the opportunity is strong and the fit is right, I may work through a stake, revenue share, or longer-term partnership instead.
Each case note explains how I am involved.
Oryza Technologies was my first venture, and it did not make it. I keep it on the record because it changed how I build. the retrospective
What this usually looks like
a few common forms the work tends to take.
A new product has to become real
A founder sees the opportunity, but the first serious version still needs to be shaped, scoped, and turned into something people can use.
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 person behind the work
I studied engineering, but I found my work in software, products, and systems.
Over time, I moved from writing code to leading technical work, supporting the systems of a company as it grew from around ten people to about a hundred. That shaped how I see software: not just as clean code, but as a system that has to fit 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. I lead the work personally and, when the build requires it, bring in a small team through Tiny Edges across software and design. 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?
How the work unfolds
start small enough to learn, serious enough to matter.
Assess the situation.
Understand where the business wants to grow, what is blocking it, and what cannot be ignored.
Shape the system.
Turn the ambition into a clear product, workflow, platform, or system design.
Build the first version.
Create the smallest serious version that can be used, tested, and improved.
Refine it with reality.
Ship, learn, and refine the system as the business, users, and constraints become clearer.
Latest notes
recent thinking on software, systems, and building.
Terence Tao's rock-climbing analogy names something I already believed when I named the business: the only way up is the handhold within reach, not the leap I keep wanting to make.
The name is a reminder that small steps beat trying to do everything at once and that the small details and advantages matter.
If you can describe where your business is trying to grow, I can help you work out the system it needs.
see the contact page to check fit, first steps, and common questions.