Docs SaaS, 6 Months In: Keep Going or Cut?

Direct Answer

Run the 7-question decision workflow. If 5 or more answers are red, shut it down or pivot the wedge. If 4 are green and 3 are red, give it 90 more days with one focused bet. If 5 or more are green, keep going and stop second-guessing every week.

Six months is the right moment to stop running on vibes. The decision is not “will this work eventually.” The decision is “is the next 90 days worth the current cost.” A docs SaaS is a hard category because the buyer’s pain is real but rarely urgent. You need to see signal in usage, not in conversation. The 7 questions below force that signal into the open.

Use This When And When To Skip It

Use this	Skip this
4 to 9 months into paid usage with mixed signals	First month of paid usage, too early to know
You have analytics, a billing source, and a notes file	You have not measured retention or revenue
You are willing to act on the result, even shutdown	You want the workflow to confirm what you already feel
The product has at least 10 paying or actively returning users	Zero paying users, no real retention to measure

Tradeoff: the framework will sometimes say “kill it” when you do not want to. That is the point. If you only want a sanity check that you should keep going, you do not need a framework.

The System

Trigger     -> 6-month checkpoint, or any month with a "should I quit?" thought
Inputs      -> billing data, retention chart, weekly active users, support load, your time log
Decision    -> answer the 7 questions, score each green/yellow/red
Rule        -> 5+ green = continue. 4 green + 3 red = 90-day focused bet. 5+ red = kill or pivot
Approval    -> sleep on the result one night before acting
Output      -> a written decision (continue, focused bet, pivot, kill) and what you will not do next quarter
Feedback    -> revisit at the next 90-day checkpoint

The rule is the point. Without a rule, every month feels like a new decision. With a rule, you make the decision once and execute.

Steal This Workflow

This is the 7-question decision framework. Answer each green, yellow, or red.

1. Unprompted repeat usage. Are at least 30% of users from month 1 still using the product in month 6 without an email reminder? Green if yes, red if under 10%, yellow in between.

2. Revenue trend. Is monthly revenue up at least 20% over the last 90 days? Green if up 20%+, red if flat or down, yellow if up under 20%.

3. Sales conversation pull. In the last 30 days, did at least 3 people ask to pay before you pitched them? Green if yes, red if zero, yellow if one or two.

4. Support load per user. Are you spending under 30 minutes per paying user per month on support? Green if under 30, red if over 90, yellow in between.

5. Differentiation. Can you name one thing your product does that a top-3 competitor does not, and that at least one paying customer cites? Green if yes with the customer quote, red if no, yellow if you can name it but no customer has.

6. Founder energy. Do you want to work on this 4 days a week for the next 90 days? Be honest. Green if yes, red if no, yellow if conditional (“if X changes”).

7. Opportunity cost. Is there a clearly better use of the same 90 days that you would actually execute? Green if no clear alternative, red if yes and you would actually do it, yellow if you have ideas but no commitment.

Apply the rule.

Result	Action
5+ green	Continue. Stop revisiting until the next 90-day checkpoint.
4 green, 3 red	Pick one of the red answers, name a 90-day focused bet to flip it, run.
5+ red	Kill or pivot the wedge. Write the postmortem. Move.

Sleep one night before acting. Then act.

What This Looked Like For This Page

The topic came from the weekly AEO run, not from a docs SaaS Chris built.

The run pulled 936 raw Reddit RSS entries, scored 314 candidates, generated 25 AEO briefs, and marked 9 as publish_now. This one passed because:

Gate	Why it passed
Source language	The thread asked “took 6 months to build a docs SaaS, no clue if I should keep going” in plain founder language
Artifact	The answer is a copyable 7-question rubric with a clear decision rule
Cluster fit	It links into the AI stack post, the workflow planner, the n8n tutorial, and the n8n agent workflow without straining

The page is research-inspired by the thread, not a claim that Chris ran this specific decision on a docs SaaS.

What Most People Get Wrong

The mistake is treating “should I keep going” as one big yes/no question.

Three failure modes:

They ask the question every week. The decision gets re-litigated on Mondays, after every harsh tweet, and every time a competitor posts a launch. Set a 90-day checkpoint and do not revisit between checkpoints.
They measure signups instead of retention. Signups are easy and lie. Retention is hard and tells the truth. At month 6, retention is the only number that matters.
They confuse audience traction with product traction. A growing follower count is a content brand, not a product. Both are fine. They are not interchangeable. If audience is growing and product usage is flat, the content brand is the asset, not the SaaS.

The rule beats the gut at the 6-month mark. After 18 months, the gut beats the rule. You are not at 18 months.

How I Would Build This In Ship Lean

The Ship Lean version makes this a workflow you run quarterly, not a one-time framework.

The data lives in a sheet. Each row is a quarter. Columns are the 7 questions, the score, the rule output, and the decision. The sheet is what tells you a year from now whether the rule was right.

n8n runs the checkpoint reminder. A quarterly cron, the same pattern as the n8n AI agent workflow, pings you with last quarter’s row and the new template. The n8n AI agent tutorial covers the trigger-decision-gate shape.

Plan the workflow before you build. Use the Claude Code n8n workflow planner to sketch the cron, the data pull, the rubric prompt, and the human decision step.

Audit any imported JSON. Run it through the n8n workflow JSON auditor.

The stack stays small. One sheet, n8n, one billing source, one analytics source. The AI stack for solo founders post goes deeper on what to keep and what to cut.

Use the same workflow on your search content. If you decide to keep going, the next bottleneck is distribution. The Claude SEO workflow post shows how to wire Claude as a workflow step so your blog stops being the weakest part of the funnel.

Next Step

If you are at the 6-month mark on any product, run the 7 questions this weekend. Write the answers. Apply the rule. Sleep on it. Then act.

The Claude Code n8n workflow planner gives you the cron, data pull, and rubric nodes in one map so the next checkpoint is a workflow, not a vibe.

Source Signal

Research-inspired by a Reddit thread where a founder asked whether to keep going on a docs SaaS after 6 months. Treat the thread as one operator’s question, not as proof of Chris’s results. Original: r/SaaS: “Took 6 months to build a docs SaaS. No clue if I should keep going”.

FAQ

What does keep going actually mean here? Another 90 days of paid attention. Not forever. The decision is about the next 90 days, not eventual success.

What is the single best signal at 6 months? Unprompted repeat usage. People returning without an email reminder.

Should I rebuild, rebrand, or shut down? Run the 7 questions first. Rebuild and rebrand both cost another 90 days. Pick the option the data supports.

Is build-in-public a substitute for users? No. Audience traction and product traction are different lines.

When should I skip this framework? Skip it if you are still in month one. Six months is the right time.

Docs SaaS, 6 Months In: How to Decide Whether to Keep Going.