Peter

Developer who ships code but sucks at marketing
Building ShipStory | $0→$10K MRR ▓░░░░░░░░░ 0%

@shipstoryapp Waitlist →

[Peter @pbergen_coding]

Quick question for builders:

When did you ACTUALLY launch your waitlist?

a) When you thought it was ready
b) Weeks later after "one more feature"
c) Right now because you saw this tweet

I just went with (a) - ShipStory waitlist is LIVE

Join the first 100 → Get 50% off forever
After that → Standard pricing

Waitlist → https://t.co/BLtPl4hvL6

[Peter @pbergen_coding]

ShipStory update

- 124 followers (growing slowly but real people)
- 12 waitlist signups (10% conversion!)
- $0 revenue (not launched yet)
- 1 determined builder (me)

slow progress is still progress 📈

[Peter @pbergen_coding]

@denicmarko Not launched yet, but there is a waiting list

https://t.co/INIQYQc9yA

[Peter @pbergen_coding]

new week. clean slate.

Last week i fell into old habits - consumed content instead of creating. watched tutorials, read threads, told myself it was "research"

It wasn't.

Monday reset: closed all tabs. opened VS Code. back to building ShipStory.

Content consumption is infinite.

shipping time isn't‼️

[Peter @pbergen_coding]

you ever fall back into old patterns?

spent the last few days deep in content consumption mode

"just one more tutorial"
"this thread has great insights"
"let me read how THEY built their SaaS"

told myself it was research
really? it was avoidance

because consuming is easier than creating
watching is safer than shipping
learning is more comfortable than building

meanwhile my GitHub: no commits
meanwhile ShipStory: waiting for me to push it forward
meanwhile my users: wondering what's next

hit me this morning: i'm solo building a SaaS to help devs CREATE content from their work

and i'm... consuming content about creating content

the irony hurts 😅

new week. closing all tabs.

no more tutorials
no more "researching"
no more productivity theater

just:
- open VS Code
- write code
- ship features
- tell the story

ShipStory isn't going to build itself by watching others build

time to create again 🚀

[Peter @pbergen_coding]

Just implemented HTTP-only cookie auth for ShipStory

Users will never see this. No flashy UI. No feature announcement.

But it's the security foundation that lets me sleep at night. Sometimes the most important code is invisible.

Building trust > building features

[Peter @pbergen_coding]

Quick appreciation post:

To the #buildinpublic community - you make coding feel less lonely.

Your replies, your feedback, your own builds... it all matters.

Building alone is hard. Building together is possible.

Thank you for being here!

[Peter @pbergen_coding]

An honest question for builders👇

How do you decide what to work on when you have 100 ideas but no confirmation? 🤔

Or rather, no confirmation because you develop without having an audience? 📉

Do you follow your gut feeling, talk to users, or just put something on the market and see what happens?

Especially in the MVP phase?

[Peter @pbergen_coding]

Become Known For Something

Pick Your Lane:
"The person who shares transparent metrics"
"The person who helps with technical challenges"
"The person building in public consistently"
"The person with great onboarding insights"

Consistency > Variety

Better to be known for ONE thing than nothing specific.

[Peter @pbergen_coding]

Real decision I'm facing with ShipStory:

Should I build X OAuth + auto-posting first (what users expect), or perfect the manual review flow (safer, more control)?

The API Costs will explode when using X API

Auto-posting = faster adoption
Manual review = better quality, less risk

What would you prioritize?

[Peter @pbergen_coding]

I'm building ShipStory to help developers share their coding journey without the friction

But right now? I'm still manually crafting every "building in public" post

It's exhausting but also... kinda perfect?

Because I'm living the exact pain point my tool solves

Every manual post reminds me WHY this needs to exist

Can't automate what you don't understand, right? 🤔

What are you working on today?

#BuildInPublic #SaaS

[Peter @pbergen_coding]

It's Thursday and I'm trying to decide: push through or save energy?

ShipStory is calling but so is my couch

Sometimes the most productive thing is admitting you need a break

what's your energy level this week? 🔋

#BuildInPublic #IndieHackers

[Peter @pbergen_coding]

@averycode That's what i love while building my own stuff!

learning along the way👏

[Peter @pbergen_coding]

@averycode Nice to hear that you have a plan to get the user started

[Peter @pbergen_coding]

Week One is ending after publishing waitlist for ShipStory.

100 followers → 122 (+22%). 🚀

12 waitlist signups (conversion: 10%). 📈

Shipped: HTTP-only cookie auth, frontend security improvements.

Learned: security work is invisible but essential. Still building.

[Peter @pbergen_coding]

@buildItN0w Congrats? 😂

[Peter @pbergen_coding]

At my day job: 15 min standup about a button color.

on my side project: shipped entire auth system in 6 hours.

The irony of being 10x more productive on something that makes $0.

Motivation is a hell of a drug <3

[Peter @pbergen_coding]

Become Known For Something

Pick Your Lane:
"The person who shares transparent metrics"
"The person who helps with technical challenges"
"The person building in public consistently"
"The person with great onboarding insights"

Consistency > Variety

Better to be known for ONE thing than nothing specific.

[Peter @pbergen_coding]

Building ShipStory taught me that the most auth tutorials store JWT in localStorage.

That's a security risk (XSS attacks) ❌

Spent extra time implementing HTTP-only cookies instead‼

Users won't see the difference - but their data is safer 🔐

[Peter @pbergen_coding]

11 people joined the waitlist

That's 11 developers who are tired of:
- Switching between builder mode and content creator mode
- Spending 2hrs/day on tweets
- Letting their commits go to waste

89 spots left for 50% off lifetime

https://t.co/INIQYQc9yA