Frequently Asked Questions

Case studies are the obvious place to start, but they're the least reliable indicator. Every agency shows its best work. The more useful thing to look at is whether the work they're showing is similar in complexity and sector to what you need – not just visually impressive, but substantively relevant.

Talk to their clients, not just the references they offer. LinkedIn makes it reasonably easy to find people who've worked with an agency and ask for an honest assessment. Two questions worth asking: would you hire them again, and were there things you wish you'd known before you started? The second question often produces more honest answers than the first.

Look at how they communicate in the process of winning your business. Do they ask good questions about your problem? Do they push back on anything or just tell you what you want to hear? Are they clear about what's included and what isn't? An agency that can't manage its own client relationship during a pitch is unlikely to manage yours differently once they've won it.

What this means for you: Weight the quality of the conversation you have with them during the pitch process over the quality of the work they show you. Work can be selectively curated; how they engage with you is a better proxy for what working with them will feel like.

This is harder than it sounds, because agency pricing is inconsistently structured across the industry. Some agencies price by deliverable, some by day rate, some by project value. A quote that looks expensive might reflect a more thorough process; one that looks cheap might be missing a significant chunk of work.

That said, there are a few things worth checking. Get quotes from at least two other agencies for the same scope – not to play them off against each other, but to understand the range. Ask each agency to break their quote into phases or workstreams so you can see where the cost sits. If an agency refuses to do that or gives you a single lump-sum number with no breakdown, that's a reasonable thing to push back on.

Day rates are a useful benchmark. A mid-weight developer in a decent agency will typically be £600-£900 per day; a senior strategist or creative director £800-£1,200+. Junior rates are lower. If you can work out roughly how many days are implied in a quote, you get a sense of whether the maths adds up. It won't be precise, but it'll tell you if something's wildly off.

What this means for you: If you're unsure whether a quote is fair, the most direct thing you can do is ask for a line-item breakdown and talk through it with the agency. A good agency won't be offended by that. If they are, or if they can't explain the logic behind individual costs, that tells you something.

A straightforward brochure website redesign for a small-to-medium business – ten to twenty pages, standard functionality, an established brand – typically takes three to five months from kick-off to launch. More complex projects, or ones involving significant content production, user research, or phased rollouts, will take longer.

Where timelines go wrong is usually in the content phase and the review cycle. Agencies can build faster than most clients can produce, approve, or supply content. If you're going into a redesign without a clear plan for who's writing copy, who's signing it off, and when – you'll hit delays. Similarly, if you have multiple stakeholders with sign-off authority who aren't aligned on the brief, you'll end up cycling through rounds of amends that nobody anticipated.

Agencies that quote very short timelines – 'six weeks to launch' for a substantial site – are either cutting things out or setting expectations they won't meet. It's worth asking what specifically would be delivered in that timeframe and what would follow in a second phase.

What this means for you: Build the content plan before you start the design process, not after. It's the single biggest variable most clients underestimate. If you don't have internal resource to handle copy, factor content production into the agency scope and budget from the start.

Websites can cost anywhere from a few thousand pounds to several hundred thousand, and both ends of that range can be the right answer depending on what you need. The variation isn't random – it reflects differences in scope, complexity, and how much strategic and creative thinking is involved.

A brochure site with five to ten pages, a CMS, and a standard set of templates will typically sit in the £10,000-£25,000 range at a competent agency. Add e-commerce, a complex integration with a CRM or data feed, a bespoke design system, or significant content production, and that number climbs quickly. Enterprise-scale builds – the ones involving multiple stakeholders, phased delivery, custom functionality, and accessibility auditing – can run to £100,000 or more.

Where agencies tend to differ is in how much thinking sits behind the build. A low-cost provider might deliver a functional website with a purchased theme and light customisation. A full-service agency working on the same brief might spend weeks on user research, information architecture, and design iterations before a line of code is written. Whether that additional work is worth paying for depends on your business, your users, and how much the website has to do.

What this means for you: Be specific about what you need before you ask for quotes. 'A new website' is too vague to price accurately – you'll get wildly different numbers because agencies will be guessing at your scope. The more clearly you can describe the functionality, user types, volume of content, and existing integrations, the more useful the quotes will be.

This varies more than it should, and it's worth getting clarity before you sign anything. In most standard arrangements, you own the website and its content. The code built for you should be yours. What you may not automatically have access to are the hosting account, any proprietary build tools or systems the agency uses internally, or the source files for design assets.

Some agencies host client websites on their own infrastructure. If yours is one of them, leaving means migrating to a new host – which is manageable, but takes time and needs careful handling to avoid downtime. Ask upfront who holds the hosting account, whether it's in your name or theirs, and what the process is for taking it over.

The same goes for the CMS login, domain registrar access, SSL certificates, and any third-party service accounts connected to the site. An agency should be able to provide a clear handover document covering all of these. If they're reluctant to discuss it, that's worth noting.

What this means for you: Before you sign a contract, ask explicitly: 'If we move to a different agency, what do we get and what's the handover process?' A straightforward answer to that question is a good sign. Make sure domain ownership and hosting access are covered in the contract, not just assumed.

Most agencies are good at pitching. They'll show you polished case studies, talk about their process, and make everything sound very considered. That's fine – but it doesn't tell you much about what working with them is actually like. The questions that matter are the ones that reveal how they behave when things get difficult.

Start with the practical stuff: who will actually work on your account day to day? Not the senior people who pitched to you – who's doing the work? Ask to speak to a project manager or developer who'll be on your project. Ask how they handle scope creep, what their change request process looks like, and what happens if a deadline slips. If they're vague on any of that, take note.

Then ask about work they'd do differently. Any agency worth hiring can point to a project that didn't go to plan and explain what they learnt from it. If they can't, they're either not being straight with you or they haven't done enough work to have had a difficult project yet. Ask for references from clients who've been with them for two or more years – longevity tells you more than any testimonial on a website.

What this means for you: Go into the conversation with specific, process-oriented questions rather than open-ended ones. 'Tell us about your approach' invites a sales answer. 'Walk me through how you handled a project that went over budget' doesn't. The more concrete your questions, the more useful the responses.

WordPress agencies build primarily on WordPress – they know it well, have a stack of patterns they can deploy efficiently, and can move quickly on projects that fit the platform. Custom development shops build from scratch, or on frameworks they choose based on the project's needs. Neither is categorically better.

The practical difference shows up in a few ways. WordPress agencies tend to be faster and cheaper for most standard website builds, because they're not reinventing the wheel on every project. The CMS is well-understood, the ecosystem of plugins and themes is large, and there's an enormous pool of people who can maintain and extend WordPress sites.

Custom shops have an advantage when your requirements don't fit the WordPress model – complex data structures, unusual user journeys, performance requirements that a standard WordPress setup would struggle to meet. The downside is cost, timeline, and the fact that bespoke code is only as good as the team that wrote it. When that team moves on, you can end up with something that's difficult and expensive to maintain.

What this means for you: Ask any agency you're considering what they'd build if you told them WordPress wasn't on the table. If they can't give you a coherent answer, they may be defaulting to what they know rather than what's right for your project.

Fixed price gives you budget certainty in exchange for less flexibility. You agree on a scope, the agency prices it, and that's what you pay – unless the scope changes. It works well when requirements are clearly defined and unlikely to shift. The risk is that agencies will sometimes add contingency to a fixed price to protect themselves from uncertainty, so you may pay a premium for that certainty.

Hourly or time-and-materials billing means you pay for actual time spent. It's more flexible – if requirements change or the project evolves, you're not constrained by what was agreed upfront. The downside is that it's harder to manage against a budget without active oversight. Costs can drift.

Some agencies offer a hybrid: a fixed price for the design and build phases, with ongoing work billed on time and materials. That often makes practical sense because the project phase is more predictable than what comes after it.

What this means for you: For a well-defined project with clear requirements, fixed price is usually fine and provides useful predictability. For ongoing retainer work or anything exploratory, time and materials tends to be fairer for both sides. The most important thing in either model is a clear, detailed scope – the pricing model matters less than the clarity around what's included.

None of these options is inherently right or wrong – they suit different situations. The mistake is defaulting to the approach that feels most familiar rather than the one that fits the problem.

A no-code tool like Webflow, Squarespace, or similar makes sense when your requirements are relatively simple, you don't have significant technical integration needs, and you want to be able to maintain and update the site without depending on anyone else. They've come a long way in terms of what they can do. The limitations tend to show up at scale or when you need something that doesn't fit the platform's model.

Hiring in-house makes sense when you have ongoing, sustained demand for digital work – not a project here and there, but a continuous backlog. It gives you someone who understands your business deeply, but you'll pay for that person whether the work is there or not, and a single hire can't cover every specialism.

An agency makes sense when you need a breadth of skills you can't justify employing full-time – strategy, design, development, content – or when you're working on something that has a defined scope and end point. The trade-off is less institutional knowledge over time and a relationship that needs active management.

What this means for you: If you're spending more than £3,000-£4,000 a month with an agency on a single service line, it's worth at least modelling what an in-house hire would cost. If you're spending less, or working on a defined project, an agency typically makes more financial sense.

Mostly scope creep – requests that come in during the project that weren't part of the original brief. Sometimes that's on the client side: new requirements emerge, stakeholders who weren't involved at the start surface with opinions, or the business changes direction mid-project. Sometimes it's on the agency side: the brief was under-scoped at proposal stage, assumptions weren't made explicit, or estimates were optimistic to win the work.

Technical complexity that wasn't visible at the start is another common cause. A third-party integration that looked straightforward turns out to have a poorly documented API. Content arrives late and in a different format than expected, requiring additional work to prepare. Performance issues appear late in testing, which take longer to resolve than anticipated.

It's rarely one party's fault entirely. The more useful question is whether the overspend was flagged early or came as a surprise at the end. A good agency will raise budget risks as they emerge and have a clear change request process – not so that they can add charges for everything, but so that both sides can make informed decisions about what to include.

What this means for you: Before a project starts, ask how the agency handles change requests and at what point they'd flag a budget risk. Agree on what 'in scope' means in writing. That one conversation will save more friction than almost anything else you can do.

It can work well, and there are genuine advantages – the brand and digital expression are developed together, which can produce more coherent results than handing a finished brand to a separate web team later. But it requires careful sequencing and discipline.

The risk is that the web project starts before the brand is stable. If you begin building pages before the identity is signed off, you'll either have to rework them later or lock the brand too early to avoid that rework. Either way you lose something. A combined programme needs a clear checkpoint between brand completion and web build commencement.

For financial services specifically, there's an additional consideration: brand assets and website copy will both go through compliance review, and it helps to sequence that so you're not getting sign-off on two major pieces of work simultaneously if your compliance function has limited bandwidth.

What this means for you: If you're running brand and web together, agree on the sequencing upfront. Brand strategy and identity should be complete and approved before the web design phase begins. Web copy can often run in parallel with identity work, but the final visual treatment needs to be stable before the site design is locked. Build that checkpoint into the project plan explicitly.

It depends almost entirely on what you mean by rebranding. A logo refresh and updated visual guidelines for a small business might be £5,000-£12,000. A full brand programme for a mid-size company – including strategy, messaging, visual identity, tone of voice, and guidelines – typically runs £20,000-£60,000. For a large financial services firm where compliance sign-off, a wide range of applications, and internal change management are involved, you can add another zero.

What drives the cost is less the output itself and more the thinking behind it. A new logo is a commodity. A new logo that's the visible expression of a clear brand strategy, built around an understanding of your audience and competitors, is a different thing. You might not be able to tell them apart in a PDF, but one will work harder for you.

The things that tend to inflate brand costs unnecessarily are excessive rounds of revision, scope that expands to include digital or print production work mid-project, and strategy phases that are billed as separate projects rather than built into the programme from the start.

What this means for you: Before you get quotes, be clear about what you're trying to solve. If the answer is 'we look a bit dated,' that's probably a refresh brief. If the answer is 'we're entering a new market and our brand no longer reflects what we do,' that's a strategic repositioning – and the cost and process should reflect that difference.

This is probably the most honest question in branding, and most agencies won't ask it because the answer sometimes means not doing the project. Familiarity feels like staleness when you're looking at the same brand every day – what your team is bored of may be exactly what your customers recognise and trust.

A few things that suggest genuine outdatedness rather than internal boredom: the brand no longer reflects what the business does (because the business has changed), it's creating friction in new markets or with new audiences, it looks noticeably dated compared to direct competitors, or it was never particularly coherent in the first place and has accumulated inconsistencies over time.

If none of those are true – if the brand is actually recognised, consistent, and reasonably well-received by customers – the case for a full rebrand is weaker than it might feel internally. A refresh might address the boredom without the risk and cost of changing something that's working.

What this means for you: Talk to customers before you commission any brand work. Ask them what they think of when they hear your name or see your logo. Their answers are usually more grounding than the internal conversation. If there's a gap between what customers think and what you think you are, that gap is worth addressing. If there isn't, that's useful information too.

A refresh keeps the fundamentals – the core visual identity, the positioning, the brand personality – and updates the execution. New typography, refined colours, updated photography style, maybe an evolved logo mark. A rebrand starts from a different place: it questions the strategy, the positioning, and sometimes the name and audience entirely. Those are meaningfully different things.

Most businesses that think they need a rebrand actually need a refresh. The strategy is sound, the audience is right, the market position is clear – it just needs a visual update to stop feeling tired. That's a much smaller project and carries much less risk. A full rebrand touches every touchpoint your business has, can create confusion in the market if handled badly, and typically takes longer and costs more than people expect.

The scenarios where a full rebrand makes sense: a merger or acquisition, a significant change in what the business does or who it serves, reputational issues linked to the brand name or identity, or a founding-era brand that was never built with any strategic intent and can't be fixed through cosmetic changes.

What this means for you: Be honest about what the brief is actually trying to solve. If you're starting with 'we don't like the logo,' work backwards to find out why. If it's strategic, you probably need a rebrand. If it's visual, a refresh is more proportionate. A good agency will help you diagnose that – and should tell you if the answer is 'neither right now.'

A logo is a visual mark. Brand strategy is the thinking that determines what that mark should communicate, to whom, and why. One is an output; the other is the foundation everything else is built on.

Brand strategy covers things like: what position you occupy in the market, how you want to be perceived relative to competitors, what your core values mean in practice, who your target audience actually is and what they care about. It also covers tone of voice – how you sound in writing – which shapes everything from your website copy to how your team responds to complaints.

A logo built without brand strategy can still look nice. But a logo built with a clear strategy has a better chance of doing what you actually need it to do – which is communicate the right things to the right people quickly and consistently.

What this means for you: If you're commissioning a new visual identity, ask the agency what their strategy process looks like and how it informs the design. If they go straight to moodboards without a discovery or strategy phase, you're getting design opinion rather than design reasoning. That may be fine for a small refresh, but it's a risk for anything more significant.

You need to define 'working' before you can answer that question – and many businesses don't do this clearly enough upfront. Clicks and impressions aren't a measure of commercial performance. Neither is follower count. The metrics that matter are the ones connected to business outcomes: qualified leads, cost-per-acquisition, pipeline value generated, conversion rate, and ultimately revenue attributable to the campaign.

Attribution is genuinely complicated in B2B or longer sales cycle businesses. Someone might see a paid ad, read three pieces of content over six weeks, attend a webinar, and then respond to a sales email. Attributing the eventual sale to the original ad is reductive. Multi-touch attribution models try to solve this but require good tracking infrastructure to work properly.

The most reliable approach is to set clear targets at the start of each campaign – a specific number of qualified leads, a target cost-per-lead, a pipeline value threshold – and review against those targets regularly. Where performance is below target, the question should be why and what changes would address it, not whether to keep going regardless or stop entirely.

What this means for you: Before any campaign starts, write down the specific numbers that would constitute success. Share those with the agency. Review them monthly. If the agency's reporting doesn't map to those numbers and instead focuses on engagement metrics and reach, ask them to build a supplementary report that shows performance against the commercial targets.

Typically three to six months before you see meaningful movement in rankings, and six to twelve months before that translates into reliable, consistent organic traffic. For competitive markets, longer. Any agency promising first-page rankings in four to six weeks is either using tactics that won't hold, or targeting terms with almost no search volume.

The pace is slow because search engines are cautious about rewarding new or changed content. They need to see that a page is consistently relevant and credible over time. A new piece of content might take two to three months to reach its stable ranking position. Building the authority to rank for competitive terms takes longer still.

That timeline is frustrating if you need results quickly, which is one reason paid advertising is often worth running alongside an SEO programme rather than waiting for organic to pick up.

What this means for you: If you start an SEO programme, set internal expectations accordingly. Month three isn't a useful measure of success. Month nine or twelve is. Build your reporting framework around leading indicators – content published, backlinks acquired, crawl health – rather than just rankings, which will be slow to move at first.

There are two separate costs here: the agency management fee and the actual media spend (the money that goes to Google, Meta, or whoever you're advertising with). These are often bundled together in a quote, which can make it harder to see what you're paying for.

Agency management fees for paid search typically run 10-20% of media spend, or a flat monthly fee if the spend is low or predictable. Expect to pay £800-£2,000+ per month in management fees for a competent independent agency or specialist; larger shops may charge more. On top of that, your media budget needs to be sufficient for the platform to gather meaningful data – broadly, under £1,500 per month in Google Ads spend is often too little to run effective campaigns in competitive markets.

Social advertising (Meta, LinkedIn, etc.) has similar structures. LinkedIn tends to require higher minimum spend to be effective and works better for B2B than B2C.

What this means for you: When getting quotes, ask agencies to separate the management fee from the media budget in their proposal. Also ask what minimum media spend they'd recommend given your market – that's often a more revealing question than the management fee itself.

The honest answer is that they work differently and shouldn't really be framed as a choice. Paid advertising produces results quickly and stops the moment you stop paying. SEO builds slowly and has compounding returns over time. Neither is inherently superior – they serve different purposes.

If you need leads or customers in the next three months, paid is the faster route. If you're playing a longer game and want to reduce your dependence on paid spend over time, SEO is the investment. Most businesses benefit from some of both, but the balance depends on where you are, what you can afford, and how patient you can be.

For businesses new to digital marketing, paid advertising often makes sense to start with – partly because it generates faster signal about what messaging and offers resonate, and partly because it doesn't require the content infrastructure that SEO demands to work properly.

What this means for you: Decide on a timescale and a goal. If the goal is awareness and long-term lead generation over 18 months, weight towards SEO with some paid support. If the goal is leads this quarter while a longer-term content strategy is built out, lead with paid. Don't let the either/or framing push you into an all-or-nothing decision.

In-house tends to work better when the volume of activity justifies a dedicated hire, when you're in a sector where deep market knowledge matters for targeting, or when the pace of change is fast enough that an external team would struggle to keep up. An in-house PPC specialist knows your product, your customers, and your business rhythm in a way an agency account manager managing ten other clients often doesn't.

Agencies tend to work better when you need breadth rather than depth – when you want someone managing paid search, paid social, and campaign strategy across multiple channels – or when you don't have the volume of work to justify a full hire. They also bring external benchmarks: they see what's working across multiple clients and sectors, which can inform your strategy in ways an in-house team can't.

The hybrid model – an in-house marketing manager with strategic oversight, an agency handling the hands-on channel management – is increasingly common for mid-size businesses and often works well.

What this means for you: If you're spending more than £6,000-£8,000 per month in media, model the cost of a specialist hire versus agency fees. At that level, the economics often favour bringing at least some capability in-house, even if you maintain an agency relationship for oversight or specific channels.

Anyone who gives you a specific number without knowing your market, margins, average deal value, sales cycle, and current conversion rates should be treated with scepticism. ROI from digital marketing varies enormously across sectors – comparing a financial services firm with a six-month sales cycle to an e-commerce retailer selling £30 products is meaningless.

What a well-run campaign should do is produce measurable, improving results over time. In paid search, you'd expect to see cost-per-acquisition declining as the campaign matures, bids and audiences are refined, and low-performing terms are paused. In SEO, you'd expect to see organic search visibility increasing over months, not weeks. The trajectory matters more than any single month's numbers.

For regulated financial services, the picture is complicated by the fact that you can't always link a piece of content or a campaign directly to a sale. Brand-building activity – thought leadership, organic content, PR – has real commercial value but it often doesn't show up in a simple ROI attribution model. That's a genuine limitation of measurement, not evidence that the activity isn't working.

What this means for you: Define what 'working' looks like before you start, not after. That means agreeing on specific metrics – qualified leads, cost-per-lead, organic traffic growth, share of voice – and reviewing them regularly. The clearer the performance framework upfront, the easier the conversation when it comes to judging whether what you're doing is worthwhile.

They overlap significantly but aren't the same thing. SEO is primarily about making sure your site is technically sound, appropriately structured, and optimised to appear in search results for terms your audience uses. Content marketing is about producing editorial content – articles, guides, reports, videos – that's useful enough for people to read, share, and link to.

In practice, good content marketing is one of the most effective SEO tactics available. A well-researched guide that other sites reference and link to will improve your search authority. A high-quality article targeting a specific search term will pull in organic traffic if it's better than what's already ranking. But content can exist independently of SEO – you might produce content for email marketing, for sales enablement, or for client education with no expectation that it'll rank in search.

The mistake is conflating them so that all content becomes SEO-driven. That tends to produce very keyword-shaped content that satisfies a brief but doesn't do much for thought leadership or brand reputation.

What this means for you: Separate the content strategy question from the SEO question, at least initially. What do you want to be known for? What questions does your audience have that you're well-placed to answer? From that, you can identify where SEO-driven content makes sense and where you're producing something for a different purpose. The two can coexist without one colonising the other.

A retainer is an ongoing arrangement where you pay a fixed monthly fee for a defined scope of work. A project is a defined piece of work with a start, end, and specific output. Both have their place.

Retainers make sense for campaign work that has an ongoing nature: paid search management, content production, SEO, social media. These benefit from consistent attention, institutional knowledge, and the kind of optimisation that compounds over time. Switching agencies or approaches frequently resets the learning curve and tends to produce worse results.

Project-based work makes sense for campaign work that has a clear deliverable and end point: producing a specific campaign asset, running a one-off paid campaign for a product launch, building a campaign landing page. You don't need an ongoing relationship to get those done.

The risk with retainers is that they can become comfortable for both sides without either party scrutinising whether the value is there. A retainer that's been running for two years without a proper review is often worth pausing to assess. The agency should be proactively demonstrating value; if you're not sure what you're getting from a retainer, ask for a line-item account of where the time went last quarter.

What this means for you: For any retainer, agree upfront on what success looks like, when you'll review it, and what would trigger a conversation about changing the scope or ending the arrangement. That isn't adversarial – it's just sensible commercial management, and a good agency should be comfortable having that conversation.

There are a handful of reasons SEO underperforms, and they're often compounding. Technical issues – slow load speeds, crawling errors, poor mobile experience – prevent pages from being indexed or ranking even when the content is good. Content that's written for internal audiences rather than search audiences doesn't attract the traffic you want. And links – the external references from other credible sites that signal authority to search engines – take time to build and can't be shortcut.

Another common issue is competing for search terms you have no realistic chance of winning. A new or mid-sized financial services firm targeting 'financial advice UK' or 'best ISA rates' is fighting major comparison sites and national brands for terms where they have no authority advantage. That's not a fixable SEO problem – it's a targeting problem.

What actually works is less glamorous than most agencies want to admit: regular, useful content that answers the questions your specific audience is searching for, a technically sound site, and a patient approach to building credibility over time. There's no shortcut that consistently produces durable results.

What this means for you: Start with a keyword audit that looks at search volume alongside competition. Focus on terms where there's genuine intent from your target audience and where you have a realistic chance of ranking given your current authority. That's a narrower target list than you might expect, but it's a more honest basis for an SEO strategy.

Yes, in ways that matter. The FCA's consumer duty obligations, the Financial Promotions regime, and sector-specific rules around risk warnings, past performance, and testimonials create real constraints that don't apply in most other industries. A generic web agency can build you a technically functional site and not realise they've created a compliance liability in the process.

The differences show up in content as much as in functionality. Financial promotions must be fair, clear, and not misleading. Risk warnings need to be prominent and meet specific wording requirements depending on product type. Communications that could be construed as advice require careful handling. These aren't design constraints – they're legal requirements with real consequences if they're not met.

None of this makes good financial services websites impossible. Some of the best digital experiences in any sector are being built for financial services firms. But it does mean the team working on your website should have sector experience and shouldn't be learning compliance obligations on your project.

What this means for you: When briefing any agency for financial services work, ask specifically about their experience in the sector and how they manage compliance requirements within projects. You want to see evidence that they've navigated this before – not just familiarity with WordPress or paid search, but experience building and reviewing content within the FCA's framework.

You can use them, but with care. The FCA's rules require that financial promotions aren't misleading, and testimonials can create problems in two specific ways: they may imply typical results when the experience described was atypical, and they may omit material information that would affect how the communication is interpreted.

Past performance testimonials – clients who achieved a particular return or financial outcome – are particularly risky. The rules require that past performance information doesn't give the impression that it's a reliable guide to future performance. Testimonials that focus on qualitative experience ('the service was excellent, they were very responsive') carry lower risk than those that describe financial outcomes.

Case studies face similar issues. A case study showing how a client achieved strong returns needs careful framing and appropriate risk warnings. A case study focused on process, relationship quality, or problem-solving methodology is less likely to create a compliance issue.

What this means for you: Get your testimonials and case studies reviewed by compliance before publishing. The review doesn't have to be onerous – a clear sign-off process with standard criteria is usually sufficient. Focus testimonials on experience and service quality rather than financial outcomes, and make sure any case study that includes performance data includes the appropriate caveats.

Not necessarily every update, but the answer depends on what's being changed and whether it constitutes a financial promotion. Updating a phone number, fixing a typo, or changing a team member's photo doesn't require compliance review. Updating product claims, changing risk warning wording, or publishing new content about services or investment performance does.

The most practical approach is a tiered review process. Low-risk updates (factual corrections, structural changes, non-financial content) can be published by the content team. Medium-risk updates (product descriptions, service pages, blog posts related to products or performance) require a light-touch compliance check. High-risk updates (financial promotions, investment communications, anything that includes performance data or product recommendations) require full approval.

The cost of getting this right is a clearly documented process and a nominated compliance reviewer who's available promptly. The cost of getting it wrong can be significantly higher: FCA enforcement action, fines, and reputational damage, none of which is proportionate to the effort a simple review process requires.

What this means for you: Build a content classification matrix that tells your team, at a glance, which category any given update falls into and what review it needs. That's a morning's work to produce and it removes ambiguity from the process. Share it with your agency so they know what to flag and what they can publish without escalation.

Yes. The FCA's definition of a financial promotion includes 'any communication in the course of business.' That covers your website, your email marketing, your social media accounts, and any paid advertising. The fact that something is on Instagram or X rather than a printed brochure doesn't place it outside the regime.

The rules apply to the substance of the communication, not the channel. A paid social ad that doesn't include appropriate risk warnings, or a LinkedIn post by a firm employee that could be interpreted as encouraging investment, can each constitute a non-compliant financial promotion.

There are some exemptions – one-to-one communications, for example, are treated differently to broadcast communications. But anything published to an audience, on any channel, that relates to a regulated activity should be treated as in scope until you have a clear basis for why it isn't.

What this means for you: Build a review process for all externally published content, not just formal campaign materials. That includes social media, blog posts, and website copy updates. The effort required to comply doesn't have to be enormous if the process is well-designed – a light-touch compliance check that takes ten minutes per piece of content is manageable and significantly reduces risk.

This is a more tractable problem than it's often made to seem. Compliance requirements constrain some specific things – what you can say, how prominently risk warnings must appear, what information must be present before a user can proceed. They don't prescribe bad design, cluttered layouts, or a hostile experience. The conflict between compliance and UX is often the result of compliance being addressed as an afterthought rather than built into the design process from the start.

Risk warnings that are integrated into the design rather than bolted on afterwards look very different. A clear, well-designed warning presented at the right point in a user journey is both compliant and better for users than a block of grey text appended to the bottom of a page. The FCA's consumer duty places a positive obligation on firms to support good outcomes for customers – which is broadly aligned with what good UX practice is trying to achieve anyway.

The tension is most real in high-volume, low-touch digital journeys where you're trying to get a user from intent to action with minimal friction. Sometimes the friction that compliance adds – an extra screen, a confirmation step, a prominent warning – is both necessary and genuinely informative for the user.

What this means for you: Involve compliance in design decisions early, not at the review stage. When compliance flags an issue, frame the conversation as 'how do we solve this design problem within the constraint' rather than 'compliance is blocking us.' Most compliance requirements can be met well or badly – the design team's job is to meet them well.

There's no single right answer, and the wrong choice in either direction creates real problems. A single unified site makes brand management simpler, improves SEO through domain authority consolidation, and reduces the cost of maintenance. A multi-site approach can make sense when products serve genuinely different audiences, when compliance requirements differ significantly between product lines, or when the brand positioning of each product is distinct enough that combining them would dilute both.

For regulated firms, the compliance consideration is often decisive. If one product is FCA-regulated and another is not, there can be good reasons to keep them separate to avoid creating an implicit association that could mislead users. If two products are both regulated but have different risk profiles and different target audiences, a shared site needs careful navigation to avoid cross-contamination of messaging.

The operational cost of multiple websites is often underestimated. Two sites means two sets of updates, two compliance review processes, two sets of redirects when things move, twice the maintenance. Many firms discover this too late.

What this means for you: If you're considering a multi-site structure, map out the compliance and audience logic before making the technical decision. If the case for separation is strong, commit to it properly with a clear governance model for both sites. If the case is marginal, the operational simplicity of a single site is usually worth more than the perceived benefit of separation.

The main framework is the Financial Promotions Regime under the Financial Services and Markets Act. Any communication that invites or induces someone to engage in investment activity – which includes most marketing for FCA-regulated services – is a financial promotion. Financial promotions must be approved by an FCA-authorised person before they're communicated, and they must be fair, clear, and not misleading.

In practice, this affects: product pages, landing pages, paid advertising copy, email campaigns, social media posts, and anything on your website that describes your services in a way that could influence a purchase or engagement decision. Static factual content (how to contact you, a description of your regulatory status) is lower risk, but the line isn't always clear.

Risk warning requirements vary by product. Investment products have specific prescribed wording. Pension products have different requirements. High-risk investment vehicles have more prescriptive rules still. None of this is optional, and the FCA has been increasingly active in enforcement.

What this means for you: Every piece of outbound marketing content should be reviewed against the financial promotions requirements before publication. If you don't have in-house compliance resource, this means either a compliance consultant or a partnership with your agency that includes compliance checking as part of the process. Don't rely on the creative or marketing team to self-certify on financial promotions – the risk is too asymmetric.

The most common content risks for financial services firms fall into a few categories. First, unbalanced content – presenting the benefits of a product or service without adequately disclosing the risks. The FCA expects balance, and the more prominent the upside, the more prominent the risk disclosure needs to be.

Second, implied advice. Content that's structured or worded in a way that sounds like a personal recommendation – 'if you're looking to grow your pension, you should consider…' – can stray into regulated advice territory depending on context. The line between information and advice can be surprisingly fine.

Third, prominence and legibility of risk warnings. It's not enough to include a risk warning – it has to be visible. Small print, low contrast, or placement below the fold where most users won't see it may not satisfy the requirement for a warning to be 'clear and prominent.'

Fourth, evergreen content that becomes outdated. A page about interest rates, product features, or regulatory requirements that was accurate two years ago may no longer be. Published content needs to be reviewed regularly, not just when you're actively working on the site.

What this means for you: Do a content audit at least annually with compliance in mind. Flag pages that include performance data, product claims, risk warnings, or anything that could be construed as advice. Those pages should have a documented review date and a named owner responsible for keeping them current.

The financial penalties are the most visible part. The FCA can impose unlimited fines for serious breaches of the financial promotions rules, and they have. In recent years there's been increased enforcement activity around digital communications and social media in particular, with fines issued to firms for non-compliant promotions on channels they didn't fully recognise as being in scope.

Beyond direct fines, there's the cost of remediation: removing non-compliant content, reviewing and re-approving a large back catalogue of material, potentially writing to customers who received non-compliant communications. If a breach results in a consumer complaint or a mis-selling claim, the costs compound further.

The reputational damage is harder to quantify but is real. For financial services firms, trust is a core commercial asset. An FCA enforcement notice is public and findable. It affects client confidence, partner relationships, and sometimes the ability to hire.

The uncomfortable truth is that compliance failures in financial services marketing are rarely malicious. They're usually the result of a marketing team moving quickly without adequate review, or an agency that doesn't know the rules as well as they should. That doesn't reduce the liability.

What this means for you: Treat compliance in your marketing as you'd treat it in any other part of your business. The investment in building a robust review process is modest compared to the exposure of not having one. If your current setup doesn't include a clear process for reviewing digital communications against the financial promotions regime, that's worth addressing now rather than when something's gone wrong.

A CMS makes sense when people who aren't developers need to update the site regularly. If you're a marketing team publishing blog posts, updating team pages, or changing event listings, a CMS gives you the ability to do that without raising a ticket with your agency or developer. That independence has real value.

Static sites – where content is baked into the files at build time rather than pulled from a database – are faster, simpler, and more secure by default. They work well for sites that don't change often, or where all content updates are made by developers anyway. They're increasingly popular for product documentation and technical sites. The build process can be a bit more involved when you do need to make changes, though modern static site generators have improved significantly on this.

For most businesses with any meaningful marketing function, a CMS is the right call. The freedom to publish and update without a developer is worth the added complexity. For a simple corporate site that changes once a quarter and whose content is always reviewed by the same two people, a static approach is worth considering.

What this means for you: Think about who will update the site after launch, how often, and what kind of changes they'll need to make. If the honest answer is 'it'll probably be a developer or the agency doing most changes,' a static site might be cleaner. If marketing own the content roadmap, get a CMS.

A staging environment is a copy of your live website hosted somewhere that isn't public-facing. It's where you test changes before they go live – code updates, CMS upgrades, design changes, new integrations. Changes are tested on staging, verified, then deployed to production.

If you're making any significant changes to your website – even plugin updates on a WordPress site – you should be doing it on staging first. The consequences of updating something on a live site and breaking it are real: downtime, lost conversions, potential data issues. The consequences of breaking staging are nothing.

Some hosting environments include staging as a feature. Others require it to be set up separately. It's not expensive, and it's a standard part of how professional web teams work. If your agency or hosting provider doesn't offer staging, or hasn't mentioned it, ask about it.

What this means for you: If you don't currently have a staging environment, ask your agency or hosting provider to set one up. If you're on a basic shared hosting plan, you may need to move to a more capable setup. The cost of this is almost always justified by the first time it prevents a live-site incident.

The legal picture in the UK is clearer than it used to be. Public sector bodies have mandatory obligations under the Public Sector Bodies Accessibility Regulations. For private sector organisations, the Equality Act 2010 requires that reasonable adjustments are made to ensure services are accessible to people with disabilities – and courts have begun to interpret this as applying to websites.

The practical standard most businesses should be working to is WCAG (Web Content Accessibility Guidelines) 2.1 at Level AA. That covers things like sufficient colour contrast, keyboard navigability, screen reader compatibility, alternative text for images, and captions for video. It's not a ceiling – there's a higher level (AAA) – but AA is the commonly accepted baseline for compliance with legal obligations.

For financial services specifically, the FCA expects firms to treat customers with characteristics of vulnerability fairly. That has direct implications for digital accessibility. A website that excludes users with visual impairments, for example, is unlikely to satisfy that obligation.

What this means for you: If accessibility hasn't been part of your web project briefs before, start by running your current site through an automated checker like Axe or WAVE. Automated tools catch roughly 30-40% of accessibility issues – the rest need manual testing – but they'll give you an idea of where the gaps are. Make WCAG 2.1 AA a stated requirement in any web development brief.

There's no rule. The 'redesign every three years' thing you'll sometimes hear is more a product of agency business development cycles than any genuine insight about website lifecycles. Some sites look and perform perfectly well at five years old. Others are a liability at two.

The triggers that warrant a redesign are more useful than a calendar. If the site is no longer converting, if the brand has changed significantly, if competitors have moved on while you haven't, if it's technically difficult to update, or if the user experience has been generating complaints – those are real reasons. 'We haven't done anything in a while' isn't.

That said, regular investment in your website is usually more cost-effective than periodic large-scale redesigns. Iterating based on user feedback and performance data – improving key pages, testing different approaches – tends to produce better results than waiting until the site is bad enough to justify starting again.

What this means for you: Set up at least basic analytics and review them quarterly. If you can see where users are dropping off, which pages have high exit rates, or what search terms are bringing people to the wrong place, you have a basis for making targeted improvements. That data also makes the case for budget much easier to build than a vague 'we need a new site.'

The right answer depends on why you're considering it. If your current platform is working – content editors can update it without help, it performs well, it's maintained – the case for migration is weaker than it might seem. Migrations carry risk and cost, and 'WordPress is popular' isn't a reason to move if what you have is functional.

Reasons that might actually justify migration: the current platform is end-of-life or no longer supported; it requires significant developer involvement for content updates that should be self-service; it's poorly performing technically; or the agency that built it is now your only viable route for maintenance. Any of those is a reasonable basis for considering a move.

WordPress makes sense as the destination when you need a large content editing team, a rich plugin ecosystem, or a platform with a very wide pool of developer support. It's not always the right answer – there are platforms that are simpler, faster, or more appropriate depending on your needs.

What this means for you: Before committing to any migration, document what's wrong with the current setup and check whether those problems could be solved without migrating. Sometimes a CMS upgrade, a caching layer, or a different hosting environment fixes what seemed like a platform problem. Migration should be a last resort, not a default recommendation.

The answer varies by agency, which is one of the reasons website quotes are hard to compare. A baseline redesign typically includes discovery and scoping, information architecture, UX wireframes or prototypes, visual design, front-end build, CMS integration, basic on-page SEO setup, and browser and device testing. Some agencies include content migration; others don't. Most don't include content writing.

What commonly falls outside scope: copy and content creation, photography, video production, complex third-party integrations, ongoing hosting and maintenance, accessibility auditing beyond basic checks, analytics configuration, and performance optimisation beyond standard practice. Those aren't unreasonable exclusions – they're each a body of work in their own right – but you need to know they're not in the baseline before you compare quotes.

The things most likely to cause unexpected costs mid-project: content that arrives late or in a different format than expected, feedback from stakeholders who weren't involved in the original brief, requests to add functionality that wasn't mentioned upfront, and integrations that turn out to be more complex than originally assumed.

What this means for you: Ask for an itemised scope of work, not just a total figure. Then check it against your actual needs: do you have copy? Do you have photography? Will you need to connect to a CRM or data feed? Each gap between what's included and what you need is a cost you'll need to plan for.

A CMS migration involves moving your content from one platform to another – and depending on how different the platforms are, it can range from a well-structured process with limited risk to a complex, time-consuming exercise with plenty of opportunities for things to go wrong.

The main areas of risk are: content loss or formatting issues during migration; changes to URL structures that break existing inbound links and search rankings; integration failures when connecting the new CMS to third-party systems; and the time required to train content editors on a new interface. None of these are unavoidable, but they all need to be planned for.

A professional migration includes a URL redirect mapping exercise, so that your existing search rankings aren't lost because pages moved. It includes a thorough content audit to identify what's worth migrating versus what should be archived. And it includes a testing phase before the new site goes live, not just after.

What this means for you: If you're considering a migration, ask the agency specifically about URL redirect mapping and how they'll handle SEO continuity. That's the area where the most damage tends to happen when it's not planned for. Also ask whether there'll be a period of running both sites in parallel before the old one is switched off – that's usually worth the extra hosting cost.

A redesign changes how the site looks and how users move through it, while keeping – or largely keeping – the underlying technology. A rebuild replaces the technical foundation: the CMS, the hosting setup, the code architecture. The two can happen together, but they don't have to.

You might want a redesign without a rebuild if your current platform is fine but the site has become visually dated or the user experience has drifted. You might want a rebuild without a full redesign if the existing visual identity is broadly right but the site is built on something fragile, outdated, or unsupported.

Doing both at once is common, and it can make sense from a cost perspective – there are efficiencies when the same team is handling both simultaneously. The risk is that combining a technical migration with a full design overhaul increases the number of things that can go wrong. Separating them, with the technical migration happening first, sometimes produces better outcomes even if it means two projects rather than one.

What this means for you: Before scoping any project, work out what problem you're trying to solve. If the main issue is 'users can't find what they need,' that's a UX and information architecture problem – you may not need a full rebuild. If the main issue is 'our site runs on a platform that's no longer supported,' that's a technical problem that might not need a redesign. Being specific about the problem keeps the scope proportionate.

Design and search performance are almost entirely separate things. A site can be beautifully designed and completely invisible in search. The two aren't related except in the sense that a slow or poorly coded site can hurt rankings.

The most common reasons a good-looking site ranks poorly: the content is thin or written for internal audiences rather than for what people actually search for; the site has technical issues that prevent search engines from crawling it properly; there aren't enough credible external sites linking to it; or the site is competing for terms it has no realistic chance of ranking for given its authority.

Often it's a combination. A professional services firm might have a polished, credible-looking website but almost no editorial content, very few inbound links, and pages that are designed to describe what the firm does rather than answer the questions its prospective clients are actually typing into Google. That's a coherent business decision in some contexts – but it doesn't produce organic search traffic.

What this means for you: Run a basic technical audit using a free tool like Google Search Console. Check whether your pages are being indexed, whether there are crawl errors, and what terms you're currently appearing for. That'll tell you whether the issue is technical, content-based, or authority-based – and the fix for each looks very different.

WordPress security is a real consideration, but it's often over-stated in discussions that are trying to push you towards a different platform. The reality is that WordPress powers around 43% of the web – it's a large target, and vulnerabilities do get exploited. But virtually all serious WordPress security incidents are preventable with basic hygiene.

The majority of compromised WordPress sites have one of a handful of things in common: outdated core software, outdated or abandoned plugins, weak credentials, or no access restrictions on the admin login page. None of these are inherent flaws in WordPress – they're maintenance failures. A site that's being actively maintained by someone who knows what they're doing is not meaningfully more vulnerable than a site on any other platform.

Where it gets more complicated is plugin quality. The WordPress plugin ecosystem is enormous, and not all of it is well-maintained. A plugin that was last updated three years ago and has known vulnerabilities is a risk. Part of competent WordPress hosting and maintenance is keeping an eye on that and acting when a plugin becomes a liability.

What this means for you: If you're using WordPress, make sure your hosting includes a Web Application Firewall, that core and plugins are being updated regularly, and that you have automated backups with tested restores. If your current setup doesn't include those things, that's the conversation to have – not whether to move off WordPress entirely.

'Ongoing support' covers a wide range and agencies define it differently, which makes comparing costs difficult. At its most basic, it means someone will fix things when they break. At a more useful level, it means proactive maintenance: keeping WordPress core and plugins updated, monitoring for security issues, managing backups, and having someone available to make content or minor functional changes without going through a full project brief.

A basic maintenance-only package for a WordPress site might run £150-£400 per month depending on complexity. That typically covers updates, backups, monitoring, and perhaps an hour or two of minor amends. A fuller retainer that includes a defined block of development or content hours each month will be more – £600-£1,500+ is common for a meaningful level of support.

What you want to avoid is paying for a support contract that is essentially a promise to respond if something breaks, with no proactive work included. Those tend to look cheap until the site gets hacked or goes down and you find out that 'support' meant email response within 48 hours.

What this means for you: Ask any agency what specifically is included in their support package and what falls outside it. Get a clear answer on response times, whether updates are included or billable separately, and what happens if there's a security incident. If they can't answer those questions precisely, the package isn't well-defined enough to be reliable.

WordPress's main argument is familiarity and flexibility. There's a large pool of developers who know it, a huge ecosystem of plugins and themes, and a CMS that most non-technical users can manage after a short introduction. For a business that needs content editors who aren't developers to update the site regularly, that accessibility matters.

Webflow is a strong alternative for marketing sites where the design team wants more direct control. It produces clean code and the hosting is good. The limitations appear when you need complex content structures, significant custom functionality, or deep integrations. It can also become expensive at scale.

Statamic is less well-known but worth considering for projects where performance and security are priorities – it doesn't use a database in the traditional sense, which removes a whole category of vulnerability. The downside is a smaller developer pool and fewer off-the-shelf extensions than WordPress.

Building custom makes sense when no existing platform fits your requirements without significant compromise. It's the most expensive option and creates the most maintenance dependency on the team that built it, so it should only be chosen when there's a genuine case for it.

What this means for you: Platform choice should follow from requirements, not precede them. Think about who needs to edit the site, what integrations you need, how much ongoing development you're expecting, and who will maintain it in three years. Those factors will usually point you towards the right choice more reliably than a feature comparison.