Back to Studio

AI-friendly Markdown · structured for AI citations

Growth · Studio

How to Decide Whether to Kill, Pause, or Double Down on a Side Project

16 min read
How to Decide Whether to Kill, Pause, or Double Down on a Side Project

A practical nights-and-weekends rubric to kill, pause, or double down on a side project—four scoring axes, a one-evening workshop, and email templates that end the fog.

To decide whether to kill, pause, or double down on a side project, stop deciding from mood. Spend one week collecting four kinds of evidence (usage, conversations, energy, life), score the project 1–5 on problem pull, distribution fit, unit of progress, and personal fit, then pick one path with a written review date. Roughly: 16–20 points is a double-down candidate, 11–15 means pause or narrow hard, and 4–10 means kill or rewrite from scratch. Whatever you pick, pre-commit the condition that would reverse it.

Last updated: Nov 12, 2026

Every nights-and-weekends builder hits the same quiet crisis: the project still “could work,” but Tuesday evenings feel heavier, progress is mostly guilt, and you cannot tell if you are being patient or just avoiding a decision.

Killing a side project is not failure. Pausing is not quitting. Doubling down is not romantic—it is a bet with a calendar and a budget. This playbook gives you a clear rubric so you stop negotiating with yourself every week and pick one of three moves: kill, pause, or double down. (There is also a quieter fourth move, selling or handing it off, covered below.)

If your MVP is still bloated, fix scope first with how to scope a side project MVP you can actually ship on weekends. A fat build makes every decision look worse than it is.

Why is “maybe later” the most expensive option?

Half-dead side projects tax you in ways dashboards never show:

  • Attention debt. You open the repo, feel behind, and close it. That loop steals evenings even when you “do nothing.”

  • Identity fog. You keep saying you are building X, so you do not start Y—even when Y is the better bet for your life right now.

  • Support residue. A few users still email. You feel obligated. Obligation without a plan becomes resentment.

  • False hope. “One more weekend” becomes a year. Hope without a review date is procrastination with better branding.

A clean kill or a timed pause frees energy. A deliberate double-down focuses it. What hurts is the fog in the middle.

If you cannot say what would change your mind in the next 30 days, you do not have a strategy. You have a habit.

What does the research say about quitting and sunk cost?

Two well-known studies are worth knowing before you score anything, because they explain why this decision feels harder than it should.

Sunk cost makes you overrate your own project. In a 1985 field experiment, Hal Arkes and Catherine Blumer had the Ohio University Theater sell season tickets to its first 60 buyers at random prices: full price ($15), $2 off, or $7 off. Everyone held identical tickets. Over the first half of the season, full-price buyers used an average of 4.11 tickets, against 3.32 and 3.29 for the two discount groups—the money was gone either way, but the people who had paid more kept showing up. In the same paper, questionnaire subjects who had already “invested” in a project rated its chance of success higher than people judging the same project without that investment. See the psychology of sunk cost (Organizational Behavior and Human Decision Processes, 1985). Your 200 evenings are the season ticket.

Undecided people may be too cautious about change. Economist Steven Levitt ran a website where people stuck on a decision could flip a coin to settle it; about 22,500 coin tosses were recorded, with follow-up surveys at two and six months. For important decisions such as quitting a job, people the coin told to make a change were more likely to do it, and on average reported being happier six months later than those told to keep the status quo. Levitt’s own caveat: the participants were self-selected and not representative. Read the paper as Levitt's coin-toss study on major life decisions (NBER Working Paper 22487, later published in the Review of Economic Studies, 2021).

Neither study is about side projects. But together they suggest a useful default: if you have been genuinely torn for weeks, your bias is probably toward keeping things as they are, and you should make the rubric below do the arguing.

How do you collect signal before you decide?

Do not decide from a mood after a bad deploy. Run a short evidence week. Write answers in a single note—no fancy tools.

1. Usage truth. How many people used the product in the last 14 days? How many paid? How many replied when you emailed them? Ignore vanity signups from three months ago.

2. Conversation truth. Talk to three people who should care: a recent user, a churned or silent signup, and one stranger in the target audience who has never seen it. Ask what they tried instead. Ask what they would pay for. Ask what they ignored.

3. Energy truth. For seven evenings, after you close the laptop, rate 1–5: “Did this session feel useful?” Pattern matters more than one heroic Saturday.

4. Life truth. Job intensity, family load, health, money runway. A project can be “good” and still wrong for this quarter.

If you have almost no users, do not invent metrics theater. Qualitative signal still counts—especially if you get brutal feedback from makers before you launch publicly. Honest “I would not use this” is more useful than polite silence.

If the whole problem is a motivation slump around the third week of a new build, that is a different diagnosis with a different fix; see keeping a side project alive through the week-three motivation dip before you score anything.

How do you score a side project on four axes?

Give each axis a score from 1 (weak) to 5 (strong). Be harsh. Soft scores keep zombies alive.

  • Problem pull. Do people seek this without you begging? Are they already hacking painful workarounds?

  • Distribution fit. Can you reach buyers with channels you can sustain after work (communities, content, outbound, partners)—not fantasy viral loops?

  • Unit of progress. In a normal week, can you ship something a user would notice? Or are you stuck in infra forever?

  • Personal fit. Does this match your skills, curiosity, and constraints for the next 90 days?

Write the four numbers. Then add one sentence for each: the evidence, not the hope.

Total score

Default path

Extra condition

16–20

Double-down candidate

Only if problem pull and personal fit are both 4 or higher and you can protect the time

11–15

Pause or narrow hard

Name the one axis dragging the total down and the test that would lift it

4–10

Kill or radical rewrite

Continuing “as is” is usually denial

Numbers are not destiny. They force trade-offs into the open. Pair them with early metrics sense from how to track product metrics that matter before your first 100 users so you are not optimizing vanity.

What does a scored decision look like in practice?

Here is an illustrative example (a made-up project, not a real case) to show how the evidence week turns into a call. “Pinwell” is a bookmark-tagging tool a developer has built on evenings for eight months.

Axis

Evidence from the week

Score

Problem pull

41 signups total, 6 active in the last 14 days, 0 paid; 2 of 3 interviewees said they use browser folders and it is “fine”

2

Distribution fit

Only channel tried is one Reddit post; no community where buyers gather weekly

2

Unit of progress

Last four weeks spent migrating the database; nothing a user would notice

2

Personal fit

Energy scores averaged 1.9 over seven evenings; new team lead role at work through March

2

Total

8

Eight points, and at least three of the kill signals below are true: weak pull after outreach, no nameable next paying customer, and low energy even while “making progress.” The honest call is kill (or sell if someone has asked about it), not pause—a pause only makes sense when the idea is fine and the season is wrong, and here the idea itself has not shown pull. Now change two facts: imagine three of the six active users had asked to pay, and all three came from the same Slack community you could post in weekly. Problem pull rises to 4 and distribution fit to 3, the total becomes 11, and with work busy until March the right move becomes a pause until March with a written “3 paid pilots” un-pause condition.

How do you choose between kill, pause, and double down?

Use the scores plus your life truth. Pick one path and write the date you will review it.

When should you kill a side project?

Kill if two or more of these are true:

  • Problem pull is ≤2 after real outreach, not after posting once on X.

  • You cannot describe a next paying customer in one sentence.

  • Energy scores stay ≤2 for two weeks even when you “make progress.”

  • The project requires full-time ops to not disappoint the few users you have.

  • You are keeping it alive mainly for ego, sunk cost, or a domain you already bought.

How to kill cleanly (45–90 minutes):

  • Email active users: what is shutting down, when, and how to export data. Give at least two weeks if anyone stores data with you.

  • Stop billing. Cancel recurring subscriptions in your payment provider so no one is charged after the shutdown date, and refund the current period if you promised ongoing work you will not do.

  • Archive the repo. On GitHub, archiving makes a repository read-only and it can be unarchived later (see GitHub's docs on archiving repositories). Put a README note first: why you stopped, what you learned, and what replaces it.

  • Decide the domain. Either let it lapse, keep a one-page farewell, or point it at your next project. If you redirect it, run it through the free redirect checker to confirm it is a single clean 301 and not a chain.

  • Cancel unused SaaS. Cancel calendar holds. Remove the open tabs.

  • Write a one-page post-mortem for yourself: hypothesis, what you tried, what signal said no, what you would do differently. Keep it private if you want. The point is closure, not content.

Killing is a skill. Builders who can end things ship more of the right things later.

When should you pause instead?

Pause if the problem still looks real, but life or sequencing says not now:

  • Job crunch, burnout, family season, or health needs the evenings.

  • You need a sharper wedge and should talk to users before more code.

  • A dependency is blocked (API access, partner, legal) and waiting is honest.

How to pause without becoming a zombie:

  • Pick an end date: 30, 60, or 90 days. Put it on the calendar with a title like “Decide: ProjectName.”

  • Tell users you are in maintenance mode: critical bugs only, no roadmap promises.

  • Freeze features. Document the one open question that would un-pause you (example: “3 paid pilots at $X” or “stable evenings again after March”).

  • Park the next three tasks in a note so restarting is not archaeology.

  • Do not half-build during the pause. That is not a pause—that is sneaking.

A pause with a review date is respectful. An indefinite “back soon” is a soft kill you refuse to name. When the date arrives and the answer is yes, the re-entry steps in restarting a side project you paused months ago make the first evening back much less painful.

When does doubling down make sense?

Double down only if problem pull and personal fit are both ≥4, and you can name the next 90-day bet in one line.

Doubling down does not mean quitting your job tomorrow. For side projects it usually means:

  • Time: protect 2–3 fixed blocks per week (put them on the calendar like meetings).

  • Scope: cut everything that is not the paid promise.

  • Distribution: pick one channel you will show up in weekly.

  • Money: put a price in front of people, or raise it if you are undercharging out of fear.

  • Learning: book real conversations, not more dashboard polish.

If the double-down is about customers, use the nights-and-weekends sales path in how to find paying customers for a side project without quitting your job. Shipping features without a path to buyers is just a hobby with deploy scripts.

Write a 90-day contract with yourself:

  • Outcome metric (example: 5 paying customers, or $500 MRR, or 20 weekly actives who complete the core job).

  • Weekly time budget (hours, not vibes).

  • One distribution habit.

  • Kill/pause trigger if the metric is missed (yes—pre-commit the exit).

Without an exit trigger, “double down” becomes another fog word. And if the double-down is tempting you toward going full-time, do that math separately: plug your savings and monthly costs into a free startup runway calculator and see how many months you would actually have before you hand in notice.

What about selling or handing it off?

If the project has users, revenue, or a codebase someone else could use, and the problem is mostly that you no longer want it, a sale or handoff can beat a kill. Small projects do change hands on marketplaces, and even a free handoff to an active user keeps the thing alive without your evenings. The full exit playbook, including what buyers check and how escrow works, is in how to sell a side project you no longer want to run.

How do you run a one-evening decision workshop?

Block 90 minutes. Phone in another room. Use this agenda:

0:00–0:20 — Evidence dump. Paste usage numbers, notes from three conversations, energy scores, life constraints.

0:20–0:40 — Score the four axes. Write evidence sentences. No debating yet.

0:40–0:60 — Forced choice. Circle kill, pause, or double down. If you hesitate, ask: “What would I tell a friend in my exact situation?” Usually the answer is obvious when it is not about your ego. If you are still truly split between two options, flip a coin and notice which result you were hoping for—that reaction is data.

0:60–0:75 — Next actions. Three concrete tasks for this week that match the choice (shutdown email, pause notice + calendar review, or calendar blocks + outreach list).

0:75–0:90 — Tell one person. Slack a friend, DM a maker, or email yourself with a future reminder. Social accountability beats private resolve.

If you cannot finish in 90 minutes, you are still collecting excuses. Schedule a second evening—not a second month.

What templates can you copy?

Kill email (short):

Subject: Shutting down [Product] on [date] I am closing [Product] on [date]. Thank you for trying it. Export your data here: [link]. Billing stops on [date]; if you were charged for unused time after that, reply and I will refund. I am pausing new work to focus elsewhere. Grateful you gave it a shot.

Pause note (short):

Subject: [Product] in maintenance until [date] I am putting [Product] in maintenance mode until [date] while I [job crunch / research / health]. Critical bugs only; no new features. On [date] I will either resume with a clear plan or shut down cleanly. Thanks for your patience.

Double-down contract (private):

Project: ___ 90-day outcome: ___ Weekly hours: ___ Distribution habit: ___ Review date: ___ If outcome missed: kill / pause (circle one)

What are the common traps that keep bad bets alive?

  • “I already built so much.” Sunk cost is not a strategy, and the theater-ticket study above shows how strongly it pulls. The market does not reimburse your evenings.

  • “Someone might need this later.” Archive it. Future-you can revive a clean repo faster than a guilt project.

  • “I will decide after one more feature.” Features rarely create pull. Pull should justify features.

  • “If I kill it, I wasted the year.” You bought information. That is only a waste if you refuse to use it.

  • “Doubling down means quitting my job.” No. Doubling down means protected blocks and a priced offer. Quitting is a later, separate decision with different math.

  • “I will just keep it running.” A project you keep online “for free” still costs a monthly bill, security updates, and the occasional support email. Count those honestly.

For a quiet way to test whether anyone cares before you bet bigger, the soft-launch mindset in how to soft launch quietly before a big launch day pairs well with a pause-or-double-down review—signal first, ceremony later.

What does good look like after the decision?

After a kill: You feel lighter within a week. You can name the lesson without rewriting history. Your evenings have room again.

After a pause: Users know the truth. You are not secretly coding. The review date is real. When it arrives, you decide again with fresh eyes.

After a double-down: Your calendar shows the blocks. Someone outside your head knows the 90-day outcome. You ship the paid promise, not the fantasy platform.

Side projects are optional. That is the privilege and the trap. Optional work still deserves adult decisions. Pick kill, pause, or double down—then protect your nights for the bet you actually chose.

Frequently asked questions

How long should you give a side project before quitting?

Long enough for one fair test, not a fixed number of months. A fair test means real outreach to the right people with a success number written down beforehand. If you have done that and the number did not come back, a few more months of building rarely changes it. If you never ran the test, run it before you quit.

Is it bad to have lots of abandoned side projects?

Abandoned is the problem, not ended. A project you killed on purpose, with users told and a short post-mortem written, is a finished experiment. The cost comes from projects left in limbo, still taking attention and guilt.

Should I pause or kill if I am burned out?

Burnout alone points to a pause, because it is a statement about your season, not the idea. Set a 60–90 day review date and stop all work in between. If the review date arrives and the evidence was already weak before the burnout, kill it then.

Can I restart a project after killing it?

Yes, if you archived rather than deleted. Keep the repo, the notes, and the post-mortem. Most restarts that work begin with a new, narrower angle that came out of the post-mortem, not with the old roadmap.

side-projectsdecisionskill-or-continuegrowthfounders