Beacons rebuilding interactive email builder
Kelvin Liu, Founding Engineer at Beacons, on the email product development process
Rebuilding the email builder is really a move to pull more of the creator workflow into Beacons’s own product. Beacons already treats email as part of a broader creator operating system, alongside audience capture, storefront blocks, and CRM like fan data. An interactive builder lets creators change layouts and content inside Beacons instead of relying on a more static editor flow, while Litmus stays in the stack mainly as a rendering safety check across Gmail, Apple Mail, and Outlook.
-
Beacons’s core product has long been block based. Creators add modules for links, video, tips, checkout, email capture, or embeds to a mobile page. Rebuilding the email builder around that same block logic creates a more natural bridge between page building and email creation, and makes email feel like another native surface in the product, not a separate tool.
-
This also matches Beacons’s strategy of owning more of the creator relationship stack. The company has described link in bio as a wedge into a broader suite that helps creators capture fan data, email known fans, manage brand deals, and run more of the business in one place. A richer email builder is infrastructure for that strategy, not just a design upgrade.
-
The split with Litmus is typical in email software. Litmus is strongest as a preview and QA layer, where teams send generated HTML into Litmus and spot check how it renders across clients. Its code editor exists, but developer workflows often stay in internal tools or coding environments, then use Litmus at the end to catch client specific bugs.
The next step is deeper convergence between creator storefronts, CRM, and outbound messaging. As Beacons adds more native creation tools, email becomes less of a standalone feature and more of the channel that turns anonymous link traffic into owned audience, repeat engagement, and sales across the rest of the product suite.