# Rabblepop — full text --- # Rabblepop https://www.rabblepop.com An end-to-end UK software studio. Web and app platforms for small and medium businesses — product, design, build and QA in one team. Most agencies build the spec. Web and app platforms for small and medium businesses. Product, design, build and QA in one team — no handovers, and a view on what should be built before anything is. The software your business runs on. Web and mobile platforms for small and medium businesses. Built as one product, not a stack of parts. CRMs & internal systems — The system of record for how your business works: pipelines, approvals, documents, reporting. Customer portals — Your clients see their own work and nothing else. Requests, approvals, files, invoices. Booking & payments — Appointments, slots, deposits and confirmations, running without anyone administering them. Web applications — Customer-facing products on the web, from first login to subscription billing. Mobile apps — iOS and Android from one codebase, where an app earns its place over the web. AI-assisted workflows — Rote work that takes your team hours — reading, extracting, filling, drafting — done in minutes and reviewed by a person. One team. No handovers. Product, design, build and QA sit in one team. Most agencies split them across four suppliers, and every handover costs you twice — once in margin, once in the weeks lost translating between them. Product — We work out what the product is, who uses it, and which features come first. Design — Interfaces designed by the team that builds them, so nothing is lost between a mock-up and the real thing. Build — Next.js, TypeScript, React Native. Serverless on AWS. The stack you could hire for. QA & launch — Tested as it is built, launched with monitoring, documented for whoever comes next. Every project runs the same way. A call, a scoping sprint, a written plan, then a build you can watch. No stage is skipped and none is a surprise. Call — Half an hour. You describe the business problem; we tell you what we think it takes. Scoping sprint — We work out what the product is, who uses it, and which features come first. Plan — Scope, architecture, sequence and cost, in writing, before any production build starts. Build in the open — One team designs, builds and tests. You see working software every week. Launch and keep going — Live, documented and yours. We stay on for what comes next. What that looks like in practice. In their words. Rus K. — We were quoted well over £100,000 by another agency. Rabblepop scoped the platform, built it and had it live in four weeks, and it now runs our whole practice — from the first request to the report we file with the regulator. Amir A. — Filling a client’s documents used to take one of our team the best part of an afternoon. It now takes minutes, and a lawyer still signs off every one — which is the only way we would have accepted it. Rabblepop understood that before we had to say it. Ali K. — We sell cars. We do not want to think about a website. Rabblepop built one we update ourselves in five minutes and a booking system that runs on its own — we have not needed to touch it since launch, which is exactly what we asked for. Platforms in production. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # What we do https://www.rabblepop.com/what-we-do Web and app platforms for small and medium businesses, end to end. CRMs, portals, booking systems, web and mobile apps — product, design, build and QA in one team. Web and app platforms, end to end. CRMs, portals, booking systems, admin tools and customer apps for small and medium businesses. One team covers product, design, build and QA, from the first call to launch and beyond. What we build. CRMs & internal systems — The system your business actually runs on. Pipelines, assignments, approvals, documents, invoicing and reporting in one place — with an audit trail, because “who did what” has to be answerable. Customer & partner portals — Give clients, agents or suppliers a window onto exactly their own work. Submit a request, approve a fee, download a report. Role-based access throughout. Booking & payments — Slots, deposits, reminders and confirmations. Built so it runs unattended, because the people who own it have a business to run. Web applications — Customer-facing products: onboarding, subscriptions, dashboards, the lot. Server-rendered and quick, on a stack another team could pick up. Mobile apps — iOS and Android from one React Native codebase, sharing logic with the web. For when a real app earns its place over a good website. AI-assisted workflows — Take the rote work out of a process without taking the person out of the loop: read source documents, extract what matters, fill the template, hand it to a human to sign. Four disciplines. One team. Most agencies split a build across a product consultancy, a design studio, a development shop and a QA team, and you pay for every handover twice — once in margin, once in time. We put all four in one team. Product — Users, journeys, and which features come first. The plan you can hold before the build. Design — Interfaces designed by the team that builds them. What you sign off is what ships. Engineering — Web, mobile, backend, infrastructure. One codebase per product, not a collection of vendors. QA & operations — Tested as it is built. Monitoring, staging and production from day one. What you get on every project. A written plan before build — Scope, architecture, sequence and cost, agreed before any production code is written. Working software every week — In your browser, on a staging environment, from the first sprint. A view on the product — We tell you which features to build first — and which not to build at all. Your code, your infrastructure — Everything in your accounts and your repositories, documented for whoever comes next. Support after launch — We stay on for what comes next. Most clients keep us on a retainer. Built on the stack you could hire for. Current versions of the tools most product teams already use: Next.js and TypeScript on the web, React Native on mobile, Postgres for data, serverless on AWS through SST or on Vercel. Infrastructure as code, with staging and production kept apart. Web — Next.js, React, TypeScript. Server-rendered, quick, accessible. Mobile — React Native, sharing logic and types with the web codebase. Backend & data — Postgres, typed queries, server actions and REST where it earns its place. Infrastructure — AWS via SST, or Vercel. Defined as code. Staging and production. AI — Language models for extraction, drafting and classification — always with a person signing off. The connective bits — Auth, payments, bookings, documents, notifications, third-party integrations. Platforms in production. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # How we work https://www.rabblepop.com/how-we-work A call, a scoping sprint, a written plan, then a build you can watch every week. Every Rabblepop project runs the same five steps. A plan before the build. Every project runs the same five steps. You know what you are getting, what it costs and when it lands before production starts — and you see it being built every week. Call. Scope. Plan. Build. Launch. In order, every time. The scoping sprint is the first phase of the contract, not a separate product — so the plan you get is the plan we build to. Call — Half an hour. You describe the business problem; we tell you what we think it takes, what the riskiest parts are, and whether we are the right team for it. Scoping sprint — One to two weeks. We work out what the product is, who uses it, which features come first and what release one leaves out. You are in the room for all of it. Plan — Scope, technical approach, sequence and cost, in writing. It is yours: build with us or take it elsewhere. Build in the open — One team designs, builds and tests. Working software on a staging site every week, and one channel with the whole team in it. Launch and keep going — Live, monitored, documented, in your accounts. We stay on for support and the next release. What the plan contains. A working document, not a slide deck. It belongs to you: take it to another developer, use it to raise money, or build it with us. Product definition — Users, journeys, scope, and the explicit list of what release one does not include. Technical approach — Architecture, data model, integrations, and the decisions that are expensive to reverse. Sequence — What ships first and why. Usually a third of what you arrived with, and better for it. Cost and timeline — A number and a date, with every assumption they rest on written beside them. What building in the open means. Working software every week — On a staging site you can open in your browser, from the first sprint to launch. One channel, the whole team in it — No account manager relaying messages. You talk to the people doing the work. Scope changes come costed, the same day — Absorb it, defer something else, or extend. You get the options and the numbers; you make the call. Documented as it is built — Decisions and their reasons, written down as they are made — so the plan and the product stay the same thing. Where AI fits. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # Work https://www.rabblepop.com/work Client platforms in production, written up in full: the business problem, the system we built, and what changed. Property, legal and automotive. Platforms in production. Client platforms written up in full — the business problem, the system we built, and what changed. Property, legal and automotive so far. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # Lab https://www.rabblepop.com/lab Products we built for ourselves — live, maintained, and built the same way we build for clients. Products we built for ourselves. Self-initiated products, live and maintained in-house. Taking an idea to a live, maintained product is what we do for clients; these are the ones we did for us. keirsdad — A consumer product that found its audience without a marketing budget. Built, launched and still maintained — the part most side projects never reach. sealedin.app — Write a message now and have it delivered at a chosen point in the future. A complete idea taken to production: scheduling, delivery guarantees, and the edge cases that come with promising to do something years from now. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # About https://www.rabblepop.com/about An end-to-end UK software studio on the Sussex coast, where the team that works out what to build is the team that builds it. Product thinking and engineering, under one roof. Rabblepop is an end-to-end UK software studio, working from the Sussex coast with clients across the country and abroad. The team that works out what to build is the team that builds it — which is unusual, and is the whole reason the studio exists. Both halves of the job. One team. Rabblepop is led by a head of product at a large international software agency who also writes production code. Our team combines expertise across product, design, engineering and QA, so the people deciding what gets built are the people who know what building it costs. Product leadership — Head of product at an international agency shipping web and mobile products at scale. Regulated delivery — A property valuation platform in production: role-based access, regulator-format reporting, live operations, retained. AI in production — Document automation for a law firm — hours of rote work per document down to minutes, with a lawyer signing off. Our own products — Two live products built and maintained in-house. We ship for ourselves, not only for clients. Five things you can hold us to. A written plan before any production build — Scope, architecture, sequence and cost, agreed first. The scoping sprint is the opening phase of every contract. Working software every week — On a staging site, in your browser, from the first sprint. Scope changes costed the same day — Options and numbers, so the decision is yours to make. Your code, your infrastructure, your documentation — In your accounts and repositories from day one. Conventional stack, no proprietary anything. A view on the product — We tell you which features to build first, and which not to build. You are free to disagree — but you will know what we think. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # FAQ https://www.rabblepop.com/faq What Rabblepop builds, who it works with, how a project runs, what it costs, and how to start. Questions, answered. What we build, who we work with, how a project runs, what it costs, and how to start. What is Rabblepop? — Rabblepop is an end-to-end UK software studio, working from the Sussex coast with clients across the country and abroad. We build web applications, mobile apps and the internal systems businesses run on — CRMs, portals, booking systems, reporting and workflow tools. Product, design, build and QA sit in one team rather than being split across suppliers. What makes Rabblepop different from other software agencies? — Two things. First, we take a view on the product: most agencies build the spec they are given, and we help you work out what the product should be and which features come first. Second, one team covers product, design, build and QA, so there are no handovers between suppliers — which is why our projects cost less and land sooner than a traditional agency’s. Who does Rabblepop work with? — Small and medium businesses that need a custom platform built or an existing one replaced, and founders taking a product to market. Recent work includes a valuation platform for a regulated property firm in the UAE, document automation for a law firm, and a booking system for a UK car dealership. How does a project start? — With a half-hour call. If it is a fit, we agree a contract whose first phase is a scoping sprint: one to two weeks in which we work out what the product is, who uses it and which features come first. You receive a written plan — scope, technical approach, sequence and cost — before any production build starts. How much does a project cost? — It depends on scope, which is why every project starts with a scoping sprint that gives you a written cost before production build. As a guide, our projects come in well under what a traditional agency quotes for the same scope, because nothing is handed over between suppliers and AI takes the time out of the mechanical work. Book a call and you will have a range for your situation within half an hour. How long does a project take? — Weeks rather than quarters. A CRM platform for a regulated property firm went from kick-off to live in four weeks. The scoping sprint gives you a date in writing for your project. What technologies does Rabblepop use? — Current versions of Next.js, React and TypeScript on the web; React Native for mobile; Postgres for data; serverless on AWS through SST, or Vercel — defined as code with separate staging and production environments. The stack is deliberately conventional so that another team could maintain it, including replacing us. Does Rabblepop use AI? — Yes. Senior engineers working with AI do the mechanical parts of a build — scaffolding, integration glue, tests, documentation — in days rather than weeks, and that saving is passed on to you as cost. We also build AI into products where it takes rote work off your team, always with a person reviewing the output. Decisions about what to build stay with people. Will I own the code? — Yes. The code, the infrastructure and the documentation are yours, in your own accounts and repositories from day one. Everything is built on a conventional, widely used stack with no proprietary components, so you can hand it to another team whenever you choose. How do you protect continuity on a long project? — Continuity is designed in rather than promised. Every project has a named lead who is with you from the first call through to launch and beyond, and everything is built so that it does not depend on any one individual: conventional technology choices, decisions documented as they are made, infrastructure defined as code, and no proprietary dependencies. If you ever needed to move the work, it would be a handover, not a rescue. Where is Rabblepop based? — On the Sussex coast, near Brighton. We work with clients across the UK and internationally — most of the work happens remotely, with working software on a staging site every week, and we meet in person in London or Brighton when it helps. Rabblepop Ltd is registered in England and Wales. How do I start? — Book a call — half an hour, no deck, no obligation. Bring an idea, a half-built product or a business problem, and you will leave knowing what it would take and whether Rabblepop is the right team for it. Book at rabblepop.com/contact or email hello@rabblepop.com. Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # Contact https://www.rabblepop.com/contact Tell us what you’re trying to build. Half an hour, no deck, a straight answer. Tell us what you’re trying to build. A fully formed spec, an idea on the back of an envelope, or a system that has stopped keeping up — it is the same half hour, and you get a straight answer. What happens on the call. You describe what you’re trying to do. We ask questions — probably more than you’re expecting, because that is the job. By the end you have a rough sense of scale, the parts we think are riskiest, and our view on whether this is something we should build for you. Or send it in writing. If you would rather write it down first, this reaches the same team. The budget question is not a filter — it is so the first call is useful rather than spent guessing. --- # Writing https://www.rabblepop.com/writing Notes from Rabblepop on product decisions, delivery, and building the right thing first. Notes on building the right product. Occasional writing on product decisions, delivery, and where software projects win or lose. All writing Tell us what you’re trying to build. Half an hour on a call with our team. Bring a spec, a rough idea or a system that has stopped keeping up, and you leave with our view on what it takes and what comes first. --- # A regulated valuation platform, live in four weeks https://www.rabblepop.com/work/archers-mena Client: Archers MENA. Sector: Property valuation · UAE. Status: In production. Retained.. Archers MENA is a property valuation firm in the UAE. Another agency quoted six figures for the platform; we scoped it, built it and had it live in four weeks — two connected applications covering the full lifecycle from request to regulator-format report. Retained since. A valuation firm is a workflow with a company around it. Two audiences. One system. The report is the product. Rus K. — We were quoted well over £100,000 by another agency. Rabblepop scoped the platform, built it and had it live in four weeks, and it now runs our whole practice — from the first request to the report we file with the regulator. Built to be handed over. If your process lives in email and spreadsheets --- # docuweave: legal documents in minutes, not hours https://www.rabblepop.com/work/docuweave Client: A law firm. Sector: Legal · document automation · product: docuweave. Status: Shipped. Productised.. A law firm re-keyed the same PDF templates for every client — hours of rote work per document. We built docuweave: it reads the source documents, extracts what the template needs and fills it in, with a lawyer reviewing before anything is issued. Minutes per document. Rote work with a law degree attached. Read. Extract. Fill. Review. Amir A. — Filling a client’s documents used to take one of our team the best part of an afternoon. It now takes minutes, and a lawyer still signs off every one — which is the only way we would have accepted it. Rabblepop understood that before we had to say it. Built as a product from the start. If your team re-types the same document every week --- # A booking system that runs itself https://www.rabblepop.com/work/beyondcars Client: BeyondCars. Sector: Automotive retail · UK. Status: Live.. A marketing site and viewing-booking system for a used-car dealership — edited by the people who sell the cars, and running without anyone administering it. The constraint that shaped everything: nobody would maintain it. Ali K. — We sell cars. We do not want to think about a website. Rabblepop built one we update ourselves in five minutes and a booking system that runs on its own — we have not needed to touch it since launch, which is exactly what we asked for. Built to be left alone. Most small-business software fails at maintenance, not at build. --- # The age of imagination https://www.rabblepop.com/writing/the-age-of-imagination When building software gets cheap, the constraint moves. What becomes scarce is knowing what is worth building at all.