Table of Contents
- Gather: a regulated investment platform with a £30 minimum
- What does FCA regulated app development involve before any code is written?
- How does a £30 minimum investment change identity checks?
- Support that works without a phone call per account
- Launch, then a seed round eight weeks later
- What do most guides to FCA regulated app development leave out?
- Where a regulated build still catches teams out
- What we would tell a founder before sprint one
- Frequently Asked Questions
- Next steps: start with the regulatory questions
For Gather, an FCA-regulated multi-currency investment platform with a small minimum deposit, Foundry 5’s FCA regulated app development began with three weeks of regulatory questions before any product code. The FCA’s 2025/26 Q2 operating metrics show 99.5% of applications were determined within the statutory deadline, so the regulator is rarely the bottleneck. Unanswered permissions questions are. Most advice on FCA regulated app development starts with a checklist. The Gather build started with questions. A wrong guess about permissions is the most expensive mistake in a regulated product, because you find out after the features exist.
For Gather, the first three weeks went on asking what the firm was permitted to do, and only then did Foundry 5 open the code editor. The decisions below appear in the order they were made, with what each one saved and what a founder should settle before sprint one.
Gather: a regulated investment platform with a £30 minimum
Gather is an FCA-regulated, multi-currency retail investment platform with a £30 minimum investment, according to the Gather project brief. It was built through the fintech software development practice at Foundry 5. Two constraints shaped almost every decision: what the firm’s regulatory permissions allowed the product to do, and a deposit small enough that costs had to be designed around it.
A retail investor opening an account at the minimum cannot be served slowly or expensively, but the account sits inside the same regulated perimeter as a far larger one. The product has to be affordable at its smallest size and compliant at every size, and those two requirements pull against each other more than a feature list admits.
The argument of this post is that regulatory constraints, not the feature list, set the order of a build. With an FCA regulated investment app, you do not decide what to build and then ask whether it is allowed. You establish what is allowed, price the smallest account, and then choose features. The sections below follow that order, from the first three weeks to the seed round.
What does FCA regulated app development involve before any code is written?
For Gather, Foundry 5 treated FCA regulated app development as a sequencing problem. The first three weeks went on regulatory questions: which permissions the firm holds and what the product is allowed to do. Product code started only once those answers existed, so no feature was built that the firm’s permissions could not support.
The first decision was the least visible one. Nobody can screenshot three weeks of questions, and a founder watching the clock may read them as delay. The opposite is true. A feature built on a wrong assumption about permissions gets cut later, after the design, engineering and testing time has been spent.
Which permissions does the firm hold?
Authorisation belongs to the firm, not to the app. The permissions on a firm’s record define which regulated activities it may carry out, and that list decides which parts of a product can exist at all. That list is the first thing Foundry 5 asks for, before anything is estimated. The team reads what the permissions cover and writes the product scope against them instead of assuming.
What is the product allowed to do?
Holding permissions is one question. Mapping them to screens and journeys is another. A product that lets a customer do something outside those permissions creates a problem that polish cannot fix. Answering this early meant the Gather scope was drawn around what the product was allowed to do, rather than trimmed back after the build.
In any regulated build, the practical step is to list each planned journey, such as opening an account, funding it or placing an investment, and write down which permission supports it. A journey with no matching permission leaves the plan until an adviser says otherwise.
None of this is about waiting for the regulator. As of November 2026, the FCA’s Authorisations operating service metrics for 2025/26 Q2 report that 99.5% of applications across all metric areas were determined within the statutory deadline. In our experience, preparation is the variable: unanswered questions about permissions are where the time disappears.
How does a £30 minimum investment change identity checks?
A £30 minimum investment sets a hard ceiling on what an identity check can cost. If verification costs more than the first deposit, every small account loses money before it invests. That rule shaped how Gather’s identity verification was designed, because the check had to cost less than the deposit it was opening the account for.
An account opened with the minimum has to clear know-your-customer (KYC) and identity verification, plus the anti-money laundering (AML) checks that sit alongside them, before it can invest. If those steps cost more than £30 to run, the firm has spent more than the customer deposited. Repeat that across every small account and the model is broken before the first trade.
This is where many fintech plans fail. The financial model prices verification as a rounding error because the founder pictured a larger first deposit. It is a unit-economics input, and it has to be tested against the minimum deposit before a provider or approach is chosen.
Keeping KYC costs low on a small minimum investment comes down to ordering. Fix the ceiling first: the check must cost less than the deposit. Then evaluate every verification and AML approach against that ceiling, instead of picking the most elaborate option and hoping the numbers work. Which checks run, and when, is a product decision made with the firm’s compliance adviser, not a purely technical one.
A low minimum is no reason to loosen verification. The obligations are the same at £30 as at any other size. What changes is how carefully the cost of meeting them is designed, and that design starts before the build, not after the invoice.
Support that works without a phone call per account
A £30 account cannot carry the cost of a phone call each. Gather’s support had to be designed so a customer could get an answer without one. That fits FCA Consumer Duty thinking, where outcomes such as consumer understanding and consumer support shape journey design from the start.
This followed from the identity-check decision. An account at the minimum that needs a phone call to resolve a routine question costs more to serve than it is worth, so the design response was clear in-app journeys that a customer can follow without ringing anyone. Support was built into the product itself, not added as a help desk at launch.
The regulatory side points the same way. The FCA’s FG22/5 guidance on the Consumer Duty covers Principle 12 and sets out outcomes such as consumer understanding and consumer support, which shape product and journey design rather than sitting in a policy document. A customer who cannot understand what they are doing in an app, or cannot get help, is a Consumer Duty problem as well as a cost problem.
Design for the smallest account and the larger ones are covered. Test the journeys with real users before launch, and confirm specific journeys and wording with the firm’s compliance adviser.
Launch, then a seed round eight weeks later
Gather launched as an FCA-regulated investment platform and raised its seed round eight weeks later. Nobody should read that as one event causing the other. A regulated product with its permissions questions already answered did give the company something concrete to show when the conversation turned to funding.
The facts are brief: Gather launched, and the seed round was raised 8 weeks after launch. Claiming the launch caused the round would be tidy and unprovable. A founder can take something narrower and more useful from the sequence.
Investors reasonably ask what a product is permitted to do, and a team that settled that early has an answer ready. A retail investment platform development effort that starts with permissions also produces a clearer scope, which makes the product easier to explain. For the full account of the project, read Gather’s case studywhich covers the product in more detail than this post.
What do most guides to FCA regulated app development leave out?
Most guides to FCA regulated app development list requirements, costs and tech stacks in the abstract and rarely show the order in which decisions were made, but the Gather build at Foundry 5 suggests order matters most: permissions first, then the economics of a £30 deposit, then support design, then features.
Open any long guide to regulated fintech app development in the UK and the shape is familiar: requirements, cost, tech stack, and a compliance checklist near the end. All of it is accurate in the abstract. None of it says what to do on the first morning of week one.
A checklist tells you what exists, while a build needs to know what comes first, and that gap has three parts.
The first is order. Permissions came before product code on Gather, the economics of the £30 deposit came before the choice of identity-check approach, and support design came before the feature list was fixed. Each step narrowed the next. Reverse the order and each step has to be redone.
The second is the effect of a low minimum. Guides written for larger tickets assume verification and support costs disappear into the account size. At £30 they do not. A low minimum changes what FCA compliant app development costs per customer, and it changes which options are viable at all.
The third is the cost of skipping the permissions questions. Nobody can quote it in advance because it arrives in pieces: a feature redesigned, a journey rewritten, a release held while someone checks whether the product may do what it does. The best teams pay a small, known price early rather than a large, unknown one later.
Constraints decide a regulated build, not the feature list. Gather is the clearest example of how Foundry 5, a London studio for fintech app development, approaches regulated fintech product development.
Where a regulated build still catches teams out
Regulated builds go wrong when teams treat permissions as a late checklist. Adding a feature because a competitor ships it can take a product outside what the firm is allowed to do. Gather spent three weeks on permissions questions before any product code so that no feature outran them. Check every new feature against the firm’s permissions first.
These are general lessons, not Gather incidents, and they apply to any FCA compliant investment app. The first is the late checklist. As an illustration, say a team builds for four months, then sends the product to compliance and finds that two journeys describe activities the firm cannot carry out. The rework costs more than the questions would have.
The second is the competitor assumption. A team sees a rival offering a feature and adds it to the roadmap, but the rival may hold different permissions. That the rival ships it proves nothing about what your firm may do. Competitor screenshots are not regulatory evidence.
The third is the later feature. A product launches inside its permissions, then grows, and each new feature is a fresh question about regulated activities whose answer may differ from the one at launch. AI features raise their own questions, and our piece on FCA regulated AI development covers what compliance will and will not let through.
Keep an audit trail of why each scope decision was made, so the reasoning survives staff changes and review. Before building, put your permissions and product questions to your compliance adviser and, where needed, to the FCA itself. This post is not legal advice, so confirm every specific with your own compliance or legal adviser.
What we would tell a founder before sprint one
Before sprint one, settle four things: which permissions the firm holds, what the product may do, what an identity check can cost against your minimum deposit, and how a customer gets help without a phone call. Those answers decide the build. Features follow from them rather than the other way round.
Each item below comes from a Gather decision, not from theory:
- Settle permissions and allowed product scope first. Gather spent its first three weeks here, before any product code.
- Test unit economics against your minimum deposit. Gather’s identity checks had to cost less than the £30 deposit.
- Design support for the smallest account. If a £30 account needs a phone call, the model leaks.
- Test in-app journeys with real users, and refine them on what you learn.
- Choose a studio that asks regulatory questions before it estimates features.
The fourth item rests on FCA guidance, not on opinion. The regulator’s good practice on consumer understanding describes tools such as calculators, videos, walkthroughs and summaries being tested to make sure they help customers, then refined based on user evidence. That is guidance rather than a statistic, and it applies to the smallest account as much as the largest.
The fifth item is the one founders skip, because estimates arrive faster than questions. A studio that quotes features in the first call has not yet asked what the firm may do. Once the scope is settled, turning it into a working product follows from it, and mobile app development works best when it starts from a scope that compliance has already read. Ask what an app is allowed to contain, not how fast it can ship.
Frequently Asked Questions
Do you need FCA authorisation to build an investment app?
The firm carrying out regulated activities needs the relevant FCA authorisation, and its permissions define what the app may do. In FCA regulated app development, Foundry 5 therefore asks about permissions first. Whether your own firm or plan needs authorisation is a question for your compliance or legal adviser, and the answer shapes the whole scope.
How long does FCA authorisation take?
No generic duration applies to every application, so Foundry 5 does not quote a single figure and instead points to the FCA’s published determination data. As of November 2026, the FCA’s Authorisations operating service metrics for 2025/26 Q2 report that 99.5% of applications across all metric areas were determined within the statutory deadline. In our experience, preparation is the usual variable, though your own timeline depends on your application.
Does an app development company need to be FCA regulated?
The firm offering the regulated service holds the permissions, and a development studio builds the product for it, so confirm the arrangement with the firm’s compliance adviser. A good studio asks about permissions before it estimates. For FCA-authorised firms, Foundry 5 builds the product and does not claim to hold those permissions itself.
How long does it take to build an FCA regulated investment app?
It depends on scope and permissions, so Foundry 5 does not quote a generic number for FCA regulated app development, and any figure without that context is a guess. The only Gather timing stated here is that the first three weeks went on regulatory questions before any product code. Those weeks decided what the build contained.
How do you keep KYC costs low on a small minimum investment?
Design the identity-check cost to sit below the minimum deposit, because a check that costs more than the deposit breaks the economics of the account. Gather’s £30 minimum forced that discipline. Test every verification option against the deposit before choosing a provider, and agree the checks themselves with your compliance adviser.
Next steps: start with the regulatory questions
In FCA regulated app development, Foundry 5 asks the regulatory questions first and designs around the product’s real constraints. If you are planning a regulated product, a 30-minute discovery call is the simplest way to test your scope against them.
Each Gather decision made the next one cheaper: permissions set the scope, the £30 minimum capped the cost of an identity check, and support was designed to work without a phone call. A useful first exercise for your own build is to list every planned journey and write beside each one the permission that supports it and the cost of the identity check behind it. Every gap in that list is a question to settle before the first sprint, and an FCA regulated investment app is far cheaper to build once those gaps are closed.
Planning a regulated product? If you are building for an FCA-authorised firm and want a studio that asks about permissions before it estimates, book a free 30-minute discovery call with Foundry 5. The call is a direct conversation about whether your scope fits.