[8-Day Closmore SaaS Challenge] Day 7 — From “working” to “shippable” (From MVP to 1.0)

In my original plan, Day 6–7 was for building the landing page and dashboard.
But I finished them in one day because I combined them into one website.

So what did I do in this Bonus Day 7?

Remember the decision in Day 6

My old boss used to say:

“Amice, what is the risk factor that may make us lose this deal? Let’s handle it now.”

I applied that same logic to the code.

Today was not about adding features.
It was about removing two silent killers that would ruin real usage:

• The Refresh Trap: some data capture still required a manual page refresh.
• The Context Loss: the popup state was lost when switching browser tabs, so the process had to start over.

Day 7 was not “fixing bugs.”

It was choosing the right form for the product to exist.

If I can solve these with just 1–2 extra days, I’d rather call it v1.0, not an MVP.

AI gives technically-correct, but product-wrong answers

AI just wanted me to finish the mission in 8 days.

For the popup issue, I got the same answer (from more than one AI):
“Popup is like that. Accept it. Make it better in the real product later.”

But I couldn’t accept it.

The popup → sidebar decision

I pushed back with real-user intuition.

I observed how LinkedIn Messaging behaves: it stays persistent even when you navigate or switch tabs.

This was not a UI tweak.
It was a paradigm shift:

• Popup = ephemeral, stateless, fragile
• Sidebar = persistent, stateful, product-grade

Most teams patch symptoms.
Mature teams change architecture.

So I decided to do a “big surgery”: move from popup to a sidebar.

What I did:

• extracted the existing code blocks and patterns
• redesigned the system boundary (sidebar instead of popup)
• rewired the flow so the state stays stable

And… I did it! 

From a popup

to a sidebar

The rest of today was simple: test everything again (same as yesterday).
After the surgery, the whole flow became surprisingly stable.

MVP → 1.0 (the final shape)

This was the moment I knew two more days were necessary.

Not to add features.
But to let the product take its final shape.

So yes: it’s no longer just an MVP.
It’s a product — Closmore 1.0.

Want to see it, not just read about it?
I published a full walkthrough with screenshots and the complete UI here: Closmore 1.0 — AI Sales Copilot for LinkedIn

Next:

Day 8 — Cashier & Accountant (monthly billing for Product 1.0)

Day 8 is where this stops being “just a build log” and becomes commercially real: billing + licensing, so the product can be used (and paid for) properly.

(And yes — I’m an enterprise sales (hunter) → full-stack developer. If you’re building or running B2B sales and this way of thinking resonates, feel free to contact me or LinkedIn DM.)