AI Engineering · $1,500 fixed
You'll build it. I'll teach you the tools while you do.
Three sessions, about six hours in total. You set up the same toolchain I use — GitHub, Claude Code, and Azure — wired together so that saving a change publishes it. Then your site goes live on it, whether you build it during the sessions or arrive with one AI already made you and nowhere to put it. You do the typing. Every account is in your name. At the end you can change your own site without calling anyone.
Why this is different
You are not buying a website.
An agency sells you a website and a reason to come back every time you want a phone number changed. A website builder sells you a subscription and keeps the keys. Both arrangements quietly depend on you never learning how any of it works.
This is the other trade. You end up with the tools, the accounts, and the working knowledge — so the first site is the cheapest thing you get out of it. The second one costs you nothing.
The part that makes it work: the training and the work are the same six hours.You are not taught on a practice project and then sent away to apply it on your own. You learn the tools by shipping the actual site, with someone experienced watching the parts that are easy to get wrong.
This site runs on the same setup. I did not pick something for you that I would not use myself.
What you have at the end
Six things, all of them yours.
- A GitHub account and repository, registered to you, holding your site
- Claude Code installed and connected to that repository
- An Azure Static Web App serving your site over HTTPS on your own domain
- Push-to-deploy wired up — you save a change, the live site updates itself
- No monthly platform fee, because there is no platform to pay for
- The ability to change your own site, because you are the one who built it
You enter your own credentials, in every account. I never hold your passwords, and there is nothing to transfer if you decide you would rather not work with me again.
How the sessions go
Three sessions, roughly six hours.
Roughly this order. The sessions flex around where you get stuck, which is usually the most useful part of the whole thing.
- 01
Set up the accounts — GitHub, Azure, and Claude Code — in your name, with you doing the clicking.
- 02
Connect them to each other, so that Claude Code can work in your repository and your repository can deploy to Azure.
- 03
Build your site, or finish the one you already started with AI. You drive Claude Code; I sit alongside and correct course when something is about to go sideways.
- 04
Point your domain at it, get HTTPS working, and put a contact form on it that actually delivers.
- 05
Go live, then change something on purpose — so you have done it once with help before you do it alone.
Scope
Fixed price means a fixed target.
The target is a static marketing site. That is a deliberate boundary rather than a limitation — it is the right size of project to learn on, because everything you build is real and nothing you build can break a customer's payment.
What's included
- Three sessions, about six hours in total
- Training in Claude Code, delivered by using it on your real site rather than a practice exercise
- All three accounts set up in your name, with you entering your own credentials
- The full toolchain connected end to end, deploying on save
- A walkthrough of buying a domain or a Claude subscription if you do not have them yet
What's not
- An application — payments, customer logins, booking, a database. That is different work and a different conversation
- Copywriting, logo design, or photography. You bring what your site should say
- Ongoing changes. After the three sessions you can make them yourself, which is the entire point
- A support retainer. Further help is a separate engagement, priced when you need it
Hosting a static site on Azure costs essentially nothing, and a domain renews for around twenty dollars a year. Both are billed to you by those providers directly. I do not mark them up and I do not hold the accounts.
And then
A good outcome is that you don't need me again.
For the website, most people don't. That is what they paid for. The ones who come back come back with something bigger — because once you can direct AI to build software, you start seeing the manual processes in your business differently.
That is how the HealthCare Comp engagement went. Scott set up the toolchain, built his own site, then built a working internal application with AI. When real work started depending on it, the architecture and hosting it had been prototyped on were not built to carry that — and that is a different job.
Never written a line of code?
That's the normal starting point, and it isn't the obstacle you'd expect — knowing your own business well enough to say what the site should do is the harder half, and you already have that. Tell me what you'd want it to say.