August update: A bit of traction and taking risks

In my last update in mid-July, I committed to a few goals for the rest of the month.

Here are the goals:

• Speak to at least 10 more makers
• Share 1 post on the Nocodelytics blog
• Ship 1 key Nocodelytics feature (Funnels) and set up emails

So, how did it go?

A teaser of the new dashboard with a convenient summary for the past 30 days (ignore the bar chart)

Speak to at least 10 more makers

Result: Goal met!

I set this goal because I enjoyed meeting new makers in the first half of the month and wanted to continue that.

So how did I do? I had 2 weeks to complete this goal and spoke to exactly 10 makers during that time, with the tenth being on the last day of the month. The conversations were mostly general but a few of them were onboarding calls with Nocodelytics customers.

I had a lot of fun meeting people from the no-code community and already plan to catch up with many of them. I’ll admit, though, I was a little exhausted by the end of it simply because most of the conversations happened in the second week (especially since some were late at night for me). So next time I’ll try to space these out more evenly.

Share 1 post on the Nocodelytics blog

Result: Not met!

I didn’t actually do this one in July. After I published the previous post committing myself to this goal, I shared a poll on Twitter to figure out what I should write about.

The blog post I was trying to get out (about key metrics) actually ended up taking longer than expected.

There was a post *I *did\ publish in August but that was part of Nocodelytics support (a guide on what you can track).

As for the key metrics blog post, it took me the whole of August to get it in a state where I felt confident sharing it. Not because it’s a big read but because 1) I started writing something but scrapped it after a couple of weeks because it didn’t feel right 2) I spent too long trying to write something perfect.

The biggest lesson for me from this was that I needed to take the same approach with the blog that I’ve taken with the Nocodelytics product. Which means, going forward, I’ll try to get to an early draft as quickly as possible and then iterate on it based on my own and others’ feedback.

Ship 1 key feature (Funnels) and set up emails

Result: Not met!

I didn’t get round to finishing this because another big product update meant I had to rethink everything.

As for emails? I still haven’t done this! It’s on the list and more of a priority now as I start to think about opening up Nocodelytics to more users.

What else did I accomplish?

I didn’t meet 2 of my 3 goals. So what else did I achieve in July?

• Got 1 more paying customer (3 in total by the end of July)
• Someone bought 20 coffees (!!!) to show their appreciation for Space Bandits
• A tweet I shared got some decent traction - 86 likes and 10 RTs - which is the most I’ve ever gotten. Some stats:

August updates and making big changes

I didn’t get round to setting goals for August but it was an exciting month!

Here are the highlights:

• Got 3 more paying customers making a total of 6 - +100%
• Made a huge new dashboard update which has been received well
• Finally made a business Twitter account
• Published the key metrics blog post
• Started a resources section with guides for Nocodelytics users

Uncertainty and making big changes

Just as important as more people finding value in Nocodelytics was the dashboard overhaul.

After 10 or so feedback sessions and many more conversations with Webflow users, I got to a point where I felt like I didn’t know where to take it. I’d been trying to build a tool which showed people the reports that I felt were important.

But this was impossible since everyone had their own questions about their own unique Webflow sites. Who am I to tell them to use some reports that I had made up?

My original plan was to take all of the different questions people were trying to answer and come up with new reports for the dashboard that could help. The problem with that is not everyone wanted to see the same reports (only 1 or 2 were relevant at most).

So giving people the ability to choose the reports they can see was my first big realisation.

The second one was that calling them “reports” was silly since in all of my conversations I had been using language like “metrics” or “KPIs”. I went with the former because it was simpler and more clear.

The problem was letting people choose their own metrics meant I couldn’t assume what they’d want.

So the previous reports had to go. Those were features that I had previously spent weeks coming up with and iterating on.

A big risk.

But if I didn’t take risks at this early stage, then how was I going to improve the product?

And with that… The new dashboard was born.

An easier way to track the metrics Webflow users care about.

Goals for September

1. Speak to 10 makers
2. Share another blog post
3. Ship the Funnels metric (finally)

See you next month!