Guide
10 Embeddable Widget Examples (and What They Get Right)
Short answer: the best embeddable widgets (Calendly, Stripe, Typeform, Intercom, DocuSign, Plaid, Loom, Google Maps, Trustpilot, Cal.com) all do one job, fit into the host's page in more than one way, take the host's look through a few settings, and keep the sensitive part inside their own frame. Each one below teaches one of those lessons.
These are descriptions of how each embed is publicly documented to work, not reviews, and none of these companies has anything to do with Ordana. Details change, so check each provider's own docs before you build against them.
1. Calendly: one widget, three placements
Calendly's booking page can be embedded inline on a page, opened as a popup from a floating button, or opened from a text link. Same scheduler, three ways in.
The lesson: offer placements, not one shape. A host's sidebar, landing page and settings screen want different things. A widget that only works as a full-width block gets embedded in one of them.
2. Stripe: the sensitive part never leaves the provider's frame
Stripe's Payment Element and its embedded Checkout put a payment form inside the merchant's own page, but the card fields live in Stripe-hosted frames. The merchant styles them through a set of appearance variables (colours, radius, fonts) instead of reaching into the form.
The lesson: isolate what matters, theme through variables. The host gets a native look; the provider keeps control of the part that would be dangerous to share.
3. Typeform: the host owns the moment
Typeform forms embed inline, full page, or as a popup, slider, popover or side tab, and several of those can be opened from the host's own button.
The lesson: let the host decide when the widget appears. A survey that interrupts at the wrong moment gets removed. One the host opens from its own button, at the step where it makes sense, stays.
4. Intercom: identity is handed over, not asked for again
Intercom's Messenger installs with a JavaScript snippet, and the host passes who the signed-in user is. Intercom also documents an identity verification step in which the host's server signs the user's id, so one user can't pose as another.
The lesson: accept the host's sign-in, and make it verifiable. A user who is already signed in to the host shouldn't meet a second login wall inside a widget.
5. DocuSign: embedded signing keeps the user in the host's flow
With embedded signing, an app shows the DocuSign signing experience inside its own flow instead of sending the signer to an email link. DocuSign still runs the signing itself and keeps the record.
The lesson: the provider keeps the trust-heavy part, the host keeps the user. Neither side has to do the other's job.
6. Plaid Link: a small, explicit result
Plaid Link is a drop-in flow where a user picks their bank and connects an account. The bank login goes to Plaid, not to the app, and what comes back to the app is a short-lived token it exchanges on its own server.
The lesson: hand back a narrow, declared output. The host gets exactly what it needs to continue, and nothing it would then have to protect.
7. Loom: widgets can create, not just display
Loom videos embed as a player on any page. Loom has also offered an SDK for recording, so a product can let its users record a video without leaving it.
The lesson: the strongest widgets produce something inside the host. A player is content. A recorder is a capability the host's product didn't have yesterday.
8. Google Maps: a URL is the whole contract
The Maps Embed API is an iframe whose URL says what to show: a place, directions, a search, a view. No SDK, no build step.
The lesson: make the simplest integration a URL with parameters. If a host can embed your widget by pasting one tag, you've removed the meeting where somebody estimates the work.
9. Trustpilot: every embed is distribution for the maker
Trustpilot's TrustBox widgets show a business's reviews and rating on its own site, added with a script and a small element. Each one also shows Trustpilot's name to that site's visitors.
The lesson: an embed is a channel. Every host that adds your widget puts your product in front of users you'd never have reached, which is exactly why a widget integration converts better than a link.
10. Cal.com: meet the host's stack
Cal.com is open-source scheduling with embeds for inline, a floating button and a popup on click, plus packages for popular front-end frameworks and theming options such as brand colour and light or dark.
The lesson: the less a host has to adapt, the more hosts you get. Meet them in their framework and their palette.
What the good ones have in common
- One job. Book a meeting, take a payment, sign a document. Not a product tour.
- Several placements. Inline, full page, popup or modal from the host's own button.
- The host's look, through settings. Colours, radius, fonts, light or dark. Never by restyling the inside.
- Isolation for the sensitive part. Cards, bank logins and signatures stay in the provider's frame.
- Identity handed over. The host's signed-in user isn't asked to sign in again from scratch.
- A small, declared output. A token, a booked slot, a signed envelope. Nothing more.
- A visible maker. The provider's name is there, quietly, which is what makes every embed a channel.
What none of these examples show
Look at who pays. In almost every example above, the host is the customer: the business that embeds a scheduler, a payment form, a chat launcher or a review badge pays the maker for it. That works when you're a category leader that hosts come looking for.
A small SaaS isn't. Nobody is searching for your widget yet. The model that works for you runs the other way: the widget is sold through the host, to the host's users, and the host keeps a share of each sale. The host takes no risk, gets a new feature, and earns when it earns, so saying yes is easy.
You can build the technical half with the patterns above; how to build an embeddable widget walks through it. The commercial half is what Ordana sets up: the price, the free uses per host, the share the host keeps (10 to 90%, your call) and automatic payouts, all agreed before anyone integrates. Ordana's fee is 10% of each sale, taken from your share.
Frequently asked questions
What is an embeddable widget?
A piece of one product that another product can place inside its own pages, usually as an iframe or a script snippet. The user gets the feature without leaving the site or app they're in. Scheduling pages, payment forms, chat launchers and review badges are the familiar examples.
What do the best embeddable widgets have in common?
They do one job, offer more than one placement (inline, popup, full page), take the host's look through a few settings, keep the sensitive part inside their own frame, accept the user's identity from the host instead of asking again, and hand back a small, explicit result.
Who pays for an embeddable widget?
In most well-known examples the host pays the widget's maker: the business embedding a scheduler, a payment form or a chat launcher is the customer. The other model is a widget sold through the host, where the host's users pay and the host keeps a share of each sale.
Can a small SaaS build an embeddable widget like these?
Yes. The patterns these companies use (one job, a few placements, theming from settings, an iframe for isolation, sign-in and payment inside the frame) don't need a big team. A coding agent can package one feature of an existing product this way in a short session.
On Ordana, a SaaS lists one feature as a widget with its terms set, and other products add it to theirs. List your SaaS as a widget, or read every guide in widget integrations.
Related reading:
- How to Embed a Third-Party Widget in Your SaaS — the host's side.
- How to Sell a SaaS Feature as a Widget — packaging and listing one.
- The 3 Types of SaaS Integration: Placement, Capability, Handoff — where an embed fits.