Services

What I build

Three kinds of work, scoped and priced before anything starts.

AI tooling integration

For businesses that want a specific, repetitive task automated — sorting inquiries, pulling details out of documents, or drafting routine replies — not a chatbot added for its own sake.

Includes

  • Wiring an AI tool into a workflow you already use, like inbox intake, document handling, or a lookup over your own files
  • A drafted result — an extracted record, a suggested reply — that someone on your team reviews before it goes anywhere
  • Testing against real examples from your business before it goes live

Scoped separately

  • Training a custom model from scratch
Discuss this service

Cloud and systems integration

For businesses that already run a website or software, but the pieces don't talk to each other.

Includes

  • Connecting the tools you already use so they share data automatically
  • Testing the connection with your real data before it goes live

Scoped separately

  • Buying or licensing the third-party tools themselves
Discuss this service

Custom website design and build

For small businesses that need a real website, not a template with a logo swapped in.

Includes

  • Design and build of the full site
  • A working contact path, not a bare email link
  • A walkthrough of how to update it yourself after launch

Scoped separately

  • Ongoing content writing or photography — you provide the words and images, or we scope that separately
Discuss this service

Process

How a project runs

Four steps from the first call to launch.

  1. 1

    First call

    I ask about the business and what needs to get built, then tell you honestly whether it's a good fit.

  2. 2

    Scope and price

    You get a written scope and a starting price before I start any work.

  3. 3

    Build

    I build it and check in along the way, so nothing surprises you at the end.

  4. 4

    Launch

    I put it live and walk you through how to run or update it yourself.

Common Questions

Frequently Asked Questions

What's the typical timeline?

Most sites take three to five weeks from the first call to launch, depending on how much content you have ready and how many rounds of feedback we go through. Systems integration work is usually faster — a few days to two weeks. You get a specific estimate in the written scope before anything starts, not a vague range.

What happens if I'm unavailable during the project?

I build in checkpoints, not one long silent stretch, so a slow week on your end doesn't stall things — I keep working on what I can and flag anything that's genuinely blocked. If you go quiet for an extended period, I pause the engagement rather than let it drift, and pick back up whenever you're ready.

Who owns the code and content?

You do. At handover you get the source code, every account, and the content itself — nothing stays locked to me or to a platform you'd need my help to leave. If you want another developer to take over later, they can, without calling me first.

Is accessibility part of the build?

Yes, as a baseline, not an add-on: semantic HTML, keyboard navigation, sufficient color contrast in both light and dark themes, and alt text on every image. I test with a keyboard and a screen reader before calling a page done, not just by eye.

Contact

Tell me what you need built.

One form, one reply, no sales team in between.

Start a Project

Prefer email? [email protected]