Three things I build

No. Most clients hire me for the website, and the brand work folds into that process because it improves the site itself. Email automation makes sense once you've got steady traffic or inquiries and want to warm leads up before the sales conversation. The right package depends on where your bottleneck actually lives. We keep the scope narrow if that's the right move, or connect the full system if the business is ready for it.

Great. In that case I spend less time extracting the message and more time pressure-testing how clearly the brand reads online. Sometimes the positioning is solid and we just sharpen how it shows up on the page. Sometimes there's a gap between how you describe yourself internally and what a buyer actually understands in the first ten seconds. I won't reinvent you. I'll make the site represent you accurately.

Yes. Your domain, your email, your content, your analytics, and the systems connected to the site all live in your accounts. I won't trap your website inside a closed platform that only I can manage. The handoff matters because a good build should increase your leverage, not create a new dependency. You'll know what's in the stack, what each piece does, and how to keep moving without me if you ever want to.

That's exactly why discovery exists. You don't need to arrive with a polished brief, an exact sitemap, or a final visual direction. I ask structured questions, study the market around you, and show you concrete options instead of making you invent the answer alone. The process is built to turn vague instincts into clearer positioning. You don't need certainty to start. You just need enough honesty and context for us to find the signal together.

Yes. Copy is part of the value, because design without language usually leaves the conversion problem unsolved. I write from interviews, research, your existing material, and the way you naturally explain the work out loud. I skip the polished agency language that could belong to anyone. I write copy that sounds like you, clarifies what you do, and gives the right buyer enough confidence to take the next step.

The first real draft usually lands within 48 to 72 hours after kickoff. That gives us something concrete to react to early instead of waiting a week for abstract updates. Most sites finish in two to four weeks, depending on page count, integrations, and how fast decisions get made. If we're adding email automation, heavier content work, or more rounds of positioning, the timeline can stretch a bit, but the process still moves quickly.

I don't build on WordPress for this work. I prefer a lighter modern stack that gives you better performance, cleaner code, and fewer plugin-driven maintenance problems. That matters for SEO, reliability, and long-term clarity. If a business has a specific constraint that genuinely requires WordPress, I'd rather say so directly than force the wrong implementation. The stack should support the outcome, not create friction every time you need to update the site.

After launch I make sure the connected pieces are behaving, show you how to handle the basic updates you're likely to need, and leave the project in a state you can actually navigate. If you want ongoing support I can stay involved for maintenance, refinements, or content work. If you don't, that's fine too. The point is to leave you with a site that keeps working instead of one that immediately becomes mysterious or fragile.