It’s a modern paradox: The more we use AI, the more we want to be in a room with other humans.
But a lot of event marketers are still juggling 17 tabs, four vendors, and a multi-tabbed spreadsheet like it’s 2018.
Today we’ve got three tips to bring you into 2026, courtesy Lovable GTM engineer Lazar Jovanovic, who builds the tools that Lovable’s sales and marketing team use.
Meet the Master
Lazar Jovanovic
GTM Engineer, Lovable
Tip 1: Match your event format to how your customers actually buy.
Jovanovic says that “if you have a product like Lovable, most of the adoption for us comes from bottoms up, meaning somebody discovers it in the company and then it spreads like wildfire.”
In other words, for a bottoms-up product, executive dinners are not the right in-person strategy. Instead, Jovanovic says to think about “a meetup or smaller event. Get people in a larger setting, in a bigger crowd, to establish a closer bond and closer relationship, so that you can get that intro to the exec."
Tip 2: Before you build anything with AI, count your tabs.
Jovanovic says to “monitor the number of tabs you always have open when you [plan an event]. That's how I knew which bits and pieces I wanted to pull into my app.”
!["Monitor the number of tabs you always have open when you [plan an event]. That's how I knew which bits and pieces I wanted to pull into my app."](https://marketingagainstthegrain.com/hs-fs/hubfs/Lazar%20Jovanovic%20quote%201.png?width=650&height=433&name=Lazar%20Jovanovic%20quote%201.png)
Email client, form builder, everything you’re using to manage your event — “basically just document your day.” That tab list becomes your spec when you build your tool.
Tip 3: AI will let you build fast and wrong — test the flow before you ship.
Don’t wait until production to test what you’ve built. For example, Jovanovic says that if he’s planning an executive dinner, “I'd say, ‘Hey, create a user, sign them up, put them on the wait list, send them an email’ — I will describe the ideal flow and have the app tick all the boxes for me.”
Once the flow works, check what it’s exposing.
You don’t want personally identifiable information all over the web. Think about “admin guardrails, role-based access controls, stuff like that, where you're asking the tool to build things in such a way that they are accessible only by the people that they should be accessible by.”
