Explore where a fintech, crypto, investment or property idea may enter regulated activity before coding, marketing or taking customer money on an untested licensing assumption. Show who holds funds, owns assets, gives recommendations and contracts with the customer.
Draw the money and responsibility flow
Show who holds funds, owns assets, gives recommendations and contracts with the customer. A technology label does not determine the regulatory position. A founder building financial software has a different question from a business arranging investments or custody. Relevant real estate activity also needs review against RERA requirements.
Ask about the right permission
CBB licensing, sandbox routes, fund-related services and crypto proposals need qualified assessment of the actual model. Sandbox participation should not be assumed to permit a full commercial launch. Prepare the founders’ roles, customer types, risk controls and outsourcing dependencies so the authority discussion is specific rather than speculative.
Design the test around boundaries
An enquiry can organise a regulatory briefing and coordinate appropriately authorised advisers. It does not itself provide regulated services or certify that a test is exempt. Define which parts of the idea can be researched without executing the regulated activity. Approval, eligibility and any testing conditions remain matters for the relevant authority.
Specific enquiries within this scope
Choose the task that matches your situation. Availability, responsible providers and any required professional permissions must be established in the written scope.
Scope to agree in writing
- Product responsibility diagram brief
- CBB or RERA question list
- Regulatory evidence preparation map
- Research-versus-live-test boundary notes
Prepare for the enquiry
- Customer journey and payment flow
- Assets or advice involved
- Target customers and jurisdictions
- Proposed technology and partners
Before you take the next step
Can I launch first and seek a licence later?
Do not base a launch plan on that assumption. Determine whether the actual activity needs permission before performing it, particularly where customer money, investments or regulated property work is involved.
Does calling the product software settle the issue?
No. The actual services, money flows, customer relationship and responsibilities matter. A technology interface can still facilitate an activity that requires regulatory review.
What can be researched before a regulated launch?
Customer needs and product assumptions can often be explored, but define the test carefully. Obtain advice before the experiment handles assets, gives regulated advice or performs a permission-dependent activity.
Continue your planning
Corporate governance and secretarial planning
Build practical ownership, approval and risk habits that support a growing business without mistaking a policy template for professional compliance or a complete governance system.
02Business licences and activities
Translate your product idea into specific activities so you can validate commercial demand without accidentally treating research, licensing and operational permission as the same milestone.
03Business plans and funding readiness
Turn customer evidence, cost assumptions and a specific use of funds into a finance brief before approaching banks, investors, Tamkeen programmes or potential acquisition partners.