Folio3, a Salesforce Consulting, MSP, ISV and Agentforce Partner, replaced Shopify with Salesforce Sales Cloud for a Dubai off-plan master developer and connected it to NetSuite and a custom construction platform through MuleSoft.
Across 3 off-plan launches of about 1,200 units, the time to secure a unit fell from 4.5 days to 45 minutes, system double-bookings were eliminated (from 3.2%), and full SPA execution dropped from 12 business days to 1. A 6 to 8 person Folio3 team delivered the project in 9 months.
Key takeaways
Keep what works
NetSuite and the construction platform stayed; Salesforce took over sales and unit inventory.
One integration layer
MuleSoft runs 7 integrations, from five lead channels to NetSuite escrow billing.
Lock units in one place
A one-second hold in Salesforce, shared by every agent, broker and channel, ended launch double-bookings.
Key results and what drove them
| Metric | Before → After | What drove the change |
|---|---|---|
| Time to secure a unit (inquiry to unit hold) | 4.5 days → 45 minutes | Instant WhatsApp replies, automatic unit holds, online booking-fee receipts |
| System double-bookings during major launches | 3.2% → eliminated | Central, all-or-nothing unit locking through MuleSoft across all channels and brokers |
| Full SPA execution | 12 → 1 business day | Automatic deal handoff to NetSuite replaced manual SPA and escrow entry |
Measured across 3 off-plan launches (about 1,200 units) over the 8 months after go-live.
Admin work is where sales time goes. Salesforce’s seventh State of Sales report (4,050 sales professionals in 22 countries, 2026) found that reps spend 60% of their time not selling, on work like data entry.
By replacing fragmented e-commerce checkouts with an enterprise Salesforce and MuleSoft integration architecture, we eliminated inventory sync friction and transformed a multi-day booking cycle into a seamless digital experience.
Enterprise Integration Lead, Folio3
Project at a glance
| Item | Detail |
|---|---|
| Client | Dubai master developer managing large-scale, multi-phase off-plan residential portfolios and luxury high-rise towers |
| Platform replaced | Shopify (brand exposure, leads and reservation deposits) |
| Salesforce products | Sales Cloud (leads, deals, reservations, SPAs, unit inventory) |
| Integration layer | MuleSoft Anypoint Platform |
| Systems retained | NetSuite ERP (financial system of record) and the custom construction platform |
| Integrations | 7 core integrations |
| Timeline | 9 months, in 3 phases |
| Project team | 6 to 8 people across Salesforce, MuleSoft integration, NetSuite ERP, construction platform, QA, and project management and business analysis |
| Results measured | 3 off-plan launches, about 1,200 units, over 8 months after go-live |
| Folio3 UAE office | Folio3 FZ LLC, Dubai Internet City, 1st Floor, Building 14, Premises 105, Dubai, UAE. Tel: (04) 575 7041 |
| Implementation partner | Folio3 |
Why did a Dubai developer move off Shopify?
Shopify worked well for brand exposure and simple reservation deposits. As sales volumes grew, three gaps appeared:
- Milestone payment plans: Shopify’s cart is built for single, immediate checkouts. UAE off-plan sales run on construction-linked plans, for example 10% on booking, 40% during construction and 50% on handover.
- Shared inventory across brokers: during big launches, in-house agents and external brokers tried to reserve the same unit at once. There was no shared inventory lock across every broker and channel.
- KYC and AML documents: buyers must provide anti-money-laundering documents, Emirates ID and passport copies before a Sales and Purchase Agreement (SPA) is issued. Shopify was not set up to capture, check and store them securely.
Folio3 implements Sales Cloud with unit inventory, payment plans and reservation workflows built for real estate.
Before: how sales ran on Shopify
- Brand exposure, leads and reservation deposits
- Single, immediate checkout; no shared unit lock
NetSuite and the construction platform ran as separate applications. The back office keyed SPAs and escrow entries in by hand.
- Financial management and ledger
- Project execution and milestones
Figure 1. Before Folio3: Shopify, NetSuite and the construction platform ran separately.
Shopify captured leads and reservation deposits. NetSuite managed finance and the construction platform managed projects. The back office keyed SPAs and escrow entries in by hand.
After: what Folio3 built
- One integration layer for all 7 integrations
- Leads, deals, reservations and SPAs
- Unit inventory and holds
- Agreed payment plan
- Escrow billing schedule
- Invoices, receipts and balances
- Reservations, booking fees, document upload
- Certifies site milestones
Figure 2. After Folio3: every lead channel, Sales Cloud, NetSuite, the construction platform and the buyer portal connected through MuleSoft.
| Component | Role |
|---|---|
| Salesforce Sales Cloud | Leads, buyers, deals, reservations, SPAs, unit inventory and the agreed payment plan |
| MuleSoft Anypoint Platform | Integration layer for all lead channels, NetSuite, the construction platform, the buyer portal and document storage |
| NetSuite ERP | Financial system of record: escrow billing, invoices, receipts and balances |
| Custom construction platform | Site milestone certification and project execution (retained) |
| Custom buyer portal and payment gateway | Unit reservations, booking-fee payments, document upload and buyer self-service |
How does the new off-plan sales process work?
1. Every lead lands in Sales Cloud
| Channel | How it reaches Sales Cloud |
|---|---|
| Property portals | Leads from leading UAE real estate portals arrive through MuleSoft, which converts each portal’s format into a standard Salesforce lead. |
| An enterprise WhatsApp Business API provider, connected through MuleSoft. Chats are logged, buyer preferences are captured, and Salesforce assigns an agent instantly. | |
| Social media | Meta Lead Ads and LinkedIn Lead Gen Forms send leads to MuleSoft as soon as a form is submitted. |
| Campaign landing pages | Forms go through MuleSoft, which checks phone formats, lead source and campaign tracking (UTM tags) before anything reaches Salesforce. |
| AI qualification chatbot | A chatbot on the developer’s website and portal asks about budget, bedrooms and purchase timeline, then creates a qualified lead in Salesforce through MuleSoft. |
During launch surges, MuleSoft queues incoming inquiries to absorb high traffic and prevent dropped requests, so lead management in Sales Cloud keeps up even on launch day.
2. A unit is held within one second of reservation
A buyer reserving a unit on the portal triggers an instant check against the unit record in Sales Cloud. The unit is held within one second, and the portal receives a confirmation with a countdown (for example, 15 minutes) to pay the booking fee. If the countdown runs out, the hold is released instantly. Agents, brokers and the portal all work from the same live inventory.
3. The payment plan is set at reservation
Sales Cloud attaches the unit’s payment plan to the reservation, for example 10% on booking, 40% during construction and 50% on handover. Sales owns this agreed plan. Joint buyers, such as spouses or investment partners, share one payment plan for the unit.
4. The deal is handed off to NetSuite
Once the deal is agreed, MuleSoft sends it and its payment plan to NetSuite through a message queue (how Folio3 integrates NetSuite with MuleSoft), which delivers each update even if NetSuite is briefly unavailable. NetSuite sets up the buyer’s financial accounts and escrow billing schedule, then returns the customer ID and contract ID.
The system handoff takes seconds. The rest of the 1 business day is human checks:
| Checkpoint | What happens | Typical time |
|---|---|---|
| KYC and AML review | Compliance checks passport and Emirates ID copies and screens buyers against sanction lists | 1 to 3 hours |
| Agreement signing | The reservation agreement or SPA is e-signed by the buyer and countersigned by the developer | 2 to 6 hours |
| Deposit clearing | Treasury confirms the booking deposit has cleared in the DLD escrow account | 2 to 4 hours |
5. Construction milestones trigger billing
Once engineers certify a site milestone, the construction platform sends it through MuleSoft to NetSuite. NetSuite raises tax invoices and payment links against the buyer’s escrow billing schedule.
6. Payment status flows back to sales
Every 5 minutes, MuleSoft brings the receipt number, amount paid and outstanding balance from NetSuite into Sales Cloud. Agents see what each buyer has paid without touching the ledger.
7. KYC documents stay out of Salesforce storage
Buyers and brokers upload Emirates ID, passport and proof of address through the buyer portal or a secure WhatsApp link. MuleSoft streams the files to encrypted enterprise cloud storage (AES-256). Salesforce keeps only short-lived secure links and file details, which saves storage costs and supports data retention rules.
Which system owns which data?
| Data | System of record | Rule |
|---|---|---|
| Leads, buyers, deals, reservations, SPAs | Salesforce Sales Cloud | Sales teams update these; NetSuite receives the deal |
| Unit inventory and holds | Salesforce Sales Cloud | One inventory for all agents, brokers and channels |
| Agreed payment plan | Salesforce Sales Cloud | Set at reservation; sent to NetSuite at deal handoff |
| Escrow billing schedule, invoices, receipts | NetSuite ERP | Finance is authoritative; Sales Cloud shows a synced copy |
| Construction milestone certification | Custom construction platform | Engineering certifies; NetSuite bills from it |
| KYC documents | Encrypted cloud storage | Salesforce stores links only |
Design decisions Folio3 made
Why a custom buyer portal instead of Salesforce Experience Cloud?
Buyers use the portal occasionally after purchase, for example to see construction updates or pay an installment. Licensing Salesforce Experience Cloud for tens of thousands of occasional users would have added high recurring cost. A lightweight custom web app also gave the developer full control over luxury branding, interactive 3D floorplans and local UAE payment gateways.
Why keep billing in NetSuite instead of Salesforce Revenue Cloud?
NetSuite was already the general ledger, set up for UAE VAT, multi-subsidiary consolidation and the developer’s escrow bank connections. Moving billing into Salesforce Revenue Cloud would have added licensing without replacing NetSuite as the statutory ledger.
Why MuleSoft instead of direct connections?
With 7 integrations across sales, finance, construction, a buyer portal and many lead channels, direct system-to-system connections would multiply quickly. MuleSoft’s 2025 Connectivity Benchmark (1,050 IT leaders) found the average enterprise runs 897 applications, but only 29% are integrated, and IT teams spend 39% of their time building custom integrations.
Folio3’s MuleSoft consulting team used MuleSoft Anypoint Platform as one integration layer, so new channels or systems can be added without rewiring existing ones.
Folio3’s MuleSoft architects design one integration layer for CRM, ERP, portals and lead channels, so every new system plugs in without rewiring.
Is Salesforce or Shopify better for real estate sales?
| Need | Shopify (e-commerce retail cart) | Salesforce Sales Cloud (CRM and pipeline) |
|---|---|---|
| Core design | Online storefront and checkout | Leads, opportunities and pipeline |
| Payment structure | Single, immediate checkout | Multi-milestone payment plans |
| Inventory | Retail product stock | Unit records with live status and holds |
| Lead routing | Outside its core scope | Native assignment rules and lead management |
| Best fit | Retail and direct-to-consumer sales | Long, high-value deals run by a sales team |
For more on how property teams use the platform, read Folio3’s guide to Salesforce for real estate.
For architects: technical details
Salesforce data model
| Object | Purpose |
|---|---|
| Lead | Inbound inquiries and pre-qualification |
| Account and Contact | Buyer profiles; joint buyers are linked as multiple contacts on one deal |
| Opportunity | Core deal pipeline, managed with opportunity management stages |
| Reservation (custom, child of Opportunity) | Unit assignment and reservation details |
| SPA (custom, child of Opportunity) | UAE legal milestones for the Sales and Purchase Agreement |
| Unit (custom) | Property inventory: specs, price and live status (Available, On Hold, Reserved, Sold) |
| Payment Milestone (custom) | The agreed construction-linked payment plan |
The 7 integrations
| Integration | Timing | Returned to Salesforce |
|---|---|---|
| 1a. Sales Cloud → NetSuite (deal and payment plan) | Near real-time, via message queue | NetSuite customer ID and contract ID |
| 1b. NetSuite → Sales Cloud (payment status) | Scheduled, every 5 minutes | Receipt number, amount paid, outstanding balance |
| 2. Enterprise WhatsApp ↔ Sales Cloud | Real-time | Lead record |
| 3. Meta and LinkedIn Lead Ads → Sales Cloud | Real-time | Lead record |
| 4. Lead gateway: landing pages and property portals → Sales Cloud | Real-time, queued during launch surges | Lead record |
| 5. AI qualification chatbot → Sales Cloud | Real-time | Lead record |
| 6. Buyer portal and payment gateway ↔ Sales Cloud | Under 1 second | Hold confirmation and expiry time |
| 7. Construction platform → NetSuite | On milestone certification | Reaches Salesforce through 1b |
Connectors and nightly jobs
- Salesforce: Anypoint Connector for Salesforce.
- NetSuite: REST web services for real-time updates such as unit and buyer changes; SuiteTalk SOAP for complex accounting transformations and high-volume historical syncs.
- Nightly batch jobs: reconcile NetSuite ledger transactions with Salesforce payment milestones, clean up any orphaned unit holds left by dropped sessions or failed payment callbacks (expired holds are already released in real time), update property valuation indexes and broker performance totals, and archive audit logs.
How long did the implementation take?
Folio3 delivered the project in 9 months with a cross-functional team of 6 to 8 people covering Salesforce, MuleSoft integration, NetSuite ERP, the construction platform, quality assurance, and project management and business analysis, following its standard Salesforce implementation services approach.
- Ph 1Months 1 to 3: Architecture and Sales Cloud foundationData model, unit inventory, reservations and SPA objects.
- Ph 2Months 4 to 6: MuleSoft integration core and NetSuite integrationDeal handoff, payment status sync and escrow billing.
- Ph 3Months 7 to 9: Custom buyer portal, WhatsApp, lead channels and UATOne-second unit holds, lead gateway and user acceptance testing.
Which UAE rules shape the CRM design?
Salesforce and MuleSoft support the process. They do not make the developer compliant on their own.
- Oqood (Dubai): off-plan initial sales are registered with Dubai Land Department through the Oqood initial-sale service. Registration stays a DLD process outside Salesforce.
- Escrow (Dubai): Dubai Law No. 8 of 2007 requires off-plan buyer payments to go into project escrow accounts. Treasury confirms each booking deposit in the escrow account, and NetSuite bills against the escrow schedule.
- KYC and AML: compliance reviews identity documents and screens buyers against sanction lists before an SPA is issued.
- VAT: residential and commercial property are treated differently. See the UAE Federal Tax Authority. NetSuite applies VAT; finance sets the treatment. For joint buyers, NetSuite invoices one primary billing entity to match DLD escrow records.
- Personal data: buyer data from portals, WhatsApp, social and chatbot channels falls under the UAE Federal Decree-Law No. 45 of 2021 on Personal Data Protection. Landing pages record each buyer’s consent, and identity documents are stored encrypted. Folio3 itself is ISO 27001 certified for information security management.
Conclusion
Folio3 showed that a Dubai developer does not need to replace every system to modernise off-plan sales. Moving sales and inventory into Salesforce, keeping NetSuite and the construction platform, and connecting them with MuleSoft cut the time to secure a unit from 4.5 days to 45 minutes and full SPA execution from 12 business days to 1.
Frequently asked questions
Who implements Salesforce, MuleSoft and NetSuite for real estate developers in Dubai?
Folio3 implemented Salesforce Sales Cloud, MuleSoft and NetSuite integration for a Dubai off-plan master developer in 9 months, with a 6 to 8 person delivery team. Folio3 has an office in Dubai Internet City. Across 3 launches of about 1,200 units, the time to secure a unit fell from 4.5 days to 45 minutes.
How do you stop two brokers booking the same off-plan unit during a launch?
In Folio3’s Dubai project, the buyer portal holds the unit in Salesforce through MuleSoft within one second and starts a 15-minute countdown to pay the booking fee. Unpaid holds are released instantly. This eliminated system double-bookings, which had been 3.2% on Shopify.
Why does SPA execution still take a day after Salesforce and NetSuite are integrated?
The system handoff takes seconds. In Folio3’s project, the remaining time is human checks: KYC and AML review (1 to 3 hours), e-signing the SPA (2 to 6 hours) and clearing the booking deposit in the DLD escrow account (2 to 4 hours).
Who should own the off-plan payment plan, Salesforce or NetSuite?
Both, for different stages. In Folio3’s design, Salesforce owns the plan agreed at reservation; NetSuite owns the escrow billing schedule, invoices and receipts. Joint buyers share one plan and NetSuite bills one primary billing entity.
Should Dubai buyers’ KYC documents be stored in Salesforce?
Not in this Folio3 project. Emirates ID and passport files go through MuleSoft to encrypted cloud storage, and Salesforce keeps only short-lived secure links. This cuts Salesforce storage cost and supports retention rules.
How do you handle lead spikes from property portals during an off-plan launch?
Folio3 routed every portal, WhatsApp, social and landing-page lead through MuleSoft, which converts each source into one lead format and queues traffic during launch surges so Salesforce limits are not hit.
Do Salesforce and MuleSoft handle DLD or Oqood registration?
No. Oqood registration stays a Dubai Land Department process. In Folio3’s design, Salesforce tracks the sale and NetSuite handles escrow billing.
Sources
- Salesforce: State of Sales, 7th edition (2026)
- MuleSoft: 2025 Connectivity Benchmark Report
- Salesforce Help: Lead management
- MuleSoft Anypoint Platform
- Dubai Land Department: Register the initial sale (Oqood)
- Dubai Law No. 8 of 2007 on escrow accounts
- UAE Federal Tax Authority
- UAE Legislation: Federal Decree-Law No. 45 of 2021
About the author
About Folio3
Folio3 has an office in Dubai Internet City and is an official Agentforce Partner with 50+ Salesforce certifications, 100+ CRM architects, developers and consultants, ISO 9001 and ISO 27001 certification, and 15+ years of CRM experience.
Folio3’s NetSuite practice was named NetSuite Alliance Partner of the Year for the Middle East in 2025.
Learn more about our Salesforce integration services and NetSuite MuleSoft integration.
More Folio3 Salesforce case studies: 40% faster quote-to-cash for a glass and door installer, 35% faster sales operations for an equipment manufacturer and 90% less manual reconciliation for a food verification company.
Folio3 connects Salesforce, MuleSoft and NetSuite so units, payment plans and escrow billing stay in sync from reservation to handover.