Your 9am overwhelm ends here
How one EA vibe coded her own daily digest with AI (and no technical background)
I guarantee you know this feeling: you log in first thing and you’re hit with chaos.
Dozens of new Slack threads, late-night emails, Asana updates, pings that arrived while you were asleep. It all blurs together.
You want to see what actually matters, but instead you’re sifting through noise before you’ve even touched your coffee.
That’s exactly where Lisa de Melogue found herself.
Not with some lofty automation strategy, just a relatable wish: “I want one clean snapshot that shows me what matters most so I can start the day focused on what my CEO needs.”
This became her doorway into vibe coding.
📆 Join this free Carve Shift to hear Lisa's story firsthand
Next Thurs, Jan 22 · 5pm UK · 12pm EST · 9am PST
You'll hear an honest, behind-the-scenes look at what it really takes to make vibe coding work as an EA – the wins, the workarounds, and the lessons learned along the way.
What is vibe coding?
Vibe coding is when you describe what you want your app to do in plain English, and get your AI chatbot to write the actual code for you.
It’s such a breakthrough for EAs because it takes the intimidation out of automation.
You don’t need to be an engineer. You don’t need to understand the code.
You just need curiosity, restlessness and enough patience to go down the rabbit hole with your AI chatbot to build a solution together.
Start with a clear problem or friction
For Lisa, the friction was clear. Her exec works three time zones ahead of her so when Lisa logged in each morning, she immediately felt behind with notifications and activity to catch up on across her tools.
What she needed was a digest of all actionable updates delivered first thing in the morning.
Let your AI chatbot guide you
Lisa started by telling ChatGPT exactly what she wanted and what tools her company already used.
First she tried using Zapier to create the digest, but it struggled under the complexity. So she moved to Google Apps Script, a lightweight scripting environment that lets you write custom logic, automate workflows, and connect Google tools with external services.
Then she started vibe coding with ChatGPT:
She had ChatGPT write code for Google Apps Script
She asked it to explain each step “like I’m six”
She uploaded screenshots anytime something broke
..and she kept going
In about three hours, she had her first working version of the daily digest, built and refined through vibe coding.
The first version wasn’t perfect – Asana comments didn’t come through, email signatures cluttered the view, Slack links needed adjusting.. and so on.
Instead of panicking, Lisa treated each issue as part of the process – she uploaded screenshots, asked ChatGPT to debug and kept refining.
That’s the classic cycle of vibe coding: try it, break it, fix it, repeat.
Pro tip: make your exec part of the journey
Lisa was really transparent with her exec on her experiments. Once when she created a different automation that flags every time her exec is mentioned in Slack, she said to her, “This might break – I’m testing something.”
Her CEO was really supportive and it opened up a new conversation about the solutions Lisa was building. Word spread internally, and Lisa is now being asked to share her learnings with other teams.
Her work didn’t just solve a problem – it created visibility.
What she needed was a digest of all actionable updates delivered first thing in the morning.
5 steps to start vibe coding yourself
Start with one painful problem you’d love to fix
Tell your AI chatbot the exact outcome you want and the tools available to you
Ask it to explain how to code a solution step-by-step in simple language, and upload screenshots to debug issues when they crop up
Expect the first version to be scrappy and imperfect!
Keep your exec informed so experimentation feels safe for both of you
A closing thought
Lisa’s story isn’t really about Google Apps Script.. It’s about identity.
Moving from thinking, “There has to be a better way” to “I think I can build a solution to this myself.”
Once you’ve built one, you start seeing your role differently. You realize you’re a builder. We are all builders now.
This is how you raise the ceiling on your role, one workflow at a time.