Questions, 

Answered. 

Webflow gives you production-grade markup and hosting without a build pipeline to maintain, and it hands editing back to your team. For marketing sites that need to change weekly, that is faster and cheaper to own than a bespoke front end — and when a project genuinely needs custom code, it still gets it.

That is a large share of the work I take on. I start with an audit of the structure, CMS collections and interactions, then fix what is brittle before adding anything new — so improvements land on a foundation that will not fight you six months from now.

Four stages: a kickoff to agree scope and success criteria, design or design review, build in staging with weekly checkpoints, then a launch pass covering performance, SEO and accessibility. You see working pages early and often rather than one reveal at the end.

Yes. Send yours over and I will sign it, or I can provide a standard mutual NDA before any details are shared. Unreleased work stays out of my portfolio until you say otherwise.

Both, though most projects lean one way. I can take a Figma file straight to a pixel-accurate build, or start from a brief and handle the design as well. If you already have a designer, I slot in as the build partner and keep the handoff tight.

A monthly block of hours you can spend on new pages, CMS work, interactions or fixes, with a shared queue so you always know what is next. No ticket expires unused inside its month, and there is no minimum commitment beyond the current one.

Feedback is collected on the staging site itself, so comments are anchored to the element they refer to instead of living in a thread. Each milestone includes two rounds of revisions; anything past that is billed hourly and quoted before it starts.

Then start with a call. Describe the outcome you need and I will tell you which plan covers it — including when the answer is that you do not need one, and a one-off project would serve you better.