I use a pie chart and table to break down data on a granular level. (This might not be necessary for you, but my default is to err on the side of transparency.)
Also, in regards to burn, @jaltma had a great point that many founders miss: burn is burn. Don't explain away "one-time expenses" because you'll *always* have one-time expenses.
Expanding on that thought: whenever you present numbers, just present the numbers.
Trying to explain or justify down revenue, missed targets, or slow growth isn't helpful.
Complicated explanations look like you're not taking responsibility trying to hide the truth.
When presenting numbers, let them speak on their own.
"Churn increased to 11.3%, MRR increased to $54,630.24 and DAU decreased by 3.47% to 4,293" should be unencumbered data.
If you feel compelled to add context, do so towards the end of your update.
5️⃣ Other traction
This might be waitlist growth, proprietary features, other IP that's been developed, or other relevant data.
What's important here is to ensure any other data is *real*.
Plain and simple: if it's not a material impact to your company, don't report it.
6️⃣ Previous month product updates
↳ Features shipped
↳ Customer feedback
↳ Usage/adoption
Showcasing how customers interact with new features illustrates you're in-touch with your users, and focused on building something people will actually use.
Clearly state where you're going, and why: investors should know if something important is happening later this month.
8️⃣ Lessons learned
↳ Important takeaways/Reflection
Did you make a mistake? Lose customers? Ship a feature people didn't like? Miss targets? Find a new competitor?
If you didn't learn at least *something* in the last month, you're not paying attention.
On adding a reflection section:
Investors want founders who are teachable, actively seeking to get better, and paying attention to their company from all angles (not just the good ones).
Openly share feedback to reinforce you're a founder who will learn from reality & adapt.
I believe you need @threads if you care about building a productive startup with happy, engaged people.
A few weeks back @ItsBrittStew and I spoke with the @threads team about how we're using their platform... a few highlights from our experience so far. 🧵
Like most, before @Threads we used Slack. Also like most, Slack was an awful, messy experience.
We were always trying to hunt down info. "Did you see this?" was common language. I couldn't stand it. Search was messy AF & information overload was constant.
It wasn't sustainable.
Needless to say we were stoked when we found @threads. In fact, we were so impressed we cancelled our Slack subscription immediately after onboarding to Threads.
It was wild to see how quickly Threads eliminated fragmentation in our tech stack…
Seeing lots of people sounding the alarm that society isn't ready for widely accessible AI after ChatGPT's popularity explosion on Twitter.
A reminder that history repeats itself, and fear of new tech, ideas, information, and societal progress is a tale as old as time. ↓
Fear of writing.
Philosopher Plato stated in 370 BCE that “writing is a step backward for truth.” ¹
He feared that "[writing] will implant forgetfulness... [people] will cease to exercise memory [but] rely [solely] on that which is written... by means of external marks." ²
Fear of books.
In 1255, author Vincent of Beauvais wrote:
"Since the multitude of books, the shortness of time and the slipperiness of memory do not allow all things which are written to be equally retained..." ³
His fear: more books = lower attention spans & worse memory.