Storylane

The tier structure answers the removal test, as it has for several vendors graded this batch. Model features are packaged as an ascending suite and metered: the free plan carries the free AI suite, Starter adds 20 minutes a month of video avatars, Growth and Premium raise that to 125 and 250 minutes, and Enterprise removes the cap. RepX, the agent that talks to website visitors, is not part of the demo suite but a separate product starting at $2,000 a month.

So the vendor sells this product with the model layer metered at the bottom and the agent detached entirely. What remains without any of it is the whole original proposition: capturing a product's own interface as screenshots, video or markup, assembling it into a guided interactive demo, publishing and embedding it, capturing leads and reporting on engagement. Ask what the platform does on the free tier, and price the model suite and the agent as the separate purchases they are.

Two autonomous surfaces, one of them with write access, and no published controls over either. The first is the assistant interface, included from the entry paid tier, which the vendor describes as letting a connected assistant build, modify and organise demos. That is write access to published customer facing material from outside the application, which is a materially larger surface than the read only assistant routes graded elsewhere in this batch.

Nothing published states whether an assistant can publish or unpublish a live demo, whether changes are logged, or whether the route can be restricted per user. The second is the separately purchased conversational agent that speaks with website visitors, qualifies them and books meetings, again with no published statement of what it may assert or when it escalates. Metering provides a partial bound, since generated presenter minutes are capped per tier. Ask whether an assistant connected through the interface can alter or unpublish a live demo, and whether those actions are logged.

The interface is documented down to the client products it connects to, and the model layer is not disclosed at all. On the published side the specificity is real: the assistant interface is named as a tier feature and names the two assistant products it connects with, generated presenter time is metered in minutes that are stated per tier, and the suite is broken into named components covering content assistance, voiceover and translation.

A buyer can tell exactly what is generated and how much they get. On the undisclosed side there is nothing: no provider, family or version for the generation, the voice synthesis, the translation or the conversational agent, and no statement of what review sits between generation and a demo going live under the customer's brand. Naming the assistant products that connect to the interface is not the same as naming the model that produces the output, and only the first is done here. Ask which models generate voice, translation and agent responses, and where they run.

Named customers and third party standing, with no measured result behind either. The vendor names large enterprise users individually in its own material, covering an infrastructure software company, a digital adoption platform and a conversation intelligence vendor, and states a customer count in the several hundreds, which is checkable attribution rather than a logo wall. Independent review platform standing is cited repeatedly and is genuine third party recognition.

What is absent is any outcome the vendor has measured: no conversion rate, no pipeline contribution, no engagement benchmark, no time to first demo, and no comparison against the alternative of a live demo call. The customer count and the enterprise names carry a date from an earlier publication and are not restated with a current figure. A case study section was not reached on this pass, so this reflects what was retrievable rather than an established absence. Ask for demo to opportunity conversion across a comparable customer set, with the period stated.

No sending here, and one adjacent capability that reaches people who took no action. Demos travel as links a customer places in their own email, embeds on their own site or shares directly, so sending obligations sit with whatever tool the customer sends from and the vendor does not claim otherwise. Graded in the middle of the band with that scope stated rather than at the floor, since the floor asserts an undisciplined sending product and this does not send.

Two capabilities sit at the edge of the axis. Lead capture forms are explicit and the visitor chooses what to supply. Account Reveal is not: from the Starter plan up, a visitor who views a demo without entering anything is resolved to an employer and reported to the seller, at up to 250, 2,500 or 10,000 companies a month by plan. Nothing published describes a suppression route for a person or organisation that does not want to be identified. Ask what opt out exists from company identification and how a viewer would find it.

Compliance is asserted and the instrument was not read. A privacy policy is published and linked from the consent banner on every page, the vendor states alignment with the European regulation alongside its security examination, and a cookie consent mechanism operates on the site. That is a reasonable baseline.

The policy itself was not retrieved on this pass, so retention periods, the lawful basis relied on, the rights exercise route and the treatment of viewer records are all unestablished and nothing here asserts they are absent. What raises the stakes is what the product collects about people who are not customers.

Every demo view generates engagement data on an identified or identifiable visitor, and from the Starter plan Account Reveal resolves anonymous viewers to their employer, so the platform accumulates behavioural records about prospects at scale on its customers' behalf. Ask for the retention period on viewer engagement records and the basis on which anonymous viewers are resolved to an organisation.

The demo content has clean provenance and one feature depends on data the vendor does not explain. Everything a customer publishes originates with them: their own interface captured as screenshots, video or markup through a browser extension, so there is no third party corpus behind the product and no brokered content. The exception is company identification.

Resolving an anonymous demo viewer to a named employer requires a third party dataset mapping network addresses or device signals to organisations, and nothing published names the provider, states the licence, describes the method or gives an accuracy rate. That is the same unexplained dependency this index records across visitor identification products generally, and it sits here inside a demo platform where a buyer may not think to ask. Ask which provider supplies the company identification data, on what licence, and what its match accuracy and false attribution rate are.

Nothing here runs on a platform belonging to somebody else. Demos are hosted on the vendor's own player and embedded by the customer on their own properties, and the capture extension records the customer's own application rather than reaching into a third party network, so no data is taken from anyone whose permission could be withdrawn.

Connected products are reached through each destination's own documented route, including a listing in the major customer record platform's own application marketplace on the higher tier, which is the sanctioned path for that integration rather than a private arrangement. The assistant interface is an outbound connection the customer initiates from their own assistant client.

It stops below the top band for the usual reason: no conformance position of the vendor's own is stated against any connected platform, so the grade rests on architecture rather than on a documented commitment a buyer could hold the vendor to.

One genuine redaction control, and the training question unanswered. The control is worth crediting because it addresses the real risk in this product: demos are captures of a live application, so real customer records, names and figures can end up inside published material, and a blur tool is available from the free tier onward to remove them. That is a stewardship feature rather than a security one and it is available to every user rather than gated.

Against it, nothing published states whether captured demo content, viewer engagement records or agent conversations are used to train or tune the generation features, or whether anything is aggregated across customers. The assistant interface adds a second open question, since demo content can be pulled into an external assistant client the vendor does not control and nothing states what that client may retain. Ask for written commitments on training and on retention by connected assistant clients.

The viewer is watched more thoroughly than they are told. Three mechanisms sit in this axis. Synthetic presenters and generated voiceover mean a prospect may be walked through a product by a person who does not exist, and nothing published states whether the viewer is told the presenter is generated. Company identification resolves a viewer who entered nothing to their employer and reports it to the seller.

And the separately purchased conversational agent speaks with website visitors directly, qualifying them and booking meetings. Against that, lead capture is explicit and consensual, the demo is plainly the vendor customer's own marketing material rather than anything disguised, and the vendor describes all three capabilities openly in its own commercial material rather than concealing them, which is why this sits in the middle of the band. Ask what a viewer is told about being identified, and whether the conversational agent discloses that it is not a person.

An assistant interface at the entry paid tier, which is the earliest any vendor in this batch exposes one. The vendor names it as a tier feature, names the two assistant client products it connects to, and states what it does, namely building, modifying and organising demos from outside the editor, which is a working and checkable route rather than a roadmap claim.

Around it sit named integrations to a messaging platform and a marketing automation system at lower tiers, a listing in the major customer record platform's marketplace at the third paid tier, a browser extension for capture, and embedding and link sharing as first class distribution.

It stops below the top band on two counts that both bear on who can actually reach the platform programmatically: conventional interface access is reserved to the quoted top tier rather than published, and no public reference, specification or endpoint list was reached on either pass. Ask what the interface exposes and why it sits only at the quoted tier.

Nothing on this question was reached. No hosting provider, region, processing location, residency election, subprocessor list or cross border transfer mechanism appears in any material retrieved on either pass, and the plans page did not render to a machine, so this reflects what was retrievable rather than an established absence of disclosure.

What is established is that the vendor states alignment with the European regulation alongside its security examination, which implies a transfer position without describing one. The question matters here because the platform hosts published demos serving worldwide viewers and accumulates engagement records identifying individuals and organisations across whatever markets its customers sell into, so the data has a geography even if the disclosure does not.

Single tenant and self hosted delivery are neither offered nor expected for a product of this shape. Ask where demo content and viewer records are processed and stored, and what governs transfers out of Europe.

Storylane runs a trust center that lists SOC 2 and GDPR compliance and an ISO 42001 certification covering its AI management system, with monitored controls across data, network, application, endpoint and corporate security and more than fifty policies and documents released on request. Its subprocessor list names AWS for infrastructure, with SendGrid, Slack, HubSpot, Zapier and MonetizeNow among the others.

The plans page states SOC 2 Type II and GDPR compliance on every plan, alongside role based access control, password protection and domain restricted access for demos, with SAML single sign on from Premium. No audit period or report date is shown on the public page.

Self serve rates cover most of the purchase. The free plan is a working product with no end date, Starter lists $40 a seat a month on annual billing and the same rate for each added seat, Growth lists $500 for five seats with extra seats at $100, and Premium lists $1,200 for ten, with monthly billing at $50, $625 and $1,500.

Usage limits are printed for each plan, covering video avatar minutes and Account Reveal volumes, and RepX shows starting prices for each band of monthly website visitors. What the page leaves unpriced are the add ons that move a larger team's bill, namely sandbox demos, hubs and presenter seats, and Enterprise, the only plan with API access, is quoted.

Demos can leave the platform in several formats. The plan comparison lists exports as GIF, video, PDF, document and markdown file, and its analytics section lists data export beside user level analytics and lead attribution. API access sits only on Enterprise. The terms of service, last updated August 6, 2025, describe ending an account as simply stopping use of the service and say nothing on retrieving demos, viewer analytics or RepX conversations after cancellation. A demo embedded on a customer's site keeps depending on Storylane to serve it.

There is no sending apparatus here at all. The platform operates no mailbox, no sending domain, no warmup, no rotation and no throttling, because a demo reaches a prospect as a link the customer puts in their own email, embeds on their own site, or shares directly. Graded in the middle of the band with that scope stated rather than at the floor, since the floor asserts a sending product without discipline and this does not send.

The one adjacent property worth recording is that hosted demos and their share links sit on the vendor's own domain, so link reputation attaches to the vendor and is shared across every customer using it, and nothing published addresses what happens if that domain is filtered by a recipient's mail security or blocked on a corporate network, which would affect all customers at once rather than one. Ask whether demos can be served from a customer's own domain, and what happens if the shared hosting domain is blocked.

The commercial ladder covers the market more completely than most records in this category, and it is evidenced by the prices rather than asserted in copy. A permanent free tier serves one person, the entry paid tier serves an individual contributor or a pair, the middle tier carries five seats, the tier above carries ten with enterprise controls, and a quoted arrangement sits above that, so every size from a single marketer to a large organisation has a described and mostly priced path.

Named enterprise customers evidence the top of that range concretely. Cross functional use is supported rather than claimed, with the same platform addressed to marketing, sales, presales and customer success. Translation into multiple languages supports an international claim at the content level.

It stops below the top band because no geographic coverage is published anywhere, with no regions, no market list and no statement of where the vendor sells or supports, and no industry breakdown appears.