Block-first email product strategy
Kelvin Liu, Founding Engineer at Beacons, on the email product development process
This shows Beacons had already moved from building an email editor to maintaining an email component system. Once a creator product has stable blocks for text, images, and links, the hard part stops being adding new content types and starts being making every variation render safely in Gmail, Apple Mail, and especially Outlook. That is why Beacons keeps the product block based in React and uses Litmus mainly as a QA layer, not as the place where emails are authored.
-
At Beacons, the unit of product is the block, not the finished email. Creators fill in properties on prebuilt blocks, then Beacons turns that into HTML. That makes coverage of core blocks strategically important, because one solid text or image block can power many layouts without exposing creators to raw email code.
-
Podia describes a similar pattern. Early on, Litmus catches big rendering bugs, then usage narrows to repeated preview cycles on the clients that matter most. In practice, email builder teams do not need endless new blocks, they need confidence that a limited set of primitives survives the messy long tail of email clients.
-
For Beacons, email is not a standalone feature, it is part of a broader creator operating stack built to help creators capture contact info and own audience relationships off platform. Stable basic blocks are enough to unlock that workflow, because the value comes from tying email to the creator CRM and storefront, not from inventing exotic email modules.
The next step is deeper integration, not more block sprawl. Creator platforms like Beacons will keep turning email into a managed output of a larger system, where audience capture, segmentation, and monetization live in one place and the email layer becomes more reliable, interactive, and invisible to the creator using it.