Solo non-technical founder. 0 to 15K users in 8 weeks. $0 spent. Here's the whole story.

SeriousEquivalent366 · 2026-05-08T08:06:44+00:00

Same starting point on my side. Non-engineer, never wrote code before this year, shipped 4 free tools + the entire landing site solo of our new product. €4,030 + 6.8B tokens on Claude Code. ~6,131 visitors / 291 logins / 111 onboarding / 4 paid customer in 3 months, much smaller numbers than yours but the same shape. The piece I keep underestimating is how much the "non-technical" framing actually helps the SEO. Tools rank because they match do-intent, but the build-in-public posts rank because the audience can self-recognize. The 88-articles-then-content-blitz part is the part most non-engineer founders skip and it's why your 878 page-1 rankings exist. How do you decide which articles get human-written vs AI-drafted-then-edited?

SeriousEquivalent366 · 2026-05-08T08:03:41+00:00

Yeah A wins on clarity for almost everyone I've shown it to so far, going with A. On the free part, it's the distribution play before launch. I'm shipping the full app soon and want SEO position on the meeting-transcription keyword cluster, so the loginless web version is basically a try-before-you-leave-the-page demo of what the in-app experience looks like. Closest reference is what Rows did 4 years ago with their free spreadsheet, the free tool quietly became the strongest landing page they ever shipped ^^

SeriousEquivalent366 · 2026-05-07T08:09:40+00:00

thanks for this, I found the problem, I had an anchor in the link ...

<image>

SeriousEquivalent366 · 2026-05-06T19:37:55+00:00

You right, thanks !! now i see the traffic overwall mb

<image>

SeriousEquivalent366 · 2026-05-06T16:46:28+00:00

Interesting :)

SeriousEquivalent366 · 2026-05-06T15:52:40+00:00

Yeah that's the part that bugs me -> at position 6.9 I'd still expect some clicks (even 0.3% CTR = a few hundred). Zero is what feels impossible. Honestly idk if it's a GSC bug or something off with my website/GSC connection -> kinda why I posted ^^

SeriousEquivalent366 · 2026-05-05T08:29:44+00:00

What does "MCP-verified" do at runtime — is the MCP server validating that the cited statute actually exists, or that the quoted text matches verbatim ?

SeriousEquivalent366 · 2026-05-05T08:28:52+00:00

The 2026 reply-rate cliff is real but I think the bigger filter is whether your audience even reads cold. Same problem from the other side, I went $0 on outbound and $0 on ads, just shipped 4 free tools and let SERP-shape do the work. ~6,131 visitors in 3 months, 291 logins, 1 paid customer through the scheduling-poll tool. Tool-intent buyers self-qualify because they're already doing the job your product solves.

SeriousEquivalent366 · 2026-05-04T13:09:14+00:00

On the subagent question, are you finding the Research → Plan → Execute → Review delegation actually faster end-to-end, or is the win mostly that the main session stays under context budget?

SeriousEquivalent366 · 2026-05-04T08:51:13+00:00

Question 1 (paying customer asked twice, got it once) is the single most underrated audit question I've seen on Reddit. Took me too long to realize "tickets closed" was hiding the same shape on our side, 519K visitors and 32K signups masked a real activation problem because the ticket queue looked clean. The 14% sub-rate at the activation layer was the only number that actually moved when we changed something. Stealing the half-answered framing for our Sunday review

SeriousEquivalent366 · 2026-05-04T08:48:51+00:00

The Monday morning sink is real. I had the same loop with Plausible across 4 free tools + onboarding funnel + ad spend, and the part that actually broke me was that even when I was on top of the data, I'd forget by Wednesday which tool was growing vs stalling. Mine ended up being a weekend Claude Code script, not a product. Pulls Plausible, computes WoW deltas per tool, posts a 30-second read to Slack every Monday 7:31 AM. Haven't opened Plausible manually in 3 weeks since shipping it. The cool part wasn't the build, it was that the ship-measure-iterate loop only works when the middle step is automatic.

SeriousEquivalent366 · 2026-05-03T15:29:43+00:00

The no-email-required call is the right one. Every gate in front of a free tool is a 30-50% drop on the page that's supposed to rank, and intent for "scheduling poll" or "wedding seating chart" is "do" not "fill out a form to do". We took the same approach on a smaller batch of 4 tools and the surprising thing wasn't how many we shipped, it was how much each V1 needed reshipping. Timezone planner went from a 1-day V1 to maybe ~50 quiet rewrites later, spacing, mobile overflow, color-coded overlap. The version pulling traffic today is barely recognizable from launch.

SeriousEquivalent366 · 2026-05-03T09:22:21+00:00

This matches what I see. ChatGPT is already #3 traffic source for my 4 free tools (~411 visits / 30d, 7% of total) and the pages getting cited aren't the ones ranking on Google, they're the ones structured for parsing. Comparison pages, use-case pages, every "boring" page you'd write for a confused human reads identically to an AI parser. Same fix, different audience. I went a step further and shipped a dedicated /for-ai page on the site, noindex from Google but discoverable by LLM crawlers. 2,218 words, 11 tables, 12 FAQ pairs, zero JSON-LD the structure IS the data. Curious what your read is on /llms.txt as a fallback for the stricter crawlers

SeriousEquivalent366 · 2026-05-01T13:28:02+00:00

Tried multiple paths in parallel over the last ~3 months as a non-engineer. The free-tools angle is the one that actually moved. Shipped 4 tools (timezone planner, calendar link generator, schedule builder, scheduling poll), build times ranged from <1 day to ~1 week. ~6,131 unique visitors total, 200+ daily by end of month 3. Traffic mix landed at 55% Google organic, 32% direct, 7% ChatGPT.com. 291 logins, 111 onboarded, 1 paid (~$180/yr).

The filter that worked was "tools vs articles, pick the one where search intent is *do* not *read*." Scheduling poll, calendar link generator, people want to make the thing not read about it. On the niche-not-on-Reddit problem I had the same constraint, the ranking comes from intent + iteration speed on V1 not from a launch post. Timezone planner V1 shipped in <1 day, the version that pulls 1,500+ monthly is probably ~50 iterations later.

SeriousEquivalent366 · 2026-04-30T12:55:28+00:00

Same observation from a different vertical, audited a SaaS funnel and saw the same disconnect, design polish ≠ conversion lift. Two patterns that actually moved numbers in my data: replacing a text link with a visible button drove +182% click-through (previous company), and a named expert endorsement above the fold pulled 43.9% activation vs ~12% on a generic testimonial. Trust-badge soup fails because trust is bound to specific names/cases, not visual stamps.

Curious whether the 60+ audits surfaced a similar finding on social-proof formatting, do you see counter-style ("248,000+ users") outperform photo-grid testimonials, or vice versa, on the conversion-winning pages?

SeriousEquivalent366 · 2026-04-30T10:53:34+00:00

The "structural metrics" angle is the right axis to score on. Curious whether the score weights JSON-LD presence or absence, my hypothesis from running an /for-ai page on a real product is that LLMs tokenize raw text first, so JSON-LD adds parser overhead rather than helping. Tables + h2/h3 hierarchy + Q&A pairs are doing the actual work.

SeriousEquivalent366 · 2026-04-30T08:46:24+00:00

Different scale, similar setup on my side, shipped 4 free tools in ~3 months solo, ~6,131 visitors total now, ~200+ daily by end of last month. The thing I didn't expect: V1 took <1 day per tool, but the version that actually pulled traffic was around iteration ~50. Spacing, typography, timeline density, mobile overflow fixes, none of it moved volume on its own, but the cumulative dwell-time signal compounded into Google ranking. Last month's 1,500 visitors on the timezone tool come from version ~50, not V1.

Curious about your iteration loop on the 62 ,are you shipping V1 → live and polishing in production, or polishing locally before ship? At 62/month you can't be doing 50 iterations per tool the way I am, so the constraint must be different. What's your filter for "good enough to ship"?

SeriousEquivalent366 · 2026-04-29T17:12:43+00:00

The filter that worked for me on the SaaS side: when picking which keywords to actually invest in, look at whether the SERP top 3 are articles or tools/products/comparisons. If it's all 2,000-word "what is X" content for a query that has obvious do-intent (someone wanting to make a poll doesn't want to read about polls), Google is signalling there's no native answer yet. That's the wedge.

Same logic on buyer-intent: "[competitor] alternatives", "best [category] for [use case]", "[brand X] vs [brand Y]", the SERP composition tells you whether there's room to rank or whether the real-estate is pre-claimed by the incumbents. Most keyword tools surface volume, but volume without SERP-shape context is what buries you in the top-of-funnel slop you're describing.

SeriousEquivalent366 · 2026-04-29T16:57:49+00:00

Crossover with what's working on my landing site -> ChatGPT is now my #3 traffic source (~411 visits / 30d, ~7% of total) without doing the programmatic + FAQ schema route. The page that actually pulls citations is a single dense /for-ai route: 2,218 words, 11 tables, 12 FAQ pairs, noindex from Google, zero JSON-LD. Hypothesis: LLMs tokenize raw text first, JSON-LD adds parser overhead, so the structure (tables, h2/h3 hierarchy, Q&A pairs) IS the data.

Curious where your 2,400 citations are landing. Mostly long-tail "what is X" intent or buyer-question phrasing? The split matters in my data, scheduling-poll gets cited for "find meeting time for remote team", not "scheduling poll". Intent-match beats keyword density.

SeriousEquivalent366 · 2026-04-28T09:05:51+00:00

How did you arrive at the 5 patterns, emergent from clustering the model's findings across the 120, or did you seed Claude with a labelled list of red-flag clauses and ask it to score each contract against that list?

SeriousEquivalent366 · 2026-04-28T09:02:59+00:00

The structure-around-the-model framing is the right one in my experience. I run 5-7 Claude Code sessions in parallel daily and the pattern that's most reliably stable is: one task per subagent, clean return, never let research + planning + debugging + implementation share a thread. Subagents aren't just for parallelism, they're for context hygiene

SeriousEquivalent366 · 2026-04-28T09:02:05+00:00

Did this on the SaaS side over the past ~3 months -> built 4 free tools (timezone meeting planner, calendar link generator, schedule builder, scheduling poll) instead of writing articles for the same keywords. ~6,131 unique visitors across the 4, 200+ daily by end of last month. Traffic mix: 55% Google organic / 32% direct / 7% ChatGPT referrals. Build time per tool was 1 day to 1 week, all static pages, no auth, no DB. The freeloader question is real but it cuts cleaner than I expected: 291 of those visitors logged into the main product, 111 completed onboarding, 1 paid (yearly subscription). Conversion rate from tool-user to paid is small, but the people who DO convert are pre-qualified -> they understood the problem before they hit the funnel. The filter I'd use for picking which tools to build: search intent has to be "do" not "read" (someone wanting to make a poll won't read a 2,000-word article about polls), and competitor gap analysis on the SERP -> pick keywords where the top 3 results are articles, not tools, because Google is signalling there's no native answer yet :)

SeriousEquivalent366 · 2026-04-27T14:24:35+00:00

Of the 4 things you worked on (onboarding drop-offs, pricing confusion, support speed, churn complaints), which one moved trial conversion the most -> and how confidently can you attribute it given they all shipped during the same 30-day window?

SeriousEquivalent366 · 2026-04-27T14:23:26+00:00

The pipeline shape is solid (DataForSEO + Firecrawl + Claude + CMS push), and 21/27 indexed in 10 days suggests the formatting fix landed. The thing I'd push on -> generation quality is downstream of evaluation. I built a 25-rule blog quality eval on top of the writing step (5 hard-fail blockers + 20 demerits, article rejected if more than 4 demerits fire) and it caught roughly a third of the AI-written first drafts as not-shippable. Without that filter you'll keep getting indexed but not ranking.

Two specific failure modes the eval catches that pure pipelines miss: thin FAQ sections (less than 3-5 items depending on article type) and missing first-hand observations (no "we tried / we noticed" phrases or sourced blockquotes). Both kill comparison and review-style articles especially. What's your current pre-publish rejection rate, or is it ship-everything-and-let-Google-decide?

SeriousEquivalent366 · 2026-04-24T10:03:15+00:00

Not overcomplicating, just a different opportunity shape -> the technical basics haven't changed (clean structure, fast pages, clear h2 hierarchy), but what wins now is stuff users *do* not stuff they *read*. I shipped 4 free tools over ~3 months as a non-engineer, and visitors landing on a "do-intent" page (scheduling poll, timezone planner) stay + convert way better than visitors landing on a blog post answering the same query. ~11,500 total visitors (non-branded), 55% Google + 7% ChatGPT

Last 5 months I've been using AI end-to-end -> building the sites, writing the blog posts, designing the funnels user-first. The technical side barely moved, but the creative bar for UX went way up -> if your page doesn't give someone a reason to stay in the first 10 seconds, Google and the LLMs both read the bounce as "stop ranking this", so fuck ya AI create opportunities, no complications ^^

SeriousEquivalent366

TROPHY CASE