[8-Day Closmore SaaS Challenge] - NO Coding in Day 1

Don't Code Today

Why I didn’t write even one line of code, even with only 8 days

With only eight working days, the most tempting thing is obvious:

Start coding.

I didn’t.

Day 1 was spent without touching a single feature.
Not because I was slow.
Because I was removing uncertainty.

The 4-Component Architecture.

What I did instead of coding

I defined the system first — end to end.

Four components, clearly separated:

1. Chrome Extension – capture LinkedIn context
2. Closmore Backend / API – analysis and generation
3. Dashboard/Mini CRM Web App  – review, scoring, iteration
4. Landing Page  – solution introduction

At first, the 2, 3, 4 are separated
Later it naturally combine into one.

That’s fine.
Architecture is allowed to evolve. Chaos is not.

Before any implementation, I hand-drew:

• The user interaction steps (intentionally minimal)
• The data flow: Extension → API → AI → Database
• The database schema (Prisma) everything would depend on

This felt slow.
It later saved days of refactoring.

My Boilerplate: The "Heartbeat" Test

I already had a working Chrome extension popup from my previous experiment. 
Building a Chrome Extension from Scratch — My ClosMore AI Experiment

It was not a mock. It could:

• Read data from a LinkedIn profile
• Send it to a Next.js API
• Modify the payload
• Return a validated response

That “Hello World” already exercised:

• Frontend logic
• Extension permissions
• Backend routing
• Response contracts

Day 1 wasn’t about theory. It was about confirming the "plumbing" worked before I started the "interior design."

Restart it, test it a bit, the development environment is still working. The Hello World still has a heartbeat. Good.

The scope is clear

By the end of Day 1, Summary:

Frontend

• Capture
• Sales Context
• Analysis
• Email Drafts

Backend

• /analyze → enrichment, scoring, reasoning
• /draft → generate three sales emails

Plus

• Landing page
• A minimal internal CRM

No feature fantasies.
No “we’ll see later.”

Tech Stack

Backend: Next.js / Typescript

Database: Neon

AI: OpenAI SDK / Gemini

Open questions (parked, not ignored)

• LinkedIn InMail character limits
• Chrome Web Store approval
• CRM login (skip for MVP?)
• News search API
• Payment flow (Gumroad?) 

Not blockers for Day 1.
But written down — because ignored questions become expensive surprises.

A lesson I learned the hard way

In a previous company, product team once told development team:

“I can’t understand your jargon.”

They weren’t wrong.

The problem wasn’t language. It was the lack of a shared source of truth. This time, the diagram is the law.

Forms were filled.
Boxes were checked.
No one knew if both sides were aligned.

This time I chose:

• One architecture
• One data flow
• One source of truth

No jargon debates. Just structure.

Here is my 8 day plan (day 1 gone!)

Day 1 produced no features.
But it removed future chaos.

Want to see if I actually finish in 8 days? Follow the journey here.

Tomorrow: how I managed execution without Jira, without Monday, and without moving dates.

Wait—Are you looking for a Technical Partner?

I’m building Closmore in 8 days to show what’s possible with a clear architecture and a focused scope.

If you have a SaaS idea and need a technical partner to help you launch your MVP with this kind of speed, Click here to book a strategy call / email me.

#BuildInPublic #SaaS #ProductManagement #Solopreneur #SalesTech