Thereβs a dozen compliance platforms out there β but they donβt understand you.
Most will give you a checklist, some APIs, and try to upsell you. Meanwhile as a founder, all you actually need is to close enterprise deals (and quickly).
Delve gets you fully compliant with SOC 2, HIPAA, ISO 27001, and GDPR in 15 hours or less. Their security experts will even get on the Zoom to help you close that deal (legit).
The results speak for themselvesβ¦
Lovable: Got SOC 2 in 20 hours
11x: Saved 143 hours and unlocked $2.3M ARR
Bland AI: Got SOC 2 and unlocked $500k ARR in 7 days
You have options, but only one chance to close your enterprise contract. Pick the right compliance partner from the start.
Use code BDE1KOFF for $1,000 off. Plus, theyβll even ship you AirPod Pros once youβre compliant (which will beβ¦ soon).

Back in March we dropped one of the more anticipated product launches of the year, and it was a total disaster.
While that definitely wasnβt the plan, I learned a whole lot from the experience and the company today is ultimately better off because of it.
The βI fucked up, donβt do what I didβ posts always seem to resonate the most, so here I am doing my civic duty. Iβll share the full backstory and my biggest takeaways so you can avoid making similar mistakes.
Iβll start with some contextβ¦
beehiiv is home to tens of thousands of the top newsletters in the world. We offer users the ability to create beautiful websites and newsletters, and equip them with a full suite of growth and monetization tools.
But we had one hard constraint in the platform that was causing issues for more advanced users: you could only have a single design for your newsletter.
If you wanted a header image with your logo, a grey background, black text, and blue links (hey that sounds like Big Desk Energy) β¦ well, you would design that once and each email you send on beehiiv would look like that.
But if you wanted to send an email with a black background, all of your emails would now have a black background (i.e. there was just a single global design). Or if you wanted to launch a special weekend edition with a different style and aesthetic: impossible.
To make matters worse, we created an isolated and cumbersome design experience, dubbed the βDesign Lab,β where you would go to make these updates. Youβd have to leave the post you were working on to make design updates, then return back to your work after.
We made the assumption when we initially built beehiiv that each newsletter would only ever have a single consistent design. And while that was true for most users, more and more advanced users were growing frustrated with the limitations.
We kicked off the year making this a top priority. The writing experience is arguably the most important workflow in the platform; ensuring it was seamless, flexible, and enjoyable was critical.

Early Figma files creating the new experience
We built this beautiful new experience where users could toggle between writing mode (i.e. focused) and design mode (i.e. to update styles) right in the editor. Design updates would only impact that particular post, and users could save the changes as new templates to reuse again in the future.

New in-editor design experience
Those templates would now be available to browse and reuse in the brand new template library. We also launched a handful of professionally designed quick-start templates for our users to leverage.

Template library
Lastly, we added net new design capabilities to support even more granular control and creativity. beehiiv is home to some of the most beautiful newsletters youβll find in your inbox, and we added even more flexibility.

Some beautiful newsletters on beehiiv
All in all, this initiative was supposed to be a home run. It removed all of the previous limitations of the platform and provided a much more refined experience. After a few weeks of QA we flipped the switch to launch it on March 27th.
We expected to take a victory lap for nailing yet another big launch; instead, it broke everything.
Hundreds of users who were actively in the editor lost their work, and thousands of templates that had been consistent for months suddenly had all sorts of problems.
There were fonts and things that werenβt displaying properly, spacing that suddenly looked different, and a ton of overall confusion regarding the changes.
It turns out that a few weeks of internal QA and a handful of beta users couldnβt have possibly accounted for the millions of unique design permutations available in the platform. We have over 30,000 active publishers, each with their own unique design and custom elements.
Scaling a company is fun and all, until you fuck up. Having thousands of angry users write in to support with issue after issue isnβt the most fun way to spend your days.
This was a good olβ fashioned fire drill. We had all hands on deck fielding issues and squashing bugs for an entire week. Then we spent another few weeks working through every unique edge case and inconsistency.
After the dust settled, we were finally able to action all of the great user feedback we received to refine the experience even more, albeit a few weeks later than I had anticipated.
Today weβre a few months removed from the episode, and the in-app experience is finally what we had always expected it to be. Weβll continue to add more templates and even build a vibrant marketplace for users to buy and sell templates (soon).
The data tells a really promising story too β 75% of new users now use the quick-start templates to create new posts (which didnβt exist previously). Overall itβs a huge win for improved user experience and onboarding.
At beehiiv, we do this thing called βsunshiningβ where we own and communicate our mistakes publicly to prevent others from making them again. Here are some of my biggest takeaways from the experience:
Users generally dislike change. Our product is habitual; people write and distribute their content on a regular basis, and grow accustomed to the way things are. Even when launching an objectively βbetterβ experience, users are often resistant to having to relearn things that they had previously mastered.
Especially with key workflows. This launch impacted arguably the most important and frequently used experience in the app, and we should have run so many more user tests prior to launching.
Gradual releases >>>. What made this episode such a disaster was that we hard launched it all at once for every user, only to then catch all of the edge cases and oversights. If we had gradually rolled it out to just a few cohorts at a time, we would have caught and addressed the issues more quickly without disrupting everyone.
Launch during off-peak times. We typically ship large updates when traffic is lighter to minimize the downside. We were so eager and excited for this launch we ended up shipping it during peak traffic in the middle of the morning.
Over-communication is good. There were a handful of very large enterprise users who were caught off-guard and were very unhappy to have their workflow disrupted. We should have given them a heads up in advance and migrated them over separately one at a time.
While all of these seem super obvious in retrospect, itβs not always so black-and-white. Prior to the release, there were dozens of high-value customers pressing us to get this to market.
I still believe that speed is a massive competitive advantage; showing urgency to solve your customerβs problems is a good thing. But as they say, everything in moderation.
We built quite a bit of scar tissue from this launch.
We immediately doubled our QA bandwidth, established a more thorough beta process, began over-communicating upcoming changes to users, and overall slowed the pace just a tad to really emphasize quality launches.
beehiiv shipping 15% slower will still out-ship nearly every other company⦠and will result in better products, better user experiences, less support tickets, and less grey hairs (for me at least).
Speaking of shipping, we just shipped these beautiful custom subscribe forms yesterday, some new AI tools, and a whole lot more β check it out.
If you enjoyed this post or know someone who may find it useful, please share it with them and encourage them to subscribe: mail.bigdeskenergy.com/p/sunshining


Credit: Marlon Keanu
It doesnβt get much more minimalist than this. Beach views while working will forever be undefeated.
Shoutout Marlon for the reader submission π«‘.
Think you can generate a better office? Reply with your submissions π¨.

Turn on, tune in, drop out. Click on any of the tracks below to get in a groove β each selected from the full Big Desk Energy playlist.

Some of my favorite content I found on the internet this weekβ¦
How Alpine became the most coveted destination for business school graduates (Invest Like The Best)
The agentic web and original sin (Stratechery)
Nice touch (on right click)
β #Ben Lang (#@benln)
6:33 PM β’ Jun 2, 2025

Chat with DenkBot β my AI clone. Itβs trained on everything Iβve ever published and the entire beehiiv knowledge base π§ .
Itβs also trained on my voice, which means you can call it and have full conversations. Give it a try and let me know what you think.

Share this newsletter with your friends, or use it as a pickup line.
π Your current referral count: {{ rp_num_referrals }} π
Or share your personal link with others: {{rp_refer_url_no_params}}
π₯ Want to advertise in Big Desk Energy? Learn More