A real number to call.
You get my direct line. Not a help desk, not a ticket queue, not a different person each time. The same builder who scoped your project answers when you call.
Hiring a builder should not feel like rolling dice. Here is exactly what happens after you send the first email, what is expected of you, what you can expect of me, and where we land at the end. No mystery boxes.
Same path every project. The pace varies, the steps do not.
A few sentences is plenty. Even rough ideas are fine. The point is to get a real conversation started, not to write a perfect brief.
I read it the same day, usually within hours. If it is something I should take on, I reply with a couple of clarifying questions and a time to talk. If it is not a fit, I tell you that too, and where you might look instead.
Twenty to forty minutes on the phone or video. We talk through what you are trying to do, why now, and what success looks like to you.
Your business, the problem you are solving, who your audience is, what platforms or tools you already use, your timeline, and rough budget. I take notes. You ask questions. We figure out together whether this is a good match.
After the first call, you get a written document that lays out exactly what is included, what is not, the timeline, and the price. No "starting from" softening, just the number.
Project objectives, deliverables broken out line-by-line, technical approach, timeline by phase, payment milestones, what you provide versus what I produce, and what happens if scope changes during the build. You read it, ask questions, and we revise together if anything needs adjusting.
Once the scope is right, you sign, the first invoice goes out, and the build begins. This is the handoff from "talking about it" to "building it."
For most projects, fifty percent at start, twenty-five percent mid-project, twenty-five percent at delivery. Smaller jobs invoice fifty-fifty. Established clients move to net-30 after the first project. I confirm receipt and we set the kickoff date.
The actual work. Design, code, configuration, content integration, testing. You stay informed without having to chase me down.
You get a status update every week, minimum. For longer projects, I post progress to a shared dashboard you can check anytime. Major milestones (design approved, beta ready, content loaded) get their own dedicated check-in. If a date is going to slip, you hear it from me before it slips, with a reason and a new date.
Before launch, you get the full build to review on a staging URL. You walk through it, list anything that needs adjustment, and we fix it together.
Two rounds of revisions are included in standard project pricing. That is enough for almost every project. Anything outside the original scope gets quoted as a change order before the work happens, so there are no billing surprises. I push back if I think a revision will hurt the project, but the call is always yours.
Site goes live, final invoice goes out, and you have a working build with documentation. But the relationship does not have to end here.
Most clients move to a maintenance plan after launch. That keeps the site updated, monitored, and improving. Some add SEO. Others come back six months later for the next project. There is no pressure to subscribe to anything, but the option is right there if you want it. Either way, you own everything we built together.
The day-to-day texture of a project. Not the contract, the actual habits.
You get my direct line. Not a help desk, not a ticket queue, not a different person each time. The same builder who scoped your project answers when you call.
Weekly progress in writing, minimum. For longer builds, a shared status board you can check anytime. You should never have to email me asking "where are we?"
If a date is going to slip, you hear it from me before it slips, with a reason and a new date. Not after. Not from your CFO asking why the launch did not happen.
If you ask for something I think will hurt the project, I tell you so. I will explain why, suggest an alternative, and if you still want it, we do it. The call is always yours, but you get a real opinion first.
Scope is written. Changes are written. Decisions are written. Verbal agreements get followed up with email so there is no "I thought we said..." three months later.
Code, content, accounts, hosting, domains. You own all of it. Even if we part ways. Full export on request, no fees, no drama. That is non-negotiable.
Projects work when both sides hold up their end. Here is what helps the work move faster.
If your question is not on the list, just ask. The first email is the right place.
Rough ideas welcome. Quick reads, straight answers.
Open a project file →