Skip to main content

Why add a marketplace

Your agents’ day runs through your CRM, but not only through it. They pull a valuation from one site, a cash offer from another, check a showing’s feedback in a third, and keep their own checklists and calculators in spreadsheets. Each time, they leave the contact they were working on. A marketplace brings those tools onto the contact, already knowing which agent is looking and at which client.

Agents stay in your CRM

The tools agents used to switch tabs for show up on the contact. The more apps an agent turns on, the more of their day happens in your product.

Your customers build on you

Most apps are built by brokerages, teams and agents for their own workflows, often with AI coding tools in an afternoon. Your contact page becomes where they put them.

Leaving means leaving their tools

When a brokerage’s own process lives on your contact page, switching CRMs means giving it up or building it again. That’s a reason to stay.

More integrations, none to build

Each app is built, hosted and supported by its publisher. You stop fielding one-off integration requests, and every approved app works on your contacts.

Vendors come to you

Valuation, cash offer, showing and transaction tools list themselves in your marketplace. You review them instead of courting them.

Parity with Follow Up Boss

Embedded apps are part of what agents know from Follow Up Boss. Apps built for FUB can come to your CRM with a few changes, not a rewrite.

Built by your own customers

Some apps come from vendors. Most are built by the people who use your CRM every day. A team lead wants the team’s listing checklist on every contact. A brokerage wants its referral form filled in with the client’s name. An agent wants a commission calculator that uses their own split. They used to need a developer for that. Now they build it themselves. What they need is a place to put it, and the context to make it useful. Each app opens already knowing which agent is looking at which contact, so the builder needs no integration with your CRM and no API key from you. Every tool they add makes your CRM fit them better.

Why Rollout’s marketplace

A marketplace you build yourself is a platform project, and a security program on top of it. With Rollout, you add two components to your pages and a token endpoint to your server. Rollout runs the rest.

The platform, run for you

An open ecosystem

Anyone can build an app for your marketplace without paying Rollout: a vendor, a brokerage, a team, or one agent with an idea. They register the app, list it in your marketplace, and you review it like any other. Nobody needs a contract with Rollout, or with you, to start building on your CRM. Publishers work with Rollout commercially when they want more than a listing:
  • One app across every CRM. A publisher with a Follow Up Boss app, or an app in several marketplaces, can have Rollout make it work the same way in every CRM, reading each CRM’s data through Rollout’s Universal API.
  • Rollout Verified. Rollout reviews and monitors the app’s security, and the app carries a Rollout Verified badge in your marketplace and your review queue.
So your marketplace fills with apps from day one, and the apps that matter most to your agents can come with Rollout’s review behind them.

Security your security team can sign off

Rollout is SOC 2 Type 2 compliant, and the report is available on request. A marketplace puts other people’s software on your contact page, so Rollout limits what an app can do, and checks whether it’s safe to approve:

Isolated from your page

Every app runs sandboxed, two frames deep, from Rollout’s origin. It can’t read your page, its storage or its cookies.

Only the data it needs

Apps never receive a contact’s emails or phone numbers. You choose which of the remaining fields each app gets.

Verified apps, scanned before review

For a Rollout Verified app, Rollout checks its TLS, framing headers, known vulnerabilities, third-party scripts and where it sends data, and shows the results beside the live preview.

Verified apps, monitored after approval

A Rollout Verified app is re-checked daily and on every code change. One that fails is suspended for everyone at once.

A log of every launch

Which user opened which app on which contact, and what it received. Searchable, exportable, and streamed to your SIEM.

Verified publishers, under contract

Every publisher is identity-verified and signs a data processing agreement with Rollout. If an incident affects your marketplace, Rollout tells you within 24 hours.
Security and data has the details of how apps are isolated and what they receive.

Compatible with Follow Up Boss

The marketplace follows Follow Up Boss’s embedded apps model: the same signed context, and the same protocol for showing an app. Publishers and brokerages that built for FUB bring their apps with a few changes, and your marketplace starts with apps your agents may already know.

You keep the decisions

You approve each app, choose what it receives, decide whether agents, admins or both can turn apps on, and suspend an app whenever you want.

Next

See what your users see, from an agent’s contact page to your review queue.