Web apps & APIs
Serverless web apps and APIs with payments, email, and dashboards — built on Netlify Functions and Node, no server to babysit.
Serverless web apps, AI integrations, automations, internal tools, and desktop utilities — built by hand to solve a specific problem and stay up in production. If it’s repetitive, manual, or held together with spreadsheets, it can probably be software.
From a one-off script to a full app — serverless-first, hand-coded, and tested against real data.
Serverless web apps and APIs with payments, email, and dashboards — built on Netlify Functions and Node, no server to babysit.
Claude-powered features wired into real products — chat, prompt/refine pipelines, lead qualification — grounded on your data, not the open web.
Scrapers, data pipelines, and batch jobs that kill repetitive, manual work — the stuff eating hours of your week.
Admin panels, ops hubs, quote and lead inboxes, PIN-gated tools — the screen your team actually runs the business from.
Python (PySide6) and C# / WPF apps — file and asset tooling, optimizers, converters, and batch processors.
Connecting Stripe, SMTP / email, databases, and third-party APIs into one flow that just works.
Not mockups — live products and tools running in production. For the deep cut — including a CAD engine you can run in your browser — see the capabilities page.
Turns a plain idea into a structured prompt via the Claude API, with Stripe pay-as-you-go credits — all on Netlify serverless functions, with no account system and no backend to maintain.
The command center behind Hand Coded Web: a PIN-gated site-audit tool, project board, quote inbox, client onboarding, and edit-request system — scattered client work pulled into one screen.
Utilities that keep a 500-resource game server fast: a texture / asset optimizer, an LOD de-duper, and a crash-log analyzer that turns thousands of log lines into the one actual culprit.
I don’t just prototype. CookMyPrompt, Skillwright, and Resourcery are live products with real users, payments, and uptime — built on exactly this stack. The best case study is software that ships and stays up.
Python and C# / WPF for desktop and automation, PySide6 for GUIs, JavaScript and Node on Netlify Functions for serverless web apps, Stripe for payments, MariaDB for data, and the Anthropic Claude API for AI features — all version-controlled in Git. No heavy frameworks unless a job genuinely needs one; the same hand-coded discipline behind the FiveM work and every site I build.
We map the problem, the inputs and outputs, and what “done” looks like. You get a fixed scope and quote before any work or payment.
I build it in the open, version-controlled, and test it against real data — not a happy-path demo that falls over on day one.
Deployed where it needs to live, documented so you understand it, and supported after handoff.
Serverless web apps and APIs, AI integrations, automations and scripts, internal tools and dashboards, and desktop utilities in Python or C#. If it's custom and it needs to actually work in production, it's in scope.
Yes — CookMyPrompt is a live example: a no-login AI product built on the Anthropic Claude API. I wire AI into real workflows, grounded on your data rather than the open web.
Usually, yes. If it's repetitive and rule-based — data entry, scraping, file processing, report generation — it can almost always be scripted or turned into a small tool that does it for you.
Yes. Admin panels, ops hubs, quote and lead inboxes, PIN-gated tools — the kind of internal software the HCW Hub is built from.
It's scoped per project. Small automations and scripts are quick and inexpensive; full apps and dashboards are larger. Either way you get a fixed quote before any work or payment.
Send a note through the contact form with the problem you're trying to solve. I'll reply with questions, a scope, and a timeline before anything is committed.
The write-ups behind the services — free, no gate.
Tell me what you’re trying to solve — you’ll get a straight answer, a scope, and a quote.