Services

I work with founders and small teams who need software built properly the first time — from the architecture underneath a product to the manual process that's quietly eating someone's week.

Software & systems design

Backend architecture and APIs built to handle real growth, not just demo traffic.

I design the layer underneath a product — the database schema, the API contracts, the service boundaries — before writing a line of application code. That groundwork is what keeps a system easy to extend a year in, instead of held together with patches.

PHP LaravelDjangoFastAPIJava Spring Boot

Websites & web applications

Full products built end to end — interface, backend, and the database between them.

Whether it's a marketing site or a full dashboard, I build the front end and the backend that powers it, so what ships is a working product, not just a design file.

ReactJSJavaScriptPostgreSQLMySQL
See it in action: Polluwatch →

Business process automation

Replacing manual, repetitive work with a pipeline that runs itself.

Most automation requests aren't really coding problems — they're a manual process nobody has mapped out yet. I map it, then build the pipeline that runs it automatically, with an alert only when a human actually needs to step in.

n8nGoogle SheetsEmail & WhatsApp integrations
See it in action: Tenant Comms & Payment Tracker →

AI-powered solutions

AI features grounded in your own data, not a confident guess.

I build AI features using retrieval-augmented generation, so answers come from your actual documents and data instead of a general-purpose model improvising. That's the difference between advice you can trust and advice that sounds right.

RAG pipelinesChromaDBGPT-3.5 / Gemini
See it in action: NutriPepper →

SEO & technical performance

Fast, structured sites that search engines and users both understand.

A site nobody can find is a site that doesn't work yet. I handle the technical fundamentals — page speed, semantic markup, metadata, sitemaps — that decide whether search engines take a site seriously.

Core Web VitalsSemantic HTMLOpen Graph
1

Discover

Understand the real problem before proposing a solution — most projects go wrong here, not in the code.

2

Design

Plan the architecture and scope that actually fits the problem, not the biggest possible build.

3

Build

Ship in working increments you can see and react to, not a single big-bang release.

4

Support

Stay involved after launch — every system needs tending, and I'm the one who already knows how it works.

Have a project like this?

Let's talk