Bolted-on Social
Bolted-on social is the failed pattern of adding share buttons or modals as final exit steps instead of designing sharing into the core product flow from the beginning. It is the cautionary tale every AI team should memorize.
This antipattern exists because teams finish the real product then remember they need growth. They throw a tweet this button on the success modal and call it distribution. It never works.
Bolted-on social is not distribution by design. It is the opposite. The share moment arrives after the user has completed their task and lost all motivation to broadcast it.
The familiar shape appeared across enterprise SaaS in 2024. Finished product. Export complete. Sparse modal with prefilled text and tracking link. User closes it immediately. Product team blames user apathy when the real problem was bad timing.
Compare that to Cluely where sharing is the natural consequence of the overlay appearing. Granola produces a tweet length summary the user already wants to send. The share is not a request. It is the output.
The fix follows the same logic as killing chat sidebars in AI native design. Remove the bolt on. Redesign the primary flow so the shareable moment is the logical end state of doing the work.
Every screen becomes a potential share surface. Every completion generates precomposed artifacts. The design team owns the entire loop instead of marketing owning a modal nobody clicks.
Avoid bolted-on social in every case. It wastes engineering time and trains the team to think distribution is someone else's problem. There is no situation where it outperforms native loops. The only tradeoff is that proper integration requires more upfront coordination between design and product which some organizations resist.
If your share prompt lives in a modal at the end you have already lost.
Kill the bolt on. Redesign the flow. Or accept zero click through forever.
Read the full guide
Related terms
Keep exploring
AI-native
A design or system built to be composed by an AI model at request time, not assembled by hand at build time.
Design Pattern
A documented solution for a recurring design problem. Patterns tell you when to use a dropdown versus a radio group, how to handle empty states, and how forms should behave.
Power Surfaces
Power surfaces are expert-only interfaces that live one keystroke away and ignore new users completely. They deliver raw speed and density for the cohort that opens your product twenty times a day.