Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #4,412 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be: Growlytics AI — Growth Intelligence Agent is a self-reported tool that connects Google Analytics 4 (GA4), Google Ads, and Meta Ads data into a unified model. It allows users to ask questions through an agent backed by deterministic tools, with persistent memory across sessions, scheduled monitoring, and safe recommendations based on live evidence.
What changed: During the OpenAI Build Week hackathon, Growlytics added features such as user-scoped memory and forget behavior, recurring GA4 and Google Ads monitoring with recovery and run history, analysis-only worker authorization, and enhanced safety tests. The project was extended from an earlier version to include these new capabilities.
The single most important open question: Is there any evidence of actual usage or traction beyond the author's self-reported development work?
What The Product Actually Is
The description states that Growlytics AI is a growth intelligence agent that connects GA4, Google Ads, and optional Meta Ads data. It normalizes this data into a tenant-scoped model and allows teams to ask questions through an agent backed by deterministic tools.
It includes:
- Cross-session memory for goals, preferences, and workflow context
- Scheduled monitoring of GA4 and Google Ads with leases, recovery, manual-run support, and visible history
- Safe recommendations that include evidence, limitations, and guardrails without silently writing to ad accounts
The product is built using Next.js, TypeScript, React, Prisma, PostgreSQL on Supabase, NextAuth, and deployed on Render. It uses GPT-5.6 and OpenAI Codex for engineering assistance.
Inference: The tool appears designed to streamline growth team workflows by centralizing data access and decision-making, but no evidence of actual customer adoption or revenue is provided.
Positioning & Claim Evolution
The author positions Growlytics AI as a solution to fragmented growth workflows where context disappears between sessions, recurring checks remain manual, and AI answers can sound confident even when source data is missing or stale.
It claims to turn that fragmented workflow into a "persistent, evidence-backed growth intelligence loop."
Inference: The positioning reflects an attempt to address inefficiencies in current analytics and advertising platforms by introducing persistence and safety into AI-driven insights. However, the description does not indicate any market validation or competitive differentiation beyond its own self-description.
Target Customer & ICP
The author describes Growlytics AI as serving "growth teams" who make decisions across analytics dashboards, ad managers, spreadsheets, and chat history.
Inference: The target customer is likely marketing or growth professionals working in B2B SaaS environments where data silos and manual processes are common. No specific ICP segmentation or customer personas are mentioned.
Business Model & Pricing Evidence
There is no evidence of pricing information, business model details, or monetization strategy in the provided description.
Not evidenced: No indication of how the product will be sold, whether it's freemium, enterprise, or another model. No mention of revenue streams or customer acquisition costs.
Technical & Delivery Signals
The application is built with:
- Frontend: Next.js, TypeScript, React
- Backend: Prisma, PostgreSQL on Supabase
- Authentication: NextAuth
- Deployment: Render
- AI tools: GPT-5.6, OpenAI Codex
- Data connectors: GA4, Google Ads API, Meta Marketing API
Key technical features include:
- Tenant-scoped data normalization
- Encrypted connector tokens
- Production safety rules preventing fabricated fallback rows and ad-platform writes without approval
- Analysis-only worker authorization
- User-scoped memory and schedule management
Inference: The technical stack suggests a modern SaaS platform built with scalability in mind, but no evidence of performance metrics or production usage.
Traction & Maturity Signals
The description indicates that the project existed before Build Week and was extended during it. It mentions:
- 259 automated tests
- A verified local release gate
- Successful production build
- Dated repository history identifying relevant commits
However, there is no evidence of actual users, customers, or revenue.
Not evidenced: No data on user engagement, retention, or adoption beyond the author’s own development work.
Competitive Context
The description does not provide any information about competitors or how Growlytics AI compares to existing solutions in the market.
Not evidenced: No competitive analysis, pricing comparison, or differentiation strategy is described.
Key Risks & Red Flags
- No traction evidence: The product appears to be a prototype or early-stage development with no demonstrated user base or revenue.
- Self-reported only: All claims are unverified and based solely on the author’s submission.
- Limited team size: Only one member is listed, which may limit execution capacity.
- High technical complexity without validation: Features like scheduled monitoring, memory persistence, and safe recommendations require robust engineering but lack evidence of real-world testing or deployment.
Diligence Questions To Ask The Founders
- What specific growth challenges are you solving for your target customers?
- How do you plan to validate the utility of persistent memory and scheduled monitoring in practice?
- Are there any known limitations or edge cases with data normalization across GA4, Google Ads, and Meta Ads?
- What is your roadmap for moving from a development prototype to a scalable product?
- Have you considered how to handle multi-tenant isolation securely at scale?
- How do you intend to monetize this tool, and what pricing models are under consideration?
Investment/Partnership Verdict
This is a self-reported project submitted as part of an OpenAI hackathon. It shows early-stage development with technical ambition but lacks evidence of traction, revenue, or customer validation.
Confidence level: Low — due to the absence of any verified metrics, users, or business outcomes beyond the author’s own description.
Verdict: Not ready for investment or partnership without further demonstration of product-market fit, user adoption, or commercial viability.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.

