Do I really need engineering for this, or can I outsource it?

**You need real engineering, and only part of it is outsourceable.** Building a public embed is not a landing-page job. **What you must own in-house:** **-** The embed contract (versioning, backward compatibility) **-** Security and data handling (your code runs in someone else's app) **-** Uptime, because a host outage caused by you burns trust fast **What you can outsource:** **-** Docs, sandbox polish, and framework example snippets **-** The badge landing page and its copy If you do not have engineering that can commit to maintaining this, run Strategic Partnerships first and build the embed later.

What if my product does not have a standalone feature to embed?

**Then this Tactic is not for you yet, and that is fine.** An embed needs one feature that delivers value on its own inside another app. **Ask honestly:** Is there a single block of my product a user could get value from in one session, without the rest of my app around it? A scheduler, a form builder, a checkout, a chat box, a calculator? **If no:** Do not force it. Use Partner-Led reach through Strategic Partnerships or Affiliate Programs instead. You can revisit embedding once a clean, separable feature exists.

Will hosts just copy my feature instead of embedding it?

**Some will, most will not, and here is why.** **Reality:** Building and maintaining a good version of your feature is expensive. Most host apps would rather rent it than own the maintenance forever. That is the entire pitch: you save them the build. **Your protection:** Keep improving the embed so renting always beats building. Make the install trivial and the maintenance invisible. The apps most likely to copy you are large enough to build anything anyway, so target the ones for whom embedding is clearly cheaper than building.

How long before this drives real signups?

**Expect 3-6 months before it compounds.** This is a long-term motion, not a campaign. **Typical shape:** **-** Month 1-2: Building the embed, no installs yet **-** Month 2-4: First hand-won hosts, slow trickle of signups **-** Month 4-6: Docs and social proof make new hosts easier, installs stack **-** Month 6+: Hosts start finding you, the loop compounds The payoff is that installs do not decay. Old hosts keep sending users long after you win them.

How do I stop an update from breaking apps that embed me?

**Version everything and pin hosts to a version.** **1.** Ship the embed as v1, then v2, never a rolling 'latest' that changes under hosts **2.** Let hosts opt in to a new version, never force it silently **3.** Keep old versions running until hosts migrate **4.** Test against a matrix of common host setups before every release **5.** Have a rollback plan, because your bug is their outage This discipline is non-negotiable. It is the difference between hosts trusting you long-term and ripping you out after one bad deploy.

Should I charge the host or the end user, and what about the badge?

**Common model: badge on free, paid removes it, host pays.** **The badge rule:** Free and low tiers show 'Powered by [You]'. Paid tiers remove it. The free badge is your acquisition engine, so guard it. **Who pays:** Usually the host app pays you (per seat, per usage, or flat) and bills their own users however they like. For volume hosts, add a revenue share so they are motivated to promote you, which overlaps neatly with Affiliate Programs. **Pick simplicity early.** A clear per-usage price beats a clever pricing model no host can predict.

🧩 Borrow Their Audience

Embedded Widget & SDK Distribution

Wrap one standalone feature as an embeddable widget, iframe, or SDK that other products drop into their own app. Every host platform then puts your feature (and a "Powered by" attribution loop) in front of their users, so their audience becomes your top-of-funnel without you spending on it.

14 min read

Last updated: Jul 24, 2026

💬

"We stopped thinking of ourselves as an email tool and started thinking of ourselves as an embeddable building block. Today our drag-and-drop builder runs inside more than a thousand other applications. Their users are our users, and we did not pay to acquire a single one of them."

Embedded SaaS Growth Lead

📅 Your First 90 Days

Setup Warm-up Outreach

Weeks 1-3

Isolate the embeddable feature + pick delivery format

⏱ ~1-2 days planning

Weeks 4-7

Build the embed (iframe/SDK) + attribution loop

⏱ core engineering block

Weeks 8-10

Ship docs, sandbox, and pricing tiers

⏱ ~1 week

Weeks 11-13

Pitch first 5-10 host apps + measure installs

⏱ ~30 min/day outreach

Ongoing

Support hosts, iterate embed, expand partner list

⏱ ongoing

Weeks 1-3

Isolate the embeddable feature + pick delivery format

⏱ ~1-2 days planning

Weeks 4-7

Build the embed (iframe/SDK) + attribution loop

⏱ core engineering block

Weeks 8-10

Ship docs, sandbox, and pricing tiers

⏱ ~1 week

Weeks 11-13

Pitch first 5-10 host apps + measure installs

⏱ ~30 min/day outreach

Ongoing

Support hosts, iterate embed, expand partner list

⏱ ongoing

Is this for you?

Great fit if...

✓Your product has one clear feature that works as a standalone block (a builder, a widget, a checkout, a scheduler, a chat box)
✓That feature solves a problem OTHER apps have but do not want to build themselves
✓You have (or can hire) engineering that can ship and maintain a stable public embed and API
✓You sell B2B or B2B2C, so a host app reaching its own users is genuinely your buyer
✓You are playing a long game and can support partners for months before installs compound

Try something else if...

Your product only makes sense as a full end-to-end app with no separable component
You cannot commit engineering to versioning, security patches, and uptime for an embed other companies depend on
You need customers this quarter (this is a long-term, compounding motion, not a quick win)
Your feature exposes sensitive data that a host app legally cannot pass to a third party
You are pre-product and still changing the core feature weekly (embeds need a stable contract)

Want partner reach without building an embed? Try Strategic Partnerships →

Not the right fit?

If Embedded Widget & SDK Distribution doesn't match your situation, consider these alternative tactics that achieve similar goals:

Strategic Partnerships

Build integration and co-marketing partnerships with complementary products.

advanced•medium•medium term

What to expect

3-6 months

Before installs meaningfully compound

Every host

Adds its whole user base to your top-of-funnel

Exponential

Reach as installs stack on each other

Quick math: This is a distribution asset, not a campaign. The first few host apps are slow and manual to win. Once the embed is stable and well documented, each new host multiplies your surface area, and hosts start finding you. Treat the embed as a product with its own roadmap, not a side project.

An embed is one feature, not your whole product. The host app already has its own login, navigation, and billing. You are giving them a single block that drops into their UI. Your first job is to find the smallest self-contained feature that another app would happily rent instead of build.

Think about the tools you already trust as embedded blocks:

🧩 The Intercom chat bubble lives inside thousands of other products🧩 Calendly, Stripe Checkout, Typeform, and Disqus are all one feature dropped into someone else's app

Score your features for embeddability

A feature is a good embed candidate when it ticks most of these:

It works on its own without the rest of your app around it
Other apps have this exact need but do not want to build it
It has a narrow, stable job (one input, one clear output)
It does not need deep access to the host app's private data
A user can get value in one session without leaving the host app

Write the one-line embed pitch

If you cannot finish this sentence cleanly, the feature is not isolated enough yet:

"Any app can drop in [your feature] in an afternoon instead of building it in [X weeks]."
Name the exact host apps that would want it
Name what the host app saves by embedding (build time, maintenance, expertise)

⚠️ Reality check before you build anything

This Tactic only works if your product has a genuinely standalone, embeddable component. If your value is the whole end-to-end app and none of it makes sense on its own inside another product, do not force an embed. Run a Partner-Led motion through Strategic Partnerships or Affiliate Programs instead, and come back to this later.

Conversation Flow

A host asks "why should we keep your badge?"

Be honest: the badge is the deal on the free tier, and it is removable on paid.

“Fair question. The free tier is free because the badge sends us a trickle of signups, that is the trade. If the badge does not fit your brand, the paid tier removes it and adds [custom theming / SLA]. Most hosts start free, see the value, then upgrade to go badge-free.”

A host worries the embed will slow their app

Address performance head-on with specifics, not reassurance.

“Valid concern, it runs inside your app. The embed loads async so it never blocks your page, it is under [X]kb, and it is pinned to a version so our deploys never touch your live install. Here is the sandbox so you can test load time yourself before committing.”

A host asks about their users' data

Data handling is where embed deals live or die. Be precise.

“Here is exactly what happens: we process [X] to render the feature, we store [Y], and [Z] never leaves your app. We can put that in the agreement and share our data-handling doc. If your users are in a regulated space, tell me and we will scope what is safe to pass.”

A host wants a revenue share to promote you

Say yes if they can actually drive volume. This ties into Affiliate Programs.

“Happy to. If you feature the embed and drive installs, we can share [X]% of revenue from users who came through you, tracked by referral. It aligns us: the more you promote it, the more you earn, and the more of your users we both reach.”