A couple of weeks ago we posted here about Powsight — a system that builds a real profile of your SaaS and tells you where the potential leverage is, based on hard data like Stripe and Google Analytics.
The post got great responses, but one idea stuck with us longer than the rest.
A founder pointed out something we hadn't fully sat with: everything we'd built assumed you already had customers and traffic to point the system at. His situation was earlier and messier than that — pre-revenue, a handful of channels (organic content, community, affiliates), and no clean signal on which one was actually working versus which one just felt productive.
What he said he wanted was simple: the same discipline our feedback loop gives people with data, just done by hand. Write down "I tried X, here's what happened, here's whether I'd do it again." Not because a model needs the data yet — just because that habit of reflection is valuable on its own, long before there's anything to measure.
We talked about it back and forth in the thread. He mentioned his actual workflow was a plain text file — one dated entry per channel, what he tried, what happened, whether he'd repeat it. It worked, but there was no way to cross-reference it against anything. If he wanted to know whether the weeks he posted more actually moved downloads, he had to do that comparison by hand.
That framing made the shape of the feature obvious. So we told him: we'd build a version of it and call it Journaling.
We shipped it.
⭐ Why this matters at every stage, not just the ones with data
Journaling exists because a huge part of what happens in a SaaS business never shows up in a metrics dashboard. You try a positioning angle that flops. You have a conversation with a user that changes your roadmap. You decide not to build something, and that decision matters just as much as the ones you ship. None of that lives in Stripe or GA — but all of it shapes what happens next.
So now, whatever stage your product is in, your journal entries feed directly into your Insights and Digital Profile — the living dataset we build about your business. The system doesn't just know what happened to your metrics; it starts to understand more about potential whys.
That's especially powerful for pre-revenue founders. Before there's a funnel to instrument, journaling lets you start generating meaningful datapoints from day one — just by documenting the journey as you live it. No customers required to start receiving powerful insights.
🚀 It compounds
This is the part we're genuinely excited about, because it doesn't stop at journaling itself:
• Digital Profile gets richer, faster — not just from metrics, but from your own account of what you tried and why.
• Insights get sharper context. We also built a new insight type, Progress, specifically to read your weekly journal entries against your financials and analytics — so it can tell you when to push harder, and when to stop and focus on other things with higher potential impact.
• Metrics stop being numbers in a vacuum. You can finally see data in the context of your actions.
None of these pieces are new on their own. What's new is that Journaling gives all of them something to build on, even before a product has a single paying customer.
❓What's still missing?
We built Journaling because one conversation showed us exactly what was needed — that's honestly one of the best parts of building in public. So we want to keep doing that.
If you're a founder — pre-revenue, early traction, further along, doesn't matter — what are the things/tools you need to accelerate your SaaS growth?
We'd genuinely like to know what we can do to help.
Also, lots of thanks to @Exemplar_Frameworks for this idea 🫡
That connection between weekly actions and output numbers is huge — tracking data without knowing the contextual story behind it usually leads to misinterpreting metrics.
As a video editor and visual communicator working with founders, here’s what I see missing that could really accelerate growth:
Visual Context & Automated Micro-Stories: Metrics tell us what happened, and the journal captures why. But for public updates, social proof, or investor pulse checks, founders need a way to turn those weekly "Progress" insights into digestible visual assets (e.g., auto-generated progress cards, mini data-story visual snippets, or timeline graphic exports).
Pre-Revenue Momentum Indicators: Pre-revenue founders often measure progress purely by finished tasks, which can get demoralizing. A system that tracks "Narrative Velocity" — mapping strategic outputs (like content released, outreach done, or features shipped) directly against audience engagement shifts — would help founders stay focused on high-potential leverage points before money comes in.
Brilliant integration overall — connecting human context to hard financial data is a game-changer! 👏
thanks :)
good points -- we're working on it 👍
the exact founder situation you're describing is where I am right now, pre-revenue, splitting time across reddit, indie hackers, and x, with genuinely no clean way to know which one's actually contributing versus which one just feels productive because I enjoy it more. ran into this literally yesterday trying to run my own account through an analytics tool and getting "sparse profile, can't read this" back because most of my activity is replies, not posts, which the tool didn't weight the same way
answering your actual question: what I need most isn't more data collection, it's something that helps me compare across channels that don't share a common unit. a reddit comment, an ih thread, and an x reply don't produce the same kind of signal, so "which channel is working" is a genuinely hard question to answer by feel alone. if Journaling eventually let me log "spent today on ih, here's what came of it" next to "spent today on reddit, here's what came of it" and surfaced which one correlates with actual downstream outcomes (waitlist signups, real conversations), that's the comparison I don't currently have any way to make
the "no customers required to start receiving insights" framing is the right instinct for pre-revenue people specifically, most tools assume you already have the thing they're trying to help you optimize
hmm, very good point
we're actually doing that (analytics do show referrals) but not at the granular level you suggest (this post brought X visitors, this reddit comment brought Y visitors)
what if I'd let you add URLs (posts, reddit comments, etc) when logging to your Journal?
that means we can at least track impressions/views over time and cross-reference with traffic
The version I would actually keep using has three enforced fields per entry: what I tried, what I observed afterward, and whether I would repeat it. That is the loop from the original founder's request, and it stays useful because the third field forces a decision instead of a diary. The risk I would watch for is turning journaling into a general notes box; once entries stop carrying that repeat-or-not verdict, the insights layer loses the connection between actions and outcomes.
it makes sense, but why not let the insights tell you if it really worked and you should repeat or not?
my concern is "whether I would repeat it" doesn't add much value, because it's obvious that if it worked you're going to repeat it, log it, and the system will know
so to me the most valuable structure is "what I tried, what I observed afterward"
I agree that building it in journaling would prompt the founder to focus on action-results so I'm going to add it in 👍 thanks for the suggestion
the thing is, insights always look at results. Sure, sharing your opinion in Journaling is relevant as it's additional datapoints we could work with, but we're always looking at hard data first (financials, analytics) so we see if your actions have had any impact.
The interesting part is that the journal isn't just a record of what happened. It gives the metrics context by capturing what you actually tried, which should make the later insights much more useful.
exactly :)