Beacons builds emails from blocks

Diving deeper into

Kelvin Liu, Founding Engineer at Beacons, on the email product development process

Interview
we sort of abstracted that stuff away into blocks.
Analyzed 5 sources

This reveals that Beacons built email like a product system, not like a one off HTML file. Instead of asking creators or internal teams to edit raw table based email code, Beacons stores a message as reusable content blocks with settings, then compiles that structure into sendable HTML at the end. That makes the builder easier to use, keeps layouts consistent, and shifts the hard part of email engineering into Beacons’s rendering layer.

  • The same block logic already sat at the center of Beacons’s core link in bio product. Creators add blocks for links, media, tips, or commerce, and Beacons turns those pieces into a mobile page. The email product extends that pattern into a new surface, with block types like rich text, images, and links rendered into email HTML instead of web pages.
  • That architecture also explains the Litmus workflow. Teams using Parcel or Litmus as an editor usually paste HTML in, tweak code, and preview it. Beacons instead sends test emails from its own system into Litmus, because the final HTML is generated downstream from React based block definitions and properties, not maintained as a hand edited source file.
  • The product implication is tighter lock in. When a creator builds emails, landing pages, audience capture, and commerce inside the same block system, switching out gets harder because the content is not just text, it is structured data, layouts, and workflows tied to Beacons’s builder. That is the same kind of product depth creator software like ConvertKit and Linktree have been racing toward from different starting points.

The next step is deeper convergence, where one creator asset model powers pages, emails, storefronts, and CRM together. If Beacons keeps expanding the block system across those surfaces, it can turn a simple link in bio tool into a creator operating layer, where every new product reuses the same underlying content objects and makes the suite more valuable as a whole.