OpenAI 2026 hackathon

DoggieAI

Doggie Education’s digital support service: practical help between lessons, with clear limits and a direct path to an educator or veterinarian.

Solo project by Boris Zarcone · 0 likes · 0 comments

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 #3,780 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

Company: DoggieAI

Self-reported purpose: A digital support service for dog owners and educators, offering practical help between lessons with clear limits and a direct path to an educator or veterinarian.

Key commercial signals: The description states that DoggieAI is a “digital support service” with two distinct paths — one public (informational), one authenticated (personalized guidance). It includes subscription management, billing via Stripe, human handoff capabilities, and a curated knowledge base.

What changed: The project evolved from an early prototype into a more complete product during OpenAI Build Week using Codex with GPT-5.6 to refactor code, improve safety, and enforce rules through application logic rather than just prompts.

Most important open question: Is there evidence of real user adoption or traction beyond the single developer’s account?

Note: This analysis is based solely on the self-reported description provided by the author. No independent verification, revenue data, customer names, or traction metrics are available.

Back to contents

What The Product Actually Is

  • The description states that DoggieAI is “the digital support service of Doggie Education.”
  • It offers two distinct paths:
    • A public chat answering general questions about services, prices, and bookings.
    • An authenticated subscriber path providing personalized educational guidance with conversation history, message quotas, account management, and extra-message purchases.
  • The system includes:
    • A curated knowledge base
    • Administration area for conversations, documents, plans, subscriptions, leads, consent records, discount codes, and AI cost monitoring
    • Integration with Stripe for billing
    • Mechanisms to hand off cases to humans via WhatsApp or encrypted callback request
  • It is described as an end-to-end service, not just a chat window.
  • The product uses retrieval-augmented generation (RAG), with Gemini-family models and embeddings for AI processing.

Inference: The system appears to be built around a hybrid approach combining AI-generated responses with human oversight and structured data handling.

Back to contents

Positioning & Claim Evolution

  • The author states that DoggieAI was already named before Build Week.
  • It emerged from a practical need: owners have questions outside scheduled lessons, but the service does not pretend to replace educators or veterinarians.
  • The positioning emphasizes:
    • Continuity in support between lessons
    • Clear limits on what AI can do
    • Pathways to professionals when needed
  • During Build Week, the product was refactored using Codex with GPT-5.6 to improve safety and structure.
  • The author claims that the service enforces important rules through code rather than relying solely on prompts.

Claim vs Fact: The description positions DoggieAI as a safe, structured AI assistant for dog training, but does not provide evidence of actual usage or user feedback beyond the developer’s own account.

Back to contents

Target Customer & ICP

  • The target customer is likely:
    • Dog owners who seek ongoing support between lessons
    • Subscribers to Doggie Education who want personalized guidance
  • The product distinguishes between:
    • Free users (public chat)
    • Authenticated subscribers (personalized guidance)
  • Subscribers are expected to pay for services, with billing managed via Stripe.
  • There is no explicit mention of specific demographics or behavioral segments beyond “owners” and “educators.”

Not evidenced: No data on customer acquisition, retention, or usage patterns.

Back to contents

Business Model & Pricing Evidence

  • The business model appears to be:
    • A freemium model, with a public chat for general info and an authenticated path for personalized support.
  • Authenticated users can:
    • Purchase extra messages
    • Manage subscriptions via Stripe
    • Access conversation history and account features
  • There is mention of:
    • Message quotas
    • Extra-message purchases
    • Subscription management through Stripe Checkout and Customer Portal
  • No explicit pricing tiers or revenue figures are mentioned.

Inference: The model likely relies on recurring subscription revenue from authenticated users, with optional add-ons for additional messages.

Back to contents

Technical & Delivery Signals

  • Built with:
    • Server-rendered PHP with MySQL/MariaDB
    • HTML5, CSS3, JavaScript
    • Hostinger hosting environment
  • Uses REST-style endpoints for chat, subscriptions, account activity, feedback, and human handoff
  • AI stack includes:
    • Gemini-family models (including embeddings)
    • RAG pipeline with retrieval from curated knowledge base
    • OpenAI tools (Codex, GPT-5.6) used for engineering assistance during Build Week
  • The system handles:
    • Simultaneous requests
    • Stripe webhook handling
    • Database migrations and updates
    • Mobile experience design
  • Codex was used to refactor code, harden authentication, and implement concurrency-safe logic.

Inference: The technical stack is lightweight and designed for shared hosting, suggesting a focus on cost-efficiency over scalability or performance.

Back to contents

Traction & Maturity Signals

  • The project has:
    • An early prototype
    • Been refined during OpenAI Build Week using AI tools
    • A functional end-to-end system including billing, subscriptions, and human handoff
  • No evidence of:
    • Real users or customer base
    • Revenue or monetization data
    • Customer feedback or usage analytics
    • Product-market fit validation

Absence of evidence: There is no indication that the product has been tested with real users or scaled beyond a single developer’s environment.

Back to contents

Competitive Context

  • The description does not reference competitors.
  • It implies a niche in dog training support services, where AI is used to supplement human educators and veterinarians.
  • No mention of similar platforms or market positioning relative to others.

Not evidenced: No competitive landscape, pricing comparison, or differentiation strategy provided.

Back to contents

Key Risks & Red Flags

  • Single developer team (1 member) — raises concerns about scalability, maintenance, and long-term viability.
  • Lightweight stack on shared hosting may limit performance and reliability at scale.
  • No verified user data or feedback — the product is unproven in real-world use.
  • AI safety mechanisms are enforced by code, which is good, but relies heavily on the developer’s ability to maintain them.
  • Use of GPT-5.6 and Codex during development suggests a reliance on AI tools for engineering rather than internal expertise — may indicate lack of deep technical depth.

Inference: The product is in early development stage and lacks real-world validation or commercial traction.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual user base, if any? How many people are using this service?
  2. Are there any real customer testimonials or feedback from users?
  3. Has the system been tested with real dog owners and educators?
  4. What are the specific use cases where the AI fails or hands off to humans?
  5. How is the curated knowledge base maintained and updated?
  6. Is there a plan for scaling beyond shared hosting?
  7. Are there any legal or compliance issues related to handling sensitive data (e.g., veterinary records)?
  8. What is the long-term vision for integrating with DoggieHub?

Back to contents

Investment/Partnership Verdict

  • Not evidenced: No financials, revenue, or customer traction are provided.
  • The product appears to be a conceptual prototype built during a hackathon, not yet validated in the market.
  • It shows some technical sophistication and clear intent around safety and user experience.
  • However, the lack of real users, revenue, or commercial activity makes it difficult to assess its viability for investment or partnership.

Verdict: Not ready for investment or partnership at this time. A more mature version with traction and user validation would be required before considering further due diligence.

Back to contents

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.