Category: Business

  • 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.

  • How UK Knowledge Workers Are Using Personal AI Assistants to Reclaim Billable Hours

    How UK Knowledge Workers Are Using Personal AI Assistants to Reclaim Billable Hours

    There is a quiet productivity reckoning happening inside British professional services firms. Consultants are finishing client reports before lunch. Solicitors are turning around first-draft contract summaries in minutes rather than hours. Analysts are walking into Monday morning meetings with data narratives that used to take most of Sunday. The instrument behind much of this is the personal AI assistant for UK knowledge workers, and the honest story is more nuanced than either the hype or the scepticism suggests.

    UK knowledge worker using a personal AI assistant on her laptop in a modern office
    Photo by Mert Coşkun on Pexels

    What ‘personal AI assistant’ actually means in a professional context

    This is not about the voice assistant on your mobile telling you the weather. In a professional context, a personal AI assistant typically means a large-language-model tool, often built on GPT-4o, Claude 3.7, or Gemini 1.5 Pro, configured with a user’s specific context: their role, their firm’s terminology, their preferred communication style, and a library of prior work. Tools like Microsoft Copilot (embedded in Microsoft 365), Notion AI, and standalone products such as Otter.ai and Mem are the platforms most UK professionals I’ve spoken to are actually using day-to-day.

    The key distinction is configuration. Out-of-the-box tools are useful; a properly configured personal assistant is transformative. A consultant who has taught their AI their proposal structure, their sector vocabulary, and their client’s industry will generate a first draft that needs genuine editing, not wholesale rewriting. That gap between generic and personalised output is where the real time savings live.

    Where the time actually goes, and where AI is recovering it

    The non-billable drain in knowledge work is well-documented. Research from McKinsey (now several years old but still widely cited) put knowledge workers spending roughly 20% of their week searching for information and coordinating with colleagues. More recent data from CIPD’s Good Work Index consistently shows that UK professionals rate administrative workload as one of the top sources of dissatisfaction and pressure. The categories where personal AI tools are compressing this the most are: drafting, research synthesis, meeting preparation, and post-meeting documentation.

    I’d break down what I’ve seen across professional contexts into rough time-saving estimates, with the honest caveat that these vary enormously by how well the tool is set up and how skilled the user is at prompting:

    • Email drafting: 40-60% faster for complex, multi-stakeholder correspondence. Less impressive for short replies.
    • Meeting notes and action summaries: Tools like Otter.ai with AI summaries cut post-meeting write-up from 30-45 minutes to under 10 for a typical 60-minute session.
    • Research synthesis: Pulling together information across documents, annual reports, and market data can drop from 3-4 hours to 45-90 minutes, though verification time should not be eliminated.
    • First-draft proposals and reports: Experienced users report saving 90 minutes to two hours per document on first drafts.

    The quality trade-offs nobody talks about honestly

    Here is where most articles go wrong. They present AI output as either flawless or dangerously hallucinated, with no middle ground. My experience, and that of most professionals who use these tools seriously, is that the quality is consistent and mediocre until it is not, and knowing when you’re in ‘not’ territory is the actual skill.

    For drafting and synthesis tasks where the source material is solid and the prompt is specific, quality is genuinely high. A solicitor using Copilot to summarise a 40-page lease against a checklist of key clauses will get a reliable output that saves substantial time. The same solicitor asking the tool to advise on a novel point of contract law without grounding it in specific precedent is asking for trouble.

    The honest position is this: personal AI assistants are strong at pattern recognition, synthesis, and generation within a defined context. They are weak at original legal reasoning, genuinely novel analysis, and anything requiring judgement about facts not in their context window. For UK knowledge workers whose value proposition is precisely that kind of judgement, AI handles the scaffolding; you still build the building.

    There is also a subtle quality erosion risk that I think deserves more attention. When drafts arrive too easily, the temptation to review them less carefully is real. Several solicitors I’ve spoken to have put explicit review protocols in place specifically because of this, treating AI drafts the way they’d treat a trainee’s first attempt: useful, but requiring proper scrutiny before it goes near a client.

    Data privacy: the question UK professionals cannot ignore

    This is the practical blocker that often gets glossed over in enthusiasm about AI productivity. UK professional services firms operate under obligations, whether FCA rules, the Solicitors Regulation Authority’s conduct obligations, or GDPR and the ICO’s guidance, that make feeding client data into consumer AI tools a genuine compliance risk.

    The firms handling this well are doing one of three things: using enterprise-tier versions of tools (Microsoft 365 Copilot’s enterprise contract, for instance, explicitly excludes customer data from model training); building internal tools using API access where data stays within controlled infrastructure; or establishing clear policies about what categories of data can and cannot be processed by AI tools. The question of how firms use their internal data compliantly is one I’ve written about before, and the AI context adds another layer of urgency to getting this right.

    If you’re a consultant or analyst at a firm that has not yet issued guidance on AI tool use, I’d push for it. The absence of a policy is not the same as permission.

    What the most effective users are doing differently

    The gap between professionals who save an hour a week with AI and those who reclaim a full billable day is not about which tool they use. It is almost entirely about prompting discipline and system design.

    Effective users maintain a personal ‘prompt library’: a document or Notion page containing their best-performing prompts for recurring tasks, refined over time. They treat prompt refinement the way a good analyst treats a financial model, testing inputs, noting what improves output, and iterating. They also integrate AI into workflows rather than using it as a bolt-on. A consultant who routes every new client brief through a standardised AI-assisted research and framing process gets compounding returns; one who uses it ad-hoc when they remember to gets occasional wins.

    There is a structural parallel here with how UK accountancy practices have started embedding AI into their client workflows rather than leaving it to individual discretion. The lesson from that sector is that firm-level adoption protocols produce better outcomes than individual experimentation, even when the individuals are highly capable.

    Building a personal system that actually sticks

    The professionals getting the most from personal AI tools tend to start narrow. Pick one recurring non-billable task, whether it is writing internal status updates, summarising research documents, or preparing meeting agendas, and build a reliable AI workflow for just that. Once it becomes habitual and you have calibrated your review process, expand to a second task.

    The temptation to automate everything at once is a fast route to half-built workflows that get abandoned. Slow, deliberate expansion compounds. The same principle applies to the knowledge management side: the firms getting the most from their internal information are the ones that invested in structure before they invested in AI.

    Personal AI assistance is not a silver bullet, and it is not hype. For UK knowledge workers willing to put in the setup work, it is a reliable way to recover several hours of billable time a week. Given what those hours are worth, that is a calculation worth doing properly.

  • How UK Charities and Community Organisations Are Using Event Microsites to Coordinate Volunteers and Supporters

    How UK Charities and Community Organisations Are Using Event Microsites to Coordinate Volunteers and Supporters

    Community events in the UK run on goodwill, volunteer hours, and a fair amount of scrambled last-minute communication. A WhatsApp thread with 47 members arguing about where to park the float. A PDF route map that nobody can open on their phone. A printed newsletter that arrived three days after the event. I’ve spoken to enough committee organisers to know this is the norm, not the exception. Event microsites for charities are changing that, not by replacing the handcrafted, community-feel elements people love, but by giving supporters a single digital address where the live details actually live.

    Volunteers reviewing printed materials and a laptop screen while building event microsites for charities
    Photo by RDNE Stock project on Pexels

    This guide is for the committee secretary who manages everything from a laptop on the kitchen table, the volunteer coordinator at a local hospice charity, and the PTA chair who also happens to be running the Christmas sleigh run. You don’t need a developer. You don’t need a budget that would embarrass a FTSE 100 marketing team. You need the right approach and a clear sense of what a microsite should actually do.

    What is an event microsite and why does it matter for non-profits?

    A microsite is a small, standalone website built around a single event or campaign. Think of it as a dedicated landing page with a few sections rather than a full website with a navigation menu, an about page, a history of the organisation going back to 1987, and a members-only area nobody uses. The microsite strips all of that out. One URL, shared on printed flyers, local Facebook groups, and the parish newsletter, points supporters directly to what they need: the date, the route, the schedule, how to donate, and any updates since the flyer went to print.

    For non-profits and community groups, this matters because printed materials, which most still rely on, go stale the moment they leave the printer. A microsite lets you publish the route map change at 9pm on a Friday without reprinting anything. The government’s own guidance on running a community event recommends keeping participants informed through multiple channels, and a lightweight microsite is one of the most practical ways to do that without needing a comms team.

    What should a charity event microsite actually contain?

    Keep it ruthlessly focused. I’d argue that most charity microsites fail because someone adds too much, the entire history of the organisation, three different donation platforms, an embedded social feed that takes six seconds to load on a 4G connection in a village hall car park. The sections that genuinely serve supporters are simpler than that.

    A countdown timer is more useful than it looks. When supporters can see that the sponsored walk is 11 days away, registration urgency becomes real. Tools like Carrd, Notion Sites, or even a basic Google Sites page can embed a countdown without any code. For groups with slightly more technical confidence, Webflow’s free tier or a WordPress.com plan gives you enough flexibility to add route maps from Google Maps, embedded directly into the page so visitors can check it on their phones the night before.

    Laptop screen showing an event microsite for charities with a countdown and route map
    Photo by Shoper .pl on Pexels

    Real-time updates deserve their own section on the page, clearly labelled. A simple reverse-chronological list, “Update 14 November: start time moved to 10:30am due to road closure on the High Street”, does more practical good than a polished news section updated monthly. Supporters want to know what’s changed. Give them that, plainly.

    Volunteer sign-up should connect to something that actually captures data. Embedding a Google Form or a Typeform (both free at basic tier) means you stop collecting names on scraps of paper. The form submissions go directly into a spreadsheet you can filter by role, shift, or location. For groups managing a sleigh run with helpers across multiple postcodes, this is genuinely transformative.

    Pairing digital tools with printed and handcrafted materials

    The microsite doesn’t replace the printed programme or the decorated collection tin. It works alongside them. The most effective community events I’ve seen treat digital and physical as two parts of the same communication plan. A QR code on the printed leaflet links directly to the microsite. The microsite references the printed map. Each medium does what it does best.

    For groups managing the creative side of community events, designing sleigh routes, festive artwork for collection materials, or advent-themed displays, the visual and the digital are genuinely complementary. If you’re working through the artwork side, there’s a longer read on how to design colourful advent calendar artwork for your community sleigh run: a uk crafter’s guide that pairs well with the practical digital setup covered here. Getting both right means your event looks professional without needing a professional agency behind it.

    One practical tip: use a custom short URL for the microsite rather than whatever long string your website builder generates. A free Bitly link or a short branded domain (registrable for under £10 through Namecheap or 123-reg) means the URL fits on a flyer, can be read aloud at a meeting, and is memorable enough that a supporter can type it a week later from memory. This small detail makes a real difference to how many people actually visit the page.

    Tools UK community groups are actually using in 2026

    Carrd remains the most popular option I’ve come across among smaller non-profits and community committees. It’s genuinely free for a single-page site, loads quickly on mobile, and requires no technical knowledge. For multi-page needs, Google Sites is free and integrates naturally with the G Suite tools most organisations already use, Google Forms for volunteer registration, Google Maps for route embeds, Google Calendar for the event schedule.

    Notion has found an unexpected second life here too. Several local groups now publish their event information as a public Notion page. It isn’t the slickest solution aesthetically, but it’s editable by anyone with committee access, updates instantly, and handles embedded maps and forms adequately. For a PTA or a local Rotary club running a single annual event, it’s entirely sufficient.

    If your group has a small budget, even £50 to £100 a year, a WordPress.com Business plan or a Squarespace personal plan opens up proper countdown widgets, better mobile formatting, and custom domain support. At that price point, it’s worth it if the event recurs annually. You update the same microsite each year rather than rebuilding from scratch.

    Keeping distributed supporters informed without overwhelming them

    The mistake most organising committees make is publishing updates in too many places simultaneously. The WhatsApp group gets a message. The Facebook event gets a post. The email list gets a newsletter. The microsite gets updated three days later when someone remembers. Supporters who follow multiple channels get conflicting information, and the organiser spends twice as long managing communications as they should.

    A cleaner approach: treat the microsite as the single source of truth, and use WhatsApp, email, and social only to direct people there. “We’ve updated the route, check the website for details” is one message. It takes 30 seconds to send, and it drives traffic to the one place where the information is always current. If you’re already thinking about how tools like this connect to broader communication strategy, our piece on what UK employers need to know about remote work communication policies touches on similar principles around information flow and channel discipline, worth a read if your organisation is growing its volunteer base.

    For larger community organisations managing multiple events across a year, it’s worth thinking about how the microsite approach scales. At some point, a lightweight content management system makes more sense than rebuilding individual pages each time. That’s also the point at which a group might want to look at how data collected through volunteer forms is stored and managed, the ICO’s guidance on data protection for charities is straightforward and freely available, and worth bookmarking before you start collecting names and contact details at scale.

    Getting the microsite live before the event materials go to print

    Timing is the element most committees underestimate. The microsite needs to exist before the flyers are printed, because that’s when the URL gets added to the design. Build the page first, even if it only has the event name, date, and a “more details coming soon” note, then add the URL to the print file. Everything else can be filled in later. Trying to retrofit a digital presence after the printed materials are already circulating is a headache that’s entirely avoidable.

    I’d also recommend setting a Google Alert for your event name. If the local press picks up the story or a supporter shares the microsite URL somewhere unexpected, you’ll know about it and can make sure the page is ready to receive that traffic. It costs nothing and takes two minutes to set up.

    The best community events feel effortlessly organised even when the reality is anything but. A clean, functional microsite, updated when something changes, easy to find, fast to load on a phone, does a lot of the heavy lifting. It won’t write your risk assessment or persuade the council to close the road for an hour, but it will stop your volunteers showing up at the wrong end of the High Street at 7am on a wet Saturday in November. That, frankly, is worth the effort.

  • How UK Landlords and Letting Agents Are Using PropTech to Navigate the Renters’ Rights Act

    How UK Landlords and Letting Agents Are Using PropTech to Navigate the Renters’ Rights Act

    The pace of legislative change hitting UK landlords right now is, frankly, relentless. The Renters’ Rights Act, which abolishes Section 21 “no-fault” evictions and introduces a new ombudsman scheme, is reshaping how private letting actually works in practice. I’ve spoken to several letting agents over the past few months, and the word I hear most often is “overwhelmed”. The paperwork alone has multiplied. The compliance window is tightening. And staff who once managed portfolios on spreadsheets and gut instinct are suddenly being asked to operate like a regulated financial firm. That’s where PropTech for landlords is stepping in to fill a genuinely critical gap.

    Letting agent using PropTech for landlords on a laptop in a modern UK office
    Photo by MART PRODUCTION on Pexels

    What PropTech actually covers in a letting context

    “PropTech” gets used loosely, so let’s be precise. In the context of letting and landlord management, it refers to digital platforms that handle one or more of the following: tenancy creation and document management, rent collection and arrears tracking, maintenance logging, compliance record-keeping, and communication audit trails between landlord, agent, and tenant.

    Tools like Arthur Online, Goodlord, Vouch, and Reapit have been around for a few years, but their relevance has sharpened considerably since the Renters’ Rights Bill moved through Parliament. The new legislation doesn’t just change what landlords can and can’t do, it creates a documentation burden that is almost impossible to manage manually at scale. When you can no longer serve a Section 21 notice and must instead rely on specific grounds under Section 8, having a clean, timestamped record of every communication and maintenance request stops being nice-to-have and becomes essential evidence.

    Compliance software and the Section 8 paper trail

    Under the reformed regime, if a landlord wants possession on grounds such as repeated rent arrears or anti-social behaviour, they need a credible evidence file. This is where dedicated compliance software earns its keep. Platforms now offer automated logging of rent payment histories, reminder workflows, and structured communication records that can be exported in a format suitable for a First-tier Tribunal.

    The government’s Renters’ Rights Bill documentation makes clear that the evidential standard for Section 8 claims will be closely scrutinised. Landlords relying on email threads and handwritten notes will struggle. Those running a platform that auto-captures and date-stamps every interaction are, at minimum, starting from a much stronger position.

    I’d argue the compliance angle is also where PropTech becomes genuinely interesting for property-adjacent businesses, solicitors, mortgage brokers, and even accountancy practices that service landlord clients. Understanding the operational complexity their clients now face creates a real service opportunity, and it mirrors patterns I’ve written about elsewhere on this blog, such as how UK accountancy practices are using AI to serve more clients without growing headcount, the logic of scaling compliance capability without scaling staff costs applies directly here.

    PropTech for landlords compliance dashboard showing tenancy management features
    Photo by Mikhail Nilov on Pexels

    Digital tenancy management: where the efficiency gains are real

    Beyond compliance, the day-to-day operational gains from proper tenancy management platforms are measurable. Referencing and onboarding a new tenant used to mean physical ID checks, paper guarantor forms, and a file that lived in a drawer. Modern platforms integrate with Open Banking to verify income, pull credit reports automatically, and generate tenancy agreements populated from a template that’s already been updated for the new legislative requirements.

    Goodlord, for example, publishes data showing that digital onboarding cuts the average time-to-tenancy from around two weeks to under five days. For agents running fifty or more properties, that’s not a marginal improvement, it’s the difference between a profitable business and one that haemorrhages staff time on admin.

    Rent collection features are similarly mature. Direct debit integration, automated arrears chasing, and real-time payment dashboards mean agents spend less time on the phone and more time on the work that actually requires human judgement. The private rental sector UK commentary has rightly noted how structurally stressed the sector is right now, tech isn’t a fix for that structural pressure, but it is a genuine operational buffer for businesses that can implement it properly.

    Smaller landlords and the accessibility question

    There’s a fair challenge to the PropTech-as-solution narrative: most of these platforms are priced and designed for agents managing sizeable portfolios. A landlord with two or three properties in Sheffield or Coventry isn’t going to subscribe to an enterprise tenancy platform. The monthly cost doesn’t stack up against the revenue, and the onboarding overhead is real.

    This is changing, slowly. Platforms like Landlord Studio and Hammock are explicitly targeting the self-managing landlord segment with lighter, lower-cost tooling. Landlord Studio offers a free tier that covers basic rent tracking and expense logging, meaningful for a small portfolio. Hammock integrates with bank feeds to auto-categorise landlord expenses, which becomes genuinely useful at tax return time given HMRC’s ongoing push towards Making Tax Digital.

    The regulatory pressure the Renters’ Rights Act creates is, paradoxically, an adoption accelerant for this segment. When the cost of getting it wrong rises, and under the new ombudsman scheme, fines and repayment orders become a live risk, paying £20 a month for a platform that creates an automatic audit trail starts looking reasonable. I’ve seen this dynamic play out before. When data protection enforcement tightened, SMEs that had resisted basic data management tools suddenly found the budget. Legislative deadlines have a way of clarifying priorities.

    What letting agents should be evaluating now

    If you’re running a letting agency and haven’t audited your tech stack in the last twelve months, the checklist is fairly clear. First, check whether your existing platform has been updated for Renters’ Rights Act compliance, specifically, whether it supports Section 8 evidence management and the new tenancy structure that removes fixed terms. Second, assess your communication logging. If your team is still resolving maintenance issues over WhatsApp without any formal log, you’re creating a liability. Third, look at your referencing workflow; anything still involving paper or manual email chains is a candidate for replacement.

    The broader point is that the digital maturity question for letting agencies is now a regulatory question, not just an efficiency one. That framing matters when you’re making the case internally for tech investment. It’s the same argument I find running through sectors like financial services, where FCA Consumer Duty requirements are forcing fintech product teams to document their design decisions in ways that feel unfamiliar but are ultimately non-negotiable. The letting market is arriving at a similar inflection point.

    The firms getting ahead of the curve

    The agencies I’ve spoken to that are genuinely ahead on this tend to share one characteristic: they made the platform decision before the legislative deadline, not after. They had time to train staff, migrate records, and iron out the integration wrinkles without a compliance gun to their head. That lead time is now shorter than it was, but it hasn’t entirely gone. The secondary regulations and the ombudsman scheme’s operational detail are still being finalised, which means there is still a window to implement sensibly rather than reactively.

    PropTech for landlords and agents isn’t a silver bullet. The legislative complexity of the Renters’ Rights Act will still require legal advice, and no platform substitutes for understanding the underlying rules. But the firms treating technology as a core part of their operating model, rather than a bolt-on, are going to find compliance significantly more manageable, and their businesses considerably more resilient, as the dust settles.

    Frequently Asked Questions

    What PropTech tools are most useful for UK landlords under the Renters' Rights Act?

    Platforms like Goodlord, Arthur Online, and Landlord Studio are widely used for tenancy management, compliance record-keeping, and rent collection. The most valuable features right now are automated communication logging and Section 8 evidence management, which are directly relevant to the new possession grounds under the Act.

    How much does PropTech software cost for a small landlord in the UK?

    Costs vary considerably. Landlord Studio offers a free entry-level tier for basic rent tracking. Paid plans across most platforms run from around £10 to £30 per month for small portfolios, scaling upwards for larger agent-focused products. Given the potential cost of non-compliance under the new ombudsman scheme, the ROI case is stronger than it looks at first glance.

    Does PropTech actually help with Renters' Rights Act compliance, or is it just admin software?

    Modern platforms do more than basic admin. They generate structured audit trails, timestamped communication logs, and exportable evidence files that are directly useful in First-tier Tribunal proceedings. Several have also updated their tenancy agreement templates to reflect the removal of fixed terms and the abolition of Section 21.

  • FCA Consumer Duty and Fintech Product Design: What UK Founders Building for Retail Customers Must Get Right

    FCA Consumer Duty and Fintech Product Design: What UK Founders Building for Retail Customers Must Get Right

    If you are building a consumer-facing fintech product in the UK right now, the FCA Consumer Duty framework is not background noise. It is the operating environment. Since it came into full force for open products and services in July 2023, the rules have reshaped how regulated firms think about everything from the wording on a pricing page to the flow of an onboarding screen. For early-stage founders, understanding this is not just a compliance exercise. It is a product discipline that, done properly, makes your offering genuinely stronger.

    Fintech team reviewing FCA Consumer Duty product design decisions on screen
    Photo by Ivan S on Pexels

    I have spoken to a number of founders who treat Consumer Duty as something to hand off to a compliance consultant. That is understandable, especially when you are stretched thin. But the FCA has been explicit: this is not a tick-box exercise. The regulator expects firms to demonstrate that good outcomes for retail customers are embedded into product decisions from the beginning, not retrofitted before an audit. That shift in posture has real consequences for how you design, price, communicate, and onboard.

    What the four outcomes actually mean for product teams

    The FCA Consumer Duty is structured around four outcomes: products and services, price and value, consumer understanding, and consumer support. Each one has a direct translation into product design choices, and founders often underestimate how granular the expectations are.

    The products and services outcome requires that whatever you build is appropriate for the market you have identified. That sounds obvious, but the FCA expects documented evidence of target market assessments. If your credit product is being taken out primarily by people in financial difficulty, and your original target market assessment said otherwise, that is a problem. You need the data to show you are monitoring who is actually using the product, not just who you intended to use it.

    Price and value is where many fintech founders get caught out. The FCA is not capping prices, but it expects firms to demonstrate a rational relationship between what customers pay and what they receive. Subscription fee structures with unclear cancellation terms, or products where the headline rate is undercut by ancillary charges, are exactly the kind of thing examiners look for. Build your pricing model so you could explain it plainly to a customer who had never heard of your brand and have it still look fair.

    Consumer understanding: the communication standard you are actually being held to

    This is the outcome that touches your marketing copy, your app notifications, your email sequences, and your in-product messaging. The FCA is not asking whether your communications are technically accurate. It is asking whether a typical customer in your target market would genuinely understand the material implications of what you are offering.

    That distinction matters enormously. Terms and conditions that are legally complete but practically incomprehensible do not satisfy Consumer Duty. Neither does a risk warning buried in a font size that most people will skip. The FCA’s own Consumer Duty guidance references the concept of a “typical retail customer” repeatedly, and the bar for what that person can reasonably be expected to understand is deliberately conservative.

    My view is that the communication standard is actually the area where strong product teams have the most opportunity to differentiate. If your competitors are hiding fees in footnotes and your onboarding is genuinely transparent, that is a commercial advantage, not just a compliance benefit. Write for a person who is unfamiliar with financial products and you will likely write better copy for everyone.

    Mobile app onboarding flow designed to meet FCA Consumer Duty fintech product design standards
    Photo by Geri Tech on Pexels

    Onboarding design under Consumer Duty

    Onboarding is where Consumer Duty theory collides with product reality most sharply. The FCA expects that customers are given information at the right moment, in a format that supports a genuine decision, and that the onboarding process does not use design patterns that exploit cognitive biases or rush users past material information.

    Dark patterns are explicitly in scope. Pre-ticked boxes for upsells, countdown timers on decisions that have no genuine time constraint, and default settings that favour the firm over the customer are all the kind of thing Consumer Duty was designed to address. If you have inherited these patterns from an earlier version of your product, now is the time to audit them. The FCA has made clear it will look at the whole customer journey, not just the product documentation.

    Practically, this means your onboarding flow should be tested with real users from your target market before you scale. Not usability testing in the narrow sense, but comprehension testing: can someone who has never used your product explain back to you what they have just signed up for? If they cannot, you have a Consumer Duty exposure before a single customer complains.

    Vulnerable customers and how to design for them without patronising anyone

    The FCA has published detailed guidance on vulnerable customers, and Consumer Duty amplifies those expectations significantly. Firms must consider how customers experiencing temporary or permanent vulnerabilities interact with their products, and make reasonable adjustments. For most fintech founders, this is less about building entirely separate product tracks and more about applying good design principles consistently.

    Readable font sizes, plain language, accessible colour contrast, clear exit routes from any process, and the ability to access human support when automated journeys fail: these are the practical basics. A customer going through a bereavement who needs to close an account should not hit a wall of automated responses. That scenario is not hypothetical; it is exactly the kind of case the FCA uses when examining consumer support outcomes.

    If you are fundraising, I would also flag that institutional investors increasingly ask about Consumer Duty compliance frameworks alongside their standard due diligence. It has become part of the governance conversation, particularly at Series A and beyond. Getting your house in order early is not just about avoiding enforcement action; it affects your cap table conversations too. For context on how the regulatory picture shapes fintech investment, the article on what FCA Consumer Duty really means for fintech startups covers some of the broader dynamics worth understanding.

    Building evidence of good outcomes, not just good intentions

    The FCA Consumer Duty framework requires firms to monitor and evidence outcomes on an ongoing basis. That means data. You need to be tracking metrics that tell you whether customers are achieving the outcomes they should be: are they understanding the product? Are they using features that serve their interests? Are they exiting at points that suggest confusion or dissatisfaction?

    Many founders I speak to have strong product analytics on engagement and retention but weaker data on whether customers are actually better off for having used the product. Those are different questions. Building that measurement layer in now is far less disruptive than trying to retrofit it when the FCA sends a data request.

    Documentation matters too. Your board or senior manager responsible for Consumer Duty (under the Senior Managers and Certification Regime, someone must own it) should be receiving regular MI that covers outcomes, not just operational metrics. If you cannot produce that documentation, you cannot demonstrate compliance, regardless of how well your product actually performs.

    The broader principle here mirrors what I have seen in other compliance-heavy areas: firms that build rigour into process early spend far less time and money on remediation later. It is the same logic that drives good financial record-keeping or, for businesses operating across different sectors, using specialists like Asbestos Compliance Solutions rather than cutting corners on regulatory obligations. The cost of getting it right upfront is always lower than the cost of getting it wrong at scale.

    If you are building a new fintech product and want a useful cross-reference for how consumer-facing financial communication is evolving alongside the regulatory landscape, the earlier piece on FCA Consumer Duty rules for fintech and financial software businesses covers the software-specific angle in more detail.

    Frequently Asked Questions

    Does FCA Consumer Duty apply to early-stage fintech startups without full authorisation?

    Consumer Duty applies to all FCA-authorised firms, including those with limited or interim permissions. If you are operating under an Appointed Representative arrangement, the principal firm carries primary Consumer Duty responsibility, but that does not mean you can ignore the framework. The FCA expects that products distributed through AR models also meet the four outcomes.

    What counts as a 'dark pattern' under Consumer Duty and how do I know if my product has one?

    The FCA considers a design pattern a problem if it nudges customers towards decisions that benefit the firm at the customer’s expense, particularly through manufactured urgency, obscured exit routes, or misleading defaults. Review your onboarding flow, upsell screens, and cancellation journey specifically. If any step would look manipulative to a regulator watching over your customer’s shoulder, treat it as a Consumer Duty risk.

    How should fintech founders document Consumer Duty compliance for the FCA?

    You need a Consumer Duty implementation plan, a target market assessment for each product, regular board-level reporting on consumer outcomes, and records of how product and communication decisions were made with good outcomes in mind. The FCA can and does request this documentation during supervisory reviews, so it needs to be current, not retrospective.

    What happens if the FCA finds a fintech firm has breached Consumer Duty?

    Enforcement options include requirement variations, public censure, financial penalties, and in serious cases, suspension or cancellation of permissions. The FCA has also made clear it expects firms to self-identify issues and remediate proactively. A firm that waits for a complaint before acting will be viewed much less favourably than one that identifies a gap and fixes it before customers are harmed.

  • 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.

  • Why UK Founders Are Choosing Revenue-Based Financing Over Traditional Bank Loans in 2026

    Why UK Founders Are Choosing Revenue-Based Financing Over Traditional Bank Loans in 2026

    If you are running a fast-growing UK business and you need capital, the old playbook said go to your bank, present three years of accounts, and hope for the best. Many founders I speak to have tried exactly that in 2026 and walked away empty-handed, or worse, with an offer tied to a personal guarantee on their home. Revenue-based financing has moved firmly into the mainstream as an alternative, and the comparison with traditional lending is worth laying out properly, without the hype from either camp.

    UK founders reviewing revenue-based financing options in a modern office
    Photo by RDNE Stock project on Pexels

    What revenue-based financing actually is

    Revenue-based financing (RBF) is a funding arrangement where a lender advances a lump sum in exchange for a percentage of your monthly revenue until a fixed repayment cap is reached. That cap is typically 1.3x to 1.5x the original advance. If your revenue drops in a slow month, your repayment drops proportionally. If you have a strong quarter, you clear the balance faster.

    There is no equity involved. No dilution, no cap table complications, no investor seat at the board table. For founders who have spent time thinking carefully about how to protect their financial position as they grow, that distinction matters enormously. You are essentially selling a portion of future revenue, not a slice of the company.

    UK providers in this space include Uncapped, Clearco (operating in the UK market), and a growing cohort of fintech lenders who have built underwriting models around open banking and real-time revenue data rather than lagging credit files.

    How high-street bank lending actually works in practice

    High-street lenders in the UK, the major ones being Barclays, Lloyds, NatWest, and HSBC, broadly assess business loan applications against a combination of trading history, credit score, profitability, and security. For smaller businesses, that security frequently means a personal guarantee, which puts the director’s personal assets on the line if the business cannot service the debt.

    The process is slow. Applications can take six to twelve weeks. Approval rates for SMEs without tangible assets as collateral remain stubbornly low. According to the British Business Bank’s Small Business Finance Markets report, a significant proportion of smaller firms either receive less than they requested or are declined outright, and many simply stop applying because they expect rejection.

    For a SaaS business or a digital-first brand with strong monthly recurring revenue but limited physical assets, the high-street model is structurally misaligned. These businesses have cash flow, not buildings.

    The Growth Guarantee Scheme and what replaced CBILS

    The Coronavirus Business Interruption Loan Scheme ran its course and was replaced by the Recovery Loan Scheme, which itself evolved into the Growth Guarantee Scheme from 1 July 2024. Under this scheme, the government provides a partial guarantee to lenders, reducing the lender’s risk and theoretically making capital more accessible to viable businesses that lack conventional security.

    In practice, it helps. The partial government guarantee does take the edge off personal guarantee requirements in some cases, and interest rates are more competitive than unsecured commercial lending. But the scheme still runs through accredited lenders who apply their own credit criteria on top of the government guarantee. You are still submitting accounts, still going through credit checks, and still waiting weeks for a decision. For a founder who needs £150,000 within the month to fund a product launch or hire a key team, that timeline is a real constraint.

    The real comparison: speed, cost, and what you give up

    Let me put the three options side by side on the dimensions that matter most to a growth-stage founder.

    Speed: RBF providers routinely give decisions in 24 to 72 hours once you connect your accounts via open banking. High-street loans take weeks. Growth Guarantee Scheme applications through accredited lenders sit somewhere in between, but rarely under two weeks.

    Cost: This is where RBF gets scrutinised, rightly. A 1.4x repayment cap on a £100,000 advance means you pay back £140,000. How expensive that is depends entirely on how quickly you repay. If you clear it in six months, the annualised rate is high. If your revenue grows and you clear it in three months, the effective cost looks different again. High-street loans and Growth Guarantee Scheme facilities will generally carry lower headline interest rates, but factor in arrangement fees, the opportunity cost of waiting, and the risk premium baked into a personal guarantee, and the comparison is less clear-cut than it first appears.

    What you give up: With RBF, nothing structural. No equity, no directorial liability. With a bank loan, potentially a personal guarantee. With an equity round, a percentage of your company permanently. For founders who have already thought through what an eventual exit looks like and what impacts the final payout, the equity question is not abstract.

    Which businesses RBF actually suits

    RBF is not a universal solution. It works well for businesses with predictable, recurring, or high-frequency revenue. E-commerce brands with strong repeat purchase rates, SaaS businesses with monthly subscription income, and digital agencies with retainer-heavy client books are natural fits. The underwriting model depends on seeing consistent revenue data; without that, providers cannot calculate what a sustainable repayment percentage looks like.

    It works less well for capital-intensive manufacturing businesses, early-stage pre-revenue startups, or businesses with lumpy, project-based income where three months of strong revenue might be followed by two quiet ones. For those businesses, a structured term loan or even a carefully constructed equity raise might be the more sensible path. If you are also weighing up how your capital structure interacts with your broader financial position as an owner, the thinking in our piece on Business Asset Disposal Relief in 2026 is worth reading alongside this.

    Practical considerations before you apply

    Before approaching any RBF provider, get your revenue data clean and accessible. Most providers will want to connect directly to your Stripe, Xero, or banking data via open banking. The cleaner your records, the faster the decision.

    Understand the repayment percentage being proposed and model it against your monthly revenue at current levels and at a reduced level. RBF is designed to flex, but if your revenue drops sharply and stays low, the total repayment period extends, and that has cash flow implications across the rest of your operations.

    Check whether the provider is FCA authorised. Not all RBF providers operating in the UK are regulated in the same way, and given the regulatory environment for lending products, it is worth confirming how the product is classified before you sign anything. The FCA register is publicly searchable at fca.org.uk.

    My overall read of the market in 2026 is that RBF has earned its place as a legitimate third route alongside debt and equity. For the right business, it is faster, structurally cleaner, and commercially rational. The founders who use it well are the ones who go in with a clear plan for what the capital will do and a realistic model of how quickly their revenue can absorb the repayment.

    Frequently Asked Questions

    What is revenue-based financing and how does it differ from a business loan?

    Revenue-based financing provides a lump sum in exchange for a fixed percentage of your monthly revenue until a predetermined repayment cap is reached. Unlike a traditional loan, there is no fixed monthly payment, no interest rate in the conventional sense, and typically no personal guarantee or collateral required.

    How much does revenue-based financing cost compared to a bank loan?

    RBF providers charge a flat fee expressed as a repayment cap, typically 1.3x to 1.5x the amount advanced. The effective annual cost depends on how quickly you repay. High-street bank loans carry lower headline rates but often include arrangement fees, slower access to funds, and in many cases a personal guarantee that carries its own financial risk.

    Do I need to give up equity to access revenue-based financing?

    No. Revenue-based financing is not equity financing. You retain full ownership of your business and there is no cap table impact. The lender’s return comes solely from the revenue repayment arrangement, not from a shareholding.

    Is revenue-based financing available to all UK businesses?

    It suits businesses with consistent, measurable revenue such as SaaS companies, e-commerce brands, and retainer-based agencies. Pre-revenue startups, highly seasonal businesses, or those with very lumpy income tend not to qualify, as the underwriting relies on stable revenue data to set a sustainable repayment percentage.

  • 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.

  • How to Use Companies House and HMRC Data to Benchmark Your Business Against UK Competitors

    How to Use Companies House and HMRC Data to Benchmark Your Business Against UK Competitors

    Most UK business owners have a rough sense of how they compare to their competitors. Gut feel, the odd conversation at an industry event, a glance at a rival’s website. But gut feel is not a strategy, and there is a substantial amount of hard financial data sitting in public registries that most founders and finance leads simply never look at. If you want to benchmark business competitors UK Companies House data is your starting point, and it costs nothing to access.

    I’ve spent time digging through filings for clients across professional services, technology, and manufacturing sectors, and the intelligence you can extract, legally and for free, is genuinely underestimated. Here is a practical guide to doing it properly.

    Business analyst reviewing Companies House filings to benchmark business competitors UK
    Photo by https://kaboompics.com/ on Pexels

    What data is actually available at Companies House?

    Every company incorporated in England, Wales, Scotland, or Northern Ireland must file accounts with Companies House. The depth of information depends on the company’s size classification, which is where many people get tripped up.

    Small companies (turnover under £10.2 million, fewer than 50 employees) can file abbreviated or micro-entity accounts. These show net assets and a very limited balance sheet, but no profit and loss. Medium companies (turnover under £36 million, up to 250 employees) must file a full profit and loss account. Large companies and public limited companies file full statutory accounts including detailed notes on headcount, remuneration, and segmental performance.

    So if your direct competitors are small companies filing micro-entity accounts, your intelligence will be limited to their net assets and overall financial health. If they are medium or large, you can see turnover, gross profit, operating profit, and cost structures. The trick is knowing which competitors are worth pulling filings for and cross-referencing what is there.

    How to find and read the right filings

    The Companies House search service lets you search by company name or number. Pull up the filing history for each competitor you want to examine, then download the most recent full accounts PDF. Pay attention to the filing date: accounts can be filed up to nine months after the year end for private companies, so you may be looking at data that is over a year old by the time you read it.

    Once you have the accounts, focus on three areas. First, turnover and gross profit, which gives you a comparable revenue figure and gross margin. Second, administrative expenses and operating profit, which reveals cost structure efficiency. Third, staff costs and average headcount, which are almost always disclosed in the notes and allow you to calculate revenue per employee. That last metric is particularly useful for services businesses.

    A practical workflow I tend to recommend is building a simple spreadsheet with one row per competitor and columns for: financial year end, turnover, gross profit margin, operating profit margin, headcount, revenue per head, and net assets. Once you have three or four competitors mapped out alongside your own figures, patterns become obvious quickly.

    Going further: using HMRC data and ONS benchmarks

    Companies House filings give you competitor-specific data. To put that data in broader context, you need sector-level benchmarks. HMRC publishes detailed corporation tax statistics and UK trade statistics broken down by industry. The Office for National Statistics publishes annual business surveys covering turnover, employment, and output by sector code (SIC code). If you are already using ONS datasets to inform business decisions, this is a natural extension of the same habit. I wrote previously about how to use ONS economic data to make smarter business decisions without a research team, and the approach applies directly here.

    The combination is powerful. ONS data tells you what a typical business in your sector looks like. Companies House filings tell you what specific named competitors look like. You can then position yourself relative to both: are you above or below sector average gross margin, and are you above or below the specific firms you actually compete with for contracts or customers?

    Tools that make the process faster

    Manual PDF analysis is fine for a handful of competitors, but it does not scale. Several tools aggregate Companies House data into searchable dashboards. Beauhurst, Fame (from Bureau van Dijk), and Creditsafe all offer company financial data with filtering and export functions. These are paid products, but even a short subscription can save hours of manual work if you are benchmarking across a larger peer group.

    For a free alternative, the Companies House API allows you to pull filings programmatically if you have any technical resource available. The API documentation is thorough, and for a developer it is a straightforward integration. If you are building an internal knowledge base for your business, this kind of structured competitive data belongs in it. Maintaining a living reference of competitor financials, updated each time new filings drop, is far more useful than a one-off snapshot. The case for building internal knowledge bases to reduce reliance on individual staff members is directly relevant here: institutional competitive intelligence should not live only in one person’s head or a forgotten spreadsheet.

    Honest limitations you need to account for

    There are real constraints to acknowledge. Filing dates mean data lags. Accounting policies vary between companies, which means gross margin figures are not always directly comparable, particularly where companies capitalise software development costs or treat certain expenses differently. Group structures can obscure individual trading entity performance. And as noted, smaller competitors filing micro-entity accounts give you very little to work with.

    You also cannot see cash flow from operations in many cases, which limits your view of liquidity. Net profit in filed accounts is after tax and often after director remuneration adjustments, so be cautious about drawing conclusions on profitability without understanding the underlying structure. This is where reading the notes to the accounts, not just the face of the statements, makes a real difference.

    How to act on what you find

    The point of this exercise is not curiosity. It is decision-making. If your gross margin is 38% and the two closest named competitors are running at 47% and 52%, that is a meaningful signal. It might mean your pricing is too low, your cost of sales is higher than it should be, or your service mix is different. Any of those warrants investigation.

    If a competitor’s revenue per employee is significantly higher than yours, that is a productivity question worth examining. Are they more automated? Do they have a different service tier? Are they simply charging more? Similarly, if a competitor’s headcount grew by 40% in one filing year, that tells you something about where they are investing and which markets they are moving into.

    Finance leads can bring this analysis into quarterly business reviews as a standing agenda item. Founders can use it to calibrate investor conversations: being able to say your gross margin is in the top quartile for your sector, with specific comparable company data to support it, is a materially stronger position than a general assertion. And if you are managing the security and digital posture of your business alongside this kind of data work, keeping that competitive intelligence properly protected matters too. The guidance on auditing your business’s digital security posture without a specialist firm is worth reading alongside this.

    Public data is not the whole picture, but used properly, it gives UK business owners a grounded, evidence-based view of where they sit in their market. That is a significant advantage over running on instinct alone.

    Frequently Asked Questions

    Is it legal to use Companies House data to benchmark competitors?

    Yes, completely. Companies House filings are public records and anyone can access, download, and analyse them. There are no restrictions on using this data for commercial analysis or competitive intelligence purposes.

    What financial information can I see in a competitor's Companies House accounts?

    This depends on company size. Medium and large companies must file full profit and loss accounts including turnover, gross profit, operating profit, and headcount. Small and micro-entity companies can file abbreviated accounts, which may only show net assets and a limited balance sheet without revenue or margin detail.

    How up to date is the financial data on Companies House?

    Private limited companies have up to nine months after their financial year end to file accounts. This means the most recent filing for a competitor with a December year end might not appear until September the following year, so the data can be 12 to 18 months old by the time you read it.

  • What UK Employers Need to Know About the Right to Switch Off and Its Impact on Remote Work Policies

    What UK Employers Need to Know About the Right to Switch Off and Its Impact on Remote Work Policies

    There’s a bill quietly gathering momentum in Westminster, and if you run a business with remote or hybrid staff, you should already have it on your radar. The right to switch off has moved from a talking point to a genuine legislative pressure point in the UK, with trade unions, employment lawyers, and the previous and current administrations all weighing in. Ireland introduced its own statutory code in 2021. Belgium legislated for it in 2022. The UK has been slower, but that gap is closing.

    I’ve spoken to a number of small and mid-sized business owners over the past few months who simply aren’t aware of where this is heading. The right to switch off UK employment law remote work conversation is no longer hypothetical. Waiting until it’s legally compelled before updating your communication policies and employment contracts is the kind of decision that tends to look very avoidable in retrospect.

    Professional working remotely in a home office, illustrating right to switch off UK employment law remote work
    Photo by RDNE Stock project on Pexels

    What the right to switch off actually means

    The core idea is straightforward: employees should not be expected to respond to work communications outside of their contracted hours. That means emails at 10pm, Slack messages on a Saturday, or Teams pings at 6am are not just poor management practice, they could become the subject of formal complaint and, eventually, legal action.

    The Labour government included right-to-disconnect provisions in its Employment Rights Bill, which received its second reading in late 2024 and has been progressing through Parliament since. The bill doesn’t hand employees an immediate statutory right to ignore their managers, but it does direct ACAS to develop a statutory code of practice on the matter. A statutory code doesn’t carry the force of criminal law, but employment tribunals must take it into account when assessing cases. Tribunals can also uplift compensation by up to 25% if an employer unreasonably fails to follow it. That changes the calculus considerably.

    Why remote and hybrid work makes this urgent

    Pre-pandemic, the boundary between office hours and home life was largely self-policing. The commute functioned as a natural buffer. Remote work removed that buffer entirely, and the data since then has been consistent: remote workers, on average, work longer hours than their office-based counterparts, and a significant proportion receive work communications well into the evening.

    For businesses that moved to hybrid models quickly in 2020 and 2021, many never updated their communication norms to reflect the new reality. Expectations that were fine in an office, where everyone left at 6pm, became genuinely oppressive when applied to someone working from a spare bedroom. I’d argue that most employers didn’t intend to create that pressure, but intent doesn’t move the needle in an employment tribunal.

    The right to switch off UK employment law remote work framework will almost certainly treat asynchronous communication differently from synchronous demands. Sending an email at 11pm is not the same as calling someone at 11pm. But if you’re building a culture where staff feel obligated to respond to that 11pm email by midnight, the distinction matters less than you might hope.

    What to update in your communication policies now

    The practical response isn’t to wait for the ACAS code and then scramble. The sensible move is to review and tighten your internal communication policies while the legislative framework is still being finalised. Here’s where I’d start.

    Define your expected response windows

    Put in writing, clearly, what “urgent” means. If your business genuinely operates across time zones or has on-call requirements, document those explicitly and compensate accordingly. If it doesn’t, your staff have every right to assume that messages sent outside contracted hours can wait until the morning.

    Review your employment contracts

    Contracts that include vague language around “flexibility” or “meeting the needs of the business” may need tightening. A clause that was harmless when written in 2019 could be problematic under an evolving statutory code. Get employment law advice if you’re uncertain, but at a minimum, make sure your contracts specify contracted hours clearly and don’t imply any implicit duty to be contactable beyond them.

    Audit your communication tools

    Slack, Teams, and similar platforms have notification settings that most people never configure. As an employer, you can set expectations around how these tools are used. Some businesses now configure notifications to automatically mute outside of working hours at the organisation level. That’s a low-cost signal with a real cultural impact. If your business already uses an internal knowledge base to reduce dependency on key staff, you may already be reducing the volume of out-of-hours pings that happen simply because information isn’t easily accessible during the day.

    Train your managers

    This is the piece most businesses miss. A policy document means nothing if line managers routinely email at 9pm and expect replies by breakfast. Manager behaviour sets the cultural norm. Training doesn’t need to be expensive or lengthy; it just needs to be explicit about what the business expects and why it matters.

    The business case beyond compliance

    I want to make one point that sometimes gets lost in the compliance framing. The right to switch off isn’t just a legal risk to manage; there’s a genuine commercial upside to getting this right.

    Burnout is expensive. The CIPD’s 2025 Health and Wellbeing at Work report found that presenteeism and stress-related absence continue to cost UK employers billions annually. Staff who feel they can’t disconnect are more likely to suffer from chronic fatigue, make more errors, and leave sooner. High turnover in remote teams is particularly costly because the informal knowledge transfer that happens in an office simply doesn’t occur, which is precisely why businesses are investing in tools like asynchronous video to replace internal meetings and reduce the synchronous load on staff.

    Businesses that get ahead of right-to-disconnect expectations also tend to communicate better during contracted hours. When everyone knows that a message sent at 8pm will be read tomorrow, they become more deliberate about what they send and when. That clarity reduces noise and improves the quality of internal communication across the board.

    What’s coming and when

    The ACAS code of practice is expected to be published for consultation once the Employment Rights Bill receives Royal Assent, which most employment lawyers expect in 2026. Businesses will likely have a transition period before the code becomes formally applicable. That transition window is your opportunity to act deliberately rather than reactively.

    My read of the situation is that the final code will distinguish between sectors with genuine operational need for out-of-hours contact (healthcare, emergency services, certain client-facing financial services roles) and those where it has simply become a bad habit. If you’re in the latter camp, the time to self-correct is now.

    For those managing the broader shift in how teams operate, it’s worth considering how right-to-switch-off expectations interact with the wider employment cost pressures UK employers are managing in 2026. Getting communication policies right is one of the lower-cost levers available, and it tends to have a disproportionate effect on retention.

    The direction of travel is clear. The question is whether your business shapes its own policies now, or has them shaped for it later.

    Frequently Asked Questions

    Is the right to switch off currently law in the UK?

    Not yet as a standalone statutory right. The Employment Rights Bill includes provisions directing ACAS to produce a statutory code of practice on the right to disconnect. Once that code is in force, employment tribunals can factor it into decisions and uplift compensation by up to 25% where employers have unreasonably ignored it.

    What counts as a breach of the right to switch off for remote workers?

    The exact definition will depend on the ACAS code once published, but the general principle is that expecting employees to respond to work communications outside their contracted hours, particularly repeatedly or under implicit pressure, would be considered a breach. This applies equally to remote and office-based staff.

    Do employers need to update employment contracts before the law changes?

    It’s strongly advisable. Contracts with vague language around availability or flexibility may already expose employers to claims under existing working time and constructive dismissal law. Tightening contracts now reduces that risk and makes any future compliance with the statutory code easier.

    How does the right to switch off apply to on-call or shift workers?

    Workers with genuine on-call requirements can have those obligations written explicitly into their contracts, with appropriate compensation. The right to disconnect is broadly aimed at roles where out-of-hours contact has become an informal expectation rather than a formal contractual condition.

    What practical steps can UK businesses take now to prepare for right-to-switch-off legislation?

    Businesses should review and update internal communication policies, define expected response windows in writing, configure notification settings on tools like Slack and Teams to mute outside contracted hours, and train line managers to model the right behaviour. An employment law solicitor can advise on any contract changes needed.