Fable

Fable doubled as a step-by-step guide builder, and the capture flow is why. Fable recorded your product through a Chrome extension. You turned it on, clicked through the workflow you wanted to show, and the extension captured each state along the way. It then auto-stitched the screens into a finished walkthrough, which is the part that saved the most time. Instead of screenshotting and rebuilding a flow by hand, you ended up with a clickable demo from one pass through your own product.

An AI copilot named Quilly handled parts of the editing work. It helped with things like cleaning up captured text and generating demo content, so you spent less time on manual touch-ups. The no-code editor sat underneath it, letting you correct mistakes, rewrite copy and adjust the flow without touching code. For teams without a designer on hand, that combination kept the demo buildable in minutes rather than days.

Demos rarely look finished without your own branding. Fable let you apply logos and colors, then layer in interactive elements like hotspots and call-to-action buttons. You could build different versions of a demo for different use cases, each pointing at a different next step. Custom domains were supported too, so a demo could live on a help center, a landing page or a subdomain of your own site instead of a vendor URL.

Fable let you publish demos on your own domain, so a walkthrough on a help center or landing page looked like part of your site rather than a third-party tool. You could also embed a demo directly into a page or share it as a plain URL, which covered the common cases: a demo on a sales page, a guide in your docs, a link dropped into an email. Choosing between embed and link came down to where the buyer already was.

The platform tracked how buyers moved through a demo. You could see who opened it, which steps they reached and where they dropped off. That feedback loop turns a demo from a one-off asset into something you tune. Sales teams used it to spot which prospects actually engaged and to follow up while interest was still warm, rather than guessing from open rates alone.

Fable connected to common go-to-market tools, including HubSpot, Salesforce, Pardot, Marketo, Slack, Zapier, Notion, Webflow, Wix and WordPress. Webhooks delivered real-time updates on actions and events inside a demo, so a completed step or a shared link could trigger a workflow in a CRM or an automation platform. That kept demo activity flowing into the same systems the rest of the team already watched.

When Fable shut down, the team published the code as open source on GitHub under the sharefable organization. That means the tool did not vanish with the hosted service. Teams willing to run their own infrastructure could self-host it and keep capturing and publishing demos. The trade-off is real: you take on the setup, the hosting and the upkeep that the vendor used to handle, and you lose the managed support that came with a paid plan.