Build, Operate, Transfer — usually shortened to BOT — is a well-established model used across infrastructure, technology and outsourced operations. A specialist partner builds a function from scratch, operates it to a defined standard for a period, and then transfers it — fully functional, documented and staffed — to the client's own team. It is not the same as traditional outsourcing, where the work stays with the provider indefinitely.
Applied to compliance, risk and legal functions inside a scaling investment firm, the same logic holds. A firm that is spinning out, launching, or growing past its early structure usually does not have — and should not necessarily build immediately — a large permanent compliance, risk or legal team. What it needs is the function built properly, run to an institutional standard while the firm is at its most exposed, and then handed over in good order once the firm has the scale, budget and maturity to run it itself.
The objective is never to make the firm permanently dependent on an external compliance officer. It is to get the function built and proven, then hand it to the firm in better shape than if they had tried to build it themselves from a standing start — if and when that handover makes sense.
Why this matters for scaling firms
Hedge funds, market makers, proprietary trading firms and crypto asset businesses face a particular problem when scaling: the compliance, risk and legal infrastructure expected by the FCA, by prime brokers, and by institutional allocators has to exist from day one — but the firm rarely has the budget, certainty, or need for a full permanent team at that stage. Hiring too early wastes capital on a role that does not yet have enough to do. Hiring too late risks regulatory exposure, failed due diligence, and lost institutional capital.
Build, Operate, Transfer basis solves this directly. The function exists from the point the firm needs it — built to the standard a regulator or an institutional allocator expects — without requiring the firm to commit to a full-time hire before it is ready to. As the firm grows, the function scales with it. And when the time comes for a permanent in-house hire, the transition is a handover, not a rebuild.
Externally hosted, or built to transfer in-house — the firm decides
A common misconception about Build, Operate, Transfer is that the third stage is mandatory and fixed in advance. It isn't. The model is a hybrid that flexes to what each firm actually wants, and that decision does not need to be made on day one.
Some firms know from the outset that they never want a large internal compliance, risk or legal headcount — the function stays externally hosted permanently, scaling in hours and scope as the firm grows, with no desk, no internal infrastructure, and no recruitment overhead to maintain. Others want the function built and proven externally specifically so that it can be transferred to an internal hire once the firm has the AUM, revenue or certainty to justify one — at which point the handover is clean because the framework, documentation and institutional knowledge already exist. Many firms don't decide which path they want until well into the Operate stage, once they have a clearer sense of their own trajectory. Reg Advantage builds the function the same way regardless of which path is eventually chosen — externally hosted indefinitely, or built with a transfer in mind, are simply two different endings to the same model.
How BOT runs alongside the SMF 16/17 question
Build, Operate, Transfer is a way of resourcing and scaling a function. It is a separate question from who holds the SMF 16/17 badge — and the two run in parallel rather than one determining the other. There are two common configurations.
Where the firm has its own SMF 16/17 — an existing employee, a director, a CCO or COO who already holds or is appointed to the badge — Reg Advantage's Build, Operate, Transfer work runs entirely in support of that person. The firm's own SMF holder carries the regulatory accountability; Reg Advantage builds the policy suite, runs monitoring and testing, manages the compliance calendar, and provides the independent challenge a well-run function needs. The BOT engagement scales up or down around that person without ever touching who holds the badge.
Where the firm does not yet have its own SMF 16/17 — typically a spin-out or early-stage firm — James Lane can take the badge directly, as a transitional leader, structured as a fractional employment relationship in line with FCA expectations. In this configuration, Build, Operate, Transfer describes James's own engagement: he builds the function, operates it as the named accountable individual, and — if and when the firm is ready — transfers the badge to an internal hire he has helped identify and onboard, with the function already proven and documented. Reg Advantage's broader resource can sit alongside this engagement too, scaling the workload without changing who is accountable for it. See how the FCA views the appointment of fractional CCOs to SMF 16/17 →
The common thread is that BOT describes how the work gets built, resourced and scaled. Whether the badge sits with the firm's own person from day one, or with James as a transitional measure until the firm is ready to take it in-house, is a separate decision — and one that can change over time without disrupting the underlying BOT engagement.
Whether you are building from scratch, mid-way through operating, or planning a transfer to an in-house hire, a short call will clarify the right next step.
Request a call →