I archived my old projects and turned Tidemason into a public lab
Over the past few months, I built too many things in private.
Apps, desktop tools, landing pages, Chrome extension experiments, domains, product docs, prototypes.
Some of them shipped.
Most of them never reached real users.
That was the pattern I finally had to face.
The problem wasn’t that I lacked ideas.
It wasn’t that I couldn’t build.
It was that I kept building before learning how to distribute, listen, and validate.
So this week I did a reset.
I archived the old experiments that no longer make sense to continue.
I cleaned up the domains.
I removed the projects that carried platform risk or had no clear user signal.
And I kept one public home:
https://www.tidemason.com/?ref=ih-reset
Tidemason is now my public lab for small apps, archived experiments, and honest build-in-public notes.
My new rule is simple:
No more building in private for weeks before talking to users.
I’m going to share what I build, what fails, what gets archived, and what real users actually say.
Curious if anyone else here has gone through this kind of reset.
How do you decide which projects to archive, and which ones are still worth validating?
I know how tough it can be to shift focus like that. I actually know a few peer founders who have gone through a similar reset process and they'd probably be happy to answer your questions about it.
Thanks — that would be really helpful.
The hardest part for me is not archiving projects emotionally, but knowing whether I’m quitting too early or finally being honest with the signal.
If any of them have gone through a similar reset, I’d love to hear how they made those decisions.
There's a supportive community called "replyz" where you can reach exactly the kind of people you're looking for. Just search who you want to connect with and you'll get real, detailed responses from them. Only thing is, you should also share your own insights with others too. It's what keeps the place running. Feel free to ask questions if you have any!
Thanks, I’ll take a look.
I’m mainly hoping to hear from founders who have actually gone through this kind of reset. I’d be curious what signals helped them decide whether to archive a project or keep validating it.
This resonates a lot.
I think archiving projects is underrated. It feels like quitting, but sometimes it is just clearing space for better signal.
The part about building before learning how to distribute really hits. I’ve been realizing that shipping something is only half the work. The other half is creating enough conversations around it to know whether it should keep existing.
Curious what criteria you used to decide what to archive. Was it mostly lack of user signal, platform risk, or just lack of energy to keep going?
That question became the core of the reset for me.
The biggest factor was lack of real user signal:
no real usage, no meaningful feedback, no reason to believe people would keep using it.
Then came platform / trust risk:
some projects were buildable, but not worth carrying long-term.
Energy mattered too, but more as a diagnostic than a reason by itself.
I started asking:
“Is this project pulling me closer to reality, or just deeper into building?”
If it was mostly engineering momentum without user signal, I archived it.
That reset is a solid move — most people stay stuck in “build mode” way longer 👍
The hard part isn’t building, it’s letting go of things that could work but don’t have signal yet.
What’s helped me think about it:
→ Keep if there’s real user behavior
(not compliments — actual usage, return visits, or someone trying to pay)
→ Pause if there’s interest but unclear direction
(people ask questions but don’t act)
→ Kill/Archive if it’s only internal conviction
(no external signal after exposure)
One simple filter:
→ “Would I rebuild this from scratch today knowing what I know now?”
If no → archive.
Your new rule is the right one:
→ talk early → build after → adjust fast
Most builders do the reverse.
Curious:
→ are you planning to test multiple small ideas in parallel now
or go deeper on one at a time?
Also, I’m running a small project (Tokyo Lore) where we surface early-stage ideas like this to a focused builder group and see what actually gets traction vs just feels promising.
Since you’re moving into public validation, this could be a good fit.
Happy to share more if you’re open 👍
Really appreciate this — especially the distinction between real behavior, unclear interest, and pure internal conviction.
That’s actually very close to how I’m trying to think now.
And for your question: I’m leaning toward going deeper on one idea at a time, not testing too many in parallel.
In the past, parallel ideas made me feel productive, but they also made it easier to avoid the harder work:
distribution, follow-up, and staying with one thing long enough to get a real signal.
So my current plan is:
pick one,
put it in front of real people,
listen carefully,
and only switch if the signal is clearly weak.
That “Would I rebuild this from scratch today?” filter has also become really useful for me.
And Tokyo Lore sounds interesting. Feel free to share more about how the group works and what kind of projects you usually include.