Questions, answered plainly.

Rabblepop is a software product studio based in London. It builds web applications, mobile apps and the internal systems that businesses run on — CRMs, portals, booking systems, reporting and workflow tools. It is led by Zeki Mirza, who is both a head of product at a large international software agency and the engineer who writes the code on Rabblepop projects.

Two things. First, the person who defines the product is the person who builds it, so there is no handover between a strategist and a delivery team — the gap where most projects lose money. Second, Rabblepop sells the definition work separately as a fixed-price Scoping Sprint, which means the recommendation at the end can honestly be “don’t build this”.

Founders with an idea that isn’t yet a specification, and established small and mid-sized businesses that need a custom system built or an existing one rescued. Recent work includes a property valuation platform for a firm in the UAE and a booking system for a UK car dealership.

A one to two week, fixed-price engagement that turns an idea into a defined, costed product. You receive a product definition, a technical approach, a risk register, a costed delivery plan and a written recommendation. The document belongs to you and can be taken to any developer. If you go on to build with Rabblepop, the fee is deducted from the build cost.

It depends almost entirely on scope, and any number given before the work is understood is a guess. That is why scoping is sold as a separate fixed-price engagement: you get a real number, with the assumptions it rests on written down, before committing to a build. Book a call and you will get an honest range for your situation within half an hour.

React, Next.js and TypeScript on the front end; React Native for mobile; Postgres with a typed ORM for data; AWS or Vercel for infrastructure, defined as code with separate staging and production environments. The stack is deliberately conventional so that another developer could maintain it — including replacing Rabblepop.

Yes, extensively — for exploring approaches, drafting and stress-testing scope documents, building throwaway prototypes quickly, and moving faster through mechanical work. It does not decide what to build, and it does not carry the responsibility for the result. AI makes a good scope faster to produce; it does not make a bad scope good.

Yes. You own the code, the infrastructure and the documentation. Everything is built on a conventional, widely-used stack with no proprietary components, specifically so that you can hand it to another developer whenever you want to. Being replaceable is a design goal, not a risk.

It is a fair question and the honest answer is that a studio this size takes on one large build at a time, which is why capacity is stated openly rather than oversold. The mitigations are structural: conventional technology choices, documented decisions, infrastructure as code and no proprietary dependencies — so any competent developer can pick the work up. For larger or more time-critical projects, that risk should be part of the conversation on the first call.

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 fit. You can book at rabblepop.com/contact or email hello@rabblepop.com.