Travel platform · 2025
Guide Lanka
Full-stack product build
A connected journey from finding a local guide to planning the visit.
Read case studyFull-stack developer · Colombo, working globally
I turn complex workflows into useful software.
I help startups shape and build web products, dashboards, and connected services from interface to infrastructure.
Start with the people, the task, and the friction. Then decide what to build.
Interfaces, APIs, and data should support the same clear product journey.
Give errors, access, and the small details the same care as the first screen.
Understand the workflow. Make scope explicit. Build in reviewable steps. Test the product in real use.
More about meBuilt products and a clearly labeled mobile concept, each shown through the decisions behind it.
Travel platform · 2025
Full-stack product build
A connected journey from finding a local guide to planning the visit.
Read case study
Operations dashboard · 2025
Dashboard and application build
A clearer view of stock and what needs attention.
Read case studycare / booking
Available appointments
← Clinic A
Select a day
Available times
A concept confirmation screen. No appointment has been made.
Independent concept · illustrative information only
Mobile product · concept
Independent concept design
A speculative mobile flow for finding an appointment and keeping the next step clear.
Read case studyFocused engineering, from the first useful version to a stronger foundation.
Responsive, database-backed applications designed around the way your team or customers actually work.
A considered foundation for subscription products, from authenticated workspaces to the first useful release.
Conversation features that help people get answers, coordinate work, and move through a service without friction.
Backend services and deployment foundations that keep application data moving safely and predictably.
Mobile experiences that make essential tasks easy to complete on the move.
Desktop tools for focused work that benefits from a larger screen and a dedicated workspace.
An example workflow; each project is scoped before work begins.
We map users, tasks, and friction. You receive a short problem brief and priorities. Typically 2–5 business days.
We agree on the core journey, features, and review points. You receive a written scope and delivery plan. Typically 3–5 business days.
I deliver reviewable increments around the agreed core journey.
I test key paths, prepare handover, and launch after review.
I work across interfaces, backend services, and the decisions that hold a product together.
More about mePractical ideas on AI, the web, and the infrastructure behind useful products.
Start with a repeated task, define what a useful answer looks like, and keep people in control.
Read articleA practical path from a local Astro build to a preview you can inspect, with a few deployment traps to avoid.
Read articleKeep inference on the server, validate the request, and return an answer the interface can review or recover from.
Read articleWhat to expect before we talk about a project.
A short description of the problem, who will use the product, and what a useful first version needs to do. The project brief helps you organize what you already know.
No. We can shape the scope together and prioritize the tasks users need to complete first.
Yes. Depending on the project, I work across interfaces, APIs, data integration, access controls, and deployment.
We review the workflow and constraints, agree on a clear scope, and break the build into reviewable steps.
Tell me what you are working toward. We can turn the first conversation into a practical next step.
I reply within 24 hours.