Do you take on consultancy-only mandates, or only when paired with portal work?
Either. The two practices are independent. Many engagements are pure consultancy — a
structuring memo, an operating-model review, a market-entry pathway. Portal work is
sometimes the output of a consultancy phase, sometimes a standalone build for a client
who has already decided.
What does an engagement typically cost, and how do you bill?
We price per stage on a fixed fee, agreed in writing before the stage begins. The brief
phase is no-fee for qualified engagements; structure and build phases are fixed-fee with
named deliverables. Ongoing operations (portal monitoring, retained consultancy) move to a
monthly retainer with a defined scope. We do not bill hourly — incentives there are wrong.
How quickly can you start?
The brief call is usually within the working week. Substantive work starts when scope and
terms are signed — typically one to two weeks from first contact, faster where confidential
documents are pre-shared. We hold a deliberate cap on concurrent engagements; if we are
fully committed, we will say so plainly rather than over-promise.
Can you operate under our paper — NDA, MSA, DPA — rather than yours?
Yes. We are comfortable reviewing and signing your standard paper. Where your terms conflict
with how we deliver (for example, a clause that requires us to subcontract to named third
parties), we will flag it in redlines rather than ignore it. NDAs are signed before
substantive discussion of confidential matters, on request.
What languages does the team actually work in?
English is the default working language. Arabic and Russian are operating languages —
memos, contracts, and client communication can be conducted in any of the three.
Translation between them is in-house, not outsourced, so technical and legal precision
carries through.
How do we verify Quantum Group FZE as a counterparty?
Quantum Group FZE is a licensed establishment under the Umm Al Quwain Free Trade Zone
Authority. On request we provide the trade license, registered address, manager details,
and any supporting KYC documentation your counterparty diligence requires. Bank
confirmations and reference letters are arranged through the engagement letter.
How do you use AI, and how is data confidentiality handled?
AI is embedded in both practices: research and document analysis on the consultancy side,
Claude Code and Codex on the portal-development side. That gives the partner reach and
speed that previously required a team. Client documents and codebases are handled only
through enterprise-tier contracts with zero data retention, or inside a client-controlled
environment, and only with written consent. The AI scope is fixed in the engagement
letter. Final judgement, code review and accountability stay with the partner.
What does the AI do, and what does the partner do personally?
The AI does the first pass — market scans, regulatory-landscape synthesis, processing of
document corpora, draft code and draft artefacts. The partner frames the problem,
validates the findings, makes the call, writes the recommendation and signs the
deliverable. No recommendation and no production code leaves us without explicit review
and sign-off by a named partner. AI multiplies the work; the accountability stays
fully human.
What changes for the client when AI is used in portal development?
Three measurable effects. First, speed: feature delivery is 2–3× faster through code
generation, automated legacy analysis and auto-generated tests. Second, quality: every
PR is run through static analysis, security review and regression checks before it
reaches the partner. Third, documentation: API specs, ADRs and runbooks are written
alongside the code, not after the fact. The partner stays accountable for the
architecture and the final code review.
What does the AI not do in your practice?
It does not make decisions for the client — the recommendation is always written and
defended by the partner. It does not communicate with the client on our behalf — every
exchange goes through the named partner. It does not produce code that ships to
production without human code review. It does not access client data beyond the scope
fixed in the engagement letter. And it is not used as a substitute for context — if a
task requires knowledge of your business, the regulation, or the industry, that's
partner work, not AI work.
