A call, then I write down what we're building, what we're not building, and what done looks like. You get a fixed scope and a fixed price before any work starts.
· Scope document
· Timeline
· Quote
2–4 days
02
Design
Wireframes first, so we argue about structure before anyone argues about colour. Then high-fidelity screens in Figma using your real content.
· Wireframes
· Figma designs
· A clickable prototype
1–2 weeks
03
Build
Front end, API, and database. You see a staging link from week one and can comment on it any day, and there is no month-long silence.
· Weekly staging builds
· A running list of what's done
3–6 weeks depending on scope
04
Handover
Deployment, a walkthrough of the admin, and written documentation. Then 30 days of support for anything that breaks.
· Live site
· Source code
· Documentation
· 30 days of bug support
2–3 days, then 30 days support
About
Who you’d be working with
08 / 10
SM
4:5
X +0.00 Y +0.00
Based
Colombo, Sri Lanka
Timezone
UTC+5:30
Experience
5 years
Works as
Software Engineer & Full-Stack Developer
I'm a full-stack developer in Colombo. For five years I've been building the whole thing, from interface to API to database, for clients who need a working product rather than a handover between three contractors. Most of that work has been booking sites, loyalty systems, and internal tools for businesses in Sri Lanka and Europe.
I design before I build, and I think that's why the projects tend to survive. A wireframe costs an afternoon; the same argument after the API is written costs a week. So I'd rather show you a grey-box layout early and have you tell me it's wrong. I also tend to over-invest in the admin side of a project, the part the client uses every day and nobody puts in a portfolio, because a beautiful site the owner can't update is a site that's dead in six months.
I also build with Arduino, making one-off boards for whatever the problem happened to be, rather than one project I can point at. It is a different constraint to work under: a couple of kilobytes to fit in, no refresh button, and a thing that either does what you wired it to do or sits there. So if a project needs software that reaches hardware, whether sensors, controllers, or something physical that has to report back, that is work I can take on rather than pass to someone else.
Stack
21 technologies
Primary
01.NET Core
02C#
03React
JavaScriptFrontend
BootstrapFrontend
PythonBackend
FigmaDesign
ArduinoHardware
PostmanTooling
JavaScriptFrontend
BootstrapFrontend
PythonBackend
FigmaDesign
ArduinoHardware
PostmanTooling
HTMLFrontend
Node.jsBackend
SQL ServerDatabases
Adobe PhotoshopDesign
GitTooling
ViteTooling
HTMLFrontend
Node.jsBackend
SQL ServerDatabases
Adobe PhotoshopDesign
GitTooling
ViteTooling
Tailwind CSSFrontend
PHPBackend
MySQLDatabases
WordPressCMS & platforms
GitHubTooling
VS CodeTooling
Tailwind CSSFrontend
PHPBackend
MySQLDatabases
WordPressCMS & platforms
GitHubTooling
VS CodeTooling
Frontend
React, JavaScript, HTML, Tailwind CSS, Bootstrap
Backend
.NET Core, C#, Node.js, PHP, Python
Databases
SQL Server, MySQL
Design
Figma, Adobe Photoshop
CMS & platforms
WordPress
Hardware
Arduino
Tooling
Git, GitHub, Postman, Vite, VS Code
Contact
09 / 10
Have something to build?
Tell me what you're working on and what it needs to do. I reply within one working day, and I'll tell you honestly if I'm not the right fit.