Weekly update 28-4th Oct 26

Was reflecting on our discussion last week and you were right MRR is not the best metric pre launch.(addressed to accountability partner)

I did some "research"(ie watching a yt video lol - from the YC Startup School playlist)

They said the pre-launch weekly metrics should be Weeks until launch or Number of users talked to.

I summarised the talk in a post here. Its mostly just what they say on the slides.

So accordingly updated my weekly update format a bit below.

Primary KPI - Weeks until launch

Actual = 4 , Goal = 4

So ideally november 5th.

Secondary KPI - Number of users talked to.

Actual = 0 , Goal = 0

I had not set a goal for this.

Biggest Obstacle to growth?

Getting derailed by out of scope task that seem easy to imlement but lead me down a rabbit hole.

Tasks accomplished?

V1 for A markdown for buildprint to map all possible user flows into Excel csv template.

Test Run on Arkhitect to generate cases.

Was able to run and do a partial verification for another proj.

See if there is a better way to display test cases and permutations.(I created a html dashboard for this which made the process of testing manually quite fun.)

There is obviously a lot of fluff, but good to brainstorm and give me a bunch of ideas.

Impact and Big learnings?

A good visual output of the testcases makes it so much more inviting to do actual testing.

So does the small things like a progress bar.

I would have never adding shortcut keys to the test case output.

Found that surprisingly good.

There is so much extra stuff in the image above. I only really was looking at the description and the expected outcome.

Take what the defense gives you.

Even though the day seems lost. The week, far gone. "Take what the defense gives you" What can I do now? The simple things. The low-hanging fruit. Play for tomorrow; maybe things will be different then. Our work is a practice. One bad day us nothing to

Weekly update 5th-10th Oct 26

Was on leave most of this week so updates were bleak Primary KPI - Weeks until launch Actual = 4 , Goal = 4 - Nov 5th I think I had accounted for this so we still should be good for Nov 5th. Secondary KPI - Number of users talked to. Actual = 0 , Goal = 0 Biggest

Time management V2

Scrappy notes based on YC talk. KPIs(Key performance indicators or North Star Metric) Pre launch Example: Weeks until launch or Number of users talked to. Post launch Identify Top KPI - MRR or some revenue-based metric for most startups Identify major bottlenecks or biggest problem. System to move your

The real issue with vibe coding

Its far too easy to push bullshit features. We no longer have constraints. So we build everything. Stop, think, build by hand sometimes. Dont run from the decision. "The ability to let that which does not matter truly slide" (not my quote)