PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Engagement scope - proposed scope

White Label Real Estate Crowdfunding Provider: What to Check

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Typical scoping questions

Who owns the source and the investor records?

  • Name the repository, the database and the register when you ask. A right to use software is not ownership, and the gap shows the first time an auditor wants a query run.

What happens the day you stop paying?

  • On a rental, access usually ends with the subscription, and the investor list may sit behind it. On a platform you own, you keep running and pay for hosting. Ask for the answer in writing.

Whose license does the offering run under?

  • It should be yours. A provider hinting that its own permissions cover your raise is describing a structure your counsel needs to see. With us, the license or exemption and each property's legal structure are yours to secure.

Where does investor money actually sit?

  • Not with a software seller. Custody and trustee arrangements belong with banks and licensed institutions you appoint. Our platform records the money on its ledger; it never holds the funds.

Is the ownership record appended or overwritten?

  • If holdings are edited in place, a beneficial-owner request turns into a reconstruction. Ask to see a transfer land as a new row while the old one stays.

What happens when a payment callback arrives twice?

  • Look for a double-entry ledger holding integers, balances computed from entries and an idempotency key on every order. Without the key, a retry will sooner or later mint a second allocation.

Who can release a withdrawal or a payout?

  • A single admin is a risk to you from inside. Ask for a second approver on withdrawals and a compliance, finance and execution chain on each distribution batch, shown live.

Where is the list of what is not included?

  • Every build here has open work. A seller with no written list either has not audited or is not saying. Ours sits on this page and names sandbox rails, screening and more.

The Six-Step Delivery Process

What happens after you say yes, in order, including the phase many sellers never mention.

Put your brand on every surface

  • Name, logo, colors and domain across the investor web app, the mobile app, the operator console, certificates, statements and emails, in the locales you launch with. Investors and staff only ever see your business.

Stand it up on infrastructure you control

  • Your servers, your PostgreSQL, your object storage and your own accounts for KYC, payments, email, push and SMS. We keep no copy running on our side, and the platform does not report back to us.

Set the operating rules

  • Country profile, currencies, minimums, investment limits, marketplace rules, fee schedules and feature flags. The thirty catalog roles are mapped to your actual team, with maker-checker thresholds you choose rather than defaults.

Your team runs the full cycle

  • A property moves from draft through underwriting and committee review to live. An investor passes KYC and subscribes. A payout batch clears compliance review and finance approval, then executes, with the audit log open alongside.

The work that comes before real money

  • Step six is where this page differs from most in the category. We would rather lose a deal on day zero than have an operator learn about the hardening scope after deposits arrive.

Red Flags That Mean Walk Away

Five sales lines that should close the meeting

  • "The platform is fully compliant, launch whenever you like." Code cannot be compliant for you. Compliance is a state of your operation: your license, your counsel, your procedures. A seller claiming otherwise has not been asked the hard question yet.
  • "We are regulated, and investor funds are safe with us." A software supplier is neither your regulator's counterparty nor your custodian. Safeguarding money is an arrangement with banks and licensed firms, never a feature in a product sheet.
  • "Bank-grade security, built in." Ask what that means in code, then ask for the written security review. No document usually means no review.
  • "You will not need the source." When the core asset of the business is the investor register, renting the system that holds it is a strategic exposure, not a convenience.

What a Real Estate Crowdfunding Platform Has to Get Right

The unglamorous parts that decide whether a platform holds up once real investors and an auditor arrive.

What We Have Not Done Yet

The limits our own security review found, set out before a sale instead of after one.

The audited build is not production-ready

  • Our technical dossier uses exactly those words, and we repeat them here unchanged. Admin route gating, webhook signature checks native to each provider and enforced lockout and password rules are hardening work finished against your environment before the platform holds real money.
  • The permissions package defines thirty roles by resource, action and scope, yet the audited build enforces routes with a simpler administrator check. We wire the full model to your org chart during delivery. Until then, no one should call it least privilege.

Sanctions and PEP screening is not running

  • The data model for screening exists; nothing screens at runtime. Regulated operation needs a screening vendor connected and an escalation policy written, and we quote that work instead of implying it is done.

Some things are not in the box at all

  • Native mobile document capture is simulated in the audited build. There is no tenant isolation, so one deployment carries one operator brand. A durable queue with leases, retries and dead-lettering is deployment work, and lifecycle test coverage is an add-on.

What we will never claim

  • Set against those limits, the finished parts are real and can be shown: the 77-model domain, the double-entry engine, SPVs and share classes, the append-only register, idempotent orders, payout batches through two approvers, the secondary market, exit windows, sale voting, about thirty operator workspaces and a ten-document suite your reviewers can read on day one.

Modelled Reference Deployment

An illustration, not a client story. Omnistu has not yet delivered a real estate crowdfunding deployment, so this shows how the platform would be configured for one kind of buyer. Every figure describes the build and none reports a result.

A Regional Syndicator Moving Its Raises Online

  • A property syndicator in the UAE that raises from private investors by email and spreadsheet today, and wants its own branded platform with Arabic and English, AED wallets and room to add a second market later.
  • The situation: investors tracked across several spreadsheets, payouts worked out by hand and emailed as attachments, and holders with no way out of a deal until the building sells.
  • The configuration: each deal in its own SPV with share classes, the append-only register answering who owns what, certificates and statements in the investor portal, payout batches cleared by compliance and finance before execution, and a secondary market so an exit does not wait for a sale.
  • What would still be scoped: the hardening package, live payment rails and KYC on the syndicator's own accounts, sanctions and PEP screening, and jurisdiction settings reviewed with its counsel. The license or exemption and the custody arrangements stay the syndicator's to secure.

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Fundrise , GetStake or any other real estate investment platform.

White label real estate crowdfunding platform describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com