# Doddle - full site text > A small, senior UK studio. We build digital platforms, AI products and MVPs, and we help teams move sensibly between OutSystems and modern stacks. Every page of https://www.doddledesign.co.uk as markdown, concatenated. Generated at build time. Prefer [llms.txt](https://www.doddledesign.co.uk/llms.txt) for the short version, or request any page with the header `Accept: text/markdown`. <|page /|> --- title: "Doddle, A senior UK studio building software that lasts." url: "https://www.doddledesign.co.uk/" section: "Home" description: "A small, senior UK studio. We build digital platforms, AI products and MVPs, and we help teams move sensibly between OutSystems and modern stacks." publisher: "Doddle" --- A senior UK studio # Where AI, low-code and modern software come together From OutSystems applications to AI-native products, we help organisations build, evolve and re-platform without betting the business on one stack. [See what we do](https://www.doddledesign.co.uk/services) [Start a project](https://www.doddledesign.co.uk/contact) Partnerships ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-icon.png) OutSystems Sales & Delivery Partner since 2021. Eighteen years on the platform. ![Anthropic](https://www.doddledesign.co.uk/logos/claude-code-icon.svg) Anthropic Two years in daily production. Engineers, designers and product, every week. ![Looking up - ambition, and the engineering that gets there](https://www.doddledesign.co.uk/images/home-hero.webp) A senior UK studio Aim further. We'll build the software that gets you there. Trusted by teams at ![UCL](https://www.doddledesign.co.uk/logos/ucl.png) ![IGLU](https://www.doddledesign.co.uk/logos/iglu.png) ![Finbridge Global](https://www.doddledesign.co.uk/logos/finbridge-global.png) ![Deloitte](https://www.doddledesign.co.uk/logos/deloitte.png) ![Cognomie](https://www.doddledesign.co.uk/logos/cognomie.png) ![Eversholt Rail](https://www.doddledesign.co.uk/logos/eversholt-rail.png) ![Fujitsu](https://www.doddledesign.co.uk/logos/fujitsu.png) ![Boardly](https://www.doddledesign.co.uk/logos/boardly.png) ![RailX](https://www.doddledesign.co.uk/logos/railx.png) ![Darwin Escapes](https://www.doddledesign.co.uk/logos/darwin.png) What we do ## Two tracks, four ways in. We're specialists. We build digital products on OutSystems and on modern AI-native stacks, we move teams between the two when context changes, and we help leaders cut through an AI landscape that's moving faster than most can keep up with. Build ### Ship the thing. ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-icon.png) Build ### OutSystems Delivery Low-code speed inside enterprise guardrails. Greenfield builds, business process automation, workflows and mobile, with modern AI capability brought safely into the estate. Read more→ ![Claude](https://www.doddledesign.co.uk/logos/claude-code-icon.svg) Build ### AI-Native Delivery Production-grade AI products built on modern stacks, with our proprietary delivery harness underneath. Includes fixed-price MVPs for funded startups. Read more→ Decide & move ### Pick the right call. Move when it's time. Decide ### Consultancy Services Short, paid engagements that produce a clear recommendation rather than code. For decision points where the answer matters more than the deck. Read more→ Re-platform ### Migrate away from OutSystems Move applications off OutSystems onto a modern stack in 6 to 12 weeks, with a relatively fixed cost tied to your application object footprint. Lower run cost, no per-user or per-app licence escalation, and a stack your team can extend. Read more→ [Start a project](https://www.doddledesign.co.uk/contact) Across the two ## Built on OutSystems in 10 weeks. Re-platformed to AI-native when it was time. Finbridge Global launched with us on OutSystems in 10 weeks. As it scaled, the same team re-platformed it onto an AI-native stack with document AI and retrieval assistants. That's the bridge, in practice. [Read the Finbridge story](https://www.doddledesign.co.uk/work/finbridge) [How we migrate](https://www.doddledesign.co.uk/services/outsystems-migrations) ![Finbridge - from OutSystems MVP to AI-native re-platform](https://www.doddledesign.co.uk/images/finbridge-migration.png) Selected work ## Some of what we've shipped recently. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. AI, three ways ## We use AI every day to deliver better software, faster. Three places it shows up in the work: building the software, keeping our OutSystems builds sharp, and inside the products we ship for clients. 01 · Building the software ### Faster, sharper builds. Engineers, designers and product use AI day-to-day to ship working software more quickly, without dropping the quality bar. [How we deliver AI→](https://www.doddledesign.co.uk/services/ai-native-delivery) 02 · Inside OutSystems ### Smarter OutSystems delivery. AI helps us build and diagnose inside OutSystems too, reviewing modules, finding the root cause of awkward bugs, and keeping your platform investment moving. [AI inside OutSystems→](https://www.doddledesign.co.uk/services/outsystems-delivery) 03 · Inside the product ### Best-in-class product features. Where it earns its place, we build AI into the product itself: smart search, in-app assistants, document automation, the features users now expect. [See what we've built with AI→](https://www.doddledesign.co.uk/built-with-ai) Partnerships ## Two partnerships, both pulling their weight. Two partners we work with in production, every week. OutSystems for low-code at enterprise scale, Anthropic for the AI tooling that sits across the rest of the work. ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-logo.svg) Sales & Delivery Partner ### Partner since 2021, 18+ years on the platform. Enterprise OutSystems platforms across travel, transport, fintech, education and the public sector. Long on craft, formally a partner since 2021. ![Anthropic](https://www.doddledesign.co.uk/logos/claude-code.svg) Two years in production ### Two years building with Claude. Engineers, designers and product use Claude Code daily, with the same quality controls we apply to anything human-written. We work directly with Anthropic's tooling and stay close to the product as it evolves. [How we build](https://www.doddledesign.co.uk/engineering) [Let's talk](https://www.doddledesign.co.uk/contact) Why Doddle ## Senior people, plain English, no surprises. A small studio, deliberately. The people you brief are the people who do the work. [More about us →](https://www.doddledesign.co.uk/about) ![The Doddle team at work](https://www.doddledesign.co.uk/images/home-team.jpg) ### Small team, senior hands The people you meet in week one are the people writing the code in week six. No bench, no handover. ### Weekly demos Working software each week, not status reports. You see the build, week by week. ### Plain English We explain things clearly, so you know what we are building, why it matters and what you are paying for. ### Honest about fit We'll tell you if we're not the right team for the job. The relationship matters more than the next invoice. In their words ## Clients we keep working with. > “We started with Doddle on OutSystems, fast MVP, fast iteration. As we matured, they helped us move onto a full AI-native stack. The speed, the thinking, and the care in execution have been exceptional.” Barbara GottardiCEO, Finbridge Global > “Doddle turned the RailX vision into a real digital platform at speed. Their product thinking and technical delivery have been key to a platform that can genuinely reshape the industry.” Steve FreemanChair, RailX > “PayWise has completely transformed how we manage supplier payments, with real-time visibility of our cash position. The return on investment has been outstanding.” Lorna VincentCFO, IGLU Recent thinking ## Notes from the work. [See all insights →](https://www.doddledesign.co.uk/insights) Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 minRead → Case notes ### From OutSystems to AI-native, how we re-platformed Finbridge in 10 weeks What it actually looks like to move a regulated financial services platform off OutSystems onto a modern AI-native stack, including the parts that surprised us. 9 minRead → Decision framework ### OutSystems in 2026: a measured view A decision framework for weighing whether OutSystems still fits your team in 2026. Where the platform wins, where it doesn't, and how to tell the difference, written by people who still deliver on it every week. 8 minRead → ## Got something on your mind? Half an hour, no decks, no sales pitch. We'll be honest about whether we can help and what we'd do next. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /services|> --- title: "What we do" url: "https://www.doddledesign.co.uk/services" section: "Services" description: "Four ways we work with you, AI-Native Delivery, OutSystems Delivery, OutSystems migrations, and Consultancy." publisher: "Doddle" --- What we do # Four ways we work, depending on where you are. We organise the work into four tracks so it's easy to find a starting point. Pick the closest match. If none quite fits, that conversation is usually the most useful one to have. [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ![Doddle services in motion](https://www.doddledesign.co.uk/images/services-hero.jpg) ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-icon.png) Build ## OutSystems Delivery Low-code speed inside enterprise guardrails. Greenfield builds, business process automation, workflows and mobile, with modern AI capability brought safely into the estate. Read more→ ![Claude](https://www.doddledesign.co.uk/logos/claude-code-icon.svg) Build ## AI-Native Delivery Production-grade AI products built on modern stacks, with our proprietary delivery harness underneath. Includes fixed-price MVPs for funded startups. Read more→ Re-platform ## Migrate away from OutSystems Move applications off OutSystems onto a modern stack in 6 to 12 weeks, with a relatively fixed cost tied to your application object footprint. Lower run cost, no per-user or per-app licence escalation, and a stack your team can extend. Read more→ Decide ## Consultancy Services Short, paid engagements that produce a clear recommendation rather than code. For decision points where the answer matters more than the deck. Read more→ Want to go deeper?[What we build with AI→](https://www.doddledesign.co.uk/built-with-ai) [How we build with AI→](https://www.doddledesign.co.uk/engineering) ## Not sure which one fits? That's a common starting point. A 30-minute call usually makes it obvious, and if it doesn't, we'll tell you straight. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Start a project](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work|> --- title: "Work" url: "https://www.doddledesign.co.uk/work" section: "Work" description: "Selected case studies from Doddle, AI-native products, OutSystems builds and migrations, and consultancy engagements that produced clear answers." publisher: "Doddle" --- Work # Some of what we've shipped. A small selection of recent work, across financial services, transport, fintech, SaaS and logistics. Different domains, same discipline. By serviceAllOutSystems MigrationsAI-Native DeliveryOutSystems Delivery ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ![RailX card](https://www.doddledesign.co.uk/images/work/railx/railx-card-image.webp) OutSystems Delivery Logistics / Sustainability ### RailX RailX makes sustainable rail freight easier to quote, book and manage, with carbon savings and final-mile logistics built in. The platform has moved 20,000 containers for 100+ customers and saved over 300,000 kg of CO₂. ![Cognomie card](https://www.doddledesign.co.uk/images/work/cognomie/cognomie-card.jpg) OutSystems Delivery Health & Wellbeing ### Cognomie Cognomie scales 1-to-1 mental fitness coaching across 50+ organisations, with automated coach matching, interactive assessments and integrated video, achieving an NPS of 95+ and a 50% to 80% uplift in mental fitness. ![PowrKidz card](https://www.doddledesign.co.uk/images/work/powrkidz/powrkidz-card.jpg) OutSystems Delivery Education / Wellbeing ### PowrKidz PowrKidz gave primary-school teachers ready-to-run exercise sessions, live engagement tracking and personalised development plans, reaching 5,000 students across 20 schools in its first six months. ![AI-powered LMS card](https://www.doddledesign.co.uk/images/work/ai-powered-lms/ai-powered-lms-card.webp) AI-Native Delivery Professional services ### AI-powered LMS We replaced an off-the-shelf LMS for a global change-management business with a bespoke learning platform built around AI-powered search, a generative AI tutor and live engagement dashboards, shipped to MVP in 14 weeks and now used by 5+ enterprise customers. ![Payment Swap card](https://www.doddledesign.co.uk/images/work/payment-swap/payment-swap-card.jpg) OutSystems Delivery Automotive / Fintech ### Payment Swap Payment Swap helps drivers find their next car by monthly payment, with digital finance approvals, a sub-20-minute collection flow and 100k+ cars listed across a 5-star Trustpilot-rated marketplace. ## Got a build like one of these? Tell us the goal, we'll come back with how we'd approach it, roughly how long, and roughly what it'd cost. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights|> --- title: "Insights" url: "https://www.doddledesign.co.uk/insights" section: "Insights" description: "Notes from the work, patterns we're seeing in AI delivery, OutSystems, migrations, and the wider digital market." publisher: "Doddle" --- Insights # Notes from the work. Short, honest writing about what we're seeing in AI delivery, low-code, migrations and the wider digital market. Opinions held lightly, refined often. FeaturedPractice ## “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 7 August 2026 8 min read Read it → Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 22 July 2026Read → Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 27 May 2026Read → Practice ### Going in-house with AI, without going it alone If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over. 13 May 2026Read → Case notes ### From OutSystems to AI-native, how we re-platformed Finbridge in 10 weeks What it actually looks like to move a regulated financial services platform off OutSystems onto a modern AI-native stack, including the parts that surprised us. 21 April 2026Read → Practice ### When AI earns its place, and when it doesn't Most AI features fail in production not because the model was wrong, but because the surrounding system was unbuilt. A short field guide. 2 April 2026Read → Decision framework ### OutSystems in 2026: a measured view A decision framework for weighing whether OutSystems still fits your team in 2026. Where the platform wins, where it doesn't, and how to tell the difference, written by people who still deliver on it every week. 12 March 2026Read → Practice ### Migrations without rubbishing the platform A practical guide to moving off a platform honestly, without the theatrics, without losing users, and without burning the partnership. 19 February 2026Read → Practice ### Evals, not demos - the AI quality habit that separates products from prototypes If your AI feature has no evaluations, it has no quality. A short, opinionated take on the discipline we apply to every AI build. 30 January 2026Read → ## Subscribe when there's something worth your inbox. No newsletter, no drip campaign. The best path to keep up is to follow us on LinkedIn or check back when there's something new. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Follow on LinkedIn](https://www.linkedin.com/company/doddledesign) [Start a project](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /about|> --- title: "About" url: "https://www.doddledesign.co.uk/about" section: "Studio" description: "A small, senior UK product studio. We combine low-code, modern engineering and practical AI to build digital products, internal systems and automation that make work easier for the people who use them." publisher: "Doddle" --- About # A product studio for organisations that need to move faster. We combine low-code, modern engineering and practical AI to build digital products, internal systems, and automation that deliver measurable impact for the people who use them. [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ![The Doddle team](https://www.doddledesign.co.uk/images/about-1.jpg) Who we are ## A boutique product studio that cares about making digital delivery faster, clearer and more reliable. We've delivered inside global banks, FTSE 100s and seed-stage startups. We know what makes those builds go wrong, and we know what makes them go right. The team is deliberately small so every engagement gets senior people, and structured so scale doesn't dilute that. Designers, engineers and product, working in the same room on the same problem. We hold a high bar on the craft, we say what we'd do and why, and we stay close to the work until it's in production and earning its keep. Low-code on OutSystems, modern engineering on AI-native stacks, and the bridge between the two when the context shifts. Same disciplines on either side. Our story ## Led by people who build real businesses, not just client projects. ![Tom Ciullo](https://www.doddledesign.co.uk/images/about-founder.jpg) Doddle was started by Tom Ciullo, a product and technology leader with eighteen years of experience delivering digital systems across global banks, FTSE 100 organisations and high-growth startups. He's worked as a CTO, held board roles, and co-founded several businesses. That gives him a working understanding of what it takes to build products that hold up in the real world. We're a small, senior team that stays close to the work and focuses on clear thinking, sensible decisions and reliable delivery. Clients trust us with internal platforms, complex workflows, and systems where quality, speed and practicality all have to land at the same time. We've also built and launched our own products, taking ideas from concept to market. That experience shapes how we work. We don't just deliver software, we build products the way founders and operators need them to work. > “We work best with organisations that want to move quickly, adopt practical technology, and build digital capability that scales.” Tom CiulloFounder What you'll notice ## Working with us, day to day. ### Small team, senior hands The people you meet in week one are the people writing the code in week six. No bench, no handover. ### Opinions, held lightly We'll tell you what we'd do, and why. If your context disagrees, we adjust. ### Weekly demos Working software each week, not status reports. ### Plain English We explain things clearly, so you know what we are building, why it matters and what you are paying for. ### Honest pricing Fixed price where the scope is clear. Flexible delivery where it is not. We will always explain what fits best and why. ### Honest about fit We'll be honest about whether we're the right team for the job. The relationship matters more than the next invoice. What we believe ## A few principles that guide what we do. Held lightly. Refined by the work. We'll change our mind when we should. ### Speed is a strategic advantage. Faster delivery unlocks value earlier. Half of getting it right is getting it in front of real people quickly, and then changing it. ### Quality and simplicity always win. Clean architecture beats complexity. Well-named identifiers beat clever ones. Boring tools beat fashionable ones, in the long run. ### AI is a practical tool, not a gimmick. Used carefully, AI cuts the cost of building things and lifts the quality bar at the same time. Used carelessly, it puts demos in front of customers. We do the first kind. ### Technology should make work easier. Digital systems exist to reduce effort for the people who use them. If a feature creates more work than it removes, it shouldn't ship. ### Small teams deliver the strongest results. Lean, experienced teams move faster, make better calls, and stay closer to the work that matters. We've stayed deliberately small for that reason. The other half of the studio is the engineering practice that turns those beliefs into software that holds up in production. [How we build](https://www.doddledesign.co.uk/engineering) ![Doddle team mid-build](https://www.doddledesign.co.uk/images/about-3.jpg) Projects with a purpose ## Working with brilliant clients on technology that does real good. Not every product we ship is a purpose project, but the ones that are stay with the team for a long time. ![RailX](https://www.doddledesign.co.uk/images/work/railx/railx-card-image.webp) Carbon ### Reducing emissions with RailX Using technology to make UK rail freight a sensible alternative to road. Over 300 tonnes of CO₂ saved across 20,000+ container movements. Read the case study→ ![PowrKidz](https://www.doddledesign.co.uk/images/work/powrkidz/powrkidz-card.jpg) Child health ### Tackling childhood inactivity with PowrKidz Bringing HIIT-style fitness sessions into primary schools. 20 schools live, 5,000 students and 700 teachers supported within six months of launch. Read the case study→ ![Cognomie](https://www.doddledesign.co.uk/images/work/cognomie/cognomie-card.jpg) Mental fitness ### Building resilience with Cognomie A digital platform for mental fitness coaching. 50+ organisations supported, NPS 95+, with reported uplift of 50–80% in mental fitness scores. Read the case study→ [See more work](https://www.doddledesign.co.uk/work) [Let's talk](https://www.doddledesign.co.uk/contact) Common questions ## The things people ask us before working together. Quick answers to the questions that come up most often. If yours isn't here, ask us and we'll add it. What size of organisation do you usually work with? All sizes. We've delivered for global banks, FTSE 100s, mid-market enterprises and seed-stage startups. The team is intentionally small enough that every engagement gets senior people, and structured enough that scale doesn't break the work. How do you charge? Fixed scope, fixed price where it makes sense, usually MVPs and migrations. Time-and-materials where it doesn't, usually longer programmes where requirements move week to week. We'll always tell you which we think fits, and why. Do you work onsite or remote? Both. We're a UK team, mostly working remote, comfortable onsite where the project needs it. Weekly demos run regardless. How fast can you start? Usually within two to four weeks of the first conversation. Discovery engagements can start sooner if the timing's tight. We don't take on work we can't staff with senior people. ## Want to know more before getting in touch? Read what we've shipped, what we've written, or come straight to the conversation. Whichever's easiest. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /built-with-ai|> --- title: "Built with AI" url: "https://www.doddledesign.co.uk/built-with-ai" section: "Studio" description: "Real products Doddle has shipped using AI: full AI-native builds, smart features inside everyday business systems, and AI brought safely into OutSystems estates." publisher: "Doddle" --- Built with AI # Real products, shipped with AI at the centre. We build practical AI into real products, internal systems and everyday workflows. Sometimes that means a full AI-native product. Sometimes it means smart automation inside the tools you already use. [See the work](https://www.doddledesign.co.uk/built-with-ai#builds) [How we build with AI](https://www.doddledesign.co.uk/services/ai-native-delivery) The patterns ## The AI shapes that turn up most often in our work. Built on modern AI-native stacks where that fits, and brought safely inside OutSystems estates where that fits better. ### Knowledge AI you can trust AI that answers questions from your own content, with citations users can verify. The technique behind it is called retrieval-augmented generation, or RAG. ### Voice-driven products Voice-based interviews, transcription and summarisation, with the analysis layer that turns recordings into something useful. ### AI that reads and matches Summarising CVs, matching candidates, classifying documents. Turning messy text into structured decisions your team can act on. ### AI that does the work end-to-end Multi-step AI that completes a task on its own, with the safety checks to know when to stop and ask a human. ### Analytics in plain English Ask a question in normal language, get a chart against your real data. Safe to run, accurate, and easy to measure. ### AI inside the systems you already have Smart features brought safely into OutSystems and other existing environments, without breaking the rest of the estate. Selected AI builds ## Three recent products where AI is the point, not the flavour. [All work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ![AI-powered LMS card](https://www.doddledesign.co.uk/images/work/ai-powered-lms/ai-powered-lms-card.webp) AI-Native Delivery Professional services ### AI-powered LMS We replaced an off-the-shelf LMS for a global change-management business with a bespoke learning platform built around AI-powered search, a generative AI tutor and live engagement dashboards, shipped to MVP in 14 weeks and now used by 5+ enterprise customers. ![Consultancy session](https://www.doddledesign.co.uk/images/consultancy.webp) Partnerships ## Two partnerships, both pulling their weight. Whichever stack the work lands on, the same two partnerships sit underneath. OutSystems for low-code at enterprise scale, Anthropic for the AI tooling we use every day. Real partnerships, real production use. [How we build](https://www.doddledesign.co.uk/engineering) [Start an AI build](https://www.doddledesign.co.uk/contact) ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-logo.svg) Inside OutSystems estates ### Agent Workbench & Mentor, used in production. We use OutSystems Agent Workbench to build agentic AI features safely inside the platform, and Mentor to keep delivery sharp, code review, refactors, performance diagnostics, all without leaving OutSystems. Sales & Delivery Partner since 2021 ![Anthropic](https://www.doddledesign.co.uk/logos/claude-code.svg) Two years in production ### Claude Code & agents, day to day. Engineers, designers and product use Claude Code and purpose-built sub-agents to ship faster on modern stacks, with the same quality controls we apply to anything human-written. We work directly with Anthropic's tooling and stay close to the product as it evolves. Why trust us with AI ## We know the tech, and we know how to deploy it safely. Most AI projects stall in the gap between a clever demo and a system the business can rely on. Closing that gap is the job we do best. ### Two years building AI for real customers Not lab experiments. Live products, real users, and the scrutiny that comes with both. ### We choose the right tool for the job We work with all the major AI providers, including Claude, OpenAI, Gemini, Hugging Face, Perplexity, ElevenLabs, Vapi and OutSystems Agent Workbench. We pick based on the workload, the risk and the outcome. ### We deploy AI safely, with the right safety checks Testing, monitoring and guardrails are part of every build. The AI you launch on day one behaves the same way on day one hundred. [Start an AI build with us](https://www.doddledesign.co.uk/contact) [AI inside OutSystems →](https://www.doddledesign.co.uk/services/outsystems-delivery) [AI-Native Delivery →](https://www.doddledesign.co.uk/services/ai-native-delivery) ## Got an AI build of your own? Bring us the goal. We'll come back with what we'd build, roughly how long, and roughly what it'd cost. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See all work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /engineering|> --- title: "Engineering practice" url: "https://www.doddledesign.co.uk/engineering" section: "Studio" description: "How Doddle builds software that holds up. The delivery harness, the toolbelt we lean on, and how we help teams stand up the same practice in-house." publisher: "Doddle" --- Engineering practice # How we build software that holds up. A demo is easy these days. A product that survives real users, real edge cases, real model upgrades and a regulator looking over your shoulder is a different job. This page covers the harness, the toolbelt and the practice that close that gap on every build. [Talk to us about a build](https://www.doddledesign.co.uk/contact) [See the toolbelt](https://www.doddledesign.co.uk/engineering#toolbelt) The Doddle harness ## Nine pillars that turn a working build into something you can rely on. Building a working version of something is the easy half. Production-grade software needs the surrounding system - testing, evals, monitoring, code analysis, security and governance - wired in from day one rather than bolted on at the end. This is the part of the practice we're known for. ### Quality testing for AI Every AI feature is tested continuously. Bad answers caught before users see them; upgrading models becomes a measured decision, not a leap of faith. ### Automated testing Tests at every level, run automatically on every change. Nothing ships without passing them. ### Code review & analysis Code is checked automatically for quality, security and architecture compliance. AI-written code is held to the same bar as human-written code. ### Continuous delivery Every change flows through the same automated pipeline. Deployable in minutes; nothing skips the checks. ### Visibility in production Cost, performance and quality on live dashboards. Every interaction can be replayed for debugging. Nothing hidden. ### Security built in Security woven through delivery, secrets, dependencies, vulnerabilities, not bolted on at the end. ### Governance & guardrails Policies enforced, sensitive data handled properly, AI outputs checked. Designed for audit from day one. ### UX consistency A shared design system means the product stays coherent as it grows, visually and behaviourally. Accessibility checks are built in. ### Brand adherence Brand is codified in the system itself, colours, typography, voice. Every sprint stays on-brand, including the AI-assisted ones. The toolbelt ## What we reach for, and why. A few we lean on most in each category. The right pick depends on your data, your risk and your cost envelope. ### AI providers Claude, OpenAI and OutSystems. Open or self-hosted models when residency or cost demand it. ### Languages, frameworks & data TypeScript, Python and Next.js on Vercel. Supabase and Postgres with pgvector for the data layer, with other shapes where the job calls for them. ### Automation & orchestration OutSystems for workflows your team needs to own end to end. Vercel Workflows and n8n for cross-app automation across the tools you already use. ### Monitoring, logging & evals OpenTelemetry, Sentry and Grafana, with Langfuse tracing every AI feature. Continuous evals wired in from day one. ### Code analysis & review CodeQL and GitHub Advanced Security on every change. Same bar for human-written and AI-written code. ### CI/CD & infrastructure GitHub Actions and Terraform. Repeatable across environments, nothing skips the checks. Tools we work with The right tool for the job, not the trendiest one. A few of the names you'll see in our recent builds. - Claude - OpenAI - OutSystems - Google Gemini - Hugging Face - Next.js - React - Vercel - PostgreSQL + pgvector - Supabase - Langfuse - Sentry - and many more For teams going in-house ## Want your team to deliver AI in-house? Start with the harness. If your strategy is to grow AI capability internally, the harness is the part most teams underestimate. We stand it up with you - evals, governance, observability, code review pipelines, the lot - then your team owns delivery, with us on speed-dial when the harder moments come. [Read the approach](https://www.doddledesign.co.uk/insights/in-house-ai-not-alone) [Talk to us](https://www.doddledesign.co.uk/contact) ![In-house AI delivery, supported](https://www.doddledesign.co.uk/images/services-hero.jpg) ## Got a build that needs to hold up? Bring us the goal and the constraints. We'll come back with how we'd ship it, what tooling fits, and where the harness earns its keep on your stack. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /agents|> --- title: "Doddle for AI agents and developers" url: "https://www.doddledesign.co.uk/agents" section: "Studio" description: "Machine-readable Doddle. Markdown content negotiation on every page, llms.txt and llms-full.txt, the Doddle MCP server, and how to reach a human." publisher: "Doddle" --- For agents and developers # Doddle, in a format a machine can read. Every page on this site is available as markdown, the whole studio is summarised in llms.txt, and the same content is callable as tools over MCP. No keys, no sign-up, no rate limit worth worrying about. [Read the agent instructions](https://www.doddledesign.co.uk/agent-instructions.md) [View llms.txt](https://www.doddledesign.co.uk/llms.txt) Files ## Published at predictable URLs Each of these is a plain static file, cached for an hour and rebuilt on every deploy from the same content the pages use, so they never drift from what the site says. llms.txt The studio in one file. What we do, the four tracks, selected work with its numbers, the stack, and when to use us. llms-full.txt Every page on the site as markdown, concatenated. One fetch for the whole corpus. agent-instructions.md When to reach for Doddle, when not to, and how to call us. Mirrored at /.well-known/agent-instructions.md. sitemap.xml Every URL with a last modified date. Generated on each deploy from the same content the pages use. robots.txt Crawling rules. Nothing here blocks AI crawlers or answer engines. .well-known/mcp.json MCP discovery in the registry server.json format. The richer manifest is served live at /.well-known/mcp. Content negotiation ## Ask for markdown, get markdown Send an Accept header and any page returns markdown instead of HTML, with the right content type and a Vary header so a CDN never crosses the two. This follows the acceptmarkdown.com convention, q-values and all. Prefer a plain URL? The same file is addressable directly. Every page maps to /md/.md, and the home page is /md/index.md. A path that does not exist returns a real 404 with a markdown body pointing at the sitemap and llms.txt, so an agent can recover in one hop. A request we cannot represent returns 406 rather than quietly handing back the wrong format. Markdown for any page `curl -H "Accept: text/markdown" \ https://www.doddledesign.co.uk/work/iglu HTTP/2 200 content-type: text/markdown; charset=utf-8 vary: Accept, Accept-Encoding` Or fetch the file directly `curl https://www.doddledesign.co.uk/md/work/iglu.md` MCP server ## The same content, as tools A Model Context Protocol server over Streamable HTTP, so Claude, ChatGPT and anything else that speaks MCP can query the studio directly. Read-only, unauthenticated, stateless. Discovery documents live at /.well-known/mcp and /.well-known/mcp.json. - get_studio_overview - What Doddle is, the four service tracks, when to bring the studio in and when not to. Start here when a user asks who Doddle is or whether Doddle fits a job. - list_services - The four service tracks Doddle delivers, with who each one is for. Use when a user asks what Doddle can do or which track fits their situation. - get_service - Detail on one service track by slug. Use after list_services when the user wants specifics on a track. - list_case_studies - Projects Doddle has delivered, with the outcomes each produced. Filter by service track or tag. Use when a user asks whether Doddle has done something similar before, or asks for proof. - get_case_study - Full detail on one case study by slug, including outcomes, timescales and the client quote. - list_insights - Long-form articles the studio has published on AI delivery, OutSystems and migrations. Use when a user wants Doddle's position or thinking on a topic. - get_insight - Metadata and the canonical URL for one article by slug. Fetch the URL with `Accept: text/markdown` for the full text. - search_doddle - Keyword search across services, case studies and insights. Use for anything specific - a technology, a sector, a platform, a problem. - get_contact_details - How to reach the studio, and what to include in a first message. Use when the user wants to start a conversation, get a quote or book a call. Endpoint `https://www.doddledesign.co.uk/mcp` Claude Code `claude mcp add --transport http doddle https://www.doddledesign.co.uk/mcp` Handshake `curl -X POST https://www.doddledesign.co.uk/mcp \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize", "params":{"protocolVersion":"2025-06-18", "capabilities":{},"clientInfo":{"name":"demo","version":"1"}}}'` When to use us ## What we are the right answer for Good fit - A funded startup needs a production-grade AI product or a fixed-price MVP, not a prototype. - An organisation runs OutSystems and needs to build on it, or bring AI into the estate safely. - A team wants to move off OutSystems onto a modern stack, usually in 6 to 12 weeks. - A decision needs evidence before anyone commits, and a short paid engagement will answer it. Look elsewhere - Staff augmentation, or contractors by the head. - Programmes that need a large delivery organisation rather than a small senior team. - Decisions already made that only need signing off. ## Reached the end of what a file can tell you? Everything here is public. The parts that matter to your build are usually the ones a conversation answers faster. Bring the goal and the constraints. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See our work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /contact|> --- title: "Contact" url: "https://www.doddledesign.co.uk/contact" section: "Contact" description: "Tell us what you're trying to do. We'll come back with what we'd build, how long it'll take, and roughly what it'll cost." publisher: "Doddle" --- Contact # Tell us what you're trying to do. Bring us the goal, not the spec. We'll come back with what we'd build, what we wouldn't, and how long it'll take. Half an hour on the phone is the usual starting point. Send us a message ## A few lines is enough to get started. Tell us what you're trying to do and any context that helps. A goal, a deadline, a constraint - whatever you have. We don't need a spec. We'll write back personally within one working day. Your name* Email* Company What's this about?*Pick the closest fitAn AI buildAn OutSystems engagementA migration off OutSystemsA consultancy engagementSomething else Tell us what you're trying to do* Send Sent straight to our inbox. No third-party tracking on this form. Direct [hello@doddledesign.co.uk](mailto:hello@doddledesign.co.uk) We'll come back within one working day. By phone [01302 499 717](tel:+441302499717) UK office hours, Monday to Friday. Follow [LinkedIn ↗](https://www.linkedin.com/company/doddledesign) The fastest way to follow what we're shipping and writing. ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /privacy|> --- title: "Privacy" url: "https://www.doddledesign.co.uk/privacy" section: "Legal" description: "How Doddle Design Ltd collects, uses and protects personal data, your rights under UK GDPR, and how to contact us." publisher: "Doddle" --- Legal # Privacy notice How we handle personal data, why we hold it, and the rights you have over it. Last updated 8 June 2026. This notice explains how Doddle Design Ltd collects, uses and protects personal data when you visit [www.doddledesign.co.uk](https://www.doddledesign.co.uk), contact us, or work with us. It also sets out the rights you have under UK data protection law - the UK GDPR and the Data Protection Act 2018. ## Who we are Doddle Design Ltd is a company registered in England and Wales (company number 11560893). Our registered office is at Warren House, Bawtry Road, Doncaster, England, DN4 7NB. We are the data controller for the personal data described in this notice. For anything to do with your data, or this notice, email [hello@doddledesign.co.uk](mailto:hello@doddledesign.co.uk). ## The personal data we collect We collect the following. - **Enquiry details.** When you use the contact form or email us, we collect your name, email address, the company you mention, and whatever you put in your message. - **Usage data.** Aggregate, mostly anonymous data about how the site is used - pages viewed, rough location, device and browser type, and how you arrived. This comes from the analytics tools described below. - **Company-level visit data.** We use a service that estimates which organisations visit the site from their network information. This identifies companies, not named individuals. - **Technical logs.** Our hosting provider keeps standard server logs, including IP addresses, for security and to keep the site running. We don't ask for special category data (such as health, ethnicity or beliefs) and we'd ask you not to send it through the contact form. ## How we use it, and our lawful bases Under the UK GDPR we must have a lawful basis for using your data. We rely on the following. - **Legitimate interests.** To respond to your enquiry, run and improve the site, understand which organisations are interested in our work, keep proper business records, and protect the site from spam and abuse. We've weighed these interests against your rights and don't think they override them. - **Consent.** For non-essential analytics where consent is required. You can withdraw consent at any time, for example through your browser settings. - **Contract.** Where we're delivering work to you under an engagement, to manage that relationship. - **Legal obligation.** Where we have to keep records to meet our legal and accounting duties. ## Cookies and analytics We use a small number of cookies and similar technologies for analytics and visitor insight. We don't run advertising cookies or cross-site retargeting pixels. Our [cookie notice](https://www.doddledesign.co.uk/cookies) lists each one, what it does, and how to turn it off. ## Who we share it with We don't sell your data and we don't share it for anyone else's marketing. We do use a handful of trusted providers who process data on our behalf, under contract and only on our instructions. - **EmailJS.** Delivers contact-form messages to our inbox. It processes the name, email, company and message you submit. - **Google.** Google Analytics 4 for aggregate site analytics, and Google Ads to measure which campaigns lead to enquiries. - **Vercel.** Hosts the site and provides privacy-friendly, cookieless usage analytics. - **Leadfeeder (Dealfront).** Estimates which organisations visit the site. It works at company level, not on named individuals. We may also disclose data where the law requires it, or to establish or defend legal claims. ## Where your data is held Some of these providers are based outside the UK, including in the United States. Where personal data leaves the UK, we rely on the transfer protections recognised under UK law - an adequacy decision, or the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, so your data keeps an equivalent level of protection. ## How long we keep it We keep enquiry details for as long as we're in conversation with you and for a reasonable period afterwards, so we have a record of the contact, then we delete them. Analytics data is held in aggregate according to each provider's retention settings. We don't keep personal data for longer than we need it. ## How we protect it The site is served over an encrypted connection. We use reputable providers, keep access to enquiry data limited to the people who need it, and review our setup from time to time. No online service can be completely secure, but we take the handling of your data seriously. ## Your rights Under the UK GDPR you have the right to ask us to do the following. - Give you a copy of the personal data we hold about you. - Correct data that's wrong or incomplete. - Delete your data, where there's no reason to keep it. - Restrict or object to how we use it. - Receive certain data in a portable format, or have it sent to another provider. - Withdraw consent, where we relied on consent in the first place. To exercise any of these, email [hello@doddledesign.co.uk](mailto:hello@doddledesign.co.uk). We'll respond within one month. We don't make decisions about you by automated means alone. ## Complaints If you're unhappy with how we've handled your data, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner's Office at [ico.org.uk](https://ico.org.uk) or on 0303 123 1113. We're registered with the ICO under registration number [ICO registration number]. ## Children This site is aimed at businesses and isn't directed at children. We don't knowingly collect data about anyone under 16. ## Changes to this notice We may update this notice as our business or the law changes. The date at the top shows when it was last revised. ## Got a question about your data? Email us directly. We'll get back to you. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /terms|> --- title: "Terms" url: "https://www.doddledesign.co.uk/terms" section: "Legal" description: "The terms on which Doddle Design Ltd makes this website available, governed by the law of England and Wales." publisher: "Doddle" --- Legal # Terms of use The terms on which we make this website available. They don't cover paid work - every engagement has its own contract. Last updated 8 June 2026. This website is operated by Doddle Design Ltd, a company registered in England and Wales (company number 11560893), with its registered office at Warren House, Bawtry Road, Doncaster, England, DN4 7NB. By using the site you accept these terms. If you don't agree with them, please don't use the site. ## Using the site You may use this site for your own information and to find out about working with us. You agree not to misuse it - that means no attempting to gain unauthorised access, no introducing malicious code, no scraping or automated harvesting at a scale that disrupts the service, and nothing unlawful. ## Our content Unless we say otherwise, the text, design, graphics and code on this site belong to Doddle Design Ltd or our licensors and are protected by copyright and other rights. You may view and print pages for your own reference. You may not republish, sell, or present our material as your own without our written permission. ## Trademarks and client references Client names, logos, trademarks and case study material remain the property of their respective owners and appear here with permission or as fair reference to work we've delivered. Nothing on this site grants you any right to use them. ## No advice, no reliance The content here is for general information about Doddle and our services. It isn't professional, technical or legal advice, and you shouldn't treat it as a recommendation for your specific situation. Any actual work we do for you is governed by a separate written contract, and that contract, not this site, sets out what we're responsible for. ## Links to other sites Where we link to other websites, we do so for convenience. We don't control those sites and aren't responsible for their content or their privacy practices. ## Availability We aim to keep the site available and accurate, but we don't guarantee it will always be up to date, error-free, or uninterrupted. We may change, suspend or withdraw any part of it at any time without notice. ## Our liability We don't exclude or limit our liability where it would be unlawful to do so - that includes liability for death or personal injury caused by our negligence, and for fraud. Subject to that, we won't be liable for any loss or damage that arises from your use of, or inability to use, this site, or from relying on its content. Different terms apply to paid work and are set out in the relevant engagement contract. ## Governing law These terms, and any dispute arising from them, are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction. ## Changes to these terms We may update these terms from time to time. The date at the top shows when they were last revised, and your continued use of the site means you accept the current version. ## Contact Questions about these terms? Email [hello@doddledesign.co.uk](mailto:hello@doddledesign.co.uk). ## Got a question? Email us directly. We'll get back to you. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /cookies|> --- title: "Cookies" url: "https://www.doddledesign.co.uk/cookies" section: "Legal" description: "The cookies and similar technologies Doddle uses, what each one does, and how to turn them off." publisher: "Doddle" --- Legal # Cookie notice What we set, why we set it, and how to switch it off. No advertising cookies, no cross-site tracking. Last updated 8 June 2026. Cookies are small text files a website stores on your device. Similar technologies, like the analytics scripts we describe below, do much the same job. We use a deliberately small set, for analytics and visitor insight only. This notice sits alongside our [privacy notice](https://www.doddledesign.co.uk/privacy). ## How we use cookies We use them to understand, in aggregate, how the site is used so we can improve it, and to get a company-level sense of which organisations are interested in our work. We don't use them to advertise to you, to follow you across other sites, or to build a profile of you as an individual. ## The cookies we set - **Google Analytics 4.** Sets the cookies named _ga and _ga_* to tell visitors and sessions apart, so we can see how the site is used overall. These last up to two years. Provided by Google. - **Leadfeeder (Dealfront).** Sets a first-party cookie (_lfa) so it can recognise returning visits and estimate which organisation they came from. It works at company level, not on named individuals, and lasts up to two years. Provided by Dealfront. - **Vercel Analytics.** Privacy-friendly usage analytics from our hosting provider. It's cookieless - it doesn't store a cookie on your device or track you across other sites. ## Managing cookies You can block or delete cookies through your browser settings, and you can usually set your browser to warn you before one is stored. Blocking the cookies above won't stop the site working. We also honour the Global Privacy Control signal where your browser sends it. To opt out of Google Analytics specifically, you can install Google's [opt-out browser add-on](https://tools.google.com/dlpage/gaoptout). For more on managing cookies generally, [aboutcookies.org](https://www.aboutcookies.org) is a good plain-English guide. ## Changes to this notice If the cookies we use change, we'll update this page. The date at the top shows when it was last revised. ## Got a question? Email us directly. We'll get back to you. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /anti-slavery|> --- title: "Modern Slavery and Human Trafficking Statement" url: "https://www.doddledesign.co.uk/anti-slavery" section: "Legal" description: "Doddle Design Ltd's statement on modern slavery and human trafficking, our policy and our commitments under the Modern Slavery Act 2015." publisher: "Doddle" --- Legal # Modern Slavery and Human Trafficking Statement Last updated 8 June 2026. Doddle Design Ltd - [www.doddledesign.co.uk](https://www.doddledesign.co.uk) This statement is made pursuant to section 54 of the Modern Slavery Act 2015 and sets out the steps Doddle Design Ltd takes to prevent modern slavery and human trafficking in our business and supply chains. It relates to the financial year ending 30 September 2026. This statement is reviewed, updated, and republished annually for each financial year. At Doddle Design Ltd, we are fully committed to preventing slavery and human trafficking in all areas of our business and supply chains. We recognise our responsibilities under the Modern Slavery Act 2015 and uphold the highest standards of ethical conduct in all our operations. ## Our business Doddle Design Ltd provides digital services to clients across the UK. We operate from the UK with a small team and a limited supply chain, primarily comprising UK-based contractors and technology service providers. ## Our policy We operate a zero-tolerance policy towards modern slavery, servitude, forced or compulsory labour, and human trafficking. We are committed to acting ethically, transparently, and with integrity in all our business dealings. ## Our commitments include - Carrying out reasonable due diligence on suppliers, partners, and contractors to ensure alignment with our anti-slavery principles. - Ensuring all employees and contractors engaged by Doddle Design Ltd are subject to UK employment laws, including rights to fair pay and working conditions. - Communicating our anti-slavery stance to suppliers, contractors, and business partners to promote awareness and compliance. - Providing a clear process for reporting concerns relating to slavery or human trafficking, with full protection for whistleblowers. - Regularly reviewing and updating our policies to ensure continued compliance with the Modern Slavery Act 2015. ## Supply chain transparency While our direct supply chain is limited, primarily involving software services, hardware procurement, and professional services, we remain vigilant. We expect all third parties we work with to maintain their own robust anti-slavery policies and procedures. ## Training and awareness Given the nature and size of our business, formal training is proportionate to risk. However, our team is made aware of the signs of modern slavery and the importance of raising concerns promptly. ## Responsibility and review Responsibility for ensuring compliance with this statement rests with the company's Directors. This statement is reviewed annually and updated as needed. ## Reporting concerns If any individual has concerns regarding slavery or human trafficking linked to Doddle Design Ltd's business or supply chain, they should report it immediately via [info@doddledesign.co.uk](mailto:info@doddledesign.co.uk). All reports are taken seriously and handled in confidence. ## Approval This statement relates to the financial year ending 30 September 2026. It was approved by the Board of Directors of Doddle Design Ltd on 15 October 2025 and will be reviewed and republished annually. Signed for and on behalf of Doddle Design Ltd Thomas Ciullo, Director, Doddle Design Ltd Date - 15 October 2025 ## Questions about this? Email us directly. We'll get back to you. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /services/outsystems-delivery|> --- title: "OutSystems Delivery" url: "https://www.doddledesign.co.uk/services/outsystems-delivery" section: "Services" description: "Low-code speed inside enterprise guardrails. Greenfield builds, business process automation, workflows and mobile, with modern AI capability brought safely into the estate." publisher: "Doddle" --- [What we do](https://www.doddledesign.co.uk/services) OutSystems Delivery Other services[AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) [Consultancy Services](https://www.doddledesign.co.uk/services/consultancy-services) ![OutSystems](https://www.doddledesign.co.uk/logos/outsystems-icon.png) Build # OutSystems Delivery Enterprise applications built at OutSystems speed, with the governance and scale you'd expect from the platform. Eighteen years on OutSystems, Sales & Delivery Partner since 2021, and one of the first partners in Europe to deliver on ODC. [Let's talk](https://www.doddledesign.co.uk/contact) [What's included](https://www.doddledesign.co.uk/services/outsystems-delivery#inclusions) Our OutSystems practice ## A Gartner Leader. We've shipped on it for years. OutSystems is consistently ranked a Leader in the Gartner Magic Quadrant, and for good reason. If you need to balance rapid delivery with enterprise governance and rock-solid workflows, it's hard to look further. In recent months its cloud-native ODC platform and Agent Workbench have pushed it into a space few others occupy. We work as a delivery team alongside yours, or as the delivery team where you don't have one. Senior people on the keyboard, weekly demos, and production discipline applied from day one. Our OutSystems credentials ## A practice OutSystems and their customers trust. Long history with the platform, a working relationship with OutSystems themselves, and a project track record to back it up. 18+ years Founders working with OutSystems since the platform's early days. Partner since 2021 OutSystems Sales & Delivery Partner. First in EU & UK Partner to deliver on ODC - three live builds inside six months of launch. EAP regulars Frequent collaborators on OutSystems' Early Access Programme initiatives. 22 × 5-star Reviews across 15 OutSystems projects shipped to date. Accredited with![OutSystems Sales & Delivery Partner](https://www.doddledesign.co.uk/logos/outsystems-logo.svg) Selected OutSystems work ## Three recent platforms, shipped on OutSystems. [See all work →](https://www.doddledesign.co.uk/work) ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise - a supplier payments platform for the UK's largest cruise and ski agent. 84% auto-match on incoming statement lines and £350m+ processed in year one, with ROI inside 12 months. ![RailX card](https://www.doddledesign.co.uk/images/work/railx/railx-card-image.webp) OutSystems Delivery Logistics / Sustainability ### RailX A digital marketplace that makes sustainable rail freight bookable like a passenger journey. 100+ customers on the platform, 20,000 container movements, and over 300 tonnes of CO₂ saved. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack - an engineering change request portal for one of the UK's major rolling stock owners. 300 train units covered, built by 10 engineers in 3 months. ![IGLU](https://www.doddledesign.co.uk/logos/iglu.png) > “PayWise has completely transformed how we manage supplier payments, with real-time visibility of our cash position. The return on investment has been outstanding.” Lorna VincentCFO, IGLURead the case study → What's included ## The breadth of OutSystems work we run. [AI features we've shipped →](https://www.doddledesign.co.uk/built-with-ai) ### Greenfield product builds End-to-end application delivery inside your OutSystems environment, to your architecture standards. ### Business process & workflows Process automation, case management, approvals, document workflows, the kind of thick business logic OutSystems is genuinely good at. ### Cross-platform mobile Mobile apps that share the same backend, business logic, and audit posture as the web apps they sit alongside, without a separate native team. ### AI inside OutSystems Agentic Systems Engineering on the platform: Agent Workbench for reasoning agents, next-generation Mentor in the IDE, and the Enterprise Context Graph for governance across the estate. Production-grade AI without leaving OutSystems. ### Augmenting existing apps Extending what you already have, new modules, integrations, UX modernisation, performance work. ### Architecture reviews Independent reads on existing OutSystems builds, scoped as part of a delivery engagement. For standalone reviews across multiple platforms or pre-decision contexts, see Consultancy. AI in your OutSystems estate ## Build AI on the platform. Use a different stack only when you actually need to. OutSystems builds AI directly into the platform now. For most AI work inside an OutSystems estate, that's where we build it. Once in a while a piece of AI work needs tools the platform wasn't designed for. When that happens we build that piece separately and connect it back. Same governance, same audit trail, same team. On the platform ### OutSystems is now a proper AI development platform. Agent Workbench for agents that reason and act, the new Mentor in the IDE for conversational development, and the Enterprise Context Graph for governance across the estate. For most AI work, this is where we build, on the platform you already trust. OutSystems is open about it too. Claude Code, OpenAI Codex and Cursor all work inside the same Context Graph governance. When something needs a different stack ### A small piece, built separately, connected back in. Some AI work needs specific tools the platform wasn't built for, such as real-time optimisation, custom machine learning, or specialised compute. We build that part in modern infrastructure and connect it to OutSystems through APIs. The platform stays the place where the application lives. RailX is a good example of this in practice. [Read the RailX case study →](https://www.doddledesign.co.uk/work/railx) How we work ## Same disciplines, low-code or not. ### Senior on the keyboard Our OutSystems work is led by people with eighteen years on the platform. The people you meet are the people writing the modules. ### Production discipline Automated tests, environment parity, observability and code review applied inside OutSystems the same way we'd apply them on any stack. ### Partnership-grade work Early access to OutSystems' Early Access Programme initiatives, ODC pre-release builds, and direct engagement with the platform team - so what we ship on your estate stays ahead of where the platform is going. Is this the right track? ## Honest about when to pick this one. Good fit ### Right for you if… - Organisations with a meaningful OutSystems investment. - Regulated industries where standardisation and governance matter. - Internal applications, portals, and process tools at enterprise scale. - Cross-platform mobile apps that share a backend with the web. - Teams who'd benefit from senior independent delivery alongside their own. [Talk to us about OutSystems](https://www.doddledesign.co.uk/contact) Not the move ### Look elsewhere if… - Funded startups looking for a lean MVP on a contemporary stack. - Teams whose context has moved beyond the platform. - When the underlying question is whether to invest further at all. Probably a better fit [AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) [Consultancy](https://www.doddledesign.co.uk/services/consultancy-services) Common questions ## The things teams ask before they bring us in. If the question you have isn't here, send it across. We'll answer it honestly and add it to this list. Do we need to be on the latest OutSystems version? No. We work across OutSystems 11 and ODC. We'll meet you wherever you are, and we'll say honestly if a version upgrade would unlock something worth doing. Can OutSystems handle AI properly now, or do you always build it separately? It can, and we use it. OutSystems is now a real AI development platform - Agent Workbench for agents, the new Mentor in the IDE for conversational development, and the Enterprise Context Graph for governance across the estate. Claude Code, OpenAI Codex and Cursor all work inside that governance too, which is unusual and good. For most AI work inside an OutSystems estate, that's where we build. If a specific piece of AI work needs tools the platform wasn't designed for - real-time optimisation, custom machine learning, specialist compute - we build that piece separately and connect it back. It's a choice we make case by case, not a default. Are you really equally fluent in AI-native and OutSystems? Yes, and the two are converging. OutSystems is now an AI platform; AI-native shops increasingly need governance and architectural coherence. Doddle sits in the middle on purpose - eighteen years on the platform on one side, two years of Claude Code in daily production use across the team on the other, and we ship both kinds of work every week. Where the answer is hybrid, we run both ends in-house. How do you work with our existing OutSystems team? Whatever shape fits. Alongside as senior delivery support, leading a workstream, or providing independent architecture review. We don't try to take over a team that's already running well. What if OutSystems is the wrong tool for our project? We'll tell you. We've delivered AI-native and modern engineering work for years now, so the alternative isn't theoretical for us. If a migration's the right answer, we'll talk you through that too. Are you really an OutSystems partner? Yes. Sales and Delivery Partner since 2021, with eighteen years of enterprise OutSystems projects behind us across travel, transport, fintech, education and the public sector. Partner status formalised what we'd been doing for years. ## OutSystems engagement in mind? Whether it's a single application or an ongoing partnership, we'll start with the smallest scope that makes the next decision easier. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Talk to us](https://www.doddledesign.co.uk/contact) [See OutSystems work](https://www.doddledesign.co.uk/work) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /services/ai-native-delivery|> --- title: "AI-Native Delivery" url: "https://www.doddledesign.co.uk/services/ai-native-delivery" section: "Services" description: "Production-grade AI products built on modern stacks, with our proprietary delivery harness underneath. Includes fixed-price MVPs for funded startups." publisher: "Doddle" --- [What we do](https://www.doddledesign.co.uk/services) AI-Native Delivery Other services[OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) [Consultancy Services](https://www.doddledesign.co.uk/services/consultancy-services) ![Claude](https://www.doddledesign.co.uk/logos/claude-code-icon.svg) Build # AI-Native Delivery Building an AI prototype is easy these days. Building one that holds up under real use is a different job. We design, build and run AI products end-to-end, with the testing, monitoring and safety checks that turn a clever demo into software you can rely on. [Let's talk](https://www.doddledesign.co.uk/contact) [What we build with AI](https://www.doddledesign.co.uk/services/ai-native-delivery#capabilities) ![Engineers working on an AI build](https://www.doddledesign.co.uk/images/ai-product.webp) What this is ## From prompt to production-grade. Software development shifted under everyone's feet this past year. Customers expect better products, AI features as standard, and delivery measured in days. Teams are spinning up MVPs and demos in tools like Lovable or Builder - and for proving an idea, that's brilliant. A sharp demo and a product you can put in front of real users are different things. Getting from one to the other takes real engineering - Claude in the loop, everything under version control, a proper delivery pipeline and testing - and twenty years of carrying a prompt all the way to production. How we deploy AI safely ## How we keep AI honest in production. Most AI projects stall in the gap between a clever demo and a system the business can rely on. The four pillars below are the ones that matter most for AI work - the rest of the harness sits underneath. ### Quality testing for AI Every AI feature is tested continuously. Bad answers caught before users see them; upgrading models becomes a measured decision, not a leap of faith. ### Visibility in production Cost, performance and quality on live dashboards. Every interaction can be replayed for debugging. Nothing hidden. ### Governance & guardrails Policies enforced, sensitive data handled properly, AI outputs checked. Designed for audit from day one. ### Continuous delivery Every change flows through the same automated pipeline. Deployable in minutes; nothing skips the checks. [Same harness underneath everything we build - see the full Engineering practice→](https://www.doddledesign.co.uk/engineering) Capabilities ## The AI patterns we build often. [See what we've built with AI →](https://www.doddledesign.co.uk/built-with-ai) ### Knowledge assistants & document AI AI that answers questions using your own content, accurately, with citations users can verify, at scale. ### AI assistants & copilots In-app helpers that understand what the user is trying to do, find the right information, and stay within the rules you set. ### Natural-language analytics Ask a question in plain English, get a chart. Safe to run on real data, with accuracy you can measure. ### Document processing Turn messy inputs into structured, audit-ready data, extracting, classifying, summarising, enriching. ### Agentic workflows AI that does work end-to-end, multi-step automation that knows when to stop and when to ask for help. ### Tuning & quality testing We tune the model where it pays off, and test every AI feature continuously, so quality doesn't drift over time. How a build runs ## Four phases. Most builds inside three months. ### Discovery & architecture 1–2 weeks What to build, which models, which guardrails, and what success looks like. Comes out as a buildable plan, not a slide deck. ### Build 3–8 weeks typically The product itself, with testing, monitoring and deployment automation built in from day one, not bolted on later. ### Hardening 1–2 weeks Cost control, security review, regression testing, accessibility checks, the polish that turns a working build into something you'd actually launch. ### Launch & iterate ongoing Live, instrumented, and ready to learn from real users. We stay close for as long as it's useful, and step back when it isn't. For funded startups ## Startup MVPs in 3–6 weeks, fixed price. For funded startups, a tighter version of the above as a fixed-price MVP. You get a real product you can demo, hand to users, and continue building on, with the same harness underneath, so it can scale into a production platform without a rewrite. [Scope an MVP](https://www.doddledesign.co.uk/contact) For enterprise teams ## Stand up AI delivery in your own team. For teams whose strategy is to own AI capability in-house. We build the harness alongside your engineers - evals, observability, governance, code review - and ship the first product together. Then your team owns delivery, with us on speed-dial for the harder moments. [Read the approach](https://www.doddledesign.co.uk/insights/in-house-ai-not-alone) [Start a conversation](https://www.doddledesign.co.uk/contact) Tools we work with The right tool for the job, not the trendiest one. A few of the names you'll see in our recent builds. - Claude - OpenAI - OutSystems - Google Gemini - Hugging Face - Next.js - React - Vercel - PostgreSQL + pgvector - Supabase - Langfuse - Sentry - and many more Is this the right track? ## Honest about when to pick this one. Good fit ### Right for you if… - Funded startups building toward product-market fit. - Product teams building on modern stacks. - Enterprise teams building AI products outside the core platform. - Anyone who values pace and adaptability over enterprise standardisation. [Start an AI build](https://www.doddledesign.co.uk/contact) Not the move ### Look elsewhere if… - Heavily governed estates that mandate a specific low-code platform. - Teams whose underlying platform is the actual problem. - When the question is 'should we even build this?' rather than 'how?' Probably a better fit [OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) [Consultancy](https://www.doddledesign.co.uk/services/consultancy-services) Common questions ## The things teams ask before they kick off an AI build. Quick answers to the questions we hear every week. Yours not here? Tell us and we'll add it. How do you decide which model to use? In discovery, against the actual workload. We benchmark a shortlist on your data, measure quality and cost, and pick the smallest model that does the job. We don't marry one provider. How do you stop the AI from hallucinating in production? Retrieval grounding, output validation, and continuous evals running against a labelled set. The harness fails a deploy if scores drop below the bar we set with you. It's not magic, it's the same engineering discipline we apply to everything else. Do we own the code, the prompts, and the evals? Yes. Everything we build lives in your repo, including prompts and eval suites. We're not building a black box you can only run through us. Can you work alongside our existing team? Often. We slot in beside in-house engineers, especially on the AI-specific pieces. We're also happy to lead end-to-end where that's the cleaner shape. We're an OutSystems shop. Do we have to leave the platform to do AI properly? No, and we'd usually advise against it. OutSystems' Agentic Systems Engineering, Agent Workbench, Mentor and the Enterprise Context Graph, makes the platform a real AI environment, and the open ecosystem means Claude Code, OpenAI Codex and Cursor all run inside the same governance model. We build there first. For workloads that genuinely need a specific stack - real-time optimisation, niche ML, custom compute - we put a service alongside and the Context Graph still governs across both. What does an MVP cost and how long does it take? For funded startups, fixed-price MVPs run 3–6 weeks. Exact price depends on scope, but it's usually similar to a single experienced engineer for that period. Longer programmes are time-and-materials, against a discovery plan. ## Got an AI build in mind? Bring us the goal. We'll come back with what we'd build, roughly how long, and roughly what it'd cost. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) [See an AI build](https://www.doddledesign.co.uk/work/boardly) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /services/outsystems-migrations|> --- title: "Migrate away from OutSystems" url: "https://www.doddledesign.co.uk/services/outsystems-migrations" section: "Services" description: "Move applications off OutSystems onto a modern stack in 6 to 12 weeks, with a relatively fixed cost tied to your application object footprint. Lower run cost, no per-user or per-app licence escalation, and a stack your team can extend." publisher: "Doddle" --- [What we do](https://www.doddledesign.co.uk/services) Migrate away from OutSystems Other services[OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [Consultancy Services](https://www.doddledesign.co.uk/services/consultancy-services) Re-platform # Migrate away from OutSystems. When OutSystems is no longer the right fit, we move applications to a modern stack in 6 to 12 weeks. You keep your governance, your monitoring and your operational confidence, and you pick up modern AI capability on the way. [Let's discuss](https://www.doddledesign.co.uk/contact) [Size a migration](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) ![A measured migration in progress](https://www.doddledesign.co.uk/images/outsystems-migrations.jpg) Why now ## Great platform. Sometimes the wrong fit. OutSystems is excellent for enterprise. We'd know - 18+ years on the platform, still shipping on it every week. Sometimes it stops being the right fit. Licence economics shift, strategy changes, an acquisition forces a replatform, or you want to go AI-Native on a more open stack. That's fine - everyone adapts to a changing landscape. The question for a business leader is how you move without giving up the control and assurance enterprise low-code gave you. And where you even start. The team best placed to help sits between the two worlds. Deep OutSystems experience, a growing portfolio of AI-Native builds and migrations. That's us. Decision framework ### Read where OutSystems still wins, and where it doesn't. A short framework for weighing whether OutSystems still fits your team in 2026, written by people who deliver on the platform every week. [Read the framework](https://www.doddledesign.co.uk/insights/outsystems-2026) [Let's discuss](https://www.doddledesign.co.uk/contact) [Try the ROI calculator](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) What to expect ## The worries teams ask us about, and the shape of the bill. The questions we get asked most - how the move actually runs, and what changes in your run cost on the other side. ### No source code or subscription change We scope from your application catalogue and a few interviews. Your OutSystems environment keeps running until you tell us the new one is ready, and your subscription only ends when you decide it should. ### Large estates move incrementally Hundreds of applications? We don't move them in one go. We pick the cleanest first, run it in production alongside the rest, then move the next in batches that suit your roadmap. ### Data migration is handled, not hand-waved The trickiest part of any move. We map data in discovery, build the new copy alongside the live one with reconciliation reports as we go, and only switch when the numbers line up. The old environment stays warm during cutover. ### Predictable run cost Run cost on the new stack barely moves with the number of applications or the number of users. Add another tenant or another mobile feature and the bill stays roughly flat. ### Every environment, included Dev, QA, pre-prod, prod, sandbox - whatever shape your team works in. The new stack doesn't charge a tier per environment, so we can match what you already have. ### Refresh, not just relocate Migration is the natural moment to retire the features no one uses, fix the UX that's been bugging everyone, and add the AI capabilities that didn't fit before. We pick those calls together in discovery. ### Quick to iterate on the other side On a modern stack with our delivery setup, teams iterate quickly with the same controls in place. Run cost goes down and ongoing delivery cost moves with it. Sizing ## Rough numbers, in under a minute. Pick the bands closest to your estate to see the cost shape, the run cost on the new stack, and the saving against what you're paying today. Discovery confirms the real numbers and locks the price. Migration sizing ### How big is your estate? Pick the bands that fit. We'll show the cost shape, the run cost on the new stack, and the saving against what you're paying today. Discovery confirms the real numbers and locks the price. Application objects (AO) 1503006008001,000+ Monthly active users 1k2k5k10k+ Current annual OutSystems spend I don't know<£50k£50–100k£100–500k£500k+ Your current OutSystems annual licence £56k estimated Pick a band on the left for a number closer to yours. Migration cost £50k–£70k Fixed-price after discovery Duration 6 weeks Users live throughout Annual run cost £3.3k–£5.3k All environments included Estimated annual saving £52k/yrpayback in 14 months Run cost on the new stack barely moves with more apps or users, so the saving compounds as you grow. Bands are indicative. Discovery runs from your application catalogue and a few interviews, so we don't need source code or touch your subscription to scope it. Not sure yet? ### Start with a one-week Estate audit. A lighter, earlier-stage engagement than Discovery. We look at your estate, map the art of the possible on a modern stack, and give you a written recommendation on whether a migration is the right next step at all. No source-code access required, and the audit fee is credited against Discovery if you proceed. [Book an Estate audit](https://www.doddledesign.co.uk/contact) Proof points ## What recent migrations have looked like. 300AO Migrated in six weeks. Small enterprise estate. 600AO Migrated in ten weeks. Mid-size estate, multi-team. 2weeks Fixed-price discovery. No source-code access needed. Why choose Doddle ## A senior team that knows the platform you're moving off. We've shipped migrations off OutSystems, and we still build on the platform. So the advice you get is neutral on the platform question, from a team that already knows what you're working with. ![Finbridge Global](https://www.doddledesign.co.uk/logos/finbridge-global.png) > “We started with Doddle on OutSystems, fast MVP, fast iteration. As we matured, they helped us move onto a full AI-native stack. The speed, the thinking, and the care in execution have been exceptional.” Barbara GottardiCEO, Finbridge GlobalRead the case study → ### 18+ years on the OutSystems platform We know what you're moving off, what you'll miss, what you won't, and what to replace it with. Sales & Delivery Partner since 2021. ### Two-plus years building with AI in production One of the things you pick up on the modern stack is native AI capability. We've been shipping production AI for real users for years, not learning on yours. ### A repeatable migration playbook Discovery, parallel build, cutover. Done end-to-end multiple times, with users on a working application throughout. Partnerships![OutSystems Sales & Delivery Partner](https://www.doddledesign.co.uk/logos/outsystems-logo.svg) ![Anthropic Claude](https://www.doddledesign.co.uk/logos/claude-code.svg) What moves across ## Every OutSystems pattern has a modern equivalent. We start by re-implementing what already works, beat for beat. Then we use the new stack to take it further, where it earns the change. Below is the surface area we cover by default, on O11 or ODC. Your applications land on a standard repository you own, with no platform licence and nothing locked behind a vendor. ### Workflows & BPT Approvals, case handling, long-running business processes. Rebuilt on modern workflow engines that keep the same behaviour and stay visible end to end. ### Timers & scheduled jobs Background work moves to standard infrastructure. Reliable, easy for your team to watch and extend. ### Client & server logic Clean separation between UI and the systems behind it. The two can evolve independently after the move. ### C# extensions & Forge Custom extensions and Forge component logic come across as first-class code. Easier to test, easier to share, no longer tied to platform internals. ### Mobile & PWA Native mobile and mobile-first PWA flows rebuilt with modern frameworks. Push, offline and biometrics handled by mature libraries. ### SSO, identity & roles Existing SSO, role models and audit trails preserved. We integrate with whichever IdP you already run. ### JavaScript & front-end Custom JS, screen logic and bespoke UI patterns re-implemented in modern frameworks, with a design-system baseline so the experience comes through cleaner. ### Data & integrations Existing data stores, REST and SOAP integrations, and ETL flows migrated in parallel and reconciled end-to-end before cutover. ### AI that does work end-to-end (new) A newer pattern that fits the modern stack naturally - AI that completes multi-step tasks on its own, under the same governance you'd apply anywhere else. Included at no extra cost. Migrations run from OutSystems 11 or ODC. Co-existence is supported during the cutover window, so users stay on a working application throughout. Why migrate with Doddle ## What you don't lose when you move. The thing teams worry about losing when they move off OutSystems is usually the stuff the platform handled silently in the background. The four pillars below cover the worries we hear most often - the rest of the practice sits underneath. ### Automated testing Tests at every level, run automatically on every change. Nothing ships without passing them. ### Code review & analysis Code is checked automatically for quality, security and architecture compliance. AI-written code is held to the same bar as human-written code. ### Visibility in production Cost, performance and quality on live dashboards. Every interaction can be replayed for debugging. Nothing hidden. ### Security built in Security woven through delivery, secrets, dependencies, vulnerabilities, not bolted on at the end. [Same harness underneath everything we build - see the full Engineering practice→](https://www.doddledesign.co.uk/engineering) Our approach ## Four phases. Most migrations inside twelve weeks. Discovery is the only paid commitment up front. It runs against the application catalogue and a few interviews, so there's no need to grant code access or change your OutSystems subscription before you've seen a plan. 01 ### Discovery 2 weeks, paid The scoping engagement once you've decided to move. We work from your application catalogue, a few interviews, and a short data audit. No source-code access required. Output is a migration plan, a fixed price for the move itself, and the lift-vs-refresh call on each application. (If you're not yet sure migrating is the right answer, the one-week Estate audit above is the starting point.) 02 ### Migration 4 to 12 weeks Incremental delivery, with users always on a working application. We move things in sensible batches, modernising where it earns the change. Data migration runs in parallel, validated end-to-end before any user is asked to switch. 03 ### Cutover 1 week Quiet switch. SSO, integrations, scheduled jobs all migrated. The old OutSystems environment stays warm during co-existence, so rollback is cheap if it's ever needed. 04 ### Support & enhance Your call Shipping isn't the moment we vanish. Most teams keep us in for one of three flavours - a support retainer for when the unexpected happens, continued enhancement while your team builds confidence, or a small care plan that keeps the pipeline, monitoring and AI capability fresh. We're equally happy training your team to take the lot in-house. We say what we'd recommend, then we do whatever fits. [Let's discuss](https://www.doddledesign.co.uk/contact) Is this the right track? ## Honest about when to pick this one. Good fit ### Right for you if… - Teams whose context has shifted and OutSystems no longer fits. - Applications where AI ambitions need a different runtime. - Estates where AO-driven licence economics have changed the maths. - Teams who want to move without losing governance or observability. [Scope a migration](https://www.doddledesign.co.uk/contact) Not the move ### Look elsewhere if… - Estates where OutSystems is still earning its keep. We'd rather you stay. - Migrations driven by fashion rather than fit. - When the right answer is a hybrid estate, not a full move. Probably a better fit [OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [Consultancy](https://www.doddledesign.co.uk/services/consultancy-services) Common questions ## The things teams ask us before they start. If something here is missing, ask us. We'll answer honestly and add it to this list for the next person. Do you need access to our OutSystems source code to scope a migration? No. Discovery runs from your application catalogue and a few interviews. We don't need to touch your existing OutSystems subscription, environments or code base to give you a fixed price. You only cancel anything when you choose to, after the move is done. How big can an estate be? Can you handle very large ones? Yes. For very large estates we recommend an incremental approach - pick one application, migrate it cleanly, run it alongside the rest, then move the next. That keeps risk small and lets the new setup prove itself before you commit to the whole portfolio. Some of our biggest engagements have started that way. What about data migration? That's usually the hardest part. It is. We've done this enough times to have a sensible playbook - map the data in discovery, build a parallel copy that reconciles against the live one, then switch when the numbers match. The old environment stays warm during cutover, so if anything looks off we can step back without panic. Are you abandoning OutSystems as a partner? Not at all. We've been on the platform for 18+ years, became a Sales and Delivery Partner in 2021, and we still deliver on OutSystems every week. The honest answer is that the platform is excellent for some contexts and the wrong fit for others. When the fit has shifted, this is what we do. What happens after the migration ships? Whatever you want. Some teams take the lot in-house and we just check in. Some keep us on a small support retainer that maintains the platform, watches monitoring and rolls in AI updates. Some keep us delivering features as their team builds confidence. We say what we'd recommend, and we work to that. Can we migrate from both OutSystems 11 and ODC? Yes, both. We've migrated from O11 and from ODC. The approach is the same - work from the catalogue, plan the lift, run a parallel build, switch. ODC migrations tend to be slightly faster because the surface area is cleaner. ## Thinking about moving off? Tell us the application catalogue and what's prompted the question. We'll come back with a view on time, cost, and whether moving is actually the right call. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's discuss](https://www.doddledesign.co.uk/contact) [Size it first](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /services/consultancy-services|> --- title: "Consultancy Services" url: "https://www.doddledesign.co.uk/services/consultancy-services" section: "Services" description: "Short, paid engagements that produce a clear recommendation rather than code. For decision points where the answer matters more than the deck." publisher: "Doddle" --- [What we do](https://www.doddledesign.co.uk/services) Consultancy Services Other services[OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) Decide # Consultancy Services Short, paid engagements that produce a clear recommendation rather than code. For the moments where the answer matters more than the slides. [Let's talk](https://www.doddledesign.co.uk/contact) [What we cover](https://www.doddledesign.co.uk/services/consultancy-services#engagements) ![Consultancy session](https://www.doddledesign.co.uk/images/consultancy.webp) What this is ## Hard to know what step to take. It's noisy out there. Almost every week Claude ships something new, and workflow and automation tools are everywhere. Your people are building Lovable reports and drafting content with LLMs. Meanwhile the questions land on your desk - do we even need this, what stack lets us embrace AI properly, how do we balance innovation against stability and governance. We get it. If you're trying to make sense of what's out there, what actually fits, and what supports where you're heading, it helps to talk to people working with these technologies day in, day out. That's the judgement this buys you - before you commit to a build, a platform, or a direction. Engagements ## The questions we help answer. ### Architecture & build reviews Independent reads on existing systems, what's working, what isn't, what would cost most to leave as-is. Includes a written recommendation and pragmatic next steps. ### AI readiness Where AI would add real value in your business, where it wouldn't, and what foundations (data, governance, observability, people) need to be in place before you commit. ### Platform strategy OutSystems, modern stacks, or a sensible mix. An honest read on the trade-offs, costs, and risks across a multi-year horizon, informed by what we see across our client base. ### Pre-build discovery Scope, sequence, risk, and cost for a build you're considering. The output is a buildable plan, by us, by your own team, or by someone else. ### Migration assessments Does the fit still hold? Should you stay or move? What would moving actually cost, and what would the new shape look like? A clear recommendation, with the workings shown. How it works ## The shape of every engagement. ### Short and defined Typically 1–3 weeks per engagement. A fixed fee, a fixed deliverable, a known end date. ### Recommendation, not just analysis You'll get a clear view on what we'd do, not a deck full of options that hands the decision back to you. ### Shown working Conclusions are backed by analysis you can scrutinise. We bring stakeholders along so the answer is shared, not handed down. ### Credited Where it makes sense, the cost is credited against a subsequent build with us, but there's no obligation either way. Is this the right track? ## Honest about when to pick this one. Good fit ### Right for you if… - You're at a decision point, buy/build, migrate/stay, AI in/out. - The answer matters enough to invest in getting it right. - Internal opinions are split, or unsupported by evidence. - You want an independent read from a team that builds, not just advises. [Book a consultancy engagement](https://www.doddledesign.co.uk/contact) Not the move ### Look elsewhere if… - You already know what to build, and need to start now. - You need a long-term advisory relationship rather than a defined engagement. - You want someone to validate a decision you've already made - that's not what we do. Probably a better fit [AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [Migrate away from OutSystems](https://www.doddledesign.co.uk/services/outsystems-migrations) Common questions ## Things teams ask before booking a consultancy. Quick answers to the questions that come up most often. How much does a consultancy engagement cost? Most run between one and three weeks, with a fixed fee agreed up front. It varies with the scope and the number of stakeholders involved. We share a quote within a day of the first call. What do we get at the end? A short written recommendation we'll put our name to, backed by the analysis behind it. We present it to your team and answer questions. No 60-slide deck nobody reads. Can the cost be credited if we then build with you? Yes, where it makes sense. We'll credit the engagement against a subsequent build with us. There's no obligation to do that. The consultancy stands on its own. Will you recommend us not to build something? If that's the honest answer, yes. We've recommended teams pause projects, switch platforms, or hand a build to a different team. The relationship matters more than the next invoice. Can you advise on AI without us already having a use case? Yes. AI readiness work is exactly that - looking across your organisation for where AI would actually add value, where it wouldn't, and what foundations you'd need in place first. ## Bring us the question. Most consultancy starts with a 30-minute call to make sure we're the right people to answer it. If we're not, we'll say so. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/finbridge|> --- title: "Finbridge Global, case study" url: "https://www.doddledesign.co.uk/work/finbridge" section: "Work" description: "Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment." publisher: "Doddle" --- Case study · Fintech · 2023 → 2025 # Finbridge Global: from OutSystems estate to AI-native. Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![Finbridge Global hero](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-dashboard.webp) Client Finbridge Global Sector Fintech Engagement OutSystems Migrations · AI-Native Delivery Duration Original MVP in 10 weeks. Migration delivered as a follow-on engagement ## A platform that already worked, and was ready for what came next. Doddle originally built the Finbridge Global platform on OutSystems. The MVP went from concept to live in 10 weeks. In the years since, more than 300 organisations have used it and the platform helped Finbridge raise £500k in investment. The context then changed. The product roadmap had moved toward AI-native workflows, intelligent document processing, retrieval assistants, natural-language analytics. The cost and shape of building those inside the existing low-code estate no longer made sense. Finbridge wanted to move, but without disrupting users, breaking compliance, or running an open-ended programme. They came back to us for a fixed-scope, fixed-window migration onto a modern AI-native stack, and an honest answer on whether moving was actually the right call. 10 weeks Original MVP 300+ Organisations on platform £500k Investment generated ![Finbridge AI assistant, surfacing insights from fintech assessments and market data.](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-ai-assistant.webp) Finbridge's AI assistant, surfacing insights from fintech assessments and market data to help institutions make informed decisions. ## From OutSystems estate to AI-native platform. **AI document processing.** Documents land in the platform and come out classified, structured and ready to use, in minutes rather than days. Every extracted field links back to where it came from, so the audit trail is built in. **AI assistant with citations.** An in-app assistant that answers questions using the firm's own documents, with citations users can verify and a clear sense of when the platform is confident in its answer. **Natural-language analytics.** Ask a question in plain English, get a chart. Permissions are respected, the AI picks from a curated query set, and users can sanity-check the answer. **URL scraping & enrichment.** Point the platform at a web page. It pulls the content, tags it against the firm's own categories, and slots it into the right place. Controlled, predictable, no rogue scraping. **AI-powered data enrichment.** Records get filled in automatically, extra context, related signals, cross-references. Quality is measured continuously, so accuracy doesn't drift as the underlying AI changes. **Quality testing for AI.** Every AI feature is tested continuously. Bad answers are spotted before users see them. Upgrading to a new model is a measured decision, not a leap of faith. > “We started with Doddle on OutSystems, fast MVP, fast iteration. As we matured, they helped us move onto a full AI-native stack. The speed, the thinking, and the care in execution have been exceptional.” Barbara GottardiCEO, Finbridge Global ![How institutions and investors see your company on Finbridge.](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-profile.webp) Automatically build and share your finbridge Profile with investors and institutions. ## A platform the team can grow into. The application went live on the new stack on schedule. Users experienced the move as a UX refresh rather than a re-platform. Run cost dropped meaningfully. The AI features that had been the original motivation shipped iteratively in the months after launch, each one shippable independently, each measured. The team can now do things on the platform that weren't possible before. They'll also be the first to tell you that the result wasn't a verdict on OutSystems, it was the right answer for them, in their context, at this moment. MarketplaceOutSystemsMigrationRAGDocument AI More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ## Got a similar question on your platform? Most migrations start with a free 30-minute scoping conversation. We'll tell you straight whether moving is the right answer. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/iglu|> --- title: "IGLU, PayWise, case study" url: "https://www.doddledesign.co.uk/work/iglu" section: "Work" description: "PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate." publisher: "Doddle" --- Case study · Travel · Multi-phase # IGLU, PayWise: from spreadsheet to platform. PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![IGLU, PayWise hero](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) Client IGLU Sector Travel Engagement OutSystems Delivery Duration Scoped, designed and delivered over several months ## Supplier payments that scaled past the spreadsheets. IGLU is the UK's largest cruise and ski agent, operating Iglu Cruise, Iglu Ski and Planet Cruise. The business serves more than 250,000 customers a year, and behind the bookings sits a high-volume supplier payments process that had outgrown its tools. Reconciliation was manual. Statements arrived in different shapes. Cash visibility lagged. The finance team needed a platform that could process the volume, match the lines, and give them a live view of where the money actually was. 84% Auto-match rate £350m+ Payments processed (yr 1) < 12 months ROI ![PayWise dashboard showing the live cash position](https://www.doddledesign.co.uk/images/work/iglu/iglu-dashboard.webp) Live cash position across suppliers, replacing end-of-day reconciliation runs. ## PayWise, a purpose-built payments platform on OutSystems. **End-to-end statement workflow.** Import, normalise, match, reconcile, pay, one tool from supplier statement to settled payment. **High-volume automated matching.** Complex matching rules that hit a 90%+ pass rate on incoming statement lines. **Live cash position.** Real-time visibility of payment status, exposure, and supplier balances, no more end-of-day reconciliation surprises. **Payment search & tracking.** Finance can find any payment, in any state, in seconds. Audit trail captured for every change. **Automated reporting & exports.** Scheduled reports and data feeds, built to plug into the existing finance stack. **FTP / S3 integration.** Files in, files out, designed for the realities of legacy supplier integrations. > “PayWise has completely transformed how we manage supplier payments, real-time visibility of our cash position. The return on investment has been outstanding.” Lorna VincentCFO, IGLU ![Statement matching workspace inside PayWise](https://www.doddledesign.co.uk/images/work/iglu/iglu-statement-matching.webp) High-volume statement matching, hitting 84% auto-match on incoming lines. ## ROI inside twelve months. Within the first year, PayWise processed over 5,000 statements, handled more than 300,000 payment requests, and moved upwards of £350m in supplier payments. Auto-match landed at 84% of statement lines, the finance team's time moved from chasing reconciliation to higher-value work. PayWise continues to run inside IGLU's finance function and is iterated on as the business grows. PaymentsAutomationEnterpriseOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ## Got a finance workflow stuck in spreadsheets? The pattern is almost always the same, high-volume, rule-heavy, audit-sensitive work that someone is doing manually. Tell us the shape and we'll come back with how we'd build it. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/eversholt-rail|> --- title: "Eversholt Rail, OnTrack, case study" url: "https://www.doddledesign.co.uk/work/eversholt-rail" section: "Work" description: "OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals." publisher: "Doddle" --- Case study · Rail / Asset management · Recent # Eversholt Rail, OnTrack: change requests, audit-ready. OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ![Eversholt Rail, OnTrack hero](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) Client Eversholt Rail Sector Rail / Asset management Engagement OutSystems Delivery Duration 3 months delivery, designed for ongoing evolution ## Engineering change, with a paper trail you can actually rely on. Eversholt Rail is one of the UK's major rolling stock owners, they own and maintain fleets that move millions of passengers every day. Change requests against those fleets had grown up across email threads, spreadsheets, and bespoke trackers. The work was getting done. The audit position was getting harder. They needed a single portal where engineers, fleet teams, and external partners could raise, assess, approve and track change requests against fleets, units, and components, with the kind of audit trail a regulated operator needs. 300 Train units covered 3 months Delivery window 2 Engineers on the build ## OnTrack, a change request portal on OutSystems. **Flexible change request engine.** Configurable by type, scope and priority. Custom workflows route requests to the right people without reconfiguring the platform. **Fleet & asset metadata layer.** Fleets, units, competencies, roles, and engineers all modelled and connected, so a change request knows what it's actually changing. **SSO and granular permissions.** Identity tied to the existing estate. Access tightly scoped per role and per fleet. **Approval chain with rationale.** Every decision captured with the person, the time, and the reasoning, defensible under regulatory review. **Reporting dashboards.** Fleet insights, asset tracking, embodiment status, surfaced cleanly for both technical and business audiences. **Internal teams + external partners.** Designed to host engineers from across the partner network without compromising on access control. ## Faster change delivery, defensible audit posture. OnTrack runs as the single record of change across the relevant fleets. The team get faster cycles and full visibility. The regulator gets a clean audit record on demand. The platform is designed for ongoing evolution, new fleets, new partners, new change types, without re-engineering. PortalChange managementOutSystemsRegulated More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Boardly card](https://www.doddledesign.co.uk/images/work/boardly/boardly-hero.avif) AI-Native Delivery Talent ### Boardly Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ## Got a workflow that lives in spreadsheets and email? That's where most platform investments earn back their cost. Bring us the process. We'll come back with how we'd structure it. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/boardly|> --- title: "Boardly, case study" url: "https://www.doddledesign.co.uk/work/boardly" section: "Work" description: "Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since." publisher: "Doddle" --- Case study · Talent · Recent # Boardly: AI-first board recruitment, live in eight weeks. Boardly helps boards recruit Non-Executive Directors faster, using AI-assisted matching across experience, sector and behaviour. A two-developer team took it from idea to live MVP in 8 weeks, with 100+ NEDs onboarded since. ![Boardly hero](https://www.doddledesign.co.uk/images/work/boardly/boardly-dashboard.webp) Client Boardly Sector Talent Engagement AI-Native Delivery · OutSystems Delivery Duration MVP delivered in 8 weeks ## Board recruitment, rebuilt around fit, not keywords. Boardly came to us with a clear thesis - the way Non-Executive Director recruitment works hasn't moved in a generation. CV-driven, keyword-matched, and blind to the things boards actually care about, communication style, lived experience, cultural fit. They needed a feature-rich MVP covering the full journey from onboarding to hiring, with credibility tight enough for early investors and users. Eight weeks. No compromise on security, scalability or usability. 8 weeks MVP to launch 100+ NEDs onboarded 2 Developers ![Boardly dashboard and onboarding](https://www.doddledesign.co.uk/images/work/boardly/boardly-dashboard-2.webp) Match with the right NEDs faster, with AI-driven CV analysis and voice-based culture-fit interviews. ## An AI-driven platform built in eight weeks. **Voice-based culture-fit interviews.** AI-driven interviews that read communication style and cultural cues, not just what's said, how it's said. **CV summarisation.** Automated extraction of the experience and signals that actually matter to boards, surfaced where they help. **Intelligent matching.** An engine that weights experience, sector alignment and behavioural traits, not just keyword overlap. **End-to-end journey.** Onboarding, job posting, messaging, connection requests, payments, the full platform, not just the AI layer. **Cloud-native, modular.** Built to scale from the founding cohort to whatever comes next, modular architecture from day one. **Production-grade from launch.** Identity, audit, security and observability wired in, not a demo dressed up as a product. > “The Doddle team absolutely nailed it, turned an ambitious idea into a live, scalable product in just eight weeks.” Sandy WillisCEO, Boardly ![Boardly AI culture call](https://www.doddledesign.co.uk/images/work/boardly/boardly-ai-culture-call.webp) Boardly's AI culture call, providing insights beyond the CV to find the right fit for your board. ## Live in 8 weeks. 100+ NEDs within days. Boardly went live on schedule. Within days of launch, more than 100 Non-Executive Directors had joined the platform, early evidence of demand and a credible product to back the next funding conversation. The platform continues to evolve. Doddle remain Boardly's long-term build partner. AIVoice analysisMVPOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Building an AI-first product? Bring us the thesis. We'll come back with the architecture, the timeline, and the parts we'd rebuild from scratch versus reuse. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/railx|> --- title: "RailX, case study" url: "https://www.doddledesign.co.uk/work/railx" section: "Work" description: "RailX makes sustainable rail freight easier to quote, book and manage, with carbon savings and final-mile logistics built in. The platform has moved 20,000 containers for 100+ customers and saved over 300,000 kg of CO₂." publisher: "Doddle" --- Case study · Logistics / Sustainability · Recent # RailX: rail freight, bookable like a passenger train. RailX makes sustainable rail freight easier to quote, book and manage, with carbon savings and final-mile logistics built in. The platform has moved 20,000 containers for 100+ customers and saved over 300,000 kg of CO₂. ![RailX hero](https://www.doddledesign.co.uk/images/work/railx/railx-booking.webp) Client RailX Sector Logistics / Sustainability Engagement OutSystems Delivery Duration Agile delivery, modelled on the booking experiences users already know ## Rail freight, bookable like a passenger train. RailX set out to make sustainable rail freight as accessible as booking a passenger journey. Large logistics operators have always had the relationships to use rail. Smaller and mid-sized businesses haven't. The market was effectively closed to anyone without an existing freight team. They needed a digital marketplace with serious logistics infrastructure underneath, and a customer experience that didn't ask non-specialists to learn the industry to use it. 100+ Customers on the platform 20,000 Container movements 300,000+ KG CO₂ saved ![RailX carbon impact view, showing CO2 saved per booking](https://www.doddledesign.co.uk/images/work/railx/railx-impact.webp) Pledge-verified CO₂ saving on every booking, surfaced where buyers see it. ## A marketplace platform built on OutSystems. **Trainline-grade booking flow.** An interface modelled on the consumer booking experiences users already know, designed for buyers who aren't freight specialists. **Approved carbon calculator.** Developed in partnership with Pledge, every booking shows verifiable CO₂ savings versus road equivalents. **Port-to-door logistics.** Managed solutions that handle first- and final-mile delivery alongside the rail leg. **Real-time tracking.** Customers see the state of their freight without having to chase the operator. **Agile delivery.** Detailed scoping, data modelling and customer-journey analysis, built in sprints with the founding team alongside. **Process automation.** The operational backbone that connects bookings to operators, paperwork to compliance. > “Their innovative approach and deep understanding of our vision, we've created an ecosystem that is reshaping our industry.” Steve FreemanCo-Founder, RailX ![RailX freight tracking interface](https://www.doddledesign.co.uk/images/work/railx/railx-tracking.webp) Real-time tracking, port to door - customers stop chasing the operator. ## A platform reshaping how the industry works. RailX is in market, growing, and delivering measurable CO₂ reductions per booking. The platform combines logistics depth with a UX that opens the market to companies who'd never have used rail before. Doddle continue to work with the RailX team as their long-term build partner. MarketplaceSustainabilityLogisticsOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Building a marketplace? Marketplaces look simple from outside and are non-trivial inside. Bring us the model and we'll come back with what we'd build first, second, and never. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/cognomie|> --- title: "Cognomie, case study" url: "https://www.doddledesign.co.uk/work/cognomie" section: "Work" description: "Cognomie scales 1-to-1 mental fitness coaching across 50+ organisations, with automated coach matching, interactive assessments and integrated video, achieving an NPS of 95+ and a 50% to 80% uplift in mental fitness." publisher: "Doddle" --- Case study · Health & Wellbeing · Discovery to launch in 12 weeks # Cognomie: coaching that actually scales. Cognomie scales 1-to-1 mental fitness coaching across 50+ organisations, with automated coach matching, interactive assessments and integrated video, achieving an NPS of 95+ and a 50% to 80% uplift in mental fitness. ![Cognomie hero](https://www.doddledesign.co.uk/images/work/cognomie/cognomie-card.jpg) Client Cognomie Sector Health & Wellbeing Engagement OutSystems Delivery Duration Ongoing partnership since launch ## Scaling coaching without scaling the friction. Cognomie's offer is high-quality mental fitness coaching, and like most coaching businesses, the bottleneck was operational. Matching the right coach to the right client, juggling calendars, running a meaningful assessment, capturing outcomes, all done by hand, all hard to scale. They came to us needing to grow from a handful of clients to thousands without losing the personalisation that made their coaching work in the first place. Discovery to launch: 12 weeks. 50+ Organisations supported 95+ Net Promoter Score 50–80% Mental fitness uplift ![Cognosis assessment interface](https://www.doddledesign.co.uk/images/work/cognomie/cognomie-assessment.webp) Cognosis, the bespoke assessment that replaced static PDFs with an interactive scoring journey. ## A coaching platform on OutSystems. **Coach-client matching engine.** Automated matching across preferences, skills, experience and availability, replacing a spreadsheet that didn't scale. **Multi-platform booking.** Real-time calendar sync with multi-calendar and timezone handling. Native integration with Teams, Zoom, 8x8 and Google Meet. **Cognosis, bespoke assessment.** A mental fitness assessment with its own scoring framework, replacing static PDFs with an interactive digital report. **Back-office admin centre.** Operations team get the tools they need to run programmes, manage coaches and clients, and see what's happening. **Interactive digital report.** Clients get a live report they can engage with, not a flat PDF they read once and lose. **Agile delivery.** Built in sprints, with prototyping rounds focussed on the UX of a high-stakes personal product. > “Doddle's platform enabled us to extend vital support during the challenging winter and peak of the COVID crisis.” Tim KneenChief Commercial Officer, Cognomie ![Interactive mental fitness report](https://www.doddledesign.co.uk/images/work/cognomie/cognomie-report.webp) The live report clients return to - not a one-read PDF. ## 50+ organisations, 95+ NPS, real mental-fitness uplift. A year on from launch, Cognomie was supporting more than 50 organisations, with thousands of employees engaged and hundreds of coaches active on the platform. Clients reported 50–80% improvement in mental fitness scores. Net Promoter Score landed above 95. The platform continues to evolve with the business. WellbeingCoachingOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Building a service that needs to scale without losing the personal bit? Tell us the shape of the service. We'll come back with the platform that supports it, and the parts to leave alone. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/powrkidz|> --- title: "PowrKidz, case study" url: "https://www.doddledesign.co.uk/work/powrkidz" section: "Work" description: "PowrKidz gave primary-school teachers ready-to-run exercise sessions, live engagement tracking and personalised development plans, reaching 5,000 students across 20 schools in its first six months." publisher: "Doddle" --- Case study · Education / Wellbeing · 6-month launch cycle # PowrKidz: fitness, deployed across schools, with no install. PowrKidz gave primary-school teachers ready-to-run exercise sessions, live engagement tracking and personalised development plans, reaching 5,000 students across 20 schools in its first six months. ![PowrKidz hero](https://www.doddledesign.co.uk/images/work/powrkidz/powrkidz-hero.jpg) Client PowrKidz Sector Education / Wellbeing Engagement OutSystems Delivery Duration Built by a single Doddle developer, pivoted mid-project to add home workouts during the pandemic ## Primary-school fitness, deployed everywhere without an installer. PowrKidz set out to do something about the gap between what schools want to deliver on physical fitness and what they can actually run on the ground. The market exists. The barriers are practical, busy teachers, mixed devices, no IT budget for installs. They needed a platform that teachers could pick up and use in a session, that worked across whatever device the school had to hand, and that could roll out across schools quickly. Engaging for the students, evidence-based for the trust, and trivial to deploy. 20 Schools live (first 6 months) 5,000 Students supported 700 Teachers supported ![PowrKidz workout session in action](https://www.doddledesign.co.uk/images/work/powrkidz/powrkidz-workout.webp) PowrKidz workout sessions, designed for primary school kids and teachers, with live engagement tracking and personalised development plans. ## A web-based fitness platform on OutSystems. **App-like, no install.** Native-feeling experience over the web, works on whatever device the school has, no IT team needed. **Teacher-led sessions.** Structured fitness classes designed by specialists, runnable by any teacher with no specialist training. **Engagement & rewards.** Students see progress and feedback in real time, the bit that makes the difference between a class kids do and a class kids enjoy. **Live reporting.** Performance dashboards for teachers, trust-level reporting for the people who fund the programme. **Home workout pivot.** When COVID-19 closed classrooms, we pivoted mid-project to support remote workout assignments, built in days, kept the programme alive. **One developer, end to end.** Delivered by a single Doddle developer on OutSystems, proof that low-code can sustain a real product in the right hands. > “It helps teachers deliver really high-quality lessons in a really simple and effective way.” Matt FreestonCEO, The Learners Trust ![PowrKidz teacher dashboard](https://www.doddledesign.co.uk/images/work/powrkidz/powrkidz-reporting.webp) Teacher dashboard, surfacing class engagement and individual student development plans. ## 20 schools, 5,000 students, 6 months. Within six months of launch, PowrKidz was live in 20 schools, supporting 5,000 students and 700 teachers. Schools reported a measurable lift in engagement, and the trust gained personalised development data they'd never had before. EducationWeb appOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Building a programme that has to land in the real world? We're good at the kind of product that has to work for users with no training, on whatever device they have. Tell us the goal. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/ai-powered-lms|> --- title: "AI-powered LMS, case study" url: "https://www.doddledesign.co.uk/work/ai-powered-lms" section: "Work" description: "We replaced an off-the-shelf LMS for a global change-management business with a bespoke learning platform built around AI-powered search, a generative AI tutor and live engagement dashboards, shipped to MVP in 14 weeks and now used by 5+ enterprise customers." publisher: "Doddle" --- Case study · Professional services · Recent # AI-powered LMS: bespoke, in fourteen weeks. We replaced an off-the-shelf LMS for a global change-management business with a bespoke learning platform built around AI-powered search, a generative AI tutor and live engagement dashboards, shipped to MVP in 14 weeks and now used by 5+ enterprise customers. ![AI-powered LMS hero](https://www.doddledesign.co.uk/images/work/ai-powered-lms/ai-powered-lms-hero.webp) Client Global change-management leader (anonymised) Sector Professional services Engagement AI-Native Delivery · OutSystems Delivery Duration MVP delivered in 14 weeks, 2-week agile sprints ## Replacing an off-the-shelf LMS with something that actually fits. A global leader in change management came to us with a familiar problem - their off-the-shelf learning platform had stopped fitting the business. Content evolved faster than the platform could keep up. Personalisation was thin. Modern AI-driven discovery wasn't on the roadmap. They needed a bespoke replacement - an LMS that could host their library, support personalised learning journeys, and bring AI into the content experience, without burning a year to get there. 14 weeks MVP delivery 2 weeks Sprint cadence 5+ Enterprise Customers ![AI-powered LMS chat assistant, providing personalised learning support and recommendations.](https://www.doddledesign.co.uk/images/work/ai-powered-lms/ai-powered-lms-ai-assistant.webp) AI-powered LMS chat assistant, providing personalised learning support and recommendations to users, enhancing their learning experience and engagement. ## A bespoke AI-powered learning platform. **AI-powered problem search.** Users describe the problem they're facing. The platform finds the resources that match, not just the keywords. **Generative AI chat interface.** A conversational layer over the learning library, grounded in the client's own content, not the model's general knowledge. **Metadata mapping engine.** Content tagged and indexed automatically, so adding material doesn't mean weeks of taxonomy work. **Personalised learning journeys.** Structured paths from introductory to advanced, with personal progress pages users can actually navigate. **Real-time engagement dashboards.** Live viewers, minutes watched, ratings, reviews, visibility for the content team and the leadership above them. **Admin portal.** Content management, user administration, and utilisation monitoring in one place, built for the operating team that runs the platform day-to-day. > “Deciding to partner with Doddle was a great decision, we moved from an initial idea to a fully functioning product, ready for users, within only 14 weeks.” Founder & CEOFounder, Global change-management leader ## MVP in fourteen weeks. Ready for users. The platform was delivered as an MVP in 14 weeks, in 2-week agile sprints. It launched with the AI features live and the content team able to manage everything themselves. The engagement is anonymised at the client's request, the work and the outcomes are real. AILMSGenerative AIOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Outgrown the off-the-shelf platform? Bespoke isn't a romantic notion any more, it's often the cheaper, faster answer. Tell us where you're stuck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /work/payment-swap|> --- title: "Payment Swap, case study" url: "https://www.doddledesign.co.uk/work/payment-swap" section: "Work" description: "Payment Swap helps drivers find their next car by monthly payment, with digital finance approvals, a sub-20-minute collection flow and 100k+ cars listed across a 5-star Trustpilot-rated marketplace." publisher: "Doddle" --- Case study · Automotive / Fintech · Recent # Payment Swap: the car, in twenty minutes. Payment Swap helps drivers find their next car by monthly payment, with digital finance approvals, a sub-20-minute collection flow and 100k+ cars listed across a 5-star Trustpilot-rated marketplace. ![Payment Swap hero](https://www.doddledesign.co.uk/images/work/payment-swap/payment-swap-card.jpg) Client Payment Swap Sector Automotive / Fintech Engagement OutSystems Delivery Duration Concept to live beta on OutSystems ## Car buying without the haggle, the paperwork, or the wait. Buying a car mid-term is a slow, fragmented process built on paperwork and negotiation. Payment Swap's thesis was simple - that doesn't have to be true. Match by monthly payment, approve finance digitally, collect the car the same day. They needed a platform that wired together stock, finance approvals, and a consumer-grade buying experience, and that dealers and finance partners could plug into without friction. 100k+ cars for sale 20+ Finance partners integrated 5★ Star TrustPilot rating ![Change your car online with Payment Swap, the mid-term car-buying platform that matches drivers to vehicles by current monthly payment, with digital finance approvals and a sub-20-minute collection flow.](https://www.doddledesign.co.uk/images/work/payment-swap/payment-swap-hero-2.webp) Change your car online with Payment Swap ## A mid-term car-buying marketplace on OutSystems. **Match by monthly payment.** Drivers find a vehicle by what they're paying today, not by stock filters that don't map to their actual budget. **Digital finance approvals.** Finance applications, approvals and contracting handled in the flow, with the major providers integrated upfront. **Mobile-first consumer experience.** Built for the way people actually shop, phone in hand, on the bus, in the kitchen. **Live dealer stock.** Dealers upload directly. Stock stays current without manual sync. **Finance partners integrated.** Northridge Finance, DSG Financial Services and Aviva wired in to support the originations flow. **Sub-20-minute collection.** The platform exists for the moment after the click, the bit where most buying flows break down. > “The experience from start to finish was fantastic, and the consumer website is one of a kind.” Nigel FalkinerFounder & Sales Director, Payment Swap ![Change your car online with Payment Swap, the mid-term car-buying platform that matches drivers to vehicles by current monthly payment, with digital finance approvals and a sub-20-minute collection flow.](https://www.doddledesign.co.uk/images/work/payment-swap/payment-swap-hero.webp) Change your car online with Payment Swap ## Concept to live beta on a low-code stack. Payment Swap moved from concept to live beta on OutSystems, fast enough to test the model in market and iterate, structured enough to take on additional dealers and finance partners as the platform scales. MarketplaceFintechAutomotiveOutSystems More work ## Other things we've shipped. [See all work →](https://www.doddledesign.co.uk/work) ![Finbridge Global card](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-hero.webp) OutSystems Migrations Fintech ### Finbridge Global Doddle helped Finbridge Global launch its fintech marketplace on OutSystems in 10 weeks, then re-platformed it onto a modern AI-native stack as the product scaled to 300+ organisations and supported £500k in investment. ![IGLU, PayWise card](https://www.doddledesign.co.uk/images/work/iglu/iglu-hero.webp) OutSystems Delivery Travel ### IGLU, PayWise PayWise helped IGLU replace spreadsheet-heavy supplier payments with automated matching, clearer workflows and real-time cash visibility, processing over £350m in year one with an 84% auto-match rate. ![Eversholt Rail, OnTrack card](https://www.doddledesign.co.uk/images/work/eversholt-rail/eversholt-rail-card.jpg) OutSystems Delivery Rail / Asset management ### Eversholt Rail, OnTrack OnTrack helped Eversholt Rail replace fragmented change request tools with one audit-ready portal covering 300 train units, built by two senior engineers in three months and now used as the single source of truth for fleet approvals. ## Building a marketplace in a regulated category? Marketplaces with finance, regulation and partner integrations are exactly the shape we like. Tell us the model. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/hired-an-ai-guy|> --- title: "“We've just hired an AI guy” - the eight questions to ask next" url: "https://www.doddledesign.co.uk/insights/hired-an-ai-guy" section: "Insights" description: "Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like." published: "2026-08-07" publisher: "Doddle" --- Practice # “We've just hired an AI guy” - the eight questions to ask next 7 August 2026 8 min read Own the IP. Own the roadmap. Both are the right instinct. The trouble starts when the plan to get there is one enthusiastic person, a Copilot licence and a push straight to main. ![A single slender pillar carrying a wide plane alone, with a row of quiet supporting columns standing unused beside it - ambition resting on one point of support.](https://www.doddledesign.co.uk/images/insights/hired-an-ai-guy.webp) We've lost count of how many times we've heard a version of the same sentence this year. “We've just hired an AI guy who says he can build this.” Sometimes it's a new hire. Sometimes it's an existing developer who got enthusiastic. Either way the strategy behind it is sound - replace outsourced delivery and per-seat SaaS with products the business owns outright. We're not going to argue with that. It's the same argument we make to clients. What we'd push back on is the assumption underneath it, which is that building the thing and running the thing are the same job. They aren't, and the gap between them is where the cost lands, usually six to nine months later when the enthusiastic person is on annual leave and something breaks. Below are the questions we ask when we walk into this situation, the answers we usually get, and what a good answer sounds like. If you're somewhere in the middle of this, use it as a checklist rather than a warning. ## The eight questions ### 1. What product experience is behind this? The answer we hear is “he did a course on Claude.” Courses are genuinely useful and the tooling has never been more approachable. But a course teaches you to build the feature. It doesn't teach you what a product owes its users on day 400, which is uptime, a support route, a change log, and someone who understands why a decision was made eighteen months ago. A good answer names shipped products, not tools. Ask what they've taken into production before, who used it, and what broke. If the honest answer is “nothing yet, but they're sharp”, that's workable. Pair them with someone who has, and be explicit that's what you're doing. ### 2. Who is accountable at 7am when it's down? The answer we hear is “me, alongside my day job, and I'm on annual leave next week.” One name and no cover is not an operating model, it's a single point of failure with a calendar. A good answer has a named owner, a named second, an agreed response time, and a written runbook that a competent engineer who didn't build it could follow. Write the runbook while you build, not after the first incident. Two people who both understand the system is the minimum viable team, however small the product. ### 3. Has it actually been security tested? The answer we hear is “yes, we've tested it, it works.” Functional testing tells you the happy path holds. It tells you nothing about what a motivated outsider can do with it, and AI features widen the surface in ways ordinary web apps don't - prompt injection through user content, tool calls that reach further than intended, model outputs rendered without escaping, keys sitting in a client bundle. - Get an independent penetration test before anything with real data goes live. Budget for it up front. - Treat model output as untrusted input. Never let it reach a shell, a database or a browser unescaped. - Scope tool access to the least the feature needs, per user, not per application. - Put secrets in a managed store and rotate them. A key in an environment file on someone's laptop is a key you can't revoke. ### 4. What are you measuring quality with? The answer we hear is “we tried about ten prompts and it got them all right.” Ten prompts is a demo. It proves the feature can work, not that it does work, and it gives you no way to answer the only question that matters after launch, which is whether today's change made things better or worse. Build an eval suite. It doesn't need to be elaborate to be transformative. Start with fifty real examples from the people who'll use the thing, write down what an acceptable answer looks like for each, and run them on every change. Add every production failure to the set as a regression case. We've written about this at length in [evals, not demos](https://www.doddledesign.co.uk/insights/evals-not-demos), because it's the single practice that separates a product from a prototype. > “Ten prompts that worked is a demo. Fifty examples you rerun on every change is a product.” ### 5. Where does the data go, and who signed that off? The answer we hear is “legal don't know about it, but it's fine, we ticked the box that says don't train on our data.” That box is real and it matters. It is also about a tenth of the obligation. - Know which jurisdiction the inference runs in, and whether your contract actually pins it there. - Know how long prompts and outputs are retained by the provider, and how long you retain them. Both need a stated period and a deletion job that runs. - Do a data protection impact assessment before launch if personal data is anywhere near it. Retro-fitting one under audit pressure costs far more. - Log what went to the model and what came back, redacted where it needs to be. When someone asks what the system told a customer in March, you want an answer. Bring legal in early and give them something concrete to review. Their objection is almost never to AI. It's to finding out about it after the fact. ### 6. How does a change get to production? The answer we hear is “I push to main and refresh the page.” It works right up until the day it doesn't, and the day it doesn't is the day you need to roll back and can't say what changed. You don't need a heavyweight pipeline. You need version control with reviewed pull requests, a staging environment that looks like production, automated tests and evals running as a gate, one-command deploy and one-command rollback. That's a couple of days of setup for a small product, and it converts model upgrades from a leap of faith into a measured decision. ### 7. What does it cost to build and to run? The answer we hear is “it's free, we're already paying for Copilot.” The licence is the cheap part. The real running cost is inference at production volume, hosting, logging and observability, the security work, and the days per month someone spends keeping it alive. Model the unit economics before you commit. Cost per request, multiplied by realistic monthly volume, plus a fixed platform cost, plus the loaded cost of the people supporting it. Then compare that against the SaaS licence you're replacing. In our experience building still wins often enough to be worth doing, but it wins by a sane margin rather than an infinite one, and knowing the real number is what keeps the project funded when someone senior asks. ### 8. What happens when that person leaves? Nobody asks this one and it's the one that bites. If the knowledge lives in one head, you haven't replaced a vendor dependency, you've swapped it for a smaller and less contractual one. The fix is unglamorous. Architecture decisions written down as you make them. Code reviewed by a second person as a rule, not a favour. Infrastructure defined in the repository rather than clicked into a console. Prompts and eval sets versioned alongside the code. None of it slows a capable team down by much, and all of it is what makes the product an asset on your balance sheet rather than a favour someone is doing you. ## The shape that works None of the above is an argument against going in-house. It's an argument for going in-house deliberately. The pattern we see working looks roughly like this. - **Pick a first product that matters but won't hurt.** Real users, real value, contained blast radius if it's wrong. An internal tool before a customer-facing one. - **Build the guardrails alongside it, not after.** Evals, observability, access control and the deploy pipeline go in with the first feature. Bolted on later, they cost three times as much and land half as well. - **Put an experienced pair of hands next to your team.** Not to take the work off them - to make sure the first product sets the standard the next five follow. - **Give it a real budget line.** Inference, tooling, security testing and support time, named and funded. Products that live inside someone's slack time die inside someone's slack time. - **Review it in ninety days against the questions above.** Honestly, in writing, with the gaps listed. If you only do three things this week - write the runbook, put fifty real examples into an eval file, and book the penetration test. Those three between them remove most of the ways this goes badly wrong. ## Where we come in We're doing exactly this with several clients right now. We help shape the internal AI function, build the first product alongside the team so the guardrails get learned by using them rather than reading about them, and then step back to a lighter cadence - code review, eval debugging, model upgrade reviews, the architecture calls when something new lands. Your team stays autonomous and owns the roadmap. They just don't learn guardrails, evals, security and deployment the expensive way. There's more detail on how that engagement runs in [going in-house with AI, without going it alone](https://www.doddledesign.co.uk/insights/in-house-ai-not-alone). And if you've read this far because a version of that sentence was said in one of your meetings recently, we'd genuinely like to talk. Half an hour, no deck. We'll tell you which of the eight you've already got covered and which two are worth doing next, whether or not you ever work with us. More from Doddle ## Keep reading. Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read Practice ### Going in-house with AI, without going it alone If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over. 7 min read ## Going in-house? Let's pressure-test the plan. Half an hour with the people who've taken AI products into production. We'll walk the eight questions with you, tell you which you've already got covered, and which two are worth doing next. No deck, no obligation. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Talk to us](https://www.doddledesign.co.uk/contact) [How we work with in-house teams](https://www.doddledesign.co.uk/services/ai-native-delivery) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/decisions-behind-production-ai|> --- title: "The AI decisions that never make the demo - prompts, residency, tokens and fallbacks" url: "https://www.doddledesign.co.uk/insights/decisions-behind-production-ai" section: "Insights" description: "Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately." published: "2026-07-22" publisher: "Doddle" --- Practice # The AI decisions that never make the demo - prompts, residency, tokens and fallbacks 22 July 2026 10 min read We've spent the last stretch deep in the parts of AI delivery that never make it into a demo. How prompts are designed, where models and data are allowed to live, open weights, the token bill versus the hardware bill, and what happens when a provider has a bad afternoon. Here's the honest, educational version of what we've learned. ![Five quiet dials in a row, each set to a different position, connected by a single thin path - one decision seen from five angles.](https://www.doddledesign.co.uk/images/insights/decisions-behind-production-ai.webp) A demo shows you the model on its best day. Production shows you everything around it. The five decisions below are the ones that decide whether an AI feature is affordable, dependable, and defensible to a risk committee. None of them are exotic. All of them are easy to skip until the bill or the outage arrives. ## Prompt engineering is engineering, not wording The name undersells it. “Prompt engineering” sounds like finding the magic phrase. In production it's closer to designing an interface against a probabilistic component, and the craft is mostly about being explicit, not being clever. The prompts that hold up over time share a few habits. - **The contract is explicit.** What goes in, what must come out, and in what shape. If you need typed fields, ask for a schema and validate against it. A prompt that says “return JSON” and hopes is not a contract. - **Examples beat adjectives.** Two or three worked examples of the input and the output you'd accept move behaviour far more reliably than a paragraph of instructions telling the model to be accurate and thorough. - **Context is curated, not dumped.** Give the model what it needs for this task and nothing it doesn't. More context is not more quality. It's more cost, more latency, and more room to get distracted. - **The stable part is separated from the variable part.** The instructions and examples rarely change. The user input always does. Keeping that boundary clean lets you cache the stable prefix and cut both cost and latency, which we come back to below. - **Prompts are versioned like code.** A prompt is a dependency. It gets a version, a change history, and a test before it ships. The last habit is the one that separates a system from a science project. A prompt change is a behaviour change, and the only way to make it safely is to measure it. This is where prompt work and evals meet. Without evals a new prompt is a leap of faith. With them, it's a controlled change you can ship on a Tuesday. > “Good prompt engineering doesn't read as clever. It reads as obvious, once someone else has done the work of making the contract explicit.” ## Residency, where the model and the data actually live For a regulated client the first AI question is rarely “is it any good.” It's “where does our data go, and where does the model run.” Get that wrong and the quality of the model is irrelevant, because the feature never clears review. It helps to separate two things people tend to blur together. - **Data residency** is about where data is processed and stored. For UK and EU clients that usually means keeping traffic inside a chosen region and signing terms that rule out training on your data and set retention to zero. The major providers support this through regional endpoints and enterprise agreements, and it's the more common answer. - **Model residency** is stronger. The model itself runs inside your own boundary, on your infrastructure, so prompts never leave the perimeter at all. This is where open models come in, and it's the answer when a regional API agreement still isn't enough for the data in question. The real-world design is rarely all or nothing. A common shape is a frontier API under a zero-retention regional agreement for the genuinely hard work, and a self-hosted open model for the paths that touch the most sensitive data. Residency stops being a blocker and becomes a routing decision, which is a much better place to be. ## Experimenting with open models, and when they win The open-weight models, Llama, Mistral, Qwen, DeepSeek, and now OpenAI's own open releases, have quietly closed most of the gap for well-scoped tasks. Extraction, classification, routing, tagging, and a lot of summarisation no longer need a frontier model. They need a good-enough model you can pin, host, and evaluate. Three reasons we keep an open model in the toolkit, even when a frontier API is the default. - **Control.** A hosted open model doesn't change under you. You pin a version and it behaves the same next month. No silent upgrade, no quiet regression the week after a release. - **Residency.** It runs inside your boundary, which answers the model-residency question above outright. - **Cost at volume.** For a high, steady workload on a narrow task, a model you host can be dramatically cheaper per request than paying per token to a provider. The honest catch is that hosting is real work. You take on the serving stack, GPU capacity, quantisation choices that trade a little accuracy for a lot of throughput, and the same eval discipline you'd apply to anything else. Open weights are free to download. Running them well is not. Open doesn't mean free. It means yours. A useful test before reaching for an open model. Write the eval first. If a small, pinned, self-hosted model passes the eval for the task in front of you, the frontier model was never the requirement. If it doesn't, you've learned that cheaply, before committing to any hardware. ## Tokens or hardware, the question behind the bill Every AI feature bills one of two ways. Per token to a provider, or per hour for hardware you run. The instinct is to frame this as a model-size question. It's really a utilisation question. ### What each one is good at - **Tokens** have no fixed cost. You pay for exactly what you use, someone else runs the fleet, and you scale from zero to spike without a capacity conversation. This is the right default for spiky, low, or unpredictable volume, which describes most products for most of their life. - **Hardware** costs the same per hour whether it serves one request or a thousand. That makes it painful at low volume and excellent at high steady volume. A GPU you keep busy is cheap per request. A GPU idling overnight is money on fire. So the break-even isn't about how big the model is. It's about how full you can keep the machine. The directional rule we use. - Spiky, low, or unpredictable volume, stay on tokens. The flexibility is worth the unit price. - High, steady, predictable volume on a well-scoped task, hardware starts to win, and if residency already pushed you to self-host, the economics often agree. And don't price hardware on the GPU alone. The real bill includes ops, on-call, capacity planning, and the engineer-hours to keep a serving stack healthy. Tokens quietly buy you out of all of that, which is a genuine part of their value, not a rounding error. Before either lever, there's a cheaper one. Caching cuts the token bill without touching hardware. Prompt caching reuses the stable prefix of a request so you're not paying to re-read the same instructions every call. Semantic caching returns a stored answer when a near-identical question comes back. On the right workload those two together take a surprising bite out of the bill before you've changed a single model. > “The AI bill is rarely a model-choice problem. It's a utilisation-and-caching problem wearing a model-choice costume.” ## Fallbacks, and why a gateway earns its keep Providers have outages, rate limits, and slow afternoons. If your product calls one model directly, your product's uptime is that provider's uptime, and you'll find that out at the worst possible time. A gateway sits between your application and the models. One interface in, many backends out. Whether it's an open-source router you host or a managed one, the value is the same. - **Failover.** Primary model returns an error or times out, the request retries on a secondary automatically. The user never sees the wobble. - **Routing.** Send easy calls to a cheap model and hard ones to a frontier model, by rule rather than by hope. - **Load balancing.** Spread traffic across keys and regions so a single rate limit doesn't become an incident. - **Central control.** One place for logging, spend caps, and caching, instead of the same plumbing copied into every service. There's a discipline that comes with it, and it's easy to miss. A fallback is a quality decision, not just a plumbing one. If your secondary model is weaker, a silent failover can quietly degrade the product in a way that's harder to notice than a clean error and harder to debug. So the fallback path gets evaluated too. You should know, before it fires in anger, that the model you fail over to is one you'd be happy to serve. Keep the layer thin. A gateway is a routing and resilience layer, not a place to hide business logic. The moment it starts making product decisions, you've moved the hard part somewhere nobody's testing. ## How the five fit together These aren't five separate topics. They're one decision seen from five angles. A clear prompt contract tells you what the task actually needs, which tells you whether a small open model can do it, which decides where the model can live, which drives whether you're really paying for tokens or hardware, and the gateway is what lets you hold all of that together and change your mind later without a rewrite. If you're commissioning an AI build, these are the questions worth asking early, because they decay slowly and they decide the bill. Which model is the flashy question and the one that changes every few months. How you prompt it, where it runs, what you fall back to, and whether you're paying by the token or by the hour, those are the questions that are still true next year, and the ones that quietly decide whether the thing works. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read Practice ### Going in-house with AI, without going it alone If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/paywise-two-years-on|> --- title: "PayWise, two years on - what an OutSystems product looks like at maturity" url: "https://www.doddledesign.co.uk/insights/paywise-two-years-on" section: "Insights" description: "Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time." published: "2026-05-27" publisher: "Doddle" --- Case notes # PayWise, two years on - what an OutSystems product looks like at maturity 27 May 2026 7 min read Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. ![Two parallel calm horizontal bands stretching across the composition with quiet measurement marks along them - steady continuous operation, measured improvement, in abstract.](https://www.doddledesign.co.uk/images/insights/paywise-two-years-on.webp) We talk a lot on this site about the moments where modern AI stacks earn their place - fast iteration, new product shapes, capability you couldn't build any other way. We talk less often about the other half of our practice, the platform work that just keeps doing its job, quarter after quarter, while the business gets on with growing. [PayWise](https://www.doddledesign.co.uk/work/iglu) is one of those. Two years in, it's the strongest argument we have for OutSystems as a platform when the workload fits. ## The recap, in a paragraph PayWise is the supplier-payments platform we built for IGLU, the UK's largest cruise and ski agent. It ingests supplier statements, normalises them, matches lines to internal records, flags exceptions, and gives the finance team a live view of cash exposure. Built on OutSystems, run inside their estate, owned by their people. ## What two years looks like, in numbers - **Zero production incidents** in two years of continuous use across the finance function. - **10,000+ statements** processed end-to-end. Roughly double the year-one volume, no change to the architecture. - **Auto-match rates at industry standard, and rising.** The matching logic has been refined every quarter against the patterns the team sees in production. - **Fully managed by a small team** on the IGLU side. No DevOps headcount added to support it. - **Operating costs fixed.** Platform licence, infrastructure and support sit on a known monthly line, not a consumption curve. > “The unglamorous version of success - nothing on fire, costs you can put on a slide, and a finance team that doesn't need to think about the tool they spend most of their day in.” ## What we've actually been doing Two years of zero incidents doesn't mean two years of nothing happening. The product has moved forward continuously, in a steady rhythm that suits how the business actually changes. - **Database evolution.** Schema changes to support new supplier shapes and new payment categories, applied alongside the OutSystems data-model tooling so migrations stayed surgical, not big-bang. - **Matching rule refinement.** Every quarter we look at the exceptions the team is resolving by hand, work out which patterns we can encode, and ship the rule. The curve has moved up steadily without ever needing a rewrite. - **Reporting updates.** Finance reporting evolves as the business does. New supplier groupings, new exception categories, new period comparisons. Each one a small, contained change, each one delivered in days rather than weeks. - **Integration extensions.** Additional supplier file shapes and a couple of new downstream feeds into the finance stack as IGLU's tooling moved. - **UX polish.** Small ergonomic improvements based on what the team uses every day. Search behaviour, export options, audit-trail filters. ## What this actually says about the platform It's easy in 2026 to write OutSystems off as last year's idea, with so much of the industry's attention on AI-native stacks. The honest read, from inside a production system that nobody's touched as a hero project for two years, is more nuanced than that. - **Mature platforms compound.** The runtime, the data layer, the deployment pipeline, the audit story - none of it has needed reinvention. Time that would have gone into plumbing has gone into making the matching better. - **The governance story holds up.** SSO, RBAC, full audit, environment parity. Two years of audit reviews, no scramble. - **Costs are predictable.** No consumption tail, no surprise bill in a busy month. Finance prefers this for obvious reasons. - **The platform stays current without forcing the team to.** OutSystems' own platform updates land in our environments on a managed cadence. PayWise has moved through several without ever stopping. ## The small-team angle One of the most underrated things about a build like PayWise is what it doesn't need. IGLU runs it with a small team. No dedicated SRE rota for the platform itself. No specialist data engineer holding the schema together. The finance team owns the product roadmap and the platform team handles the runtime, and it works because the runtime doesn't demand attention. For finance leaders evaluating where to put capability - in-house team, managed service, build-it-and-leave-it platform - that's the variable most pricing comparisons miss. The cost of *operating* a platform over a five-year horizon eclipses the cost of building it. Operating costs that sit on a flat line are easier to plan around than ones that scale with usage. ## The honest verdict Two years on, PayWise is the kind of product that doesn't get written up as a case study often, because the story is “it kept working, and quietly got better.” That story is harder to dramatise than a re-platform, but it's the one most finance teams actually want. A platform that absorbs growing volume without re-architecting, a maintenance rhythm a small team can sustain, a cost profile that's knowable up-front. If you have a high-volume, rule-heavy, audit-sensitive workflow that's currently in spreadsheets - or in a brittle bespoke build that's been quietly costing you - the PayWise shape is one to look at seriously. Talk to us and we'll be honest about whether it's the right fit. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Practice ### Going in-house with AI, without going it alone If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/in-house-ai-not-alone|> --- title: "Going in-house with AI, without going it alone" url: "https://www.doddledesign.co.uk/insights/in-house-ai-not-alone" section: "Insights" description: "If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over." published: "2026-05-13" publisher: "Doddle" --- Practice # Going in-house with AI, without going it alone 13 May 2026 7 min read If your strategy is to grow AI delivery capability inside your own team, the harness is the part that decides whether it works. Here's the shape we use to set it up, then hand the keys over. ![An ordered structural lattice taking shape - interlocking beams and pillars, warm amber blocks fitted into the structure. Capability being built carefully.](https://www.doddledesign.co.uk/images/insights/in-house-ai-not-alone.webp) We see two patterns when leadership decides to invest in AI. The first is to outsource the build entirely, ship a product, and treat AI as a vendor relationship. The second, which is becoming far more common, is to build AI capability inside the existing engineering team. Cost discipline, control of the IP, speed of iteration, retention of the people doing the work. All of those favour going in-house. It also tends to fail in a way that takes six to nine months to become obvious. ## The bit teams underestimate The model isn't the hard part. There are good models, good SDKs, good worked examples, and any competent engineer can have a working prototype on a laptop by the end of the week. The hard part is the surrounding system that turns a prototype into a product the business can rely on. We call ours the harness, and most of it is invisible from the outside. - **Evals.** Programmatic checks that say whether a prompt or model change made the product better or worse. No evals, no honest answer to “is this an improvement?” - **Observability.** Cost, latency and quality on a live dashboard, with every interaction replayable for debugging. Without it, nobody knows what production is actually doing. - **Governance and guardrails.** Policies enforced, sensitive data handled properly, AI outputs checked before they go anywhere. Audit-ready from day one, not retro-fitted when legal asks the awkward question. - **Identity, RBAC and audit.** SSO, role-based access, an audit trail. The boring scaffolding that survives a regulatory review. - **Code analysis and review.** Quality, security and architecture compliance checked automatically on every change, the same bar for human-written and AI-written code. - **CI/CD with eval gates.** A pipeline that fails a deploy when AI quality drops below the bar the team set. Upgrading a model becomes a measured decision, not a leap of faith. Each of those is a few weeks of work in isolation. The composition is the hard bit, and the team building the product is rarely the team best placed to build the harness around it from scratch. > “The model isn't the hard part. The system around the model is the part that decides whether you have a product or a demo.” ## What “in-house, with a partner” actually looks like The shape we've found that works is two-phase. We stand the harness up with your team, building the product alongside it so nothing is theoretical. Your engineers learn it by working in it, not by reading a deck about it. Then we step back. Your team owns delivery, and we're on call for the harder moments - the patterns you haven't seen before, the regressions that don't have an obvious cause, the model upgrades that need a careful eye. The split usually looks something like this. - **Weeks 1–2, discovery.** What you're building, what the data shape is, what the harness needs to look like, who on your team will own which parts. Comes out as a buildable plan, not a slide deck. - **Weeks 3–10, build alongside.** We build the first product with your team embedded. The harness goes in at the same time, not at the end. Pair programming, joint code review, shared eval ownership. By the end of it your team has shipped a real thing and built the muscle to ship the next one. - **Weeks 11+, handover and partner mode.** We shift to a lighter cadence - code review, eval debugging, model-upgrade reviews, architecture calls when something new comes up. Your team is doing the delivery; we're the partner you call when it gets hard. ## What “on speed-dial” actually means It's not a retainer with a minimum hours commitment that becomes invoice padding. It's a relationship where your engineers know they can put a question into a shared channel and get a useful answer the same day, where we sit on the harder code reviews, and where we run a quarterly check-in on the harness itself - what's drifted, what new patterns you're hitting, what the wider AI landscape has done that affects you. - Joint code reviews on the changes your team flags as risky. - Eval debugging when a number moves and nobody can explain why. - Model-upgrade reviews - before you bet a quarter on a new release. - Architecture calls when a new use case lands that needs a fresh shape. - A quarterly harness review, so quality doesn't drift quietly. We're happy to be the contractor in the room when a regulator, auditor or board reviewer wants someone independent to explain the architecture. That's usually the moment a partner relationship earns its keep. ## When this is the right shape - You have a competent engineering team that's new to AI delivery specifically. - AI capability is a strategic asset you want owned internally, not a vendor-managed black box. - You're willing to invest in the harness up-front, because you understand the cost of not having one. - Leadership is on board with a partner relationship that tapers, rather than a hand-off cliff. ## When it isn't - You need the product shipped end-to-end and don't have an in-house team to grow. That's a straight build engagement instead. - The strategy is to outsource AI entirely and let the supplier carry the risk. Fine, but pick the supplier on that basis. - The team isn't ready to learn a new operating model alongside their day jobs. The harness only sticks if the team owns it. ## The honest verdict The teams that go in-house and succeed are almost always the ones that built the harness with someone who'd done it before. The teams that struggle are the ones that treated AI delivery as a normal engineering problem and discovered, six months in, that production was a different shape from prototype. The cost of the partner is small compared to the cost of getting that wrong. If this is the shape you're considering, the conversation we'd want to have first is about your team - what they can already do, what they want to own, what they'd rather lean on a partner for. The harness flows out of that, not the other way round. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/finbridge-migration|> --- title: "From OutSystems to AI-native, how we re-platformed Finbridge in 10 weeks" url: "https://www.doddledesign.co.uk/insights/finbridge-migration" section: "Insights" description: "What it actually looks like to move a regulated financial services platform off OutSystems onto a modern AI-native stack, including the parts that surprised us." published: "2026-04-21" publisher: "Doddle" --- Case notes # From OutSystems to AI-native, how we re-platformed Finbridge in 10 weeks 21 April 2026 9 min read Migrating a regulated financial services platform off OutSystems in ten weeks sounds aggressive. The truth is, with the right scope, the right team, and an honest read on what to rebuild versus what to lift, it's not as dramatic as it sounds. ![A heavy angular geometric form dissolving into pixels and reforming as a lighter open structure - the re-platforming itself, in abstract.](https://www.doddledesign.co.uk/images/insights/finbridge-migration.webp) We talk a lot about migrations on this site, including how to do them without being precious about platforms. Here's a longer write-up of one of them. Finbridge agreed we could share the engineering side. The commercial side stays private. ## The situation Finbridge had been running on OutSystems for several years. The platform had done its job. It shipped the original product fast, kept the audit trail tight, and got the business through the regulated stages no founder enjoys. By the time we got involved, the product roadmap had shifted toward AI-native workflows, and the cost of building those inside the existing estate had become the thing slowing the company down. We had two conversations before we agreed to take the work. The first was about scope and timeline, the second about whether moving was actually the right call. We told them — honestly — that OutSystems is still excellent for the workflows it was already running, and the right answer might be to migrate only the parts the new roadmap really needed. After looking at it together, they decided to migrate the whole platform. Their reasoning was sound. Operating two stacks long-term added cognitive overhead they didn't want to carry, and they had a clear architectural direction for the AI layer that depended on owning the data plane. ![Finbridge Global platform](https://www.doddledesign.co.uk/images/work/finbridge/finbridge-dashboard.webp) Finbridge Global, post-migration. AI-native stack, OutSystems retired. ## What we did ### Week 1, discovery We mapped the surface area, applications, integrations, scheduled jobs, identity flows, audit hooks. We tagged each component as lift-and-shift, rebuild, or rethink. About 60% of the platform fell into “lift-and-shift”, same shape, new stack. The remaining 40% needed either a fresh rebuild (because the OutSystems shape didn't fit the new runtime) or a rethink (because we were going to change its job to support the AI workflows coming). ### Weeks 2–3, foundations Next.js, Postgres, infrastructure-as-code, OpenTelemetry, identity via the existing IdP, audit log parity. Nothing exciting, and that was the point. The new stack's foundation had to be observably equivalent to what OutSystems was already giving them, before we put a single user-facing feature on it. ### Weeks 4–8, feature parity We migrated the user-facing flows incrementally. Users were on a working application throughout, initially the old one, then progressively the new one as flows shifted across behind a traffic-routing layer. We modernised UX where the lift was cheap and visible. We deliberately deferred ornamental changes that would have lengthened the schedule without changing the outcome. ### Week 6 onwards, the AI overlay From week six we started layering AI features in. The document processing pipeline went first. Then the RAG-powered assistant. Then the prompt-to-query analytics. Each one shipped behind a feature flag and graduated as its eval suite passed. None of them blocked the migration timeline, and all of them were live within ninety days of go-live. ### Weeks 9–10, handover Documentation, runbooks, knowledge transfer to the client's team. We stayed available for the first AI feature iterations post-launch, but the goal was always for the platform to be operable without us. ## What surprised us - **The lift was bigger than the integrations.** We assumed integrations to bureaux, identity, and audit would be the long pole. They weren't. The long pole was user-facing flows where the original OutSystems implementation had “clever” behaviour buried in the platform's conventions. Re-expressing that cleanly on the new stack was where the time went. - **AI features were the easiest part.** Once the stack was modern and the data plane was ours, adding RAG, assistants, and prompt-to-query was straightforward. The hard work had been the platform, not the AI. - **Users didn't notice the migration.** They noticed the UX refresh. They noticed the new assistant. They didn't notice that the entire underlying stack had moved. That's how you want it. > “The hard work in a re-platform isn't the new stack. It's being honest about the old one, what was earning its keep, what wasn't, and what was hiding behind platform conventions you only see when you have to leave.” ## What we'd say to anyone considering it First, don't migrate as a gesture. If the platform is still the right tool, stay. Migration is justified when the platform's shape is genuinely blocking the work the business wants to do, not when there's a vague sense that something newer would feel better. Second, get the scope right. A fully-scoped 10–12 week migration is enormously different from an open-ended “we'll see what we find” engagement. Discovery exists to make that scope honest. Third, pick a partner who's comfortable telling you not to migrate. If everyone you're talking to is enthusiastic about the move, you're hearing what they want to sell, not what you need. If you've got a platform decision in front of you and you'd like an independent read, that's exactly what our [consultancy](https://www.doddledesign.co.uk/services/consultancy-services) engagements are for. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/ai-earns-its-place|> --- title: "When AI earns its place, and when it doesn't" url: "https://www.doddledesign.co.uk/insights/ai-earns-its-place" section: "Insights" description: "Most AI features fail in production not because the model was wrong, but because the surrounding system was unbuilt. A short field guide." published: "2026-04-02" publisher: "Doddle" --- Practice # When AI earns its place, and when it doesn't 2 April 2026 7 min read Most AI features fail in production not because the model was wrong, but because the surrounding system was unbuilt. A short field guide to noticing the difference, and what to do about it. ![A grid of identical quiet geometric tiles with a single tile lit softly in warm amber - the one that earned its place.](https://www.doddledesign.co.uk/images/insights/ai-earns-its-place.webp) We've now built AI features into enough products to spot the pattern reliably. The teams whose AI launches succeed and the teams whose AI launches stall don't differ in their model choice. They differ in everything around the model. ## The wrong question Most AI strategy conversations open with “which model should we use?” That's almost never the question worth starting with. Models change every few months. The decisions that matter more, and that decay slower, are about evaluation, retrieval, observability, and the boundary between the model and everything else. ## The questions worth asking - **How will we measure quality?** If you don't have evals before launch, you'll be debugging in production via Slack screenshots. - **Where does the context come from?** Most interesting AI features are retrieval problems wearing model clothing. The quality of the retrieval will outweigh the quality of the model in real-world performance. - **What can we see when something goes wrong?** Logs, traces, replay. If a user complains, you need a reproducible record of what the system saw, what it sent, what came back. - **Where does the model's authority stop?** The model proposes, a deterministic layer disposes. Especially for anything that touches user data, money, or business state. - **How do we swap the model?** A new model release shouldn't be a leap of faith. With proper evals, it's a controlled change. ## The work that's usually missing On every AI engagement we've run, the same parts of the system are the ones the original team hadn't prioritised. Evals. Observability for cost, latency, and behaviour. Prompt regression suites. A clear separation between model-generated content and system-of-record state. None of this is exotic. None of it is hard to learn. It's just missing in the parts of the industry that are still working out what production AI looks like. > “The difference between a working AI product and a clever prototype isn't the model. It's the rest of the iceberg.” ## What “earning its place” looks like AI earns its place in a system when it does work the rest of the system can't reasonably do, and when its outputs flow back into a structured layer the rest of the system can act on. Free text is dangerous, typed extraction is useful. A black-box prediction is suspicious. A prediction with confidence, provenance, and a deterministic safety check is operable. If you can articulate what your AI feature is doing in terms of “turning shape X into shape Y, with the following error modes,” you're in good shape. If the answer is “making things feel smart,” the surface area is still too vague to build well. ## One last test Ask whoever's proposing the feature, “how would we know this regressed?” If the answer is anything other than “we run evaluations and they would drop,” the feature isn't ready to ship, even if it currently looks fine. That's most of the discipline. There's craft inside the details, but the high-level shape is unspectacular — define what good looks like, measure it, build the surrounding system that the model needs to do its job. AI earns its place when those things exist. It doesn't, when they don't. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/outsystems-2026|> --- title: "OutSystems in 2026: a measured view" url: "https://www.doddledesign.co.uk/insights/outsystems-2026" section: "Insights" description: "A decision framework for weighing whether OutSystems still fits your team in 2026. Where the platform wins, where it doesn't, and how to tell the difference, written by people who still deliver on it every week." published: "2026-03-12" publisher: "Doddle" --- Decision framework # OutSystems in 2026: a measured view 12 March 2026 8 min read Where the platform still wins, where it doesn't, and how to tell the difference for your team, written by people who still deliver on OutSystems every week. ![A layered geometric landscape - older blocky structures alongside newer lighter forms, a low horizon line, soft gradient sky. The measured long view.](https://www.doddledesign.co.uk/images/insights/outsystems-2026.webp) It's easy to read the tech press right now and conclude that low-code is over. It isn't. It's just maturing into a category that fits some teams beautifully and some not at all, and the noise is mostly about the second group. Here's the read we use when teams ask us, in 2026, whether OutSystems is still the right tool. ## Where OutSystems still wins - **Regulated estates with broad delivery teams.** Where standardisation across teams is more valuable than any one team's preferred stack. - **Internal applications, portals, and process tools at enterprise scale.** Where the surface area is large, the business logic is dense, and the value of low-code velocity compounds. - **Modernisation of legacy estates.** Where the alternative is a five-year programme that the business won't green-light, and incremental shipping is the difference between progress and stasis. - **Workflows that need governance baked in.** Where the platform's audit, identity, and lifecycle features are earning their keep. ## Where it doesn't - **Funded startups pre-product-market-fit.** The licence economics rarely work, and the product flexibility you need at this stage tends to clash with the platform's shape. - **AI-native products where the data plane matters.** You can do AI inside OutSystems, we do, but if the AI layer is the product, owning the data plane on a modern stack is usually cheaper and freer. - **Teams that hire only on modern stacks.** The available talent pool matters. Hiring for low-code is its own decision. If you've already made the opposite decision, fighting it costs more than choosing differently. ## Where the honest answer is “a mix” Plenty of teams sit somewhere in the middle. The most useful question isn't “is OutSystems good?” (it is) or “should we leave?” (sometimes). It's “does the fit still hold?”, and the answer often turns out to be “for parts of the estate, yes. For others, no.” We see this most often in mature estates that have grown sideways. Operations and compliance modules tend to still pay off on low-code. Customer-facing surfaces have often drifted toward the kind of UX velocity that's easier on modern stacks. The right answer is usually neither “migrate everything” nor “leave it alone”, it's consolidate, with intent. ## A few decision tests - **The five-year horizon test.** Imagine the platform in 2031. Does its shape still match what you'd need? If you can't answer, build the answer before the migration question. - **The hiring test.** Could you hire the team you'd want to hire onto this stack? If not, no platform choice will outlast that constraint. - **The AI test.** Do the AI features your roadmap implies fit naturally inside the platform, or do they want a different runtime? Either answer is fine. The wrong answer is “we don't know yet, but we'll find out.” ## One conclusion, two opposite directions We still deliver on OutSystems every week, for teams it suits. We also help teams move off OutSystems every week, for teams it doesn't. The platform is a tool. The work is choosing the right one for the situation you're actually in, not the one the industry told you to want. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/migrations-without-rubbishing|> --- title: "Migrations without rubbishing the platform" url: "https://www.doddledesign.co.uk/insights/migrations-without-rubbishing" section: "Insights" description: "A practical guide to moving off a platform honestly, without the theatrics, without losing users, and without burning the partnership." published: "2026-02-19" publisher: "Doddle" --- Practice # Migrations without rubbishing the platform 19 February 2026 6 min read A practical guide to moving off a platform honestly, without the theatrics, without losing users, and without burning the partnership. ![Two distinct geometric zones in balance - a soft circle and an angular form connected by a quiet amber path. Two platforms, one bridge between.](https://www.doddledesign.co.uk/images/insights/migrations-without-rubbishing.webp) Migrations get marketed dramatically. “Escape the legacy.” “Liberate your stack.” It plays well in conference talks. It plays badly when you're actually doing the work, and worse, when the platform you're leaving is one you'll still need to talk about in the years to come. Here's how we approach migrations. None of it is novel. The opinion is that you should treat all of it as table stakes. ## 1. Start with the question, not the answer Before scoping a migration, scope the question that produced it. Why is the team thinking about moving? Is it a real cost-benefit signal, licence economics, architecture mandate, roadmap fit, or is it a frustration that would still be there on a new stack? If you can't articulate the trigger crisply, the migration will feel arbitrary to everyone except the people who picked it. That's how programmes lose momentum. ## 2. Be specific about what you're moving “Migrating the platform” is usually a euphemism. Most estates are a mix of components, some earning their keep, some drifted. The honest answer is usually to migrate part of the estate and modernise the rest in place. The dishonest answer is to commit to a full re-platform without examining whether you need one. ## 3. Keep users on a working application throughout A migration that requires a freeze on user-facing change is a migration that's allowed to take too long. Plan for incremental delivery. Plan for traffic routing that lets you flip flows one at a time. Plan for the failure modes. The slow migrations we've seen weren't slow because the work was hard. They were slow because someone agreed to stop shipping. ## 4. Modernise sparingly, on purpose It's tempting to use a migration to rebuild everything you'd quietly wanted to rebuild for a year. Resist most of the temptation. Identify the small set of changes that are cheap in this context and that genuinely matter. Defer the rest. Scope creep is the single biggest reason migrations overrun. > “A migration is a re-platform, not a rewrite. Conflate them and the timeline doubles, the risk triples, and the business loses patience.” ## 5. Don't rubbish the platform you're leaving This sounds like a tone point. It isn't. Rubbishing the platform you're leaving is operationally bad — it disrespects the team that built on it, it makes it harder to get knowledge transfer, and it locks you into having to justify the migration post-hoc when it gets challenged. It's also usually unfair. Most platforms are competent inside their fit. The honest framing is “the fit has changed.” That framing keeps the conversation about your specific situation, rather than the abstract merits of platforms. ## 6. Plan for handover from day one The platform you migrate to is a platform someone has to operate. If the migration team is the only group who understands the new build, you've created a different version of the problem you set out to solve. Documentation, runbooks, and knowledge transfer aren't the last week of the project, they're a continuous output. ## What this looks like at Doddle - Free 30-minute scoping conversation up front. - Paid discovery week to map the surface area and confirm scope. - Fixed-window, relatively fixed-cost migration (typically 6–12 weeks). - Users on a working application throughout. - Documentation and handover as ongoing outputs, not deliverables at the end. - Available to stay, available to step back. If any of this resonates and you've got a platform question in front of you, our [migrations page](https://www.doddledesign.co.uk/services/outsystems-migrations) has the engagement detail. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk <|page /insights/evals-not-demos|> --- title: "Evals, not demos - the AI quality habit that separates products from prototypes" url: "https://www.doddledesign.co.uk/insights/evals-not-demos" section: "Insights" description: "If your AI feature has no evaluations, it has no quality. A short, opinionated take on the discipline we apply to every AI build." published: "2026-01-30" publisher: "Doddle" --- Practice # Evals, not demos - the AI quality habit that separates products from prototypes 30 January 2026 5 min read If your AI feature has no evaluations, it has no quality. A short, opinionated take on the discipline we apply to every AI build. ![Concentric rings and arcs arranged vertically like calibrated gauges - the rigour of continuous measurement, in abstract.](https://www.doddledesign.co.uk/images/insights/evals-not-demos.webp) The single highest-leverage practice we've adopted across AI delivery is also the most under-sold — evals. Not demos. Not screenshots. Not “our model's really good now.” Evaluation suites, written down, runnable, and run. ## What we mean An eval is a programmatic check. Given this input, is the AI feature producing an output we'd accept? It's a test, but the assertions are usually softer than a unit test (does it cite the right document? is the answer factual against the source? does it hit the right schema?), and the assertions are often produced or graded by another model or a human. Evals don't exist to prove the model is perfect. They exist to make change safe. A new prompt, a new model version, a new retrieval setting, without evals, all of those are leaps of faith. With evals, they're changes you can ship with confidence. ## Why teams skip them - **They're boring to build.** A good eval suite is meticulous work, gold sets, edge cases, regression cases. The reward isn't a shippable demo, it's a number that quietly moves up over time. - **They feel optional during the build.** The feature appears to work. The model seems fine. It's only weeks later, when something quietly regresses, that the absence becomes a fire. - **They require discipline the team hasn't built.** Unlike a unit test, an eval needs ongoing curation. The first version is the easy part. ## What to evaluate first Start with the questions you'd ask in production if a user complained. - Did the model retrieve the right context? - Did it cite its source, and was the citation correct? - Did the answer match the source factually? - Did it follow the required output shape (JSON schema, structured fields)? - Did it stay inside the guardrails (no PII, no policy violations, no out-of-scope responses)? - Did the cost and latency stay within budget? > “Evals don't replace human judgement. They replace end-of-week panic.” ## What good looks like - A small gold set, hand-curated, that covers the most common inputs and the most painful edge cases. - A larger synthetic set, generated to cover input variations the gold set won't. - A scoring pipeline that produces a single composite number per run, and lets you drill into individual cases when it moves. - A CI gate that blocks deploys when the composite drops below an agreed threshold. - A regular cadence, weekly, monthly, for adding cases the team encounters in production. ## The honest verdict Most AI features you see in the wild don't have proper evals. You can tell because they regress unpredictably, change behaviour when models update, and require their team to be constantly available to firefight. The teams whose features feel reliable are almost always the teams who've invested in this work. If you're commissioning an AI build, asking “how will we measure quality?” before “which model?” will tell you a lot about the team you're considering hiring. More from Doddle ## Keep reading. Practice ### “We've just hired an AI guy” - the eight questions to ask next Owning the IP and the roadmap is the right instinct. One enthusiastic person, a Copilot licence and a push straight to main is not a delivery model. The questions we ask when we walk into this, the answers we usually get, and what good looks like. 8 min read Practice ### The AI decisions that never make the demo - prompts, residency, tokens and fallbacks Prompt engineering, model residency, open-model experiments, paying for tokens versus hardware, and gateway fallbacks. The unglamorous engineering that decides whether production AI is affordable and dependable, drawn from the work we've been doing lately. 10 min read Case notes ### PayWise, two years on - what an OutSystems product looks like at maturity Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time. 7 min read ## Want to talk about this? We're always up for a conversation about the work, the patterns we're seeing, what's worked, what hasn't. No pitch deck. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's talk](https://www.doddledesign.co.uk/contact) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk