How I Work
What to expect when we work together
One of the most common questions I get is: "What's it actually like to work with you?"
Fair question. Working with someone new—especially on something as important as your digital presence—shouldn't feel like a leap of faith.
Here's how I approach projects, what you can expect from me, and what I'll need from you to do my best work.
My Work Process
We Start With A Real Conversation
Before any proposal, we talk. I need to understand what you're trying to accomplish, what's working, what isn't, and what success looks like. This isn't a sales call—it's discovery to determine fit.
Sometimes this reveals what you think you need isn't the solution. I'll say so honestly, even if it means recommending something smaller or different.
If aligned, you get a written proposal: specific deliverables, clear scope, realistic timeline, costs, and what's explicitly out of scope to prevent surprises.
Communication Is Clear And Regular
Once we start, you'll hear from me regularly—weekly updates for active projects covering what's completed, what's in progress, decisions needed, and what's next. I respond to questions within one business day, usually faster. When I need something from you, I'm clear about what, when, and why it matters for the timeline.
We work in phases: discovery, design/strategy, development, testing, launch. You see work as it develops, not all at once—allowing us to course-correct early if needed.
Feedback Is Structured Not Endless
When I share work for review, I'm clear about what kind of feedback I need.
Early stages: big-picture reactions, strategic direction, whether the approach feels right. Later stages: specific refinements, copy tweaks, final polish. I don't ask "what do you think?" without context.
Revisions are built into the process. I don't charge extra for reasonable refinement within agreed scope. But "reasonable" means refining the agreed direction, not completely changing it after approval.
Timelines Are Realistic
I build buffer into timelines because things always take longer than they should.
Content arrives late, feedback takes time, unexpected technical issues appear, life happens. Timelines that assume everything goes perfectly always slip.
I'd rather tell you it takes six weeks and deliver in five than promise four and miss the deadline. If something's genuinely urgent, we discuss that upfront and adjust scope or availability accordingly.
You Dont Need To Be Technical
I handle hosting, domains, integrations, code, and all the backend complexity.
I explain things in plain language when decisions need your input, but you're never left wondering what the jargon means. If you are technical and want implementation details, I'm happy to discuss. But it's not required.
My job is to make the technical side invisible so you can focus on your business.
Training And Ongoing Support
When we launch, I make sure you know how to manage what we've built.
This usually means a walkthrough session where I show you how to update content, add pages, or make basic changes. I record these sessions and provide written documentation so you can reference them later.
Launch isn't goodbye. Most clients continue working with me in some capacity—ongoing support retainers, periodic updates, new features, or just knowing I'm available when questions come up.
What I Need From You
Good work requires good collaboration.
I need you to be responsive when I ask for feedback, content, or decisions. Delayed responses delay timelines. I need you to be honest—if something isn't working, say so early. And I need you to trust the process, especially in early stages when work doesn't look polished yet.
You'll also need to provide what we agreed you'd provide—content, images, access to accounts, timely feedback. The timeline assumes you'll hold up your end.
Why Process Matters
Process might sound boring, but it's what makes good outcomes possible.
Clear expectations, regular communication, structured feedback, and realistic timelines create the conditions for doing excellent work without stress, confusion, or conflict. When both sides know what to expect, we can focus on the actual work instead of managing anxiety.
Every project is different, and the framework adapts to what the work actually needs. What doesn't change: clear communication, realistic timelines, no surprises, and work that meets the standards we agreed to.