Product Engineering
Full products, built end to end — from first Figma frame to a production deploy your users can hit.
- SaaS platforms
- MVP builds
- Web applications
- E-commerce & marketplaces
- Dashboards & internal tools
Services
Three ways
to ship together.
Engagements are scoped tightly and shipped to production. No retainers that quietly become maintenance contracts.
AI & Automation
LLM features and agent workflows that are grounded, observable and actually useful in production.
- AI product features
- LLM integrations
- AI agents & workflows
- RAG pipelines
- Workflow automation
Systems & Infrastructure
The unglamorous machinery underneath: APIs, data, deploys and the performance work nobody sees until it's missing.
- Backend APIs & services
- Database design & migrations
- Real-time sync & queues
- Platform integrations
- Performance optimization
Process
How an engagement runs.
- 01
Scope
A call, then a written brief: what we're building, what we're deliberately not building, and what done looks like.
- 02
Architect
Data model, service boundaries and deploy story decided before the first component — the decisions that are expensive to change later.
- 03
Build
Shipping to a real environment from week one. You see progress running, not in a status update.
- 04
Harden
Instrumentation, error paths, performance and the migration story. The part that separates a demo from a product.
- 05
Hand over
Documentation, runbooks and a walkthrough — so the system outlives the engagement.
Questions
The things people ask first.
- What kind of software do you build?
- Full products, end to end: SaaS platforms, web applications, marketplaces, internal dashboards, and the backend APIs and databases underneath them — plus AI features built on LLMs where they earn their place. The work so far spans event tech, restaurant software, AI tooling, marketplaces and travel.
- Where are you based, and do you work with clients abroad?
- Sri Lanka, working remotely with clients worldwide. Engagements run asynchronously with a regular call; the working day is 09:00–18:00 Sri Lanka time, which overlaps the European morning and the Australian afternoon.
- Can you build a website as well as an application?
- Yes. Marketing sites, e-commerce and content-driven websites are part of the product engineering work and are built on the same stack as the applications — which is why they end up fast, measurable and straightforward to keep updating, rather than a template somebody else has to maintain.
- What does an engagement look like?
- Five stages: scope, architect, build, harden, hand over. It starts with a call and a written brief covering what is being built, what is deliberately not being built, and what done looks like. Code ships to a real environment from week one, so progress is something you can use rather than something you read about.
- What technologies do you work with?
- TypeScript and JavaScript across the stack, with React and Next.js on the front end, Node.js and Python services behind it, and PostgreSQL as the default datastore. Mobile work is React Native. Infrastructure is chosen per project rather than from a fixed template.
- Do you take over an existing codebase?
- Yes — inherited projects are ordinary work. That usually starts with an audit of the architecture, the data model and the deploy story before anything is changed, because the expensive decisions in an existing system are the ones already made.
- How do I start?
- Send an email or book a 30-minute intro call from the contact page. No brief or deck is required: what you are building, what is blocking it, and whether this is the right fit is enough for a first conversation. You get a reply within 24 hours, including a no.