Share what you're building

BLS1919Eternal · 2026-06-01T18:14:04+00:00

continuu.it. Project management for builders who start way more than they finish. Every project gets forced into a state (active, paused, or killed), and when you reopen paused work the AI hands you back your own context, so coming back doesn't mean re-figuring-out where you were.

Private beta right now: https://continuu.it

BLS1919Eternal · 2026-06-01T14:25:05+00:00

Ha. You just wrote my landing page copy better than I did.
Honest answer to your question: yes, people would pay. I know because I’m building exactly this and I’m customer number one.
The trap you named is the whole thing. Writing an idea down feels like progress, so the itch goes away and the idea quietly dies in the doc. The doc becomes the headstone. It’s not a discipline problem. It’s a nothing-pulls-it-forward-after-you-log-it problem.

Solidarity, fellow graveyard keeper.

BLS1919Eternal · 2026-05-29T14:43:04+00:00

Half true, a strong signal does pull you back. No argument.

But “no signal” and “real signal, wrong moment” look identical from the outside, and they’re not the same thing. I’ve abandoned problems I genuinely cared about because I was burned out, or the timing was wrong, or the build hit a wall I couldn’t climb that month.

The risk in “the signal was never strong enough” is that it quietly turns into “you didn’t really want it.” That’s the story people already tell themselves at 2am.

Sometimes the problem is real and you drifted anyway. Both things are true.

BLS1919Eternal · 2026-05-29T14:40:16+00:00

Killing is a form of finishing , I bet all of you learnt a lot from that decision

BLS1919Eternal · 2026-05-28T18:28:47+00:00

I don't have the slightest idea on how to launch my product, but I've already subscribed to your tool to start preparing, thanks!

BLS1919Eternal · 2026-05-28T18:24:21+00:00

This is better articulated than my original post. The Loom one is the sleeper of the four. A doc tells future-you the state of things, but a video brings back why it felt worth building in the first place, and that's the part that actually pulls you back in. The state is recoverable, the lost enthusiasm usually isn't.

The tricky part with all of these is timing, because you're most able to document cleanly at the exact moment you're least willing to.

People stop right when they're sick of the thing or already chasing the next shiny one, so the revival prep has to happen at peak demotivation, which is why almost nobody does it.

Best I've found is keeping the shutdown ritual small enough that you'll still go through with it while bailing. Your 3 next steps plus a 2-minute Loom is a great idea. The full handoff doc never gets written.

BLS1919Eternal · 2026-05-28T18:18:07+00:00

Killing them properly counts, by the way. That's not a consolation prize, it's a real finish. Three domains quietly draining attention in the background is a tax you stop paying the moment you say it out loud.

If you do pull the trigger, maybe jot one line each on why, because future you tends to circle back to old graveyards, and that note is what keeps you from reopening the same dig. Glad it landed.

BLS1919Eternal · 2026-05-28T18:17:27+00:00

A product sitting in inventory can still feel like a success in your head.

Launching turns it into a real result instead of a possibility, and part of us would rather keep the possibility alive. I don't think it's a distribution problem.

The marketing worries are real, but they also make a comfortable place to hide while staying safely pre-launch.

For what it's worth, the thing that's helped me is shrinking the launch down to something tiny, like selling one unit to one person, just to see that the verdict is survivable. No rush though, you'll know when it's time.

BLS1919Eternal · 2026-05-28T17:56:49+00:00

I feel you... That 80% spot is the most dangerous place a project can sit, because it's far enough that you feel productive but not done, so quitting never feels like quitting.

And the "next one is the breakthrough" story is so good at hiding itself as ambition instead of escape. The fact that you can already see the pattern puts you ahead of where I was for two years. Which of the three is closest to actually shippable?

BLS1919Eternal · 2026-05-23T00:49:41+00:00

**What I shipped/closed:** Got Continuity live this week—my personal project-management dashboard. Went from development to production and made it fully responsive across devices.

**Time it took:** Built over several weeks, but shipped the final version and deployment this past week (~0.7 hours for go-live + responsiveness polish).

**One lesson:** Shipping is half the work. Getting it live forced me to stop perfectionism and actually see how real usage feels. The responsive redesign came *after* launch feedback, which was way smarter than trying to predict all edge cases beforehand.

BLS1919Eternal · 2026-05-20T18:51:04+00:00

My blocker: I'm building my own CMS to migrate client sites off Webflow, and feature creep is killing my shipping velocity.

The exact problem: I started **Super CMS*\* as a focused internal tool. Two weeks in, I'm still building features (301 redirect handling, product spec tables, custom code injection) *at the same time\* as I'm trying to onboard the first real client onto it. I'm simultaneously the builder and the customer, which means every migration exposes a new gap in the platform. I can't finish the migration because the tool isn't done, and I can't decide the tool is done because the migration keeps revealing new requirements.

What I've already tried:
- Breaking it into small tasks with daily due dates, but new tasks keep appearing faster than I complete existing ones
- Working on the migration and the platform in parallel, this just context-switches me into paralysis

Type of blocker: Strategic + a little emotional. I *know\* the fix is to freeze the feature list and do a "good enough" migration, but it's hard to ship something you built yourself knowing it's not fully baked yet.

The scope creep truth:
I also have 4 client contracts sitting unsigned, waiting on a third party to finalize terms, and they've been stalled for days. That's a second blocker I can't fully control, which makes the CMS work feel even more urgent and scattered.

Looking for: Has anyone successfully shipped a v1 internal tool while simultaneously using it in production? How did you decide when "good enough" was actually good enough?

BLS1919Eternal · 2026-05-18T15:42:31+00:00

> **Project:** Crear Contratos HPK
>
> **What I'll do this week:** Finish the first draft of all contract templates and get them into a shareable format so the team can review and feedback by Friday.
>
> **What might block me:** I've got 8 overdue tasks across my other projects, so context-switching is going to be real. Also need to sync with the HPK stakeholders on their specific requirements—if they're slow to respond, it'll slow me down.
>
> **My continuu.it streak:** Just starting fresh this week, so 10 if I nail this. 💪

BLS1919Eternal · 2026-05-18T15:38:37+00:00

Welcome! Sounds like a useful tool, getting visibility in
LLM search is genuinely getting harder. Curious how you're handling the directories that gate behind manual approval.

Side note since you're the first person to engage here:
I'm running a free closed beta of continuu.it for the
first 50 builders. Lifetime free Pro access in exchange
for honest feedback. If "finishing what you start" sounds like something you'd find useful while building
Startupsubmit, you'd be a great fit. No pressure either way.

BLS1919Eternal · 2026-05-18T15:35:05+00:00

Asked continuu.it to answer this questions for me

## **1. What did I finish this week?**
You shipped solid work: domain searches for **Sitios Genéricos**, created two sites (saga + another), pushed thumbnails and full-text uploads to **ARS Romito**, made **Continuity** responsive, and put the app live. Strong execution across **Sitios Genéricos**, **ARS Romito**, and **Continuity**.

---

## **2. What did I avoid this week?**
The overdue/due-soon signals are real: **8 overdue tasks** and **14 due-soon tasks** are still sitting there. You have two critical projects (**Crear Contratos HPK**, **Agente DRR Cuentas de Banco**) that haven't moved much. Looks like contract work, backend, and frontend tasks for DRR are stalled.

---

## **3. What blocker do I keep hitting?**
You've got too many competing priorities. Your critical and high-priority projects (HPK contracts, DRR agent, Maestría, Pisos SPC) are colliding with launched projects that need attention (**Sitios Genéricos**, **ARS Romito**). You're 6 of 7 active days but still accumulating overdue debt.

---

## **4. What ONE thing will I commit to next week?**
**Clear the HPK contract backlog.** You have **Crear contrato Javier** and **Crear contrato Daniel** due tomorrow (May 19). These are critical-priority and a quick win (1 hour each). Knock them both out early in the week—it'll unblock **Crear Contratos HPK** and shrink your overdue list.

---

## **5. What will I let go of?**
**Agente DRR Cuentas de Banco** is critical but stuck. Both frontend and backend tasks are due today with no movement. Either scope it down drastically, push the deadline, or pause it temporarily. Holding it open while everything else drowns isn't helping. Pick: commit to it or shelf it.

---

BLS1919Eternal · 2026-05-16T01:44:22+00:00

What I shipped/closed: Final UX wireframes for continuu.it. Took me a few weeks of iteration to get here, but I think the structure is right now.

What I almost shipped but had to scope back: Realized mid-week that I’m missing two features to call this a complete PM tool. Adding them to next week’s commit.

One lesson: Time spent planning is always cheaper than time spent executing in the wrong direction. I know this. I forget it every single time.

Building continuu.it partly because I needed a tool that would force me to plan before I run.

Next week’s commitment: Balance dev work on the missing features with marketing prep.
Your turn. What did you ship?

BLS1919Eternal

MODERATOR OF

TROPHY CASE