[8-Day Closmore SaaS Challenge] Day 2 — Why Tools Didn’t Save Me

In many teams, “progress” looks like this:

Jira tickets move to the right column.
Monday.com timelines shift.
Standups end with: “Let’s adjust the deadline.”

Everything moves. Nothing advances.

I’ve lived in that loop before.
In a team, having tools makes you feel “managed” and good.
That feeling is a poison for a sprint.

AI is also an extremely common tool.

People say AI helps developers a lot!
A helpful tool? — YES.
For most common code? — YES.

But in some cases... Hmmm...
Let me share my story.

My Tasks in Day 2

So for Closmore, Day 2 had a single real goal:

Get the Chrome extension to reliably extract data from a LinkedIn profile.

No dashboards. No task grooming. Just one concrete outcome.

The first real blocker: Two AIs told me to "Accept it"

The extension could not consistently read a LinkedIn profile unless the page was refreshed.
I asked two different AIs for a fix.

Both answered the same thing:
I summarized as : That’s normal. LinkedIn is an SPA. Just ask the user to refresh. Problem solved.

Technically correct.
Product-wise? Unacceptable.

If I have to “serve” a tool, I won’t use it.
As a sales professional, I know this breaks trust.
The AI was telling me to sacrifice user experience for a "quick fix."

What I decided on Day 2: The Art of Parking

I refused to “normalize” the flaw.
But I also refused to block the entire 8-day sprint because of it.

This is where judgment beats tools.
Instead of "digging" into the problem and delaying the schedule, I made a senior choice:

I decide to park it.

I wrote one line in my notebook:
“Have to Review : ! Must Refresh the page !"

Not buried in a backlog.
Not hidden by a Jira status label.
Explicitly acknowledged.

Judgment > AI

Tools make it easy to move schedules.
AI makes it easy to write "good enough" code.
Neither helps you move Uncertainty.

This is why Day 2 matters:

I didn't let a "Managed" feeling hide the delay.
I didn't let the AI talk me into a bad product decision.
I prioritized Momentum over Perfection.

Day 2 produced no new UI.
But it prevented a fragile foundation.

Next: Why being a developer wasn’t enough—and why Closmore was actually built by a salesperson and the UI

Wait—Are you looking for a Technical Partner?

I’m building Closmore in 8 days to prove that speed isn't about rushing—it's about judgment. I show founders how to avoid the "Jira Poison" and focus on what actually moves the needle.

If you have a SaaS idea and need a technical partner who prioritizes Product Integrity and Rapid Execution, let’s talk. I help founders launch MVPs that users actually trust.

Click here to book a strategy call. / Connect me via Linkedin.

#BuildInPublic #SaaS #ProductManagement #Solopreneur #SalesTech