So we’ve officially decided to outline the entire journey of Amazemeet, hoping it will be helpful to others or just informative to our users. We believe that there is value in knowing what a team’s all about, not just the app, so we want to share our highs and lows with you, open our kimonos, and get to know one another better through this crazy startup process.
This week is a MAJOR MILESTONE for Amazemeet because it marks our very first round of private beta. It’s private for now and we’ve limited the number of testers, so we can extract the most value from our most eager users (and by users we mean friends, but we have to use this term because everybody else does).
Because the interest in testing the app has been amazing, we’ve decided to throw another couple of beta rounds for those who didn’t get the chance to play with the first iteration. So if you’re a hard-core early adopter who’s been praying for a new solution to boring meetings, download the canvas from the main site, and we’ll contact you when we have some spots left for early access.
Now, let’s see what the goals for this week are and what we’ve learned from last week. The closer we get to launch, the crazier this startup journey gets!
Violeta got a little color-crazy.
(Ignore the fact that Violeta is referring to herself in the third person.)
In my defense, Trello does not exactly provide label presets, so what do you do when you see six colors, which you can group with any kind of words to provide meaningful labels? Here’s what I did:
I’m not entirely sure if Mike (my technical co-founder) was happy with this turn of events, but he did give me a 7th color for milestones. Sometimes it pays to go along with “the crazy ones” because we see things as they could be. And if you ask me, that’s a pretty powerful tool in anyone’s startup toolbox.
Question: Are you using all of trello’s useful features?
Mike worked on the app all weekend.
He found himself in Krakow, Poland for the weekend and instead of going to see Wawel Hill, Auschwitz, the Wieliczka salt mine or even rack up a healthy bill at his client’s expense, he worked on the app. If that isn’t dedication to help people have amazing meetings, I don’t know what is!
But it wasn’t all work – he spent 2 hours in the spa, swimming and braising himself in the sauna!
It’s all really worth it though – because we are building something really beautiful that 130 really lucky people are going to see and use very soon!
The first BETA email campaign could have been better.
Feedback is so important, especially at the start when you’re fumbling your way through all the things you should be doing, could be doing, and could have done better, but you didn’t know at the time. In our case, our subscribers saved us from fumbling through all our net email campaigns by telling us what went wrong:
There was a “yes, I’d like to test the app” button on the bottom of the email, which unfortunately, some people didn’t even see. So when I got the excited “yes, I want to beta test”, I had to make sure they’d pressed it. When they said “no, I didn’t see it”, it was clear we messed up.
Also, I am so grateful for my co-founder’s sage advice to segment the subscribers and pace our campaigns in this way instead of bulk-sending to everyone. If it weren’t for him, we would have lost on potential beta testers because we didn’t position the button right (it could have been closer to the top) and because the text on the button was invisible.
That said, we’re happy that we got lost of clicks anyway. Thanks to everyone for being as excited about this app as we are. Seriously, we couldn’t do it without you.
Takeaways: Listen to your co-founder, segment your subscribers, heed all feedback, and always improve your efforts.
How metaphors can help you launch:
This is the part where I tell you how important your pre-launch strategy is.
I am personally taking Amazemeet’s pre-launch strategy very seriously because we’ll likely not get another chance. (I don’t want us to become one of those startups that pivot and re-launch constantly, which we’ll do if we have to.)
So I created an entirely new Trello board for it and together, we (Mike and I) came up with two metaphors (well, similes) for our pre-launch experience:
- Launching is like a tsunami. Every wave builds up on the next until the final tidal wave strikes, and the after-waves bring additional sign-ups to make sure the buzz doesn’t die too quickly or at all.
- Launching a startup is like launching a rocket into space. You need certain parts to get to certain altitude, after which you need to jettison or re-imagine them to get into your established trajectory.
Based on these visions, we can clearly see what needs to be done to launch successfully. After all, launching needs to be a unique experience for each startup, rather than everyone following the same old frameworks.
Question: What’s the metaphor for your startup launch vision?
What we learned this week:
- As long as it helps, you can be a little crazy with your strategy.
- Always do better than the last time and take feedback very seriously.
- Don’t be afraid to be creative when it comes to strategy. Think metaphors.
- Some tools are indispensable at the start, like Typeform for user feedback.
P.S. We hope you enjoyed this post and if you have any questions, ping us on twitter because Violeta lurks there and never leaves a mention unanswered.