A technical partner for fintech founders.
For founders with an idea, a prototype or a codebase that needs an owner.
You have a financial product to build and no technical co-founder, or a developer who needs direction. You do not need an agency with account managers. You need one experienced engineer who understands money systems, makes the technical decisions with you, and then builds the thing.
What I take on
Technical discovery
Before anything is built: what you actually need, what your third-party access really allows, where the legal questions sit, and what a first release should leave out.
Architecture and feasibility
A written architecture you could hand to any team: components, data model, integrations, failure handling, hosting and running cost, with the trade-offs in plain language.
MVP development
Backend, front end, database and deployment, built in milestones on a staging environment you can use from the first weeks.
Infrastructure and operations
Environments, CI, backups, monitoring and alerts, plus runbooks so the system can be operated by someone other than me.
Working with your developer
If you already have an engineer or a front end, I read what exists, keep what is sound, and take the architecture and the risky parts.
Longer-term technical leadership
After launch I can stay on as your technical lead: roadmap, code review, hiring help and the releases that carry real risk.
Proof, not promises
- SolveMYMy own productI built a three-sided marketplace alone, end to end: Go API, Next.js website, Flutter apps, infrastructure and store releases. It is live.
- MT5 Manager API service and real-time risk monitorFreelance · TradersFlow (TRFC)On a live prop-trading platform I owned the MetaTrader 5 integration and the monitor that fails accounts within seconds of a breach.
- Payments and crypto back office at a live brokerJob · CFI FinancialMy full-time role is on a live multi-asset broker: payment methods in production, a crypto back office and event-driven services.
How we can work together
Start small. Commit when it works.
Every engagement starts with a written scope. You know what you are getting, what it costs and what is left out before any work begins.
- 01Fixed fee · 1 to 3 weeks
Technical discovery sprint
I review your requirements, existing code and third-party access, then deliver a written architecture, a feasibility and risk report and a milestone plan. Yours to keep, whoever builds it.
- 02Paid by milestone
Fixed-scope MVP build
A defined first release, built in milestones on a staging environment you can use throughout. You pay for delivered milestones, not for hours.
- 03Monthly
Founding engineer contract
I join as your hands-on technical owner: architecture, backend, front end, infrastructure and releases, working directly with you.
- 04Part-time · monthly
Fractional technical lead
You already have a developer or a small team. I own the architecture and the risky parts, review the work and keep delivery honest.
I quote each engagement in USD after a first call. I work from Malaysia with no agency layer, so the budget goes into engineering, not account management. I price on scope and responsibility, and I am not the cheapest option.
- You work with the person doing the work
- Written scope and milestones
- Source code, access and documentation handed over
- NDA on request
How we would work
- 01
A short call
A no-obligation conversation about what you are building, what exists already and what success looks like.
- 02
A written scope
What I will build, what I will not, the risks and the price. Larger or unclear projects start with a short, paid discovery sprint.
- 03
Small, visible releases
You see working software early and often, on a staging environment you can click through.
- 04
Handover and support
Source code, access, documentation and runbooks, with ongoing support if you want it.
Questions
- Are you a fractional CTO or a founding engineer?
- The work is the same: architecture, building, infrastructure and technical decisions, done hands-on. "Fractional CTO" fits when you already have developers and need direction. "Founding engineer" fits when I am the one building. I am happy with either label and prefer to describe the work.
- Can one engineer really build a fintech MVP?
- A focused first release, yes, and I have done it for a marketplace of comparable breadth. What makes it possible is scope discipline: one integration route, manual operations where automation can wait, and a modular codebase other engineers can join later. I will tell you early if your scope needs more people.
- What does a first engagement look like?
- Usually a paid discovery sprint of one to three weeks. You get a written architecture, a risk list and a milestone plan with prices. You can then build with me or take the documents to another team.
- How do you use AI coding tools?
- Every day, for speed. Each change still goes through the same checks as hand-written code: tests, a read of the diff and a run on staging. AI assistance does not replace verification, least of all on money paths.
- How much of your time do we get?
- I take on a small number of engagements at a time and I am clear about capacity before we start. We agree working days, overlap hours and response times in writing.
- Who handles licences, KYC policy and regulation?
- You and your advisers. I am an engineer, not a lawyer or a regulated entity. I design the system so that the controls they ask for (approvals, audit trails, record keeping) can be met, and I will say when a feature needs a legal answer before it is built.
Tell me what you are building.
A few lines are enough: what it is, where it stands today, and what you need from an engineer. The form is just below, or email me if you prefer. I reply within two working days.