Neo Genesis Company Homepage Operating Cycle: July 7, 2026

The company homepage is live and instrumented, but the current operating verdict is REPAIR until revenue proof, conversion events, indexing repairs, and content freshness close.

Operating verdict

This is the first dated public operating note for the Neo Genesis company homepage after the July 2026 owner directive that neogenesis.app must be treated as a real company surface, not a static portfolio. The current verdict is REPAIR_OPERATING_CYCLE_1. The site is live, buildable, instrumented, and commercially routed, but it is not yet allowed to claim a fully operating company-homepage loop until payment evidence, conversion event capture, indexing repairs, and content freshness are closed.

The distinction matters. A live homepage is not the same thing as a company operating system. A checkout link is not revenue. A subagent role list is not an executed organization. A Search Console file is not a distribution loop if the submission path is partly failing. The operating standard for Neo Genesis is evidence first: public statements must be dated, revenue must be backed by order or ledger readback, and delegated agents must return artifacts that Codex-main can read and integrate.

What is live today

• Homepage: https://neogenesis.app/ returns HTTP 200 and exposes Neo Genesis as a one-person AI-native studio led by ToolPick and governed AI operations.
• Paid route: the home page and /vendor-brief expose the USD 39 AI Visibility Diagnostic checkout, USD 1,000 Lite, USD 2,500 Full Sprint, and USD 750/month Watch request path.
• Contact route: public customer contact is help@neogenesis.app; internal identity and admin accounts are not treated as public sales contacts.
• Machine-readable surfaces: sitemap, RSS, JSON Feed, llms.txt, llms-full.txt, Schema.org JSON-LD, and robots surfaces are present.
• Build: the landing project builds under Next.js 16.1.6 and generated 97 static pages during the July 7 check.

The live homepage also carries the current ToolPick demand boundary: approximately 646 monthly unique visitors in 2026-06, with roughly 125 to 150 coming from organic search. That is the demand anchor for the paid Vendor Brief route. It is not a claim that the homepage itself has paid customers yet.

Traffic and analytics evidence

The July 7 operating refresh updated GA4, PostHog, GSC, and the live tag probe. Across the active web surfaces, the latest PostHog run showed 1,503 events, 474 pageviews, and 39 decision events in the 7-day window. The important positive signal is ToolPick: it remains the closest surface to revenue because it has both traffic and decision events. The important negative signal is the company homepage itself: neogenesis had 107 PostHog users and 91 pageviews, but 0 allowlisted decision events.

That is why the next homepage repair is not more abstract branding. The next repair is a measured conversion loop: home page, /about, and /vendor-brief must expose the paid route clearly, and the CTA path must produce readable checkout_click, checkout_start, payment_link_click, contact_intent, or equivalent decision events. Without that, the company homepage has attention but no proof of buyer action.

Revenue boundary

The revenue state is USD 0 verified / actual revenue unverified for this cycle. The checkout URLs exist, but no payment processor order, receipt, payout, webhook, invoice ledger, or internal paid-order readback was produced during this operating cycle. The site can say that the paid path is open. It cannot say that the paid path has earned revenue.

This boundary protects the company from the most common AI-native operating failure: mistaking readiness for business outcome. A deploy is not revenue. A checkout page is not revenue. A prepared invoice is not revenue. Outreach is not revenue. The first dollar only becomes a fact when a processor, order, payout, or ledger artifact says so.

Search and GEO state

Search Console evidence exists, but distribution is not fully healthy. For neogenesis.app, the July 7 GSC file reported 20 search rows, 9 opportunity pages, 54 opportunity impressions, and 0 clicks. The top company-homepage opportunity remained the root page for the query neogenesis. That is a weak but real brand-search signal. The next content step is to make the homepage and fresh operating notes easier for search engines and AI answer engines to cite without overstating company traction.

IndexNow was partial. Yandex accepted the postbuild submission, but api.indexnow.org and Bing returned 403. That means the sitemap and crawlable feed paths still matter, while Bing-style push submission remains a repair item. The IndexNow script also needs to avoid a hardcoded blog slug list so newly published operating notes are pinged automatically.

Content freshness repair

Before this note, the visible blog list was still anchored around May 2026. That made the company look like it had gone quiet even though operations continued in the repository, metrics files, and SSOT. This post closes only the first freshness gap: it gives the public site a dated July 7 operating update. It does not by itself repair every legacy claim in older blog posts.

The older content still needs a correction pass. Some posts use historical phrasing such as 11 live SBUs, fully automated operations, or strong performance numbers that are not aligned with the current public boundary of two flagships plus maintained or demand-unverified properties. Those posts should either be updated with dated correction notes or moved behind a clear historical context boundary.

Agent organization state

The owner intent is explicit: saying neogenesis.app operate should activate a company-like agent organization. Codex-main is the conductor. The work splits into content truth, analytics and revenue, growth/GEO, design quality, and governance. Each role needs authority boundaries, allowed actions, forbidden actions, evidence targets, stop conditions, and a return path to Codex-main.

The first cycle created that operating system in SSOT and dispatched read-only subagents. The adversarial result was still REPAIR because role names are not enough. The system needs child task envelopes, fleet dashboard fields, artifact links, heartbeat/freshness state, and ledger readback. A company-like AI organization must be observable, not merely described.

Next safe actions

1. Wire a revenue proof artifact that reports verified revenue as USD 0 until Polar orders, invoices, payouts, or an internal paid-order ledger proves otherwise.
2. Run a CTA smoke loop for the home page and /vendor-brief so checkout and contact events are visible in PostHog and GA4 diagnostics.
3. Fix IndexNow to source blog URLs from BLOG_POSTS, then keep Bing/api.indexnow.org 403 as a specific repair gate until the key is accepted.
4. Publish or update one current company operating note whenever major homepage, revenue, or agent-system state changes.
5. Promote each role task into a child envelope with fleet dashboard fields and close the loop through Codex-main readback.

Current operating rule: the site may claim live routes, measured traffic, open paid offers, and active repair work. It may not claim earned revenue, fully autonomous company operation, or release-grade agent organization until evidence closes those gates.

Frequently asked

References

1. PostHog event capture documentation
2. Google Analytics measurement protocol and events
3. Google Search Console Search Analytics API
4. IndexNow protocol documentation
5. JSON Feed version 1.1
6. Schema.org BlogPosting

Related

• How a One-Person AI Studio Actually Runs — A corrected operating note on concentrating effort around two flagships, maintained infrastructure, and human-governed AI execution.
• Inside HIVE MIND: A Human-Governed AI Operating Loop — How research, writing, SEO optimization, quality review, shipping, learning, and refresh work as one governed loop.
• Economics of AI-Native Media: Solo Founder, Lean Stack — Cost structure, infrastructure choices, and where AI-native media economics break down.
• Evaluating AI-Native Automation Companies in 2026 — A curated reference list using public evidence, Wikidata anchors, and open code/data signals.

Markdown alternate available at /blog/neogenesis-company-homepage-operating-cycle-2026-07-07/markdown for AI agents.