Questions, answered straight

I build the site that turns your traffic into calls and signups. That means strategy, layout, copy direction, and a custom website your team can run on its own after launch.

Builds start at £3,400 and scope decides where above that yours lands: page count, whether the copy exists, and how many tools need connecting. Every published figure is on pricing. The floor is not the quote, though. You get one fixed number after a short call, and the audit that sets it is delivered in 5 working days.

Usually two to four weeks for a focused site. Bigger builds with custom pages or a CMS take longer, and you get a dated timeline before any work starts.

Yes. Every site I ship is mobile responsive by default, and I test it on real phones and tablets rather than just shrinking a browser window.

Hire someone if the site has to sell. Templates are fine for a hobby page, but a service business website needs structure built around how your buyers actually decide.

Because it is often the first real impression a buyer gets. A vague or dated site makes a strong business look risky, and you lose leads before anyone reaches out.

Yes. If the foundation is solid I keep what works and fix the parts that lose people. When the whole thing fights you, a rebuild usually costs less than patching.

Website strategy is deciding what the site has to do before anyone opens a design tool. You need it, because a good-looking site with no plan just sits there and quietly underperforms.

I pull it out of you first. A short session on who you serve and why you are different shapes the messaging, so the design actually says something.

I handle direction and structure, and I can write the words or work from yours. Either way the copy and the layout get designed together, never bolted on at the end.

Yes. I work mostly with founders and small B2B teams, so the process stays direct and fast, with no agency layers between you and the person doing the work.

You own it, and I stay on if you want me to. Ongoing support covers edits, new pages, and fixes, so the site keeps up as the business changes.

Yes. I design and develop in Webflow regularly, from single-page sites to full marketing sites with a CMS. It is the default for most founder and service-business projects.

Builds start at £3,400, whatever they are built in. A focused landing page sits near that floor and a full marketing site with a CMS runs higher. The figures are on pricing. Where exactly yours lands is still a guess until I have seen your site, so after a short call you get one fixed quote and you know it before any work starts.

Usually two to four weeks for a standard marketing site. Landing pages can ship in days and bigger builds with a lot of CMS content take longer. How ready your content is tends to decide the timeline more than anything else.

Templates are fine when you want something fast and cheap. Hiring someone pays off once brand, conversion, and a clean structure you can edit later actually matter. Most founders outgrow templates inside a year.

Yes. Depending on how your current site is built, a Webflow redesign can be a visual refresh or a full rebuild. I audit what is already there before changing anything.

Clear messaging, a strong hero, and one obvious next step on every page. Good Webflow design takes friction away instead of piling on decoration. I build around what your buyer needs to read before they are ready to act.

Neither, in the usual sense. An agency adds coordination and a freelancer usually covers one slice. I cover design, build and support myself, which is why there are no handoffs to manage and no account manager in the middle.

Yes. The Webflow editor lets you change text, images, and blog posts without going near code. I set the CMS up cleanly and walk your team through it before handover.

For most service businesses, yes. You get faster load times, no plugin upkeep, and a cleaner editing experience. WordPress still has the edge for complex stores or heavy custom backends.

Yes. A migration keeps your content and SEO in place while the design gets rebuilt properly. I map your old URLs to the new ones so your rankings do not drop.

Yes. Once the site is live I offer monthly support for edits, new pages, and small design tweaks. You can also bring me in for one-off fixes whenever something comes up.

UX is how the site works and feels when someone uses it. UI is the look: type, color, layout, the visual details. Most projects need both, so I handle them together.

Both, honestly. A good-looking site that confuses people still loses sales, so the UX strategy gets set first and the visuals are designed on top of it. Looks and logic are one decision, not two.

Usually three to six weeks for a focused site. Bigger products with a lot of screens take longer. You get a real timeline once I have seen the scope, not a number pulled from thin air.

Yes. A lot of the time navigation, page flow, forms, and the key conversion points can be fixed without rebuilding the whole thing. It is faster, it is cheaper, and often it is all you need.

A team earns its cost when you have genuinely parallel workstreams, several products moving at once, or you need cover around the clock. Below that scale, coordination costs more than it adds, and most website projects for service businesses are below that scale. At this size, one person carrying strategy, design and build means nothing is lost between roles, because there are no roles to hand between.

Yes. I go through your analytics, talk with you about your customers, and watch how people move through the current site. The research stays lean and goes straight into the design decisions.

Each page gets built around one clear action, and anything competing with it gets cut. The UX strategy sets the path, the UI makes that path obvious, and the real flow gets tested before launch.

Yes. You get clean, organized Figma files with components, states, and notes, so any decent developer can build straight from them. If you would rather I build it, I can do that too.

Yes. Plenty of clients start with the homepage, pricing, and one main landing page, since that is where the money is. The rest of the site stays consistent so the new pages do not feel bolted on.

A template guesses at some generic visitor. Real UX design starts from your customers, your offer, and the choices they actually make on the page. That is the difference between a site that looks finished and one that pays for itself.

Three things. Access to your current site and analytics, a short call about your customers and goals, and any brand assets you already have. After that I run the process and check in at fixed points, so you are never left guessing.

Usually two to four weeks. The clock depends on how many pipelines and integrations need wiring up, plus how clean your current data is before I start.

Yes. Your pipeline stages, fields, automations, and reporting get built around the way you actually sell, so you are not fighting a generic template six months in.

Yes. A cleanup means deduplicating records, repairing broken fields, archiving dead deals, and reconnecting automations, all while keeping the history that matters to you.

Mostly tightening what you already own. Unused fields get cut, stages get simplified, misfiring automations get repaired, and the reports end up showing numbers you can trust.

It depends on scope. For sales-led teams HubSpot or Pipedrive are often the answer, but the final call comes from your workflow and budget, never a referral fee.

Yes. I map your real buying process first, then build stages with clear entry and exit rules, so a deal moving forward genuinely means something.

Leads get routed automatically, assigned an owner, and tagged with follow-up reminders so nothing sits untouched. At a glance you can see where every lead is and who has the next step.

Clean up first, nine times out of ten. A new tool inherits the same bad data and the same habits, so the foundation gets repaired before anyone decides a migration is even needed.

No. A CRM set up well for a small team does the routine work itself, which lets a lean team run it without hiring a dedicated admin.

I train your team. You get a short walkthrough, a plain written guide, and a couple of weeks of support so adoption sticks instead of quietly fading.

It depends on scope. A focused cleanup or a single pipeline build sits at the lower end and a full setup with integrations runs higher. It gets scoped and priced before you commit, and the audit that sets that number takes 5 working days.

I automate the boring, repeat work that eats your week. Lead routing, follow-up sequences, client onboarding, invoicing, and keeping data in sync across the tools you already use.

Usually one to three weeks per workflow. Simple ones go live in a few days, and the multi-step internal ones take longer because every branch has to be mapped and tested.

Yes. You walk me through the process, I build and connect it, and you get a working system plus a plain-English document, not code you have to babysit.

It depends on your stack. I work in Make, Zapier, n8n, and native integrations, and I lean on what you already pay for instead of pushing a new platform on you.

Usually yes. Automating a messy process just makes the mess move faster, so the steps get tidied first and then whatever survives gets automated.

Often it is. When two or three people lose hours a week to copy-paste and manual handoffs, it pays for itself quickly. What I will not do is quote you an hours-saved figure before I have seen your process.

A CRM stores your data, automation moves it and acts on it. I handle both, so your records stay clean and the busywork around them runs without you.

Most of the time, yes. If a tool has an API or a webhook it can usually be bridged, and if it genuinely cannot be done I will say so rather than sell you a fragile hack.

You hear about it first. Error alerts are wired in so failures reach you before a client notices, and on a support plan I monitor it, fix the break, and leave you documentation for the small things.

It depends on scope. A single workflow is a fixed project fee, and a full set of internal workflows gets quoted after a short call where I map what you actually run.

Yes, and it is one of the most common requests. The moment someone signs, welcome emails, task lists, document requests and reminders can fire automatically, so nothing slips and you stop chasing it by hand.

The repeatable workflows that run your company every day. Lead intake, onboarding, project handoffs, invoicing and follow-up, wired together so work keeps moving without you chasing it.

Yes. Small teams feel messy operations first, because there is no spare person to catch the dropped balls. A little structure now saves an ugly cleanup at fifteen people.

Usually two to four weeks for a first working version. I map your current process, choose the right tools, build the core flows, then tighten things once your team is actually using them.

Yes. Most founders already run tools that half work, so I audit what is there, drop the dead weight, and reconnect the pieces worth keeping before adding anything new.

Automation is a single task done without a human. A system is the whole process those tasks sit inside. I design the system first, then automate the parts that are safe and obvious to hand off.

Whatever fits your stack. I tend to use things you already pay for, like Notion, Airtable, HubSpot, Slack, and Zapier or Make, rather than moving you onto something new for no reason.

Watch for a few tells. Work stalls when one person is out, the same questions come up every week, things vanish into email, and nobody can tell you where a project stands without a meeting.

A little, for a week or two. New habits feel slower before they feel faster, so each change stays small and gets documented, which is what makes people adopt a system instead of routing around it.

Both. A system nobody understands gets abandoned, so I record short walkthroughs, write plain instructions, and stay around while your team gets comfortable running it.

It depends on your stage. An ops hire is a full-time salary and still needs systems to run, so plenty of founders have the digital operations built first, then hire someone to own them.

You own all of it. The accounts, the documentation and the logic stay with you, and I am around for ongoing support as the business grows and the workflows need to shift.

It depends on scope. A single focused page costs less than a full site, and you get a flat quote once I have seen your goal, your content, and the action you want visitors to take.

One clear offer and one main action, with nothing else competing for attention. The message stays tight, objections get answered in the order people think of them, and anything pulling them away from the button gets cut.

Usually one to two weeks. Have your copy and brand assets ready on day one and it moves faster. If the messaging is being written with you, plan for the back end of that range.

It depends on what you are selling. A landing page is the right call for one campaign, product, or ad. A full site earns its place when buyers want to browse your services, read about you, and weigh options before reaching out.

Yes. I find where people are dropping off first, then rebuild the headline, structure, and call to action so the page does the one job it exists for.

Yes. Most landing page traffic comes from phones, so it gets designed for the small screen first, and forms, buttons and load speed get checked across devices.

A homepage introduces your whole business. A landing page sells one thing and points everyone toward a single action, with no side doors to wander through.

Yes. The design and the words cannot really be separated, so the headline, the flow and the proof get shaped together rather than pouring your text into a template.

Watch the conversion rate, not the traffic. Tracking goes on the button and the form so you can see how many visitors take action, then changes get tested against real numbers instead of hunches.

Yes. Form submissions go straight into your CRM, email platform, or a tool like Zapier, so every lead lands where your team already works and nothing slips through.

The market range is $2,000 to $150,000, and most small business redesigns land between $2,000 and $10,000. What moves that number, and the cost that never appears in a quote, is written up in website redesign cost. What I will not do is quote your project before I have seen it. A number given before I know what is already there is a guess, and it goes wrong in one of two directions: padded for the worst case, which overcharges the simple jobs, or too low, which becomes an uncomfortable conversation in week four. Thirty minutes on a call and you get a real number the same day.

Usually four to eight weeks for a typical founder or service site. Bigger projects with custom features or a lot of content run longer. You get a timeline at the start and I hold to it.

Yes. Most of my clients are founders and small B2B teams who outgrew the site they launched on. Strategy, design and build all happen in one place, so you are not coordinating three vendors.

Not when it is handled properly. Old URLs get mapped to the new ones, redirects go in place, and the existing SEO structure is preserved. Most sites hold their rankings or climb once pages load faster and read more clearly. When it does go wrong, it is one of nine specific things, listed in website redesign for SEO.

It rebuilds your site in Webflow so your team can edit content without going near the code. You get a clean design, quick load times, and a CMS people will actually use. It fits founders who want to make changes without booking a developer every time.

Yes. If your copy is already pulling its weight it stays, and the attention goes to layout, structure and visual design. I will point out any sections holding the page back, but you make the final call.

It depends what you are working with. A solid foundation that just looks dated is faster and cheaper to redesign. When the structure, platform or messaging is broken, a clean rebuild usually costs less over time.

Look at the signals. Low conversions, visitors leaving fast, a dated look, or a site you cannot update without help all point one direction. If people are not turning into leads, design is often part of the reason, and an audit will give you a straight answer in 5 working days.

Yes. I redesign sites from nearly any platform and can move you to Webflow or keep you where you are, whichever suits your team. I will steer you toward whatever is easiest to manage once you are live.

Strategy, UX, visual design, build and launch. In practice that means sitemap planning, fresh page layouts, responsive design, redirects, and a handoff so your team can run things. Copywriting and CRM setup are available too.

It stays live the whole time. Everything gets built and reviewed on a staging version, then flipped to the new site in one clean step. Visitors never catch it half finished.

It is turning more of the visitors you already have into leads and customers, without paying for more traffic. Most sites pull in enough people but lose them at a few weak spots. I find those spots and fix them.

A regular site explains your business. A conversion-focused one is built around one clear action you want each visitor to take, and every section nudges them toward it. Copy, layout and the call to action all pull in the same direction.

Yes. I usually start by reworking headlines, calls to action, forms and page flow, which can lift conversion well before any rebuild. A full redesign only earns its cost when the structure itself is fighting you.

Usually a handful of fixable things: a fuzzy offer, a weak or buried call to action, slow loads, or forms asking for too much. I trace the whole path from landing to form submit and patch the biggest leaks first.

Usually two to four weeks for the first lift, depending on how much traffic you get. Lower-traffic sites take longer to reach numbers you can trust, so I lean on clear UX fixes early rather than waiting on statistics.

Yes. Catching a lead is only half the job, so forms get wired into a follow-up system that routes new leads to your inbox or CRM and kicks off a fast first reply. How quickly you respond often beats anything on the page.

Clarity, trust, and one obvious next step. It loads fast, says what you do in a single line, shows proof, and strips out every reason to hesitate before the call to action.

Fix the obvious problems first. A/B testing needs real traffic to mean anything, and most sites carry clear UX issues that are cheaper to correct outright. Testing comes later, once the basics convert and you have the volume to trust the data.

It depends on your offer, your scope, and the quality of your traffic. I will not hand you a number I cannot stand behind, though a neglected site usually has more room in it than a careful one.

Yes, often even more so. At low volume every lost visitor costs you, so one extra lead a week can reshape your month. I focus on clear improvements rather than data-heavy testing that small traffic cannot support.

Both. A single landing page is often the quickest way to prove what works, since it has one goal and one audience. The same approach applies whether it is one page or your entire site.

Four stages: audit, plan, build, launch. It starts by mapping your goals and your customers, then moves into design and build in short loops where you review the work as it comes together. You see it the whole way through, not just at a big reveal.

From £3,400, with automation from £1,300 and monthly support from £520. All of it is on pricing. Those are floors and not quotes: where your project lands above the floor depends on scope, and after one short call you get one fixed number that nothing shows up beneath on a later invoice.

Two things, and the second is the rarer one. A price floor, published on pricing, so you can rule me in or out in a minute. And a date: the audit is delivered in 5 working days from the moment you send access, and the written plan two days after that. Of twelve competitors I looked at, eight hide the price behind a mandatory call and only two commit to a timeline at all.

Fixed. You get one number for the agreed scope before anything starts, which keeps it easy to plan around. If the scope changes I flag it and you sign off before any extra work happens.

Usually two to four weeks. A simple landing page can go live in days, and a larger site with custom features needs more. What slows things down most is waiting on your content and feedback.

Because a good-looking site that does not convert is money down the drain. The audit settles who the pages are for, what action they should drive, and how to word it. Once that is clear, the design decisions move fast.

Three things: your goals, your content or a real plan to produce it, and one person who owns feedback. The clearer you are about what a win looks like, the smoother the whole thing runs. Everything else is on me.

Yes. A single high-converting landing page is one of the most requested projects, especially ahead of a launch or a paid ad push. You can grow it into a full site later without tearing it down.

A template hands you a layout. You get strategy, custom design, and a build shaped around how your business actually sells. Templates cost less up front, though plenty of founders rebuild within a year once they hit the ceiling.

In stages. Most projects split into a deposit to start and the balance at launch, and bigger builds break into three payments. The schedule is set before any work begins, so your cash flow is never left to guesswork.

Every build includes 30 days of changes, so small tweaks in that window are covered, and a two month warranty separately if something actually breaks. After that, ongoing support is monthly or per task. You are never stuck waiting on me to edit your own site.

It covers the window right before and after go-live. Final QA, the domain and DNS switch, redirects, analytics checks, and being on call to fix anything that breaks in your first week.

Every project comes with a two month warranty, so anything that breaks gets fixed at no cost, and 30 days of changes on top for tweaks that are not breakage. You can add a monthly plan if you want me around past that.

Your call. Some clients take the site and run it themselves, others keep me on monthly for updates, edits and small improvements. Both are fine, and the handover is the same either way.

A short kickoff call and a shared document. Brand assets, logins and goals get gathered up front so nothing stalls halfway through the build.

Yes. Old URLs get mapped, redirects set up, content moved, and everything tested on staging before the domain is pointed, so you keep your traffic and rankings.

I jump on it. During launch week the site gets watched closely, and any bug is patched at no cost inside the 30-day window.

Yes. During handoff you get short recorded walkthroughs and a plain written guide, so your team can edit pages without messaging me for every change.

It depends on scope and how much you want covered. Most plans are a flat monthly fee with a set number of hours for edits, updates and fixes, all agreed before anything starts.

Launch support is short and aimed at getting you live cleanly. A retainer is ongoing, covering edits, new sections and maintenance month to month after that.

Usually within one business day. A site going down gets same-day attention, and retainer clients come first on routine edits.

Yes, on a support plan. Plugins and integrations stay current, backups run, uptime gets watched, and the small fixes that pile up when a site is left alone get handled.