What should a demo in a partner directory show?

The connection being set up, including the authorisation step, and data actually moving -- with the partner's interface visible so the reader recognises their own tool. Three or four steps: it answers one question rather than touring your product.

Should I make one demo for all integrations?

No. Each reader is looking for their own tool and will not translate from a generic example. Integration demos are short enough that one per major partner is realistic, and each is reusable in docs, sales and your changelog.

How does an integration demo help the partner?

Their team has to explain integrations they did not build to customers asking questions they cannot answer. A link removes that work -- and being the integration that generates fewest support questions is a genuine advantage with whoever decides directory placement.

← Back to blog

Demos for Partner and Integration Directories

August 28, 2026

Integration directories, app marketplaces and partner pages have a common property: a company you do not control is describing your product to customers who trust them more than you.

You usually get a logo, a paragraph and a link, and the paragraph is doing work no paragraph can do.

The reader has a specific question

Nobody arrives at a partner listing wondering what your product is in general. They are asking one thing: does this work with the tool I already use, and what does that actually look like?

A demo showing the connection being made, with the partner's product visibly on screen, answers it in a way a compatibility claim cannot.

What to record for this audience

The connection being set up, including the authorisation step people worry about.
Data actually moving, since that is the claim being evaluated.
The partner's interface, so the reader recognises their own tool.
Short. Three or four steps; this is one question, not a product tour.

It helps the partner too

Partner teams have to explain integrations they did not build, to customers asking questions they cannot answer. Giving them a link removes work from their side.

That is also the practical route to better placement in a directory: being the integration that generates fewest support questions is a real advantage with the team who decides ordering.

Keep one per major integration

A single generic integration demo serves nobody well, because each reader is looking for their own tool and will not translate.

These are short enough that one per major partner is realistic, and each one is reusable in your own docs, your sales conversations and your changelog.

Frequently asked questions

What should a demo in a partner directory show?: The connection being set up, including the authorisation step, and data actually moving -- with the partner's interface visible so the reader recognises their own tool. Three or four steps: it answers one question rather than touring your product.
Should I make one demo for all integrations?: No. Each reader is looking for their own tool and will not translate from a generic example. Integration demos are short enough that one per major partner is realistic, and each is reusable in docs, sales and your changelog.
How does an integration demo help the partner?: Their team has to explain integrations they did not build to customers asking questions they cannot answer. A link removes that work -- and being the integration that generates fewest support questions is a genuine advantage with whoever decides directory placement.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →