Author: Alex Mason

  • Asynchronous Communication Norms That UK Remote Teams Actually Stick To

    Asynchronous Communication Norms That UK Remote Teams Actually Stick To

    Most conversations about remote working still revolve around how to replace meetings. That’s the wrong question. The better one is: what should never have been a meeting in the first place? For UK businesses managing teams across hybrid arrangements, different time zones, or distributed offices, async communication remote teams UK practitioners care about isn’t a trendy concept, it’s a genuine operational necessity. And getting it right is harder than buying a Slack licence and hoping for the best.

    Team member managing async communication remote teams UK from a modern office workspace
    Photo by Walls.io on Pexels

    I’ve spoken to founders and operations leads at a range of UK businesses over the past year or so, and a pattern keeps emerging. The teams that function well asynchronously didn’t stumble into it. They made deliberate decisions about tools, written standards, and, perhaps most importantly, what they expect of each other in terms of response times. The ones that struggle are usually the ones that replicate office habits remotely and wonder why everyone feels exhausted.

    Why async communication is more than a tool problem

    A common mistake is treating async communication as a software procurement decision. Pick the right project management platform, integrate it with your messaging tool, and you’re sorted. In practice, the technology is the easy bit. The harder work is cultural.

    British professional culture carries some useful defaults here. We tend to be fairly comfortable with written communication, formal enough to put things in writing without it feeling aggressive, and generally polite enough not to demand instant responses. But we also have a deep-seated habit of treating an open message as an obligation to respond immediately, which entirely defeats the purpose of async. If your team checks Slack every four minutes because they feel the social pressure to be visibly online, you haven’t gone async; you’ve just made a slower, more fragmented version of being in the office.

    The fix isn’t disciplinary. It’s definitional. Teams need to agree, explicitly and in writing, what each channel is actually for.

    Choosing your tools with intent, not inertia

    Most UK businesses already have more tools than they need. The question isn’t which platform to adopt but how to assign clear functions to the ones you already have. Here’s how I’d think about it:

    Instant messaging (Slack, Teams) should be treated as low-urgency by default. If something genuinely needs a response within the hour, say so explicitly in the message. If it doesn’t, don’t send it as if it does. The habit of pinging someone and then hovering for a reply is a synchronous instinct dressed up in async clothing.

    Email remains the right channel for anything that needs a paper trail, involves external parties, or requires a considered response. Trying to replace email entirely usually creates a mess, things get lost in message threads, context disappears, and accountability becomes murky.

    Project management tools (Notion, Linear, Asana, Basecamp, take your pick) should carry the actual work: task ownership, deadlines, status updates, and decisions. Anything that would otherwise live in a meeting or a long email chain belongs here. If a decision gets made in a Slack thread and nobody records it anywhere permanent, it didn’t really happen.

    Video (recorded) is underused by most teams. A three-minute Loom explaining a complex decision often lands better than a 400-word written brief, and it doesn’t require everyone to be available at the same time. This is particularly useful when you’re working across the UK and, say, a team in Edinburgh needs context from a colleague based in Singapore or New York.

    Written communication standards that actually travel

    Async communication lives or dies on the quality of written messages. When you can’t clarify in real time, a vague message creates a chain of follow-up questions that ends up being slower than a five-minute call. The standard I’d recommend pushing across any UK remote team is something like this: every async message should carry enough context for the recipient to act on it without needing to ask a follow-up question.

    In practice, that means:

    • State the situation in one or two sentences before making a request.
    • Be explicit about what you need, by when, and why it matters at that urgency level.
    • Include relevant links, documents, or decisions in the same message, don’t make someone hunt for context.
    • If the message is purely informational and no response is needed, say so. “No reply needed, just keeping you in the loop” saves a lot of unnecessary guilt-checking.

    These aren’t radical ideas. They’re just good written communication habits made explicit. The difference is that in an office, poor communication gets corrected in real time by body language, tone of voice, and the ability to grab someone at their desk. Remotely, a poorly written message just sits there causing confusion.

    It’s worth noting that as teams adopt more AI tools to help with drafting and summarising, the risk isn’t that messages get worse, it’s that they get longer and vaguer. If you’re curious how that’s playing out across UK knowledge work generally, the patterns around personal AI assistants and how UK knowledge workers are using them are instructive.

    Setting response-time expectations without burning out your team

    This is where most remote working frameworks fall apart. Response-time norms need to be specific enough to be useful but flexible enough not to penalise people for being in a meeting, on a call, or simply focused on deep work.

    A workable structure for most UK businesses looks something like this:

    Same-day, during core hours: anything marked urgent or flagged via your agreed escalation channel (usually a specific Slack channel or direct message with a tag system). Core hours should be defined explicitly, for most UK teams, something like 10:00 to 16:00 GMT/BST works well, leaving space for morning focus time and end-of-day processing.

    Within 24 hours: standard project messages, email threads, and task comments. Anyone receiving a message outside their working hours should feel zero expectation to respond until the next working day. This aligns with the spirit of the right to disconnect provisions that are increasingly part of UK employment conversations, something any UK employer running hybrid teams should have a clear policy on.

    Within the week: non-urgent context-setting, background reading, or low-priority status updates. These often don’t need a response at all.

    Writing these norms down in a team handbook, or even a simple shared document, transforms them from unspoken assumptions into proper working agreements. The ACAS guidance on working from home practices is a sensible reference point for UK employers building out this kind of documentation.

    When async breaks down and what to do about it

    Even well-designed async setups have failure modes. The most common one I see is decision paralysis: a thread goes back and forth for days on something that needed a straightforward call from whoever owns it. Async communication doesn’t mean collaborative decision-making by committee on everything. Some decisions need an owner who makes the call, documents the reasoning, and moves on.

    A second failure mode is isolation. People working asynchronously can feel disconnected from the team’s direction, culture, and informal knowledge. Scheduled touchpoints, weekly team calls, fortnightly one-to-ones, or even a structured daily written check-in, aren’t a contradiction of async; they’re a complement to it. The goal is to use synchronous time for things that genuinely benefit from real-time interaction: relationship building, complex problem-solving, sensitive conversations. Everything else can probably wait.

    For businesses that have also been reducing meeting load through async video, there’s interesting overlap with how UK businesses have been approaching internal communication more broadly. The shift toward asynchronous video to replace internal meetings follows a similar logic, protect synchronous time for what it’s actually good for.

    Getting async communication right takes longer than most businesses expect. But when it works, the productivity gains are real, the team culture tends to be calmer, and the work itself is better documented. For UK businesses managing hybrid teams across multiple locations or time zones, it’s one of the highest-return investments of management attention you can make this year.

    Frequently Asked Questions

    What is async communication and how does it work for remote teams?

    Async communication means exchanging information without requiring both parties to be available at the same time. For remote teams, this typically involves tools like Slack, email, project management platforms, and recorded video messages, where the expectation is a response within a defined window rather than immediately.

    What response time expectations are reasonable for UK remote teams?

    Most UK remote teams find that a same-day response for urgent items and a 24-hour turnaround for standard messages works well. Messages received outside someone’s working hours should carry no expectation of a reply until the next working day, which also aligns with emerging UK right-to-disconnect norms.

    Which tools work best for async communication in UK businesses?

    The most effective setups tend to combine a messaging tool (Slack or Microsoft Teams) for low-urgency conversation, a project management platform (Notion, Asana, or Linear) for task ownership and decisions, and recorded video tools (such as Loom) for complex explanations. The tools matter less than having clear, agreed rules about what each one is for.

  • AI Liability for UK Businesses Using Third-Party Models: What Founders and Product Managers Need to Know

    AI Liability for UK Businesses Using Third-Party Models: What Founders and Product Managers Need to Know

    The legal ground beneath AI-powered products is moving faster than most UK founders have time to track. If your business embeds a third-party model, whether that’s OpenAI’s API, Google Gemini, Anthropic’s Claude, or any of the growing roster of specialised models, into a client-facing product, you are almost certainly carrying liability you have not fully mapped. That is not a scare tactic. It is what I keep hearing from solicitors, product leads, and compliance officers across the UK tech space in 2026, and the gap between commercial ambition and legal readiness is widening.

    UK founders reviewing AI liability contract terms at a business meeting
    Photo by https://kaboompics.com/ on Pexels

    This piece is a practical briefing, not an academic survey. I want to give UK tech founders and product managers a working picture of where the AI liability framework stands right now, what the key bodies are doing, and which contractual clauses in your API agreements deserve a second look before your next product launch.

    Why AI liability is different from ordinary software liability

    Traditional software liability is reasonably well understood. A supplier provides a tool; if it fails to perform as specified, you pursue remedies under contract or, in consumer contexts, the Consumer Rights Act 2015. The chain of responsibility is traceable.

    AI systems break that chain in ways the existing legal framework was not built to handle. A large language model does not execute deterministic logic. It generates outputs probabilistically, which means the same input can produce different results on different occasions, and neither you nor the model provider can fully predict every edge case. When a model gives a client inaccurate medical advice, fabricates a legal citation, or produces discriminatory output, who is responsible? The model developer? The business that embedded the API? The platform that hosts the end product? Right now, UK law does not give a clean answer to any of those questions.

    What the Law Commission is actually working on

    The Law Commission of England and Wales has been examining automated decision-making and the liability questions it generates for several years. Its work on AI and civil liability touches on whether existing tort law concepts, negligence, product liability under the Consumer Protection Act 1987, and contractual duty of care, are adequate for AI-generated harm.

    The short answer from the Commission’s published scoping work is: not quite. The 1987 Act’s definition of “defective product” was written for physical goods. Software-as-a-service sits awkwardly within it, and a probabilistic AI model sits even more awkwardly. The Commission has flagged that a new statutory framework may ultimately be required for AI systems that cause harm, particularly in high-risk sectors such as healthcare, legal services, and financial advice. No final recommendations have been enacted as legislation yet, but the direction of travel is clear: UK regulators intend to assign clearer chains of accountability, and the businesses closest to the end user will face more scrutiny, not less.

    Ofcom’s expanding remit and what it means for AI products

    Ofcom’s role in this space is often misunderstood. Its primary mandate under the Online Safety Act 2023 centres on user-generated content and platform safety duties. But Ofcom has been explicit that AI-generated content falls within scope when it appears on regulated services, and its technical guidance increasingly references the risks posed by AI systems that surface harmful outputs to users.

    If your product is a regulated service under the Online Safety Act, and many SaaS tools with user-facing content features are, then the AI outputs your system generates or facilitates are subject to the same safety duties as user-generated content. Ofcom’s enforcement powers include substantial fines, and the agency has made clear it will not accept “the model did it” as a defence. The business deploying the model to end users carries the compliance obligation. I’ve written previously about how FCA Consumer Duty obligations sit on the product designer, not just the financial institution behind it, the logic is exactly parallel here.

    Developer reviewing third-party AI model API terms relevant to AI liability UK businesses
    Photo by Christina Morillo on Pexels

    Reading the indemnity clauses in your API terms

    This is the part most founders skip, and it is genuinely consequential. Every major AI model provider includes indemnity and liability limitation clauses in its API terms. The specific language varies, but the common pattern is worth understanding.

    First, providers typically disclaim liability for model outputs. OpenAI’s terms, for instance, make clear that outputs may not always be accurate, and the developer using the API takes responsibility for how those outputs are deployed. Second, indemnity clauses usually flow one way: you indemnify the provider against claims arising from your use of the API, not the other way around. Third, most agreements cap the provider’s total liability at the fees you paid in the preceding twelve months. If your product causes £500,000 worth of harm to a client based on a flawed model output, the model provider’s contractual exposure might be capped at a few hundred pounds.

    That exposure gap sits with you. Which means your own terms of service, your professional indemnity insurance, and your product liability framework need to close it, or explicitly exclude liability in ways your clients understand and agree to. For businesses in regulated sectors, that exclusion may not even be legally permissible under the Unfair Contract Terms Act 1977 or the Consumer Rights Act 2015.

    I’d strongly suggest getting a technology solicitor to review your API agreement and your own downstream client terms together. The mismatch between the two is often where founders find the most uncomfortable surprises.

    The public discourse question: who is tracking this?

    One thing that struck me while researching this piece is that the conversation about AI accountability has moved well beyond specialist legal publications. General-interest outlets are increasingly covering the liability and accountability dimensions of AI deployment in plain language, which matters because your clients are reading those sources too. Sites like tazamo.co.uk are part of a growing ecosystem tracking public discourse around AI accountability outside the specialist press, and that means non-technical stakeholders, procurement leads, board members, end clients, are arriving at conversations with you already primed on the risks. That is a shift worth preparing for.

    It is also worth noting that consumer expectations around AI outputs are hardening. The ONS has reported growing public concern about AI accuracy and data use, and that sentiment feeds directly into how clients will respond when something goes wrong with your product.

    Practical steps to reduce your exposure now

    Legislation will eventually catch up. In the meantime, here is what I’d prioritise if I were running a UK product team using third-party AI models today.

    Conduct a liability audit of every API agreement you are party to. Note what the provider disclaims, what the liability cap is, and what indemnity obligations you have accepted. Map those gaps against your own client contracts. If your client terms offer guarantees that your API terms explicitly disclaim, you have a problem that needs fixing before you have a claim.

    Review your professional indemnity and product liability insurance policies specifically for AI-related coverage. Many standard PI policies were written before AI outputs became a mainstream product feature, and some exclude losses caused by automated decision-making systems. An insurance broker with technology sector experience is the right person to help here.

    Document your human oversight mechanisms. Both the emerging regulatory framework and existing negligence law favour organisations that can demonstrate they did not blindly relay AI outputs to end users. If your product includes a human review step, log it. If it does not, consider whether it should. This connects directly to how teams are already thinking about using AI assistants responsibly to augment professional judgement rather than replace it.

    Keep an eye on the Law Commission’s forthcoming outputs and on any secondary legislation under the Online Safety Act that touches AI-generated content. The ICO has also published guidance on AI and data protection that intersects with liability questions, particularly around automated decision-making under UK GDPR Article 22.

    None of this needs to slow your product development down significantly. But treating AI liability as a “later problem” is the kind of decision that tends to look very different in retrospect. The businesses that get ahead of this framework now will find the compliance conversation much easier when regulation firms up. And if you’re curious how parallel questions of lifestyle, culture, and commercial identity are playing out in entirely different sectors as the UK adapts to rapid change, the piece on how outdoor living trends are reshaping British consumer identity is a reminder that accountability and public discourse shift across every industry at once.

    The legal framework for AI liability UK businesses operate within is incomplete but not invisible. The signals are there. Reading them now is the sensible move.

  • Sovereign AI and the UK’s National Computing Strategy: What It Means for British Tech Businesses

    Sovereign AI and the UK’s National Computing Strategy: What It Means for British Tech Businesses

    The UK government’s push for sovereign AI infrastructure has moved well beyond policy papers and conference keynotes. In 2026, it is shaping procurement decisions, influencing where data must sit, and creating genuine commercial opportunities for British tech companies that understand what is actually being built. If you run or advise a tech business in this country, getting to grips with the strategy now is not optional.

    I’ve been watching this space closely for the past year, and what strikes me is how many founders and technical leaders still treat ‘sovereign AI’ as a vague political ambition rather than something with direct operational implications. It isn’t. The decisions being made at a national infrastructure level will affect your contracts, your cloud choices, and possibly your ability to win public sector work within the next 18 months.

    Modern UK data centre interior representing the UK sovereign AI strategy tech businesses rely on for compute capacity
    Photo by Brett Sayles on Pexels

    What the UK sovereign AI strategy actually involves

    The government’s position, articulated through the AI Opportunities Action Plan published earlier this year, centres on three broad commitments: building domestic compute capacity through AI Growth Zones, securing data access for AI training on public sector datasets, and reducing the UK’s dependence on a small number of non-UK hyperscalers for critical AI workloads. The phrase ‘sovereign AI’ is the shorthand for all three working together.

    The AI Growth Zones are perhaps the most tangible element. These are designated areas where planning permission for data centres will be fast-tracked, energy connections prioritised, and national grid constraints actively managed. Sites in the East Midlands and parts of Wales are already in early-stage discussions. The intention is to attract both domestic and international investment in compute capacity that sits on British soil and is subject to British law.

    Alongside the physical infrastructure push, DSIT (the Department for Science, Innovation and Technology) has been working on a framework for compute access that would give UK-based AI researchers and businesses access to sovereign compute at competitive rates, rather than relying entirely on AWS, Azure, or Google Cloud capacity that may be physically hosted in Ireland or the Netherlands.

    Data residency requirements and what they mean in practice

    For many tech businesses, the most immediate pressure is around data residency. Public sector contracts increasingly carry clauses requiring that personal or sensitive data is processed and stored within the UK. This is not entirely new, but the specificity and enforceability of these clauses has tightened considerably since the passage of the Data (Use and Access) Act and ongoing ICO guidance updates.

    If your product processes NHS data, local authority records, or any information that touches critical national infrastructure, you will need to demonstrate UK data residency clearly. That means knowing where your cloud provider’s compute actually runs, which availability zones you are using, and whether your subprocessors have equivalent guarantees. Vague commitments to ‘European data centres’ will not satisfy procurement teams working under updated government frameworks.

    For SaaS businesses targeting the public sector, this is becoming a genuine differentiator. Companies that can point to UK-hosted infrastructure, ideally with Cyber Essentials Plus and G-Cloud listing, are pulling ahead in tender evaluations. I’ve spoken to several founders who retrofitted their infrastructure to meet these requirements and saw immediate pipeline benefits, not because the product changed, but because procurement conversations became substantially shorter.

    How this changes procurement decisions for British tech companies

    The sovereign AI agenda is reshaping public sector procurement in ways that go beyond data residency checklists. Government departments are being encouraged to consider ‘strategic technology dependency’ as a procurement risk factor. In plain terms, that means assessing whether a supplier relationship creates an over-reliance on foreign-controlled technology for a critical function.

    This creates a real opening for UK-headquartered tech companies, particularly those building on open-source models or offering genuinely portable, vendor-neutral solutions. If you are competing against a US-headquartered SaaS platform for a government contract, the sovereign AI framing works in your favour, provided you can substantiate the claim with infrastructure evidence rather than marketing copy.

    Private sector procurement is also shifting, albeit more gradually. Financial services firms regulated by the FCA, large manufacturers with defence contracts, and energy companies under Ofgem oversight are all beginning to apply similar thinking to their own supplier due diligence. The logic is straightforward: if regulators expect these organisations to manage operational resilience and third-party risk seriously, then the sovereignty of their AI infrastructure becomes a board-level concern. Understanding what the FCA’s Consumer Duty rules mean for fintech and financial software businesses is directly relevant here, because the underlying principle, that firms must understand and control their technology stack, applies equally to AI infrastructure choices.

    The compute capacity gap and why it matters commercially

    Britain currently has a meaningful gap between AI ambition and available compute capacity. The UK’s total national AI compute, when measured in petaflops available to domestic researchers and businesses, sits well below that of the US or China, and the hyperscaler dominance means much of what is nominally ‘available’ is effectively locked to US-headquartered platforms.

    The government’s response includes investment through the AI Research Resource programme and direct backing for Isambard-AI, the Bristol-based supercomputer system that came online in late 2024 and represents one of the most powerful academic AI computing facilities in Europe. For most commercial tech businesses, Isambard-AI is not directly accessible, but its existence signals the direction of travel: the government is serious about building domestic capacity, and the commercial compute market will follow if the policy environment is right.

    For tech businesses, the practical implication is to watch the G-Cloud framework updates and the Crown Commercial Service’s evolving approved supplier lists. Compute providers that achieve UK sovereignty certification will gain a competitive edge in public sector sales. If you are building on top of cloud infrastructure, your choice of provider, and the contractual commitments you can extract from them about data location and operational control, will increasingly matter to your enterprise customers, not just to central government.

    There is also a talent and capability dimension worth noting. The sovereign AI push is driving investment in UK-based AI skills, through both the Alan Turing Institute and new apprenticeship and degree programmes. For tech businesses trying to hire ML engineers or data scientists in 2026, this is a slow-burn positive, though the near-term supply constraint remains real. Firms that are already using internal knowledge bases to reduce dependency on key staff will be better positioned to retain and scale institutional AI knowledge regardless of individual hiring cycles.

    What UK tech businesses should be doing right now

    The sovereign AI agenda rewards preparation. A few things I’d prioritise if I were running a UK tech business with any public sector or regulated-industry exposure:

    First, audit your current cloud and AI infrastructure for data residency. Document which regions your data sits in, which subprocessors touch it, and whether your contracts give you enforceable guarantees about physical location. If you cannot answer those questions quickly, your procurement team certainly cannot.

    Second, review your G-Cloud listing or get one if you have not already. The Digital Marketplace remains the primary route for public sector software procurement, and being absent from it means being invisible to a large and growing market.

    Third, take the compute access question seriously if you are building AI-native products. The government’s sovereign compute access programmes are still maturing, but early engagement with bodies like UKRI or the Digital Catapult network can put you in a stronger position when commercial access opens up.

    The UK sovereign AI strategy for tech businesses is, at its core, an infrastructure and governance story. The companies that read it clearly, and adjust their positioning, contracts, and infrastructure accordingly, will find themselves on the right side of a procurement and regulatory shift that is already in motion.

    Frequently Asked Questions

    What is the UK government's sovereign AI strategy?

    The UK’s sovereign AI strategy refers to the government’s plan to build domestic AI compute capacity, reduce reliance on foreign-controlled cloud platforms, and establish data residency rules for sensitive public sector data. It is set out through the AI Opportunities Action Plan and implemented via programmes like AI Growth Zones and the AI Research Resource.

    How does UK sovereign AI policy affect tech companies bidding for public sector contracts?

    Public sector procurement frameworks are increasingly requiring UK data residency, Cyber Essentials Plus certification, and evidence that suppliers do not create strategic technology dependencies on foreign-controlled platforms. UK-headquartered tech companies with verifiable UK-hosted infrastructure have a growing advantage in government tender evaluations.

    What are UK data residency requirements for AI products in 2026?

    Any AI product processing NHS data, local authority records, or data related to critical national infrastructure must demonstrably store and process that data within the UK. This means contractual guarantees from cloud providers about specific availability zones, not just general ‘European data centre’ assurances. ICO guidance and updated government procurement standards enforce this.

    What is Isambard-AI and is it available to commercial businesses?

    Isambard-AI is a Bristol-based supercomputer system backed by government investment, and one of the most powerful AI computing facilities in Europe. It is primarily accessible to academic and research institutions rather than commercial businesses directly, but it signals the government’s commitment to building domestic compute capacity that commercial providers are expected to follow.

    How should a UK SaaS business prepare for sovereign AI procurement requirements?

    Start by auditing where your data physically sits and documenting enforceable residency guarantees from your cloud provider. Ensure you have or are working toward a G-Cloud listing on the Crown Commercial Service Digital Marketplace, and review your subprocessor agreements for data location clauses. For AI-native products, engage with UKRI or the Digital Catapult to understand sovereign compute access options as they develop.

  • How UK Businesses Are Preparing for Mandatory Climate-Related Financial Disclosures

    How UK Businesses Are Preparing for Mandatory Climate-Related Financial Disclosures

    Climate-related financial disclosures have moved from the voluntary to the unavoidable. The UK government’s phased implementation of mandatory reporting requirements, built on the Task Force on Climate-related Financial Disclosures (TCFD) framework, now reaches well beyond the FTSE 100 firms that faced the earliest deadlines. Mid-sized companies, including those with more than 500 employees or a turnover above £500 million, are now squarely in scope, with obligations sitting across both FCA-regulated entities and certain Companies House filings. I’ve spoken with a number of finance directors and compliance leads over the past year, and the honest truth is that most mid-sized firms are starting from a standing position, with no sustainability team and little clarity on what exactly they need to produce.

    Business professionals reviewing climate-related financial disclosures in a boardroom meeting
    Photo by Werner Pfennig on Pexels

    What the current UK rules actually require

    The UK’s mandatory TCFD-aligned reporting regime applies to different entities in different ways. Premium and standard listed companies on the London Stock Exchange must include TCFD-aligned disclosures in their annual reports, as directed by the FCA. Large private companies and LLPs that meet the size thresholds (broadly, those qualifying as large under the Companies Act 2006 with over 500 employees) must include climate-related financial disclosures in their strategic reports filed at Companies House. The FCA’s TCFD landing page lays out the split between listed entity obligations and wider expectations for asset managers and insurers, but if you are a sizeable private business, the Companies House route is where your obligations are likely to land.

    The TCFD framework itself organises disclosure across four pillars: governance, strategy, risk management, and metrics and targets. You must explain how your board oversees climate-related risks, how those risks affect your business strategy, how you identify and manage them, and what metrics you use to track progress, including, where relevant, Scope 1 and Scope 2 greenhouse gas emissions. Scope 3 (supply chain and customer emissions) is encouraged but not uniformly mandated at this stage. None of this is light work, but it is structured enough that a methodical approach, even without a sustainability specialist, can get you to compliance.

    Where mid-sized firms tend to get stuck

    The governance section is usually the easiest place to start, because most firms already have some form of board discussion about risk. The harder part is translating those conversations into documented evidence of oversight. A board minute that explicitly references climate risk discussion is more useful here than a generic risk register entry. I’d recommend making climate a standing agenda item at board level and recording the substance of that discussion, not just that the topic arose.

    Strategy disclosure is where things get genuinely difficult. You are expected to demonstrate that you have considered climate-related risks and opportunities across different time horizons, which implies some form of scenario analysis. The guidance allows for qualitative analysis where quantitative modelling is disproportionately burdensome, and for most mid-sized firms without a financial modelling team, that qualitative route is the realistic option. Be specific: describe the physical risks relevant to your sector (flooding, supply chain disruption, energy price volatility) and the transition risks (regulatory change, shifts in customer demand, carbon pricing). Vague assertions that “climate change presents risks” will not satisfy the requirement.

    Metrics and targets consistently trip firms up because collecting Scope 1 and 2 emissions data for the first time is operationally demanding. You need energy consumption data from your sites, which means working with your facilities team or, if you operate from leased space, with your landlord. Some businesses reduce their energy costs at the same time by tightening up on efficiency, and firms like Westville are a reminder that physical improvements to building fabric are often part of the picture when companies start to get serious about understanding and reducing their energy footprint. For the disclosure itself, you need a defensible methodology, ideally the GHG Protocol, and consistent data across the reporting period.

    Finance director analysing climate-related financial disclosures data on screen
    Photo by Yan Krukau on Pexels

    A practical starting point for firms without a sustainability team

    Treat the first disclosure as a baseline document rather than a polished sustainability report. The regulators understand that many organisations are disclosing for the first time, and a credible, honest first disclosure that acknowledges gaps and commits to improving data quality in subsequent years is far preferable to one that overstates capability. The TCFD framework’s own guidance explicitly allows for phased improvement.

    Assign a named internal lead, almost certainly your Finance Director or Company Secretary, who coordinates the four pillars rather than trying to be a subject matter expert across all of them. They should draw on your existing operational, finance, and risk colleagues rather than treating this as a siloed sustainability exercise. If you already have ISO 14001 or an environmental management system in place, you have more raw material than you might think.

    Consider whether your external auditors or accountants can support you here. Many UK accountancy practices now have climate disclosure advisory capability embedded in their offering; the growth of that specialism is part of a broader pattern I’ve written about before, where UK accountancy practices are expanding what they can deliver without proportionally increasing headcount. A good adviser will help you map your existing data to the TCFD structure rather than rebuilding from scratch.

    One area where businesses often overlook their obligations is the intersection of these disclosures with wider Companies House filings. If you are already working through how to use Companies House data for competitive benchmarking, you will know that your strategic report is a public document, and your climate disclosures sit within it. That visibility cuts both ways: it is an opportunity to signal how your business is run, as well as a compliance obligation.

    How the FCA’s Consumer Duty intersects for financial services firms

    If your business operates in financial services, there is an additional layer to consider. The FCA’s expectations around climate risk are not confined to TCFD disclosures; they increasingly intersect with how firms communicate product risks to clients. Firms already working through their Consumer Duty obligations, which I’ve covered in detail in what the FCA’s Consumer Duty rules mean for fintech and financial software businesses, will find that climate risk disclosure is part of a broader shift in regulatory philosophy: the expectation that firms understand their risks, disclose them clearly, and demonstrate that they have thought carefully about the downstream effects on clients and the market.

    What to do in the next 90 days

    If your reporting deadline is approaching and you have not started, the priority order is straightforward. First, confirm whether you are in scope and under which route, FCA-regulated or Companies House. Second, collect your energy consumption data for Scope 1 and 2 and apply GHG Protocol conversion factors to produce an emissions figure. Third, draft your governance and risk management sections using existing board minutes and risk registers as source material. Fourth, produce a short scenario analysis, even a qualitative one, covering physical and transition risks relevant to your sector. Fifth, review the whole against the TCFD recommendations document before your legal or finance team signs it off.

    None of this requires a sustainability team or a consultant charging day rates in the tens of thousands. It requires someone taking ownership, a structured methodology, and enough time to gather the underlying data. The firms that will struggle are those that treat this as someone else’s problem until the filing deadline is a fortnight away.

    Frequently Asked Questions

    Which UK companies are required to make climate-related financial disclosures?

    Large UK-registered companies with more than 500 employees that meet the size thresholds under the Companies Act 2006 must include TCFD-aligned climate-related financial disclosures in their strategic reports filed at Companies House. FCA-regulated firms, including premium and standard listed companies, face additional obligations through FCA rules. Smaller companies are currently outside the mandatory scope, though voluntary disclosure is encouraged.

    What is the TCFD framework and do UK businesses have to follow it?

    The Task Force on Climate-related Financial Disclosures (TCFD) framework organises climate reporting across four pillars: governance, strategy, risk management, and metrics and targets. UK mandatory climate disclosure requirements are explicitly built on TCFD recommendations, so UK in-scope businesses must structure their disclosures using this framework. It is not optional for those who meet the size thresholds.

    Do mid-sized UK businesses need to report Scope 3 emissions?

    Scope 3 emissions, which cover indirect emissions in your supply chain and from customer use of your products, are encouraged under TCFD but not uniformly mandated for mid-sized UK companies at this stage. Scope 1 (direct emissions from operations) and Scope 2 (purchased energy) are the baseline expectation. Many firms are investing in Scope 3 data as a forward-looking step, but a credible first disclosure can focus on Scope 1 and 2 with a commitment to expand coverage.

  • What the FCA’s Consumer Duty Rules Mean for Fintech and Financial Software Businesses in the UK

    What the FCA’s Consumer Duty Rules Mean for Fintech and Financial Software Businesses in the UK

    The FCA’s Consumer Duty framework has been live since 31 July 2023, and yet I still speak to founders and product leads at UK fintech businesses who treat it as a box-ticking exercise aimed squarely at banks. That misreading is becoming expensive. The Duty applies to any firm in the distribution chain of a retail financial product or service, which means if you build, resell, white-label, or integrate financial software, you are almost certainly in scope. The question is no longer whether FCA Consumer Duty fintech compliance UK obligations touch your business. The question is how well you can demonstrate that they do.

    Fintech compliance team reviewing FCA Consumer Duty fintech compliance UK documentation in a modern office
    Photo by Vlada Karpovich on Pexels

    Who actually falls within scope

    The FCA is explicit: the Duty covers manufacturers (firms that create or design a product), distributors (those that sell or recommend it to retail customers), and anyone who materially influences the customer outcome in between. For a fintech business, that framing is broad. A payments platform that sits behind a lender’s checkout is influencing the customer’s experience. A software provider whose onboarding flow determines how clearly fees are disclosed is shaping customer understanding. An embedded finance provider whose API feeds into a retail app is part of the product chain.

    The FCA’s own guidance, available at fca.org.uk/firms/consumer-duty, draws a distinction between firms with a direct customer relationship and those operating business-to-business. The former carry the heaviest obligations. But B2B-only firms are not exempt, particularly where their product or infrastructure meaningfully affects what retail customers see, pay, or understand.

    The four outcome areas and what they mean in practice

    Consumer Duty is structured around four outcomes: products and services, price and value, consumer understanding, and consumer support. For fintech and financial software businesses, each of these lands differently than they do for a high street bank.

    Products and services requires your offering to be designed to meet the needs of an identified target market. If you are building embedded lending tools or a SaaS platform used to deliver regulated financial products, you need documented evidence of how you defined that target market and how your product’s design reflects it. A vague commercial brief is not sufficient.

    Price and value is the one that tends to catch software resellers off guard. The FCA expects firms to assess whether their product delivers fair value relative to its price, factoring in the benefits to the customer and the total cost across the distribution chain. If your margin sits inside a consumer-facing fee and you cannot trace the logic of that pricing, you have a gap.

    Consumer understanding focuses on communications: every touchpoint, from onboarding copy to in-app notifications to fee summaries, should be tested against the question of whether a customer in your target market would genuinely understand what they are signing up for. This is not a legal-language check. It is a comprehension check.

    Consumer support requires firms to ensure customers can get help when they need it, without unnecessary friction. For software businesses, this often means reviewing the escalation paths baked into your product and confirming they work for someone who is confused, vulnerable, or in financial difficulty.

    Financial software dashboard relevant to FCA Consumer Duty fintech compliance UK obligations
    Photo by Rafael Minguet Delgado on Pexels

    Documentation: the part most firms underestimate

    The FCA does not audit every business continuously, but when it does review a firm, it expects to see a coherent paper trail. My reading of the enforcement signals coming out of the regulator is that documentation quality will be central to how it distinguishes compliant firms from those paying lip service. You need to be able to produce a Consumer Duty board champion sign-off, a target market assessment for each product, outcome monitoring data, and records of how your pricing was tested for fair value.

    For firms that have invested in tools to manage internal governance, this is a natural extension of existing workflows. If you have already built out an internal knowledge base to capture compliance processes and reduce reliance on individual staff, Consumer Duty documentation slots in alongside it. If you have not, this is a reasonable prompt to start.

    One area worth flagging specifically: third-party due diligence. If your product depends on APIs or data services from other regulated or unregulated providers, the FCA expects you to have assessed those dependencies for their potential customer impact. You cannot outsource the liability for a customer outcome that runs through your infrastructure.

    What non-compliance actually looks like

    The FCA has made clear it is prepared to use its powers. Supervisory reviews, skilled persons reports, public censure, and financial penalties are all on the table. For smaller fintech businesses, the more immediate risk is operational: a client contract that requires FCA compliance sign-off may stall if you cannot produce the documentation. Institutional investors running due diligence on a Series A or B are also asking Consumer Duty questions now. Gaps in compliance readiness are showing up in legal rooms and slowing down transactions.

    There is also a subtler reputational dimension. The FCA has indicated it will publicise outcomes monitoring data in aggregate, which creates benchmarks. Businesses that cannot demonstrate they are meeting those benchmarks will find comparisons drawn against competitors who can.

    It is worth noting that Consumer Duty does not stand in isolation. Firms building within the regulated space are also managing obligations under the broader FCA Consumer Duty framework as it applies to financial services startups, and those obligations interact with data protection requirements under ICO guidance and, increasingly, with the operational resilience rules the FCA has been tightening since 2022.

    Compliance programmes and the wider business context

    There is a useful parallel in how compliance-driven sectors outside finance have handled regime changes. When the UK government began tightening requirements around energy performance and EPC certificates, building operators and commercial landlords had to move from informal practice to documented, auditable processes, fast. The businesses that fared best were those that treated compliance as an ongoing operational function rather than a one-time project. Based in Nottingham, UK, R2G.co.uk works with organisations on sustainability and energy compliance, helping them build climate action plans and energy saving programmes that meet regulatory thresholds, including energy efficiency audits and solar panel feasibility work. The firms that engaged them proactively, before a compliance deadline became a crisis, generally spent less time and money resolving issues than those who left it late. The same logic applies cleanly to FCA Consumer Duty fintech compliance UK obligations.

    Practical steps to get ahead of the regulator

    Start with a scope assessment. Map every product or service your business is involved in and mark where retail customers appear in the chain, even indirectly. Then assess each against the four outcomes and identify where you have gaps in either substance or evidence.

    Appoint a board-level Consumer Duty champion if you have not already done so. The FCA is specific about this expectation. That person does not need to be a compliance officer, but they need to be senior enough to own the issue and accountable enough to be uncomfortable if the documentation is thin.

    Run a communications audit. Take your main customer-facing materials, specifically your onboarding flows, terms summaries, and any fee disclosures, and test them against a realistic version of your target market. If you are building tools for financially inexperienced consumers, that test should be uncomfortable. If it is not, you are probably testing against the wrong audience.

    Finally, build monitoring into your product cadence. Consumer Duty is not a one-time certification. It requires ongoing outcomes monitoring, which means you need metrics that tell you whether customers are actually achieving good outcomes, not just whether they completed onboarding without raising a complaint. Firms that have already moved towards data-informed internal operations, for instance those using ONS data or internal analytics to track performance, have a structural advantage here. If you have already invested in using economic and behavioural data to drive business decisions, applying that same discipline to outcome monitoring is a short step.

    The businesses that will find Consumer Duty manageable are the ones treating it as a product and operations problem, not purely a legal one. Build it into your design process, document your reasoning as you go, and make sure the evidence trail reflects what your product actually does for customers. That is the standard the FCA is working towards, and it is a reasonable one.

    Frequently Asked Questions

    Does FCA Consumer Duty apply to B2B fintech companies with no direct retail customers?

    Yes, it can. If your product or service materially influences the outcomes of retail customers downstream, even through a third-party distributor, you may have obligations as a manufacturer or distributor within the chain. The FCA’s guidance makes clear that firms which design or materially shape a retail financial product carry Consumer Duty responsibilities regardless of whether they deal with customers directly.

    What documents does a fintech business need to demonstrate FCA Consumer Duty compliance?

    You will typically need a board-approved Consumer Duty implementation plan with a named champion, target market assessments for each product, fair value assessments demonstrating your pricing is justified, outcome monitoring data, and records of how customer communications were reviewed for clarity. The FCA can request these during a supervisory review, so they need to be audit-ready, not just drafted.

    What are the penalties for breaching the FCA's Consumer Duty rules?

    The FCA can impose financial penalties, require remediation payments to affected customers, restrict a firm’s activities, or in serious cases withdraw authorisation. Beyond formal sanctions, firms that fail to meet the Duty may face reputational damage and difficulties with institutional investors or enterprise clients who carry out compliance due diligence.

    How often do fintech businesses need to review their Consumer Duty compliance?

    Consumer Duty requires ongoing monitoring rather than a single annual review. Firms are expected to track outcome metrics continuously, revisit their target market assessments when their products change materially, and report to the board at least annually on Consumer Duty performance. Any significant product change or new distribution agreement should trigger a fresh assessment.

    Does Consumer Duty apply to white-label financial software providers in the UK?

    Very likely yes. If you supply a white-label product that is sold on to retail customers under a distributor’s brand, and your product design influences what those customers pay, understand, or can access, you sit within the distribution chain and carry obligations as a manufacturer. You should agree in writing with your distributor how Consumer Duty responsibilities are split between you.

  • What the FCA’s Consumer Duty Really Means for Fintech and Financial Services Startups

    What the FCA’s Consumer Duty Really Means for Fintech and Financial Services Startups

    Most fintech founders I speak to can recite the four Consumer Duty outcomes from memory by now. Products and services, price and value, consumer understanding, consumer support. Reciting them is the easy part. Operationalising them, building them into how a product is designed, how a board is run, and how customer data is reviewed every quarter, is where most early-stage firms are still well short of where they need to be.

    The FCA Consumer Duty fintech UK picture is messier than the regulator’s own guidance sometimes suggests. This piece goes past the headline obligations and looks at the practical changes authorised firms need to embed before they become a supervisory concern.

    Fintech team reviewing FCA Consumer Duty fintech UK compliance requirements in a London office meeting room
    Photo by RDNE Stock project on Pexels

    Why the Consumer Duty is harder than it looks for fintechs

    The Consumer Duty came into full force for open products and services on 31 July 2023, with closed products following a year later. By now, most authorised firms should have completed their initial gap analysis. The problem is that the Duty is not a one-time compliance exercise. It is a continuous obligation, and the FCA has been explicit that it will use its supervisory tools to test whether firms are genuinely delivering good outcomes, not just producing paperwork that says they are.

    Fintech businesses face a particular structural challenge here. Many have been built for speed: fast onboarding, minimal friction, automated decisioning. Those are genuine product virtues. But they can also create blind spots. An automated credit decision that works efficiently at scale might still produce systematically poor outcomes for a specific customer segment, and the Consumer Duty requires you to know that, before the FCA tells you.

    Outcome monitoring: what it actually requires

    The most common gap I see in early-stage fintech compliance programmes is outcome monitoring that exists as a concept but has not been turned into a data process. The FCA expects firms to track whether customers are actually achieving good outcomes, not whether the firm’s process technically followed the rules.

    In practice, this means identifying proxy metrics that indicate whether your product is doing what it promises. For a savings app, that might be whether customers are consistently saving, or whether they are withdrawing funds immediately after deposit in a pattern that suggests the product is not meeting their actual need. For a lending platform, it means looking at whether your customer communications around arrears are changing behaviour, or just generating compliance logs.

    You need a data infrastructure that can segment by customer characteristic, product type, and distribution channel, and you need someone responsible for reviewing it at a cadence that gives the business time to act. Quarterly is a reasonable minimum. Monthly is better for high-volume consumer products.

    Fair value assessments: beyond the cost-benefit table

    The price and value outcome requires firms to assess whether the overall package of benefits a customer receives is reasonable relative to its price. The FCA has published some useful guidance here, but many fintechs are treating the fair value assessment as an annual document-signing exercise rather than a live business process.

    A credible fair value assessment for a fintech product needs to account for the full customer journey cost, including the cost of poor outcomes. If a significant proportion of customers are paying a monthly subscription fee but using the product so infrequently that they derive almost no benefit, that is a value problem. The fact that the fee is transparently disclosed does not resolve it.

    For firms with tiered pricing models or freemium structures, the assessment needs to look at whether customers are being effectively pushed towards higher-cost tiers through product design rather than genuine need. Upselling mechanics that exploit behavioural nudges are exactly the kind of thing FCA supervisors are interested in, and the Consumer Duty gives them a clear framework for challenging it.

    Board-level accountability: what governance actually needs to look like

    The Consumer Duty places explicit obligations on Boards and senior management under the Senior Managers and Certification Regime. The FCA expects a named individual to own Consumer Duty outcomes at Board level, and it expects the Board to receive regular management information that allows it to assess whether the firm is meeting those outcomes.

    That means your Board pack needs a Consumer Duty section that contains real data, not summaries of compliance activities. The FCA has been clear that it wants to see evidence of challenge and discussion at Board level, not a rubber-stamp review of a 40-page report that nobody had time to read properly.

    For smaller fintechs with lean governance structures, this can feel disproportionate. But the expectation scales with the size and complexity of the firm. What matters is that the accountability is genuine. If your Consumer Duty champion cannot explain what your worst-performing customer segment looks like and what the firm is doing about it, that is a problem the FCA will find eventually.

    It is also worth noting that the Duty applies across distribution chains. If your product is distributed through a third-party platform or embedded in another firm’s app, you have obligations around how that distribution is managed. The way your product is contractually and technically integrated with partners matters here, and many firms have not yet done the work to understand where their Consumer Duty responsibilities end and their distributor’s begin.

    Product design changes that firms are actually making

    The more mature fintech compliance teams I have come across are treating Consumer Duty as a product design constraint rather than a compliance overlay. That means running a Consumer Duty lens over new feature releases before launch, not after. It means asking, at the design stage, which customer segments might be harmed by this feature, and what the worst-case outcome looks like.

    Concretely, that has led some firms to redesign cancellation flows that were previously buried, remove auto-renewing add-ons that customers rarely noticed, and introduce proactive prompts for customers who have not used a paid feature for an extended period. These are not just regulatory concessions; firms that do this well tend to see improved retention and lower complaint volumes, which has a real commercial upside.

    If your fintech is at an earlier stage and still building out its governance infrastructure, the fractional model for senior compliance and finance resource is worth considering. A part-time Consumer Duty champion with genuine regulatory experience can be significantly more effective than a full-time junior compliance officer who is learning on the job.

    Where the FCA is likely to look next

    The FCA published its Consumer Duty Board Report in February 2024, which gave firms useful visibility into where the regulator thought progress was lagging. Firms in the retail lending, insurance, and investment platform spaces have received the most supervisory attention so far. But the FCA has been explicit that it will move across sectors.

    The areas where I expect increased scrutiny over the next 12 to 18 months are: outcome monitoring data quality, fair value assessments for subscription and fee-based models, and consumer support journeys for customers in financial difficulty. The FCA’s Consumer Duty hub remains the authoritative source for current guidance and thematic reviews.

    For fintech firms that are also navigating fast growth and the pressures that come with it, the temptation is to treat regulatory compliance as something to bolt on later. The Consumer Duty makes that approach genuinely risky. The firms building this into their operations now, into their product roadmaps, their data pipelines, and their Board governance, are the ones that will spend less time on remediation when supervisory attention arrives.

    Understanding your regulatory obligations is part of understanding the commercial landscape you are operating in. The same discipline that makes a founder read a Companies House filing carefully, or model the tax implications of a business exit, is the discipline that makes Consumer Duty compliance genuinely robust rather than superficially presentable. The firms that treat it as a real management tool rather than a compliance tick-box are already ahead.

    Frequently Asked Questions

    Does the FCA Consumer Duty apply to all fintech startups in the UK?

    The Consumer Duty applies to all FCA-authorised firms that operate in retail financial markets, including early-stage fintechs. If you hold FCA authorisation and your product is available to retail customers, the Duty applies to you regardless of company size or stage.

    What does outcome monitoring actually involve under the Consumer Duty?

    Outcome monitoring means tracking real customer data to assess whether your product is delivering the results it promises, not just whether your internal process followed the rules. You need metrics that can identify poor outcomes by customer segment, product type, and distribution channel, reviewed at regular intervals by senior management.

    How often does a fair value assessment need to be reviewed?

    The FCA expects fair value assessments to be reviewed at least annually, and more frequently if there are material changes to your product, pricing, or the customer base it serves. A static document produced once and left untouched will not satisfy supervisory scrutiny.

    Who at Board level is responsible for Consumer Duty compliance?

    Under the Senior Managers and Certification Regime, the FCA expects a named individual at Board or senior management level to hold accountability for Consumer Duty outcomes. This person must be able to demonstrate active oversight, including reviewing management information and challenging the business where outcomes are falling short.

  • Business Asset Disposal Relief in 2026: What UK Founders Must Understand Before Exiting

    Business Asset Disposal Relief in 2026: What UK Founders Must Understand Before Exiting

    Exit planning used to feel like something founders dealt with later, once the business was actually on the market. The revised Business Asset Disposal Relief rules have changed that calculation entirely. If you built your company with the expectation of a reduced Capital Gains Tax rate on exit, the recent Budget changes mean you need to revisit those assumptions sooner rather than later. Business asset disposal relief UK 2026 is a materially different proposition from what it was even two years ago, and I’ve spoken to several founders who were genuinely surprised by the revised numbers when they modelled their exits properly for the first time.

    This guide cuts through the noise. What the relief actually covers, what qualifying conditions apply, how the lifetime allowance has shifted, and what practical steps you should be taking well before any sale discussions begin.

    Business founder reviewing business asset disposal relief UK 2026 planning documents in a London office
    Photo by Vlada Karpovich on Pexels

    What business asset disposal relief actually does

    Business Asset Disposal Relief (BADR), previously called Entrepreneurs’ Relief, reduces the rate of Capital Gains Tax payable when you dispose of qualifying business assets. Rather than paying the standard CGT rate on gains, eligible individuals pay a preferential rate. The relief applies to gains made by individuals, not companies, which matters for how you structure your business ahead of a sale.

    Following the October 2024 Budget, the preferential rate changed. HMRC confirmed that for disposals made on or after 6 April 2025, the BADR rate increased to 14%, and from 6 April 2026 it rises again to 18%. That second step is now in effect. To put it plainly: the gap between BADR and the standard higher CGT rate has narrowed considerably, but the relief still delivers a meaningful saving on large gains. On a £1m gain, the difference between 18% and 24% is £60,000. On a £5m gain, that figure becomes impossible to ignore.

    For detailed background on the current CGT rates and how the relief integrates with wider Capital Gains Tax rules, the HMRC guidance on business asset disposal is the most reliable reference point.

    The qualifying conditions founders must meet

    The relief is not automatic. HMRC applies a specific set of conditions, and falling short of any single one disqualifies the entire gain from the preferential rate. I’d argue these conditions are where most founders encounter problems, usually because they weren’t structured correctly at the point of incorporation.

    For a trading company disposal, the key conditions are:

    • You must have owned the shares for at least two years immediately before the disposal.
    • The company must be a trading company (or holding company of a trading group) throughout that two-year period. Investment activity, including significant property holdings, can jeopardise this classification.
    • You must be an employee or officer of the company throughout the two-year qualifying period.
    • Your shares must entitle you to at least 5% of the ordinary share capital and at least 5% of the voting rights. You must also be entitled to at least 5% of the distributable profits and net assets on a winding-up, or alternatively 5% of the sale proceeds in the event of a disposal of the whole company.

    The 5% threshold is a genuine trap for founders who have diluted heavily through multiple funding rounds. If your equity has dropped below 5% through investor dilution, you may have lost BADR eligibility. There is a mechanism called an election under the 2019 Finance Act rules to crystallise a deemed gain at the point of dilution below 5% and bank the relief at that point, but this requires forward planning. By the time you’re heading to exit, it’s often too late to use it.

    How the lifetime allowance has changed

    The lifetime allowance for BADR remains at £1 million of qualifying gains. This has not changed since the reduction from £10 million in 2020. What has changed is the rate at which that allowance delivers value, given the stepped rate increases now in place.

    The practical consequence: founders who have already used BADR on a previous exit get no further relief once the £1m lifetime limit is exhausted. It’s a cumulative allowance, not a per-disposal one. If you sold a previous business and claimed BADR on £800,000 of gains, you have £200,000 of lifetime allowance remaining. This is something many serial founders overlook entirely, particularly those who sold earlier businesses informally or via a share buyback without a formal CGT computation at the time.

    It’s also worth noting that Investors’ Relief, the separate relief aimed at external investors in unlisted trading companies, still carries a higher lifetime limit (currently £10 million), though its conditions are quite different and it’s not available to employees or officers of the company. That distinction matters for how you think about co-founder and investor structures.

    What structures put the relief at risk

    Several common business decisions can unintentionally disqualify BADR, and founders often make them without understanding the CGT implications. Property held inside the trading company is the most frequent issue I see raised. If a significant proportion of the company’s assets or income is non-trading, HMRC may not accept trading company status for the whole two-year qualifying period. This is especially relevant for businesses that have accumulated cash or invested in property as a store of value.

    Holding company structures require particular care. If you own shares in a holding company that sits above a trading subsidiary, BADR can still apply, but the group must qualify as a trading group and the conditions around employment and shareholding must be met at the holding company level. Getting this wrong at the point of setting up a holding company structure is costly. I’ve written previously about how to structure a holding company in the UK, and the BADR implications are one reason the structuring decisions you make early on carry long-term consequences.

    Share classes also matter. If your company has created alphabet shares or restructured equity in ways that affect voting rights, profit entitlements, or winding-up rights, the 5% tests may not be satisfied even if you nominally hold more than 5% of the share capital.

    Planning steps to take well before a sale

    The two-year qualifying period means any structural fixes need to happen at least 24 months before completion of a sale. This is not advisory padding; it’s a hard HMRC condition. A tax adviser can help you review the position, but there are a few specific questions worth working through now.

    First, check your trading status. If your accountant’s year-end filing classifies significant revenue as investment income, or if your balance sheet carries substantial property or cash assets, consider whether this affects trading company status. Taking specialist advice on this point is not excessive caution; it’s straightforward commercial prudence.

    Second, review your equity position. If you’re approaching or below the 5% threshold, talk to your solicitor about the deemed gain election mechanism. Doing this retroactively is not possible.

    Third, model the actual after-tax proceeds. Founders sometimes focus on headline valuation without modelling net proceeds properly. At an 18% BADR rate versus a 24% standard CGT rate, the difference is meaningful but not transformative on smaller exits. On larger exits, it absolutely is. Running the numbers properly informs negotiating posture as well as planning decisions. This is precisely where fractional finance directors can add significant value, particularly for founders who don’t have an FD embedded in the business full-time.

    Fourth, consider how intellectual property is held inside the business. If valuable IP sits outside the company structure, it may not form part of the qualifying disposal. The decisions around how and where to hold intellectual property in a UK business intersect directly with exit tax planning.

    The honest position on BADR in 2026

    Business asset disposal relief UK 2026 is still worth claiming. An 18% rate versus 24% on large gains is a real saving. But it is no longer the transformative relief it once was, and the conditions are unforgiving. The founders who benefit most are those who structured correctly from the beginning, monitored their qualifying conditions actively, and planned their exit with specific tax dates in mind rather than treating BADR as an afterthought.

    If you’re two or more years from a planned exit, you still have time to fix most structural issues. If you’re closer than that, your options narrow quickly. Either way, this is not a conversation to have for the first time when a buyer’s offer letter arrives.

    Frequently Asked Questions

    What is the Business Asset Disposal Relief rate in 2026?

    From 6 April 2026, the BADR rate is 18% on qualifying gains. This follows the interim rate of 14% that applied between 6 April 2025 and 5 April 2026. The standard higher Capital Gains Tax rate for shares is currently 24%, so the relief still delivers a meaningful saving on larger exits.

    What is the lifetime allowance for Business Asset Disposal Relief?

    The lifetime allowance remains at £1 million of qualifying gains per individual. This limit is cumulative across all disposals throughout your lifetime, not per transaction. If you’ve used BADR on a previous exit, the amount already claimed reduces what you can claim in future.

    Do I still qualify for BADR if investor dilution has taken my shareholding below 5%?

    If your shareholding has fallen below 5% due to dilution, you may have lost BADR eligibility on any gain accrued after that point. However, there is an election mechanism introduced in the 2019 Finance Act that allows you to treat a deemed disposal at the point of dilution and crystallise the relief at that moment. This must be done proactively and cannot be applied retrospectively.

    How long must I own shares to qualify for BADR?

    You must have owned the shares for at least two continuous years immediately before the disposal. During that period you must also be an employee or officer of the company, and the company must qualify as a trading company throughout. If either condition is broken at any point in the two years, BADR will not apply.

    Can I claim BADR if my company has a holding company structure?

    Yes, BADR can apply where you hold shares in a holding company above a trading subsidiary, but only if the group qualifies as a trading group and you meet the 5% shareholding, voting, and employment conditions at the holding company level. The structure must be set up correctly and maintained throughout the qualifying period.

  • Venture Debt in the UK: What It Is, When It Makes Sense, and What Founders Get Wrong

    Venture Debt in the UK: What It Is, When It Makes Sense, and What Founders Get Wrong

    Most founders approach their capital stack as a binary choice: take equity from investors or borrow from a bank. Venture debt sits in neither camp cleanly, which is partly why it gets misunderstood and partly why it can be genuinely powerful when used correctly. For venture debt UK startups exploring beyond Series A, it has become an increasingly relevant option, but it comes with specific mechanics and risks that deserve proper scrutiny before signing anything.

    UK startup founder reviewing venture debt documents with financial adviser in London office

    What Is Venture Debt and How Does It Differ From Other Funding?

    Venture debt is a form of debt financing extended to venture-backed companies that typically lack the hard assets or sustained profitability that traditional bank lending requires. Unlike a high street business loan, it does not demand property collateral or years of audited profit. Unlike equity, it does not immediately dilute your cap table. Instead, lenders accept the risk on the basis that you have already attracted credible institutional investors who have validated the business.

    The structure usually involves a term loan, often between 12 and 36 months, accompanied by a warrant package. Warrants give the lender the right to buy a small percentage of equity at a fixed price, typically between 5% and 20% of the loan value expressed as a warrant coverage figure. This is how the lender compensates for the elevated risk relative to a secured business loan. Interest rates for venture debt in the UK tend to sit between 8% and 14% depending on the lender, the stage of the company, and prevailing base rates.

    Who Are the Main Venture Debt Lenders in the UK?

    The UK market has matured considerably over the past decade. Silicon Valley Bank (now operating under First Citizens Bank ownership following its 2023 collapse) historically dominated this space and remains active in the UK. British Business Bank, whilst not a direct lender, facilitates debt options through accredited partners and is worth understanding as part of the broader funding landscape. You can review their programmes at british-business-bank.co.uk.

    Dedicated venture lenders with UK presence include Kreos Capital, which has been active across European growth-stage companies for some years, and Lighter Capital, which focuses more on revenue-based structures. TriplePoint Ventures and Claret Capital Partners are also worth knowing. More recently, a number of challenger finance providers and fund structures have emerged specifically targeting UK scale-ups between Series A and Series C.

    Typical Term Structures: What to Expect

    A standard venture debt facility in the UK might look something like this: a £2 million to £5 million term loan, drawn in one or two tranches, over a 24 to 36 month period with an initial interest-only window of six to twelve months before principal repayments begin. The interest-only period is a key feature, it preserves cash during the early phase when the company is deploying capital most aggressively.

    Fees matter here and are easy to overlook. Origination fees of 1% to 2% are common, as are end-of-term fees (sometimes called back-end fees) of 1% to 3% of the facility value. On a £3 million facility, that back-end fee alone can add £60,000 to £90,000 to the effective cost. Run the full blended cost model before committing, not just the headline interest rate.

    The warrant component typically represents the most negotiable part of the deal. Coverage percentages, strike prices, and expiry windows all vary. A founder who goes into these negotiations without an experienced corporate finance adviser is, frankly, leaving money on the table.

    Covenants Founders Must Understand Before Signing

    This is where a lot of founders get caught out. Venture debt agreements often include financial covenants and operational covenants that, if breached, give the lender significant leverage. Common covenants to scrutinise include minimum cash requirements (often expressed as a percentage of the facility), minimum monthly recurring revenue thresholds, and restrictions on additional debt without lender consent.

    Material Adverse Change (MAC) clauses deserve particular attention. These are broadly worded provisions that allow the lender to call the loan if there is a significant deterioration in the business or its prospects. In practice, MAC clauses are rarely triggered aggressively by reputable lenders, but they exist and they matter when trading conditions shift. Understand what constitutes a MAC event under your specific agreement, not just the general principle.

    Change of control provisions are equally important for startups anticipating an exit. Many venture debt agreements include provisions requiring early repayment upon acquisition, which is usually manageable but needs to be factored into any M&A modelling from day one.

    When Venture Debt for UK Startups Actually Makes Sense

    The scenarios where venture debt genuinely earns its place are fairly specific. It works best as an extension of existing equity runway rather than a replacement for it. If you have just closed a Series A and want to extend your runway by six to nine months without raising a bridge round or diluting further, venture debt can be an efficient tool. Similarly, if you need capital to hit a specific milestone that will materially improve your valuation ahead of a Series B, debt that preserves equity is worth considering.

    It also makes sense when the company has predictable, recurring revenue, SaaS businesses being the obvious example. A business with £80,000 monthly recurring revenue and strong retention metrics is a far more credible venture debt candidate than an early-stage pre-revenue company hoping to bridge to commercialisation. Lenders want to see that the loan can be serviced from operations, even if the full thesis still depends on growth.

    Where it does not make sense: as a last resort when equity is unavailable. Lenders can smell distress and the terms will reflect it. Venture debt taken under duress, at punishing rates, with aggressive covenants, rarely ends well. It accelerates problems rather than solving them.

    The Most Common Mistakes Founders Make

    Treating venture debt as free money is perhaps the most common error. It is cheaper than equity in pure dilution terms, but it is not cheap in absolute terms. The cash repayment obligation is real and it arrives whether or not the next funding round closes on schedule.

    Underestimating the importance of the lender relationship is another. The best venture debt lenders are genuinely supportive partners who have seen hundreds of growth-stage companies navigate turbulence. The worst are transactional and will enforce covenants sharply. Reference checks on lenders matter as much as any other part of the due diligence process.

    Finally, founders often fail to model the warrant impact correctly. A £3 million facility with 15% warrant coverage and a current valuation of £20 million means warrants over £450,000 of equity at today’s price. If the company exits at £100 million in three years, the effective cost of those warrants is considerably higher. That is not a reason to avoid venture debt, but it should be part of the calculation.

    Used deliberately, with clear milestones attached and a realistic repayment model, venture debt is a sophisticated capital tool that many UK scale-ups underutilise. The key is going in with your eyes open, a good adviser at your side, and a firm understanding of what the lender actually needs from the deal.

    Frequently Asked Questions

    What is venture debt and how does it work for UK startups?

    Venture debt is a form of loan financing designed for venture-backed companies that lack the assets or profitability required for traditional bank lending. In the UK, it typically involves a term loan with an initial interest-only period, accompanied by a warrant package that gives the lender a small equity stake in the company.

    How much does venture debt typically cost in the UK?

    Interest rates for venture debt in the UK generally range from 8% to 14% per annum depending on the lender and company stage. When you factor in origination fees, back-end fees, and the value of warrants granted, the true blended cost is typically higher than the headline interest rate suggests, so founders should model the full economic cost carefully.

    Do you need existing investors to get venture debt in the UK?

    In most cases, yes. Venture debt lenders extend credit on the basis that the company has already been validated by credible institutional investors. A startup that has not completed a formal equity round from a recognised VC will find it very difficult to access venture debt on reasonable terms in the UK market.

  • The Real Cost of Shadow IT: What UK Finance and Operations Leaders Need to Address

    The Real Cost of Shadow IT: What UK Finance and Operations Leaders Need to Address

    Someone on your finance team is using a free online PDF tool to process invoices. Your operations manager signed up for a project management app last month without telling IT. A junior account manager is storing client data in a personal Dropbox folder. None of this is malicious. All of it is a liability. Shadow IT, the use of software, applications, and cloud services outside the knowledge or approval of your IT and security functions, is one of the most underestimated shadow IT risks UK businesses are sitting on right now.

    Finance team in a UK office facing shadow IT risks UK businesses commonly encounter
    Finance team in a UK office facing shadow IT risks UK businesses commonly encounter

    The scale of the problem is considerable. According to research cited by the UK’s National Cyber Security Centre, a substantial proportion of data breaches involve some element of unmanaged or poorly governed technology. When employees reach for a convenient tool to solve an immediate problem, they are rarely thinking about data residency, third-party access permissions, or whether that application has ever seen a penetration test. They are thinking about getting the job done. That instinct is not wrong. The gap in governance is.

    Why Shadow IT Has Exploded in UK Organisations

    Remote and hybrid working accelerated the problem sharply. When teams are distributed, the friction of raising an IT request and waiting for approval feels disproportionate to the urgency of a Tuesday afternoon deadline. The SaaS market has also made it trivially easy to spin up a free or low-cost tool with a credit card and an email address. No procurement process, no security review, no contract.

    There is also a generational dynamic at play. Younger employees, particularly those entering the workforce after years of frictionless consumer technology, find rigid IT policies baffling. If they can manage their personal finances, health data, and social lives through polished apps on a mobile, why should their employer’s equivalent be a clunky internal system that crashes on a Tuesday afternoon? The expectation of convenience has fundamentally shifted, and IT governance frameworks in many mid-sized UK businesses have not kept pace.

    The GDPR Exposure Most Businesses Are Not Accounting For

    This is where shadow IT risks UK businesses face move from inconvenient to genuinely serious. Under UK GDPR, as administered post-Brexit through the Data Protection Act 2018 and overseen by the Information Commissioner’s Office (ICO), organisations remain the data controller for any personal data they hold, regardless of which tool an employee used to process it. If a staff member uploads a client list to an unapproved SaaS platform, your organisation is accountable for what happens to that data, even if you had no knowledge the upload occurred.

    The ICO has the power to impose fines of up to £17.5 million or 4% of annual global turnover, whichever is higher, for serious infringements. More practically, the reputational damage from a notifiable breach, which must be reported to the ICO within 72 hours of discovery, can be disproportionate to the size of the organisation. A mid-sized professional services firm in the Midlands has the same reporting obligation as a FTSE 100 company. The compliance burden scales differently; the legal exposure does not.

    You can read the ICO’s current guidance on UK GDPR obligations for organisations at ico.org.uk, which is worth circulating to your legal and operations leads if they are not already familiar with it.

    Professional accessing unapproved software illustrating shadow IT risks UK businesses face
    Professional accessing unapproved software illustrating shadow IT risks UK businesses face

    Security Risks Beyond GDPR

    Data protection is only one dimension. Shadow IT also creates meaningful cybersecurity exposure. Unapproved tools are rarely enrolled in your organisation’s single sign-on (SSO) or multi-factor authentication (MFA) framework. That means if an employee’s personal email account is compromised, the attacker may gain access to multiple business-critical systems without triggering any of your existing security monitoring.

    There is also the question of data sprawl. When sensitive business information lives across dozens of unofficial platforms, your incident response capability collapses. You cannot contain what you cannot see. Ransomware operators and social engineers actively look for peripheral, poorly governed access points precisely because they are less likely to be monitored.

    For finance and operations leaders specifically, the risk extends to financial data. If an analyst is using a personal Google Sheets document shared externally to work on budget projections, that document is potentially accessible to anyone the analyst decides to share it with, stored on Google’s infrastructure, and completely outside your data retention and deletion policies.

    Building a Practical Audit Framework Without Strangling Productivity

    The instinct of some IT and compliance teams is to respond with a blanket ban and a lengthy approved-software list. That approach tends to fail. Employees find workarounds, productivity drops, and resentment builds. A more effective model treats shadow IT governance as a continuous process rather than a one-time crackdown.

    Start with discovery. Tools such as network traffic analysis, endpoint detection platforms, and SSO audit logs can surface the applications your staff are actually using. Many businesses are surprised to find 30 to 50 unapproved tools in active use across a team of 50 people. Once you have visibility, you can triage rather than react.

    From there, a tiered approval model works well in practice. A fast-track review process for low-risk, non-data-intensive tools (think basic productivity utilities) can be completed in days rather than weeks. High-risk tools touching personal or financial data require a fuller review: data processing agreements, security questionnaires, and confirmation of UK or EEA data residency where applicable. The goal is to remove the friction of legitimate tool adoption, not to replace one bureaucratic bottleneck with another.

    This is also a conversation about business efficiency, not just IT policy. Agencies and businesses that operate with significant web presence understand this tension well. dijitul, a Mansfield, Nottinghamshire-based digital agency specialising in SEO, hosting, and web design, encounters the software governance question regularly when working with clients on their marketing technology stacks and business efficiency frameworks. Their approach at dijitul.uk reflects what many forward-thinking organisations are working out: that the right software, properly integrated and governed, produces better business outcomes than a collection of unsanctioned quick-fixes. Good web design and marketing operations depend on clean, auditable data pipelines, which shadow IT directly undermines.

    Communicating Policy Without Creating a Culture of Fear

    Governance only works if people engage with it voluntarily. A policy that employees treat as a hurdle to jump over rather than a framework to work within will not reduce your exposure; it will just drive shadow IT underground. The tone of internal communication matters here.

    Frame policy updates around why the rules exist, not just what they prohibit. Most employees, when they understand that a GDPR breach could result in a client losing trust in the business, or that an unreviewed tool could be the entry point for a ransomware attack, make better decisions. Regular, brief training sessions, a named internal contact for software queries, and a visible fast-track approval route all reduce the likelihood that someone defaults to an unapproved tool simply because the legitimate route seemed too slow.

    Finance and operations leaders who treat this as a technology problem alone will miss the point. Shadow IT is a people and process problem that happens to manifest in technology. The businesses managing it well are the ones that have made legitimate tool adoption easier than the alternative, building that business efficiency into the fabric of how teams work rather than imposing it from the outside. Organisations working with external partners on their software and marketing ecosystems, whether that is a digital agency like dijitul helping to rationalise web and software platforms, or an internal IT team reviewing the full stack, benefit from approaching the audit with both commercial and security lenses simultaneously.

    Where to Start This Week

    If shadow IT risks UK businesses face are not yet on your board or senior leadership agenda, they should be. A reasonable starting point is to commission a basic software audit, even an informal survey of department heads asking what tools their teams use day-to-day can surface meaningful gaps quickly. From there, define what a tier-one review looks like for your organisation, assign ownership (IT, legal, or a combined function), and set a realistic timeline for the first round of rationalisation.

    The aim is not a perfect, locked-down environment. It is a governed one, where the tools employees are using are known, assessed, and appropriate. That standard is achievable for most UK businesses within a single quarter, and the risk reduction it delivers is significant relative to the effort involved.

    Frequently Asked Questions

    What is shadow IT and why is it a problem for UK businesses?

    Shadow IT refers to software, applications, or cloud services used by employees without the knowledge or approval of the IT or security function. For UK businesses, it creates GDPR liability, cybersecurity vulnerabilities, and data governance gaps that can result in regulatory fines or reputational damage.

    Can UK businesses be fined for shadow IT-related data breaches?

    Yes. Under UK GDPR, the organisation remains the data controller regardless of which tool was used to process personal data. The ICO can impose fines of up to £17.5 million or 4% of global annual turnover for serious breaches, and any notifiable breach must be reported within 72 hours of discovery.

    How do I find out which unapproved tools my employees are using?

    Network traffic analysis, SSO audit logs, and endpoint detection platforms are the most reliable methods. A simpler starting point is a department-by-department survey asking managers to list all tools their teams use regularly, which often surfaces a significant number of unapproved applications quickly.

    How can businesses reduce shadow IT without hurting productivity?

    A tiered approval process is more effective than blanket bans. Low-risk, non-data-intensive tools should have a fast-track review measured in days, whilst tools that handle personal or financial data require fuller scrutiny. Making legitimate approval easier than workarounds is the key to changing behaviour sustainably.

    Is shadow IT more of a risk for small businesses or large organisations?

    Both face genuine exposure, but mid-sized UK businesses often carry the greatest risk because they lack the dedicated security resource of larger enterprises whilst still holding significant volumes of personal and financial data. The ICO’s compliance obligations are the same regardless of company size.

  • How UK Founders Are Structuring Equity Splits to Avoid Costly Co-Founder Disputes

    How UK Founders Are Structuring Equity Splits to Avoid Costly Co-Founder Disputes

    Getting the equity conversation right at the start of a business is one of the most important things founders will ever do. Yet it is also one of the most avoided. Splitting shares equally feels fair in the early days, but that 50/50 handshake arrangement has quietly killed more promising businesses than bad products or poor timing. A poorly structured co-founder equity split UK startup founders rely on can unravel fast the moment a co-founder loses interest, walks away, or falls out with the team before the business reaches meaningful revenue.

    This guide covers how to think about equity splits sensibly, what legal structures you actually need in place, and the warning signs that your current setup could become a problem when investors come knocking.

    Two co-founders reviewing a co-founder equity split UK startup shareholder agreement in a London office
    Two co-founders reviewing a co-founder equity split UK startup shareholder agreement in a London office

    Why Equal Splits Are Not Always Fair Splits

    The instinct to split equity equally is understandable. It feels collaborative. It avoids an awkward conversation. But equal splits work best when co-founders bring identical skills, identical time commitment, and identical risk exposure to the business. That almost never happens.

    One founder typically has the original idea. Another brings technical skills. A third might contribute cash. These are fundamentally different inputs and they change over time. The person who goes full-time in month one is taking a very different risk from someone keeping a consultancy going on the side for the first year. Treating those contributions as equivalent rarely serves anyone well.

    A more defensible approach is to map out what each founder is actually bringing: capital invested, opportunity cost, relevant experience, and projected workload. There are frameworks that score these contributions numerically, such as the Slicing Pie model, though in practice most UK founders end up in a direct negotiation. The point is to have that negotiation explicitly and document the outcome properly, rather than defaulting to equal shares because the conversation feels uncomfortable.

    Vesting Schedules: The Mechanism That Protects Everyone

    Equity vesting is the single most effective structural tool available to co-founders, and it is still underused at early-stage UK companies. A vesting schedule means co-founders earn their equity over time rather than receiving it all upfront. If someone leaves the business early, they take only the portion they have vested. The rest returns to the company for redistribution.

    The standard arrangement in the UK market is a four-year vest with a one-year cliff. That means no equity is earned in the first twelve months; after the cliff, the remainder vests monthly over the following three years. This protects the team from the scenario where a co-founder takes a quarter of the business and disappears six months in.

    Vesting schedules should also address what happens at an exit or investment event, specifically whether unvested shares accelerate. Single-trigger acceleration means all unvested shares vest immediately upon acquisition. Double-trigger requires both an acquisition and involuntary termination. Most investors prefer double-trigger because it keeps founders incentivised post-acquisition, so it is worth knowing this before you structure the arrangement.

    Close-up of a founder signing a co-founder equity split UK startup shareholder agreement document
    Close-up of a founder signing a co-founder equity split UK startup shareholder agreement document

    The Shareholder Agreement: What Needs to Be in It

    A shareholder agreement is the legal foundation of your co-founder relationship. The articles of association filed at Companies House set out basic governance rules, but a shareholder agreement sits alongside those articles and covers the specifics that protect everyone involved. Without one, you are relying on company law defaults, which rarely match what founders actually want.

    A robust shareholder agreement for a UK startup should include:

    • Share vesting provisions as described above, including good leaver and bad leaver definitions. A good leaver (someone who exits through illness or redundancy) typically retains more vested equity than a bad leaver (someone who resigns or is dismissed for cause).
    • Drag-along and tag-along rights. Drag-along allows majority shareholders to compel minority holders to accept an acquisition offer. Tag-along lets minority shareholders join a sale on the same terms as the majority. Both matter enormously when an exit happens.
    • Pre-emption rights on new share issuances, giving existing shareholders the right to maintain their percentage before new investors come in.
    • Decision-making thresholds. Define which decisions require unanimous consent versus simple majority. Common reserved matters include taking on debt, issuing new shares, and changing the business’s core direction.
    • IP assignment clauses confirming that all intellectual property created by founders belongs to the company, not to individuals.

    The Solicitors Regulation Authority (SRA) maintains standards for commercial law practitioners across the UK. Engaging a solicitor experienced in startup equity work is not an optional luxury; it is a practical necessity. A poorly drafted agreement discovered at due diligence can delay or kill a funding round.

    For further context on how shares and ownership structures are registered, the gov.uk guidance on shareholders and companies provides a clear starting point on legal obligations under UK company law.

    Warning Signs Your Current Equity Structure Is a Problem

    Most founders do not realise their equity structure is broken until a funding conversation surfaces it. Here are the warning signs worth watching for before that moment arrives.

    No vesting in place. If co-founders hold fully issued shares with no vesting schedule attached retrospectively, any departure is a clean exit with full equity retained. Investors will spot this and ask hard questions.

    A silent co-founder with a large stake. Someone who contributed early but is no longer active in the business holding 20 to 30 per cent of the cap table creates a significant problem. Their equity dilutes the active team and raises red flags for Series A investors about motivations and future conflicts.

    No shareholder agreement at all. Surprisingly common among companies incorporated via online formation services without legal advice. If disputes arise, founders fall back on the Companies Act 2006 defaults, which are unlikely to reflect anyone’s actual intentions.

    Equal splits with no tiebreaker mechanism. A 50/50 split with no casting vote or dispute resolution process creates a structural deadlock. Every contentious decision becomes a potential standoff.

    Restructuring Before a Funding Round

    If your current structure has problems, it is not too late to fix them before approaching investors, but the window for doing so cleanly is finite. Restructuring equity is straightforward when the company has low valuation and no third-party investors. Once a seed round closes, amendments become more complex and more expensive.

    The practical steps for restructuring typically involve a combination of share buybacks (the company repurchasing shares from a departing or disengaged co-founder), share transfers between parties, and the introduction of a new shareholder agreement that all parties sign. A growth share scheme or EMI options can also be used to realign incentives for active founders without requiring expensive share purchases at inflated prices.

    It is worth having a direct conversation with any co-founder whose position needs to change before involving solicitors. The legal process formalises an agreed outcome; it rarely creates one. Founders who approach restructuring as a collaborative necessity rather than a confrontation tend to get cleaner results.

    Getting the Foundation Right Pays Dividends

    A well-structured co-founder equity split UK startup founders build from the outset is not just about avoiding conflict. It is a signal to investors, employees, and partners that the business is run by people who think clearly about incentives and governance. The founders who put in the effort early, with proper documentation and legal advice, spend far less time untangling problems later.

    Equity is how the work of building a business converts into long-term wealth. Treating its structure with the same rigour applied to product, sales, or finances is simply good business sense.

    Frequently Asked Questions

    What is a fair co-founder equity split for a UK startup?

    There is no universally fair split; the right division depends on each founder’s capital contribution, time commitment, experience, and opportunity cost. Equal splits work when contributions are genuinely equal, but most founding teams benefit from mapping inputs explicitly and negotiating from there rather than defaulting to 50/50.

    Do co-founders in the UK need a shareholder agreement?

    Yes, a shareholder agreement is strongly advisable for any multi-founder UK company. Without one, the business operates under Companies Act 2006 defaults, which rarely match what founders actually intend around decision-making, share transfers, and exits. Investors will typically require one before closing a funding round.

    How does a vesting schedule work for UK startup founders?

    A vesting schedule means founders earn their equity gradually over time rather than receiving it all at incorporation. The most common UK arrangement is a four-year vest with a one-year cliff, meaning no equity is earned until month twelve, after which it vests monthly. This protects the company if a co-founder leaves early.

    Can you restructure equity after a startup has already been formed?

    Yes, equity can be restructured before external investment closes, typically through share buybacks, transfers, or introducing retrospective vesting via a new shareholder agreement. It is significantly easier and cheaper to do this at low valuations before a funding round, so acting early is advisable.

    What is the difference between drag-along and tag-along rights in a shareholder agreement?

    Drag-along rights allow majority shareholders to force minority shareholders to accept an acquisition offer on the same terms, preventing a small stakeholder from blocking a sale. Tag-along rights do the opposite, giving minority shareholders the right to join a sale on the same terms as the majority so they cannot be left out of an exit.

The Latest