We launched Meet-Ting on Gmail to move fast. It got us out there, but we quickly built up technical debt and a heavy reliance on Google's APIs.
This was a problem. Our most valuable potential users (the "meeting-heavy" pros) all use Outlook.
After months of focused work to improve core reliability, it was time to expand our ecosystem. We call it our "Ting everywhere" strategy. Our native Outlook integration is live.
Ting is a free AI assistant that books meetings in email the way they really happen - human, messy. Just CC Ting - it reads the thread, checks calendars, suggests times, and sends the invite. Like Calendly, with an LLM.
*Closed beta - PH users jump the queue*
In our recent Ting v2 launch, we talked about giving your calendar your brain so it can make decisions for you. That means moving from reactive proactive full automation.
Inspired by Lenny s podcast with Ethan Smith (so good, you need to listen - the advice for builders is insane and can't believe it's free...), I wanted to share a few things I ve been seeing going deep into Answer Engine Optimization (AEO) for @Meet-Ting.
I spend a lot of my day in GPT and Gemini, and over the last few months I started getting more curious about how their recommendations are actually pulled from the web. I'm not an expert, listen to the podcast, but I am actively tackling it so have some tactical learnings.
Hopefully this isn t your second Ting notification overload in a couple of days
We got top three launch for the day yesterday! We're so delighted and grateful. Thank you for upvotes, comments, good vibes and giving us the energy to keep pushing.
We said we d give Product Hunt something extra, but we didn't want to spam yesterday.
LOTS going on. Google just turned a core part of our product into a feature - which is always fun - BUT, we saw it coming when they added it to Workspace not long ago. Inevitable, really, importance of keeping an eye on the market. The wave of AI scheduling assistants is as validating as it is like white-water rafting...!
