"Done for you" build days.

You already know how your process runs. It just doesn't run itself.

You have a way of doing things, especially for repeated projects.

It lives in a Google Doc, the open tabs permanently in your browser, a couple of spreadsheets, and your head. It works perfectly well when you have one or two things on the go.

But when life gets busy, it stops working, and you lose track of where you're at.

Build days are a commitment to putting that process somewhere it can actually live. Not a template or a course. The real thing, whether it's a dashboard, an automated system or a combination of both, built with you so that you'll actually use it.

An AI Home for Your Work

If you've been frustrated with AI in the past, it's likely because you've been working in a chat window.

You describe what you need done, it's semi-helpful, and then you close the tab.

A chat can't track your work over time. It has no way of fully understanding the scope of your work and what's relevant for the next time you need it.

It's a good thinking partner, but it can't hold all of your thoughts and background knowledge in one place, or keep you accountable by surfacing relevant information when you need it.

That's the gap we'll aim to close with Build Days. Somewhere for the work to live, so that it's actually useful when you need it most.

What the Process Looks Like

Book an 8 hour day, which I'll fully dedicate to building your system.

Before the day, you'll share the details of what you want to build and set up your accounts on the platforms I'll be using. I'll send instructions, and can set some up on your behalf if you prefer.
On your Build Day you'll be there for the first hour or two for scoping, then get on with your work while I lay the groundwork and bring it to life. I may check in occasionally for clarification if needed.
We'll do a review at the end of the day for feedback, and I'll set Claude up to make additional changes overnight, so you're not just left with the first version.
Within the next 48 business hours, depending on other bookings, I'll do a handover and everything is yours to keep.

A Living System

Think of what we build together as a foundation.

The best systems adapt with you as you work and find ways to make them better, so one build day isn't meant to be the end of the process.

After handover, you'll own everything, in your own accounts, so you can continue to add new elements and refine what we've made over time.

You may want to pair your Build Day with a place in my six week cohort, where you'll learn to use Claude Code and can spend time extending the system we've built, so that it's yours for life.

I'll support you to change anything you don't like or make updates and additions, so you're never relying on an external developer when something in your business shifts.

Or, take what we've made and run with it!

If you're not planning to join a cohort, you'll need to book a minimum of two build days, to allow time for refinements and a full handover.

You own all of it

I'll build everything inside your personal or company accounts, so there's no handover at the end and no moment where it transfers. It will be yours the whole time.

That means the code, the data, the templates, the prompts and the workflows. Nothing is licensed back to you and nothing is proprietary to me. At the end of the day you can revoke my access, and I'll tell you how.

It's also built on widely used tools, so if you ever want to move it somewhere else or hand it to a developer, you can.

What about confidential information?

If your work involves confidential data, we'll plan for that and structure your system accordingly.

As part of your Build Day prep, I'll also show you how to strip personal details out of any documents you send me, so the system is built on your processes, but I don't see your real numbers or client information.

What it costs

$1,500 + GST for Day 1, then $1,000 + GST per additional day.

The rate covers:

The Build Day itself, including the prep work and scoping session.
Foundations from my own projects that can be reused rather than rebuilt.
My Claude Max subscription, with faster models and higher limits than a standard plan, so the day produces considerably more.
The overnight background run for any first-round adjustments.
A handover document within 48 business hours.

Ongoing Costs

Depending on what we build, you may incur the following ongoing costs, paid directly to the providers through your accounts, and never through me.

Claude Pro, about $30 a month, cheaper annually. This is what you use to keep making changes with Claude Code, which isn't included on the free plan.
For a dashboard or system that lives online, hosting costs around $29 a month. There is a free tier you could use for a personal system, but it's not licensed for commercial use.
Database, free at the volume most businesses here will use.
Emails from the system (e.g. daily updates or messages to users), free up to 100 messages a day.
Anything generative, charged on use. We'll estimate your use during scoping and leave anything out that isn't worth it. As an example, our podcast dashboard runs on around a dollar a week if we use every AI feature.

What's not included

Ongoing maintenance or support after the day. That's what the cohort is for.
A guaranteed feature list. We'll agree on the priorities on the morning and build as far as a day goes.
Anything needing a licence, integration or API you do not already have. We can talk about what you'll need and set anything relevant up before I build.
Bulk migration of historical data. We'll use examples of your existing templates and documents as a reference when setting up your structure and processes, but pulling everything in will waste time on the day that is better suited to a build. If the data is important, we can build in a way for you to import it all later.

Questions

How long until I can use it?
You'll see what's been built in our end-of-day wrap-up, and I'll do a full handover within 48 business hours. After that, it's yours to use.
Do I need to know how to code?
No, I'll set up the foundations for you, and you'll be able to make any updates in plain English.
Can I just do this myself from scratch?
If you want to! Join the cohort and I'll get you started in Claude Code.
What if I don't like what gets built?
We'll aim to avoid this by scoping together as clearly as possible through your pre-work and our time together at the start of the day. You'll have the chance to give feedback at the end of the day for Claude to work on overnight, and we'll do our best to make something as useful as possible, within the limits of the day. From there, you'll have full ownership to keep building and make any changes you need, or you can book additional time.
Can you work with the tools we already have?
Usually. We'll plan for this as part of your pre-work and scoping process, or if you want to check in advance, send me an email.
What happens if I get stuck after my Build Day?
If you're part of the cohort, you'll have ongoing access to me through the weekly workshop sessions, office hours and session replays to refer to. Otherwise, reach out and book some additional time, either a full day or a shorter support call.

Ready to book?

[Send me an email] with a quick overview of what you're looking for and I can tell you whether a Build Day is a good fit. If I need more detail we can jump on a call.