Failed Projects & Post-Mortems

Archived: 4

Projects that did not work out. I shut them down, abandoned them, or pivoted. Documenting failures is more useful than hiding them — it prevents repeating the same bad assumptions.

OneStopWrite

FAILED
Started: 2026-05Stopped: 2026-09Time invested: 3 monthsStack: Next.js, TypeScript, SEO / AEO / GEO
What I built

A legal document and policy generator on onestopwrite.com (privacy policies, terms, cookie policies, business letters) that originated from a domain flip attempt, pivoted to pay-per-use, and was eventually retired.

Why I thought it would work

I originally purchased onestopwrite.com intending to flip the domain. When that didn't work out, I built a web-based policy generator, hypothesizing that providing instant legal policies for website builders and startups would attract search traffic and pay-per-use revenue.

What I expected

Expected pay-per-use document purchases or substantial organic search volume by providing customizable policy generators.

What actually happened

Pay-per-use pricing attracted zero buyers. Transitioning the tool to 100% free brought 3–8 daily organic users who actively generated policies. However, despite running multiple SEO, AEO (Answer Engine Optimization), and GEO (Generative Engine Optimization) experiments, traffic remained stuck in single digits.

Why I stopped

The legal document niche is overwhelmingly dominated by high-authority incumbents with massive backlink moats (e.g. TermsFeed, Termly). The single-digit daily traffic volume did not justify continued maintenance or domain renewal, so I allowed the domain to expire.

What I learned

1. In commoditized utility niches dominated by entrenched high-DR players, pure on-page SEO, AEO, and GEO cannot overcome massive backlink deficits. 2. Pay-per-use pricing creates excessive friction for simple template generators when competitors offer functional free tiers with higher trust signals.

OneStopRead

FAILED
Started: 2026-04Stopped: 2026-08Time invested: 4 monthsStack: Next.js, Python, Gemini Flash, Cron, Web Scraping
What I built

A blog website on onestopread.com that was pivoted into an AI-automated government exam alert portal with Gemini Flash summarization and cron-driven scrapers.

Why I thought it would work

Initially thought publishing articles on trending topics would attract organic search traffic. After that failed to rank against high-DA media sites, I pivoted to government exam notifications—hypothesizing that automated scrapers and Gemini Flash could generate clean, structured exam updates faster than cluttered legacy portal competitors.

What I expected

Expected automated programmatic exam coverage to rank quickly for low-competition notification keywords and build compounding search impressions.

What actually happened

Phase 1 (trending blog) got 0–1 clicks/day. Phase 2 (AI exam portal) showed promising early traction, growing to 20–30 daily clicks across Google and Bing. However, after 20–25 days, clicks abruptly collapsed to 0 and daily impressions flatlined to 5–20. Manual content rewrites with verified official government links failed to recover search rankings.

Why I stopped

The domain suffered an algorithmic content penalty or sandbox de-valuation typical of fresh domains running programmatic AI pipelines. Recovering search visibility without substantial external backlink authority was unsustainable, so I abandoned the project.

What I learned

1. Fresh domains running automated AI generation are heavily scrutinized by search engine spam and unhelpful content classifiers, regardless of UI cleanliness or metadata optimization. 2. Automated aggregation without proprietary primary data or pre-existing domain authority is fragile against search algorithm updates.

ZyoraAI Resume Builder

FAILED
Started: 2025-01Stopped: 2026-05Time invested: 5 months activeStack: Next.js, TypeScript, LLMs, PDF Generation
What I built

An AI-powered resume builder, JD optimizer, and interview prep platform with 50–80+ templates hosted on zyoraai.com.

Why I thought it would work

Hypothesized that combining job description (JD) keyword tailoring, AI cover letter generation, and interview question preparation into 50–80+ curated resume templates would convert job applicants into paying subscribers.

What I expected

Expected organic job-search queries and career communities to drive consistent freemium signups and paid template exports.

What actually happened

Built the complete platform (JD parser, cover letter writer, interview prep, 50–80+ templates including 8–10 tailored for large tech companies) by combining LLM tooling (ChatGPT, DeepSeek, Claude, Antigravity) with Next.js. Deployed on zyoraai.com. However, across 2–4 months of experimentation, organic user acquisition stalled and paid conversion was near zero in a crowded category.

Why I stopped

The AI resume builder niche became saturated with heavily-funded incumbents. Organic keywords required massive backlink authority that a new domain could not achieve quickly without unsustainable ad spend. Dropped the product and repurposed the domain for a computer vision project.

What I learned

1. Adding more features (50+ templates, interview prep, cover letters) does not solve distribution in a hyper-competitive search category. 2. Building specialized micro-utilities with clear technical moats (like biometric photo compliance) produces higher conversion than generic AI text generators.

Resourcify

FAILED
Started: 2023Stopped: 2024Time invested: 6+ monthsStack: Flutter, Dart, SendGrid
What I built

An ad-free Android mobile app providing curated semester exam preparation materials, previous year question papers, and educational notes for college students.

Why I thought it would work

College students consistently struggle to find organized, reliable semester syllabus notes and previous year question papers. Most existing resources were scattered across disorganized drives or buried behind ad-heavy websites.

What I expected

Expected steady organic adoption across university cohorts by offering a clean, completely free mobile app with zero ads.

What actually happened

The app achieved organic traction, reaching 1,000+ downloads on the Google Play Store and actively helping students prepare for semester exams.

Why I stopped

In 2024, during my final college year, I joined Mobiloitte in Pune as a Software Developer (left after 3 months due to lack of active project allocation) and then joined Collegedunia as a Software Developer. Due to full-time engineering commitments, I was unable to dedicate time to push required Android target SDK and Play Store policy compliance updates. After 3 warning notices from Google Play, the app and developer account were suspended.

What I learned

Mobile apps carry ongoing compliance and maintenance debt. Unlike static web utilities, app stores continuously enforce SDK upgrades and policy revisions. A zero-revenue free utility without automated maintenance or dedicated upkeep will eventually decay under platform policy shifts.