One page, done properly
A single page that has to convert — a launch, a campaign, a product. Design and build, mobile first.
- 1 page, up to 8 sections
- Design in Figma, then built
- Contact or signup form wired up
- Roughly 1–2 weeks
// services
Design and build, by one person.
No account manager, no handoff between a designer and a developer who've never spoken. You brief one person and that person is accountable for what goes live.
// the work
What a project actually includes
Most quotes hide what's missing. Here's the full list, so you can compare mine against anyone else's.
Phase 01
Design
Desktop and mobile laid out in Figma before a single element gets built. You see real content in real widths, not a pretty mockup that falls apart at 390px. Two rounds of revisions are included, and I'd rather you use them here than after the build.
Phase 02
Webflow build
Built to the design, not near it. Every breakpoint checked on real devices, interactions that work on touch as well as hover, and CMS collections structured around how you'll actually publish — so adding a case study or a job posting doesn't need a developer.
Phase 03
Launch & handover
Domain connected, SSL live, analytics in, meta tags and sitemap done, redirects mapped if you're replacing an existing site. Then a short recorded walkthrough of your CMS so your team can publish in week one instead of emailing me.
After
Two weeks of support
Included, not billed. Anything broken gets fixed; anything you're unsure how to do, I show you. After that we either part ways cleanly or agree a retainer — no automatic monthly charge you have to remember to cancel.
// how projects are shaped
Three shapes most projects take
Every quote is fixed before work starts. Ranges below are a starting point, not a price list — scope moves the number.
Marketing site
The one I do most. A full site with a CMS your team runs afterwards without help.
- 4–8 pages
- CMS collections (blog, work, team, jobs)
- Full design system in Figma
- Recorded CMS walkthrough
- Roughly 2–4 weeks
Dev-ready design
For teams who build in-house. Because I build in Webflow myself, I design knowing what a developer will hit.
- Figma file with real component variants
- Tokens for colour, type and spacing
- States and breakpoints documented
- A call to walk your developer through it
// inside a build
What the process looks like from your side
Every project starts with the boring part: a colour palette and a type scale written down as real tokens, so the build matches the design and your developer never has to guess a value.
// before you ask
Questions I get every time
Why Webflow?
You get a real CMS without a maintenance burden: nothing to patch, no updates that quietly break a layout, no hosting to babysit. For a marketing site that has to look exact and load fast, it's the shortest path from an approved design to a live page. If your project genuinely needs something else, I'll say so rather than force the tool.
What do you need from me to start?
Your copy, or a decent draft of it, plus logo files and any brand assets. Content is the thing that delays projects most often, not design. If your copy isn't ready, we can still start on design — I'll use realistic placeholder text rather than lorem ipsum so the layout is tested against real lengths.
What if I don't like the design?
Two revision rounds are included, and the design phase exists precisely so this gets resolved before anything is built. If we're two rounds in and it still isn't right, that's usually a brief problem rather than a taste problem, and we go back to the brief. I'd rather fix it there than build something you're lukewarm on.
Do you write the copy?
Not as a service, but I will tell you when a section isn't working as written, and suggest a structure that would land better. Layout and copy aren't separable — a headline that's twice as long changes the design.
Who owns the site when we're done?
You do. The project is transferred to your own Webflow account, and the Figma file is yours. Nothing stays hostage on my account, and you're not locked into me for future changes.
How do payments work?
Half up front, half on launch, against a written scope agreed before anything starts. Larger projects can be split into more milestones. If scope changes mid-project, we agree the change and the cost in writing before I do the work — you never get a surprise invoice.
// let's work together
Tell me what you're building.
Send a few lines about the project, your deadline, and a link to anything that exists already. I reply within one business day, and I'll tell you straight if I'm not the right fit.
Available