A 90-Day AI Search Visibility Plan for AI-First Founders

Most AI search visibility plans read like roadmaps for a 6-person marketing team with quarterly OKRs. That is not the working pattern for an AI-first founder. The working pattern is a single operator who is already shipping product 30 hours a week, has 3 to 5 hours of visibility-work capacity per week, and needs the work to compound rather than queue. This post is the plan I actually run on Foglift and the cadence I recommend to every other AI-first founder who has asked me how to start. Ninety days is the right horizon: long enough that the structural work compounds, short enough that the founder can defend the time investment if the channel does not pay back.

The premise the plan assumes. AI citation is a real acquisition channel. Wynter’s 2026 B2B CMO Sentiment Survey reported that 84% of B2B CMOs use AI or LLMs for vendor discovery, with ChatGPT, Perplexity, and Gemini named as the top sources. Ahrefs Brand Radar’s October 2025 analysis of the top 1,000 ChatGPT-cited URLs found 28.3% had zero Google organic keywords, so the channel is mechanically independent of classical SEO. If you ship the structural foundation now and let it compound for 90 days, you measure a real change. If you skip it, your buyer goes to a competitor who shipped it instead. The plan below assumes you have decided the channel is worth 4 hours a week. The rest is sequencing.

The plan in one paragraph. Days 1 through 7 install the structural foundation: Organization JSON-LD on the root layout, FAQPage on the landing, Product schema on /pricing, a minimal /docs page, an MCP server, and freshness signals. Weeks 2 through 4 measure the baseline and close the lowest-scoring AEO dimensions. Weeks 5 through 8 ship one keystone content post per week using the 5-layer content stack. Weeks 9 through 12 build external citations through Reddit, Hacker News, Indie Hackers, and partnership backlinks. On day 90 you re-run the day 1 baseline prompt set and measure mention rate. The metric to watch is described in the final section.

Days 1 through 7: Install the structural foundation

The first week is a single 7-hour push that installs every layer the rest of the plan compounds on. Do not split it across multiple weeks. The downstream work assumes the foundation is in place; deferring any one item turns the next 11 weeks into retroactive fixes rather than forward leverage. The detail for each artifact is in the pre-launch checklist post; this section sequences them.

1. Day 1 (90 minutes). Ship Organization JSON-LD on the root layout. Include name, url, logo, sameAs (LinkedIn, GitHub, X/Twitter, Crunchbase), founder array, and a one-sentence canonical description. Repeat the canonical description in the homepage hero and meta description.
2. Day 2 (60 minutes). Ship FAQPage JSON-LD on the landing. Six questions, each wired to visible on-page content. Q1 is the entity definition; Q2 through Q5 are buyer questions a real prospect would type into a chat window; Q6 covers integration or pricing.
3. Day 3 (60 minutes). Ship Product or SoftwareApplication schema on /pricing. Required fields plus an offers array with price and priceCurrency. The block turns into a quotable price reference for LLMs answering “how much does X cost?”
4. Day 4 (90 minutes). Ship a minimal /docs page with TechArticle JSON-LD. Three sections at most: install, the simplest working example, and the env vars or auth header pattern. Long enough to be cited; short enough to keep the model on a single quotable page.
5. Day 5 (90 minutes). Ship an MCP server. The Model Context Protocol exposes your product to AI agents directly. For an AI-first founder, this is a Day-1 entity signal: it tells extractors your product is consumable by AI workflows, not just human-driven UIs. Foglift’s reference build for an MCP server is in /integrations/mcp.
6. Day 6 (30 minutes). Wire freshness signals. Sitemap with accurate lastmod, dateModified populated on every page that ships JSON-LD, and an IndexNow ping on every deploy. This is the cheapest 30 minutes you will spend in the 90 days.
7. Day 7 (60 minutes). Run the baseline. Use the AEO checker on the homepage, pricing page, and /docs. Save the scores. Run an AI Visibility scan across 8 to 15 buyer prompts on all five major engines. Save the mention rate per engine. These two snapshots are your day 1 baseline; everything after is measured against them.

At end of day 7 you have a brand with a disambiguated entity site-wide, five schema blocks live, an MCP server in the wild, freshness signals wired, and a baseline snapshot on file. That is the foundation. The next 11 weeks add layers; none of them work without this foundation present.

Weeks 2 through 4: Baseline measurement and gap closure

The next three weeks are the diagnostic phase. The point is not to ship more content; it is to read the baseline carefully and close the structural gaps the day 7 scan surfaced. Most founders skip this phase and start writing content immediately. That mistake costs 4 to 6 weeks because each new page inherits the structural weaknesses of the foundation.

Week 2 (4 hours). Open the AEO checker output and rank the 8 dimensions by score. The three lowest are your fix targets. Each dimension maps to a stack layer from the content stack: Structured Data Richness and AI Crawler Access are Layer 1 and Layer 5 fixes (more schema, better sitemap); Entity Identity is Layer 2 (sameAs gaps); Heading Clarity, FAQ Quality, and Content Depth are Layer 3 (prose); Citation Formatting and Topical Authority are Layer 4 (sources). Pick one dimension per page and ship a single fix. Re-scan; verify the dimension moved at least 10 points. If it did not move, the fix was too small.

Week 3 (4 hours). Read the AI Visibility scan results. For every prompt where the brand is not mentioned, note which competitor is. That competitor is winning the query, and the structural pattern that earned them the citation is the playbook for the keystone post you ship in weeks 5 through 8. Diagnose three of the prompts deeply: which page is the competitor citing from, what schema does it ship, what is the headline structure, how many external citations does it carry. The diagnostic loop is described in detail in the ChatGPT diagnostic post.

Week 4 (4 hours). Pick the eight prompts that will define the 90-day plan. The selection rule: each prompt must be one a real buyer would type, must have at least one engine where the brand is not currently mentioned, and must map to a piece of content the founder can authentically write. Eight is the floor; fifteen is the ceiling. Below eight the sample size is too small to measure movement; above fifteen the writing cadence becomes unsustainable for a solo founder. Lock the prompt set. Do not change it during the 90 days; changing the prompt set mid-plan invalidates the day 90 comparison.

Weeks 5 through 8: Keystone content shipping

Weeks 5 through 8 are the content phase. The deliverable is one keystone post per week, targeted at a single locked prompt from the week 4 prompt set, structured per the 5-layer content stack. Four posts in four weeks is the target. Each post is roughly 1500 to 2200 words, has its own FAQPage block with 6 questions wired to visible content, and ships with 6 or more inline-anchored external citations mixed across research, expert, and raw-data types.

The shipping order matters. Order the eight prompts by competitor strength, weakest first. Posts targeting weakly-defended prompts earn mention faster, which produces an early-win signal that keeps the founder shipping. Posts targeting strongly-defended prompts come in weeks 7 and 8 once the entity has accumulated enough authority footprint to compete.

Per-post mechanics. Open the empty page. Write the one-sentence definition that opens the article: noun + is + category + that + differentiator. Sketch the 6-question FAQ block; each question is verbatim phrasing a buyer would type. Write the answers; two to four sentences each, entity-first, no marketing language. Draft the body in 4 to 6 H2 sections; open each section with a definitional sentence. Add inline-anchored external citations as you write; the goal is 6 minimum, mixed types. Ship the JSON-LD; bump the sitemap lastmod; ping IndexNow. Re-scan the page on the AEO checker before publishing; if any dimension scores below 60, fix it before shipping.

One keystone post per week is the working cadence. A solo founder who has internalized the 5-layer stack can ship a keystone post in 3 to 4 hours; the founder who has not will spend 6 to 8 hours on the first post and 3 to 4 on each post thereafter. Front-loading the schema and stack discipline in week 1 makes the content phase 2 hours per post cheaper across the four-week window.

Weeks 9 through 12: Citation building and community presence

On-site content alone caps the mention rate around 40 percent on most prompt sets. The remaining lift comes from external citations: third-party sites that quote, link, or reference the brand. Weeks 9 through 12 are the external-signal phase. The budget is roughly 4 hours per week; the deliverables are a mix of community contributions, third-party citations, and listicle submissions.

Reddit and Hacker News (90 minutes per week). Pick 2 or 3 subreddits the buyer reads (for B2B SaaS: r/SaaS, r/Entrepreneur, r/SideProject, r/SEO depending on category). Reply to existing threads where the buyer is asking a question your product genuinely solves; do not start threads, do not link the product on first contact. The goal is to be quoted in someone else’s context as a knowledgeable voice in the category. Reddit and HN content is heavily indexed by LLM training corpora; a single well-placed comment that gets quoted in a top thread can move mention rate on a single prompt by 10 to 20 percentage points.

Indie Hackers and developer-facing build logs (60 minutes per week). Indie Hackers and Dev.to reward founders who write about how they built a feature, not what the feature does. Ship a 600 to 900 word build log per week describing one technical decision you made on the product. Reference the canonical entity definition in the byline so the post inherits the entity disambiguation work from week 1. The Indie Hackers community in particular over-indexes on AI-first founder readership.

Listicle and directory submissions (60 minutes per week). Find 3 listicles per week that cover your category (“best ___ tools in 2026”) and submit your product. Many are open submissions; some require an outreach email. The goal is to be on every list a buyer or AI engine might consult when scanning for category candidates. Listicle inclusion compounds: each listicle that mentions the brand strengthens the entity claim across every other listicle’s training corpus.

Partnership backlinks (60 minutes per week). Identify 1 to 2 adjacent SaaS tools per week whose buyer overlaps with yours. Reach out with a one-line integration proposal or a guest post offer. Each partnership backlink from a domain with Moz Domain Authority 50 or higher carries more entity-graph weight than 10 self-published posts.

Day 90: The measurement

On day 90 you re-run the day 1 baseline. Same eight to fifteen prompts. Same five engines. Same scoring method. The comparison is the single answer that tells you whether the channel is real for your brand. The metric: mention rate, calculated as the percentage of (prompt x engine) pairs where the brand is mentioned in the AI response, with secondary tracking on sentiment and citation position.

Three outcome bands. 0 to 20 percent mention rate. Something structural failed. Most often: a stack layer was skipped (usually Layer 2 entity disambiguation), the prompt set was too aspirational for current authority, or the content phase shipped fewer than four keystone posts. Diagnose the gap and ship a 30-day patch plan before continuing. 20 to 50 percent mention rate. The channel works; you are early. Roll into the maintenance loop and re-measure at day 180. Above 50 percent mention rate. The brand is now a default candidate on the locked prompt set. Lock the maintenance loop, broaden the prompt set by 4 to 8 prompts, and start the second 90-day cycle on the new ones.

Two secondary metrics. Citation position. When the brand is mentioned, is it first or third in the response. First-position citation is roughly twice as valuable as third-position because most buyers stop reading after the first concrete recommendation. Multi-engine coverage. A brand mentioned in 3 of 5 engines is more durable than one mentioned in 1 of 5 even if the single-engine rate is higher; multi-engine coverage indicates the underlying signals are well-formed across model architectures rather than over-fit to one.

What the plan does not do

Three things this plan does not promise. It does not replace product-market fit; an AI-cited brand with a weak product still produces unhappy buyers and the citation regresses within 2 quarters. It does not produce overnight results in the first 30 days; the compounding curve is real but it takes 60 to 90 days for retrieval indexes and trained corpora to integrate the new structural signals. And it does not work without the day 1 foundation; founders who skip the schema-and-MCP week and start with content alone typically see no mention rate movement at day 90 even after shipping the same content volume.

The plan also does not assume a content team, an agency, or paid distribution. It is sized for a single founder. If those resources are available the plan scales: parallelize comparison pages, glossary entries, integration docs, and category roundups across the same 90 days while the founder anchors the keystone narrative posts. The single-founder track stays the same; the multi-track work multiplies coverage without changing the structural sequence.

Day 91: Roll into the maintenance loop

Day 91 transitions the work from a one-time plan into a permanent operating loop. The maintenance loop is monthly: one keystone post, a weekly re-scan on the locked prompt set, monthly review of the AEO score on the top five pages, and a quarterly addition of 2 to 4 new prompts to the tracked set. The maintenance loop is described in detail in the solo-founder optimization loop post; that post is the operational rhythm the 90-day plan ramps into.

The compounding shows up most clearly between day 91 and day 180. Pages that earned mention in the day 60 to day 90 window typically retain it through day 180 because the entity disambiguation is now stable enough that new pages inherit citation faster. New keystone posts in the maintenance phase earn mention in 14 to 28 days instead of the 28 to 56 days that posts shipped in week 5 needed. That is the long-term payback: the 90 days is the foundation; the maintenance loop is where the channel becomes durable.

The honest version

The honest version of this post. Ninety days is enough time to install the foundation and verify the channel is real for your brand. Ninety days is not enough time to become a default category recommendation in every engine. That goal is a 12 to 18 month effort; the 90-day plan is the on-ramp that proves the channel and earns the right to invest the next 12 months. The founders I have seen succeed at AI search visibility all share one pattern: they shipped the day 7 foundation, measured the day 90 baseline against day 1, and continued the maintenance loop for at least 6 more months past day 90. The ones who stopped at day 90 lost the gains. The ones who continued doubled them.

Start day 1 this week. The detail for each artifact is in the pre-launch checklist. The structure for each keystone post is in the content stack. The diagnostic to run in week 3 is in the ChatGPT invisibility diagnostic. The maintenance loop you transition into on day 91 is in the solo-founder optimization loop. Five posts now cover the full arc. This one is the schedule.

FAQ

The FAQ block below is rendered as both human-readable text and FAQPage JSON-LD.

Is 90 days realistic for a solo founder shipping product at the same time?

Yes. The plan is structured for 3 to 5 hours per week, sequenced so the highest-leverage work happens first. Days 1 through 7 are a single 7-hour push that installs the structural foundation. Weeks 2 through 12 average one keystone content edit per week. A solo founder shipping product 30 hours per week can absorb 4 hours of visibility work without slipping the product roadmap.

What is the single metric I should care about on day 90?

Mention rate on a fixed prompt set of 8 to 15 buyer queries, measured across the five major AI engines. Run the baseline on day 1; re-run on day 90 with the same prompt set. A realistic target for a brand that started at zero mentions is 30 to 50 percent mention rate by day 90, with at least 2 engines citing the brand directly.

Why front-load the schema work in week 1 instead of spreading it across the 90 days?

Every downstream layer compounds on top of the entity definition. If the Organization JSON-LD lands on day 60 instead of day 7, every blog post, FAQPage block, and citation built between day 7 and day 60 carries weaker entity signal than it could have. Front-loading day 1 schema turns the rest of the plan into compounding gains rather than retroactive fixes.

Do I need a content team for this plan or can a single founder ship it solo?

Solo is the design point. The weekly content cadence is one keystone post per week, roughly 1500 to 2200 words, anchored on a single buyer query the founder has personal expertise on. A founder writing about the product they built has a depth advantage no agency can match. The 90-day plan only requires 8 to 10 keystone posts total.

What happens after day 90?

Day 91 transitions into the maintenance loop: one keystone post per month, weekly AI Visibility re-scan on the original prompt set plus 2 to 4 new prompts per quarter, monthly review of the AEO score on the top 5 pages with the lowest-scoring dimension as the next sprint target. The maintenance loop is where the gains compound.

Which platforms get most of the leverage and which can I skip in 90 days?

Prioritize Perplexity and Google AI Overviews in the first 60 days; ChatGPT and Claude take 60 to 90 days because their retrieval pipelines re-train on slower cycles. Perplexity reflects content changes within 1 to 2 weeks, so it is the fastest feedback signal during the plan. Skip Bing Copilot and smaller engines until day 90 unless they over-index in your buyer segment.

Fundamentals: Learn about GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) (the two frameworks for optimizing your content for AI search engines).