Builder · Products · Automation · Websites

If it needs to exist,
I'll build it.

Custom AI tools, internal applications, automation systems, websites. I work across a broad stack, and I skip the part where you talk to a project manager who passes messages to the person actually doing the work. That person is me.

Build Areas

What I
build

Three typical areas where I spend most of my time.

AI-powered tools & applications

Products and internal tools where AI is the core, not a tacked-on feature. Conversational interfaces, document intelligence, automated decision support, custom internal copilots. Built on the major LLM APIs and designed to work inside your team's actual workflow.

LLMsWorkflowsCopilots

Internal tooling & automation

The operational layer most companies underinvest in. Custom dashboards, process automations, internal systems that cut manual overhead. Built for how your team actually works, not the generic version of it.

DashboardsAutomationOps

Websites, products & MVPs

From landing pages to full product MVPs. I work with Vue and Nuxt for frontend applications, WordPress where it fits, and custom code where that is the right call. Fast, clean, and handed over with documentation.

Vue/NuxtWordPressMVPs
Process

How a project
works

A clear route from scope to handover, without agency theatre in the middle.

01

Scope

We spend 30 to 60 minutes on what you actually need, not just what you first thought you needed. I'll tell you if there is a simpler approach, or if what you described is really three projects.

02

Proposal

Fixed scope and fixed price where possible. You know what you are getting and roughly when.

03

Build

I work in sprints. You see progress early. When something is unclear, I ask rather than guess.

04

Review

You give feedback on a working thing, not on a mockup. One round of revisions is built into most projects.

05

Handover

You get the code, the documentation, and a walkthrough session. No lock-in. No dependency on me to keep it running unless you want ongoing support.

Stack & Tools

What I use,
without being dogmatic

I do not have a preferred stack that I force onto every project. Vue and Nuxt for frontend apps. WordPress for content sites where it earns its place. Python for backends and AI integrations. n8n and Make for automation. OpenAI, Anthropic, and others for AI features.

I also use AI coding tools heavily, not because I cannot write the code, but because building fast and building well are no longer as separate as they used to be. That benefits your timeline and your budget.

VueNuxtWordPressPythonn8nMakeOpenAIAnthropic
Example Builds

A few
examples

Anonymized, but concrete enough to show how the work looks in practice.

Full-stack product build · Startup

Sponsorship platform

Built the complete platform and all operational automations for a sponsorship marketplace, from database architecture to the user-facing product to the internal tooling keeping day-to-day operations running.

Outcome: product, operations, and automation shipped as one connected system.

LLM-powered application · B2B SaaS

AI process discovery tool

Co-built an AI system that maps and analyzes business processes by talking to teams in natural language and turning those conversations into structured documentation.

Outcome: prototype to production in three months.

Internal system · E-commerce

Commerce operations dashboard

Built the internal tooling layer for order flows, warehouse visibility, and partner operations so one team no longer had to work across several disconnected systems.

Outcome: one operational view across orders, inventory, and execution.

Builder

Have something in mind?

I take on a limited number of projects at a time. If you have something concrete to scope, or just an idea you want a real reaction on, reach out.