Morning Sync and a Minor Panic
Woke up thinking about the onboarding flow (again). I had this nagging feeling overnight that something was off—turns out, I was right. A user reported they couldn’t sign up using Safari. Checked the flow, and sure enough, Safari was silently killing a redirect step. Spent two hours tracing the issue with Maciej. We hotfixed it. No longer embarrassed… just exhausted.
Pro tip: test your signup flow in every major browser regularly. I always assume users are on Chrome. They're not.
Tracking: Finally Activated
We’re finally collecting real data. Installed an initial round of event tracking—signup, onboarding complete, first action, and churn signals. It’s crude, but already illuminating. Watching real-time flows is oddly addictive. Like Google Analytics, but for your hopes and dreams.
Still, it's wild how blind we’ve been. Felt like trying to fly a plane by screaming into the cockpit.
Next: build a dashboard tomorrow to visualize key user paths. Want to see drop-offs clearly.
Investor Ping Incoming (Maybe)
One of our warm angels sent a “What’s your schedule like this week?” message.
My brain: "MONDAY. WEDNESDAY. FOREVER. WHATEVER MAKES YOU HAPPY.”
Spent 90 minutes rewriting slides instead of eating lunch. New deck now starts with a user quote instead of market stats. Feels more real. More us.
Goal: tell a story that actually flows. No more Frankenstein pitch decks stitched from old medium posts.
Competitor Raised. Pressure: Felt.
Our main competitor raised a chunky pre-seed and is now flooding Twitter with testimonials. I spiraled for about 14 minutes. Then I remembered: nobody cares about their features if ours work better.
Today was about making the thing work better.
What I Learned Today: How to Set Up Core Event Tracking in 30 Minutes
Here’s a barebones recipe for getting analytics running fast without getting buried in tool fatigue:
- Pick a tool you like (we used Mixpanel, but Segment or even PostHog works).
- Define 3–5 key events. Ours:
- Signed Up
- Completed Onboarding
- First Feature Usage
- Invite Sent
- Inactive 2 Days
- Use unique user IDs, not anonymous ones.
- Add
track()calls inside whatever logic powers your key actions. - Set aside an hour to QA all events in real-time → Confirm they're firing exactly when expected.
Bonus: create a shared doc called “Event Dictionary.” This saves future-you from guessing what “onboard_complete_v2-B” even means.
It’s Getting Fun Now
Fixing bugs, collecting data, reworking the pitch—it’s chaos, but it’s our kind.
Today didn’t scale the company, but it laid bricks under next week’s climb. That’s something.
Onward.
