Work with me

Three things I can build for you

A portfolio is not a track record with customers, and I will not pretend otherwise. What I can show is the work itself: each offer below links to a public repo you can read, run and check before you write to me.

Lead intake automation

Who it is for. A small business whose form leads get copied by hand into a spreadsheet or table, and sometimes get missed.

What you get

A form (or webhook) wired to the table where you want leads to land, with the fields mapped.
A check script that submits a unique test lead and confirms exactly that lead arrived.
A written spec of the automation, since a Zap is built in an editor and cannot be committed as code.

How it works

You tell me where leads arrive today and where they should end up.
I build it and push a test lead through the real form, not a mock.
I hand over the spec and the check so you can rerun it yourself.

Out of scope

Replacing your CRM.
Plan fees. Some Zapier steps need a paid plan, and that is your account.
Anything past two steps of mapping, unless we agree it first.

Proof

Two automations run end to end on made-up leads. The checks pass 6 of 6 and 5 of 5, and the README lists the limits.

zapier-lead-intake-lab

Storefront catalogue and cart

Who it is for. A shop that wants its own catalogue and cart where the server, not the browser, decides prices and stock.

What you get

A React front end with filters, search, sorting and pagination.
A Spring Boot API that computes cart totals and refuses to oversell.
Tests that run against a real database, and a one-command local setup.

How it works

You send the catalogue shape and the rules that matter, such as stock and totals.
I build the API and the interface together and drive both in a real browser.
You get the code, the test commands and a short note on each decision.

Out of scope

Payment processing and tax rules beyond what we scope up front.
Migrating or restyling an existing hosted shop.
Hosting. The first build runs locally for you.

Proof

37 API tests against a real Postgres container, 25 front end tests, and a browser pass that checks a 390 pixel screen.

spring-react-storefront

Private RAG over your documents

Who it is for. A small firm that wants cited answers from its own PDFs and Word files, and wants the files kept on its own machines.

What you get

Upload for PDF, DOCX, TXT and Markdown, then questions answered with citations.
A local stack: Qdrant in Docker and a model served by Ollama, so documents are not sent to a hosted service.
A small eval on your documents, so you see where retrieval misses before you rely on it.

How it works

You pick a small set of documents and a few questions you already know the answers to.
I ingest them, run the questions and show you the hits and the misses.
We tune the retrieval on what failed, then I hand over the setup steps.

Out of scope

Any promise about accuracy: the eval shows you the hits and the misses on your own documents.
A hosted version. The stack runs locally.
Conversation memory that survives a restart.

Proof

hit@1 of 85% vector and 90% hybrid on 20 questions. The README spends most of its length on what broke, including a ranking bug that every test missed.

enterprise-rag-knowledge-base

Start with one message

Tell me what you copy by hand today, or what you want to ask your documents. I will tell you straight whether it fits one of these.

Send a message

Charting course...