A business plan that answers the bank, the regulator and the authority, not a pitch deck.

A pitch deck sells a story to someone deciding whether to invest: the market is large, growth compounds, the team can execute. A bank or a regulator is not deciding whether to invest — it is deciding whether the business, as described, is the business it will actually see in the account or under the licence. The same ambitious revenue curve that reads as conviction to an investor reads as a volume the bank did not expect to a compliance officer, and a mismatch between what was projected at onboarding and what the account later shows is itself a flag, independent of whether the business is doing well or badly.

The fix is not a smaller number. It is a plan that states its assumptions plainly — the activity, the customer base, the expected currencies and counterparties — so that whatever the business later does, it was already consistent with what was said.

Six things have to agree with each other inside one plan: the licensed activity, as named on the application; the corporate and ownership structure; the expected banking flows, in currency and counterparty terms; the operating model, including any contracts already in place; the headcount the plan implies; and the premises that headcount and that activity actually need. A plan that proposes fifteen staff on a licence sized for three, or revenue flows that do not match the activity named on the application, creates its own question before anyone else asks one.

This is why the plan is written alongside the licence application and the bank-readiness file rather than beforehand in isolation — each one constrains the others, and reconciling them once is cheaper than discovering the mismatch at the bank's desk.

A financial model attached to a plan that nobody checked against the narrative is common, and it is usually the first thing a careful reader finds wrong. The model has to use the same assumptions as the prose — the same customer count, the same pricing, the same timeline to revenue — and it has to produce the same transaction pattern the bank file describes. Where the business raises external capital, the model also has to show how that capital is used, because an investor, a bank and a regulator each read the use-of-funds line differently.

A document issued outside the UAE — a certificate of incorporation, a power of attorney, a personal document for a foreign director — usually has to travel a chain before a UAE authority will accept it: notarisation in the country that issued it, authentication by that country's own foreign ministry, and processing by the UAE's diplomatic mission in that country, after which it enters whatever further step the receiving UAE authority specifies. The exact chain depends on the document's country of origin and on which UAE authority is receiving it, and that authority decides what it will accept — we do not set the requirement, and we do not perform the notarisation, the foreign-ministry authentication or the UAE mission's own step ourselves.

What we do is work out which chain applies to which document, sequence the steps so nothing arrives at the wrong stage, and track the pack until every document the application needs is in the form the receiving authority specified.

The business plan, the financial model and the corporate profile are not three separate deliverables filed separately — they are one file read by up to four different readers, each checking a different part of it. The licence application reads the activity and the structure. The bank reads the flows and the source-of-funds narrative that sits beside it. A regulator, where one applies, reads the governance and the controls that follow from the business model the plan describes. We write and check the pack as one piece precisely so a reader of any one part does not find it disagreeing with another.