PawScript AI

Company: PawScript AI

Self-reported purpose: A clinic workspace for post-operative recovery workflow management in veterinary medicine.

Key claim: To provide secure, structured workflows that bridge the gap between clinic and home care without replacing veterinary judgment.

What changed: The project is a prototype built over a hackathon period, with no evidence of revenue, customers or traction beyond its own description.

Most important open question: Does the described product have sufficient commercial viability to justify further investment or partnership, given the lack of verified market data and customer feedback?

The description states that PawScript AI is a clinic workspace for post-operative recovery workflow management. It allows clinic staff to:

• Create owner and patient records
• Record surgeries
• Schedule follow-ups
• Capture structured home-context questionnaires
• Create veterinary review cases
• View consolidated patient case summaries

It also provides restricted owner access through expiring, revocable links that allow owners to view follow-up appointments and send non-urgent check-ins.

The system is described as not diagnosing, prescribing, or generating recovery plans. It does not assess wounds or provide emergency guidance.

Not evidenced: No information on pricing, monetization, or actual use cases beyond the prototype.

The author states that PawScript AI was inspired by a need to bridge the clinic and home without replacing veterinary judgment, aiming for a secure workflow that organizes patient context, procedures, follow-ups, intake information, and owner updates.

It is positioned as:

• A secure workflow tool for veterinary clinics
• Not a diagnostic or advisory system
• Designed to keep veterinary professionals in control

The claim evolution shows a deliberate focus on safety boundaries, with the team stating they learned that healthcare-adjacent software needs clear safety boundaries, not just good features.

Inferred: The positioning is cautious and risk-aware, focused on administrative workflow rather than clinical decision-making.

The description states that PawScript AI targets veterinary clinics, specifically those managing post-operative care for pets. It is designed to support:

• Clinic staff
• Pet owners (via restricted access)

It is not described as targeting individual pet owners directly, but rather as a tool for clinics to manage owner engagement.

Not evidenced: No information on clinic size, geographic scope, or specific use cases beyond post-operative recovery.

The description does not provide any evidence of pricing, business model, or monetization strategy. It is unclear whether PawScript AI will be sold as a SaaS subscription, a one-time license, or through other means.

Not evidenced: No mention of revenue streams, customer acquisition costs, or pricing tiers.

The system was built using:

• Frontend: Next.js 15 and TypeScript
• Backend: NestJS and TypeScript
• Database: Neon PostgreSQL with Prisma
• Deployment: Render
• CI/CD: GitHub Actions
• AI tools used: GPT-5.6 and Codex for development assistance

The system includes:

• Clinic-scoped roles and authorization
• Expiring, revocable owner-access links
• Owner check-ins protected with idempotency controls
• Activity and authentication audit records
• Responsive interfaces for clinic and owner portals

Inferred: The technical stack suggests a modern, scalable SaaS architecture, but no evidence of production deployment or performance data.

The project is described as a prototype built during a hackathon, with no evidence of:

• Revenue
• Customers
• User adoption
• Product-market fit
• Market traction

It was submitted to the OpenAI 2026 hackathon on Devpost, indicating it is in early-stage development.

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

The description does not provide any information about:

• Competitors
• Market size
• Existing solutions in veterinary workflow management
• Differentiation from current tools

Not evidenced: No competitive analysis or market positioning beyond the self-reported claims.

• No revenue, customers or traction: The project is a prototype with no verified commercial activity.
• Unclear business model: No pricing or monetization strategy described.
• High regulatory risk: Healthcare-related software requires strict compliance; the system must navigate clinical safety, privacy, and data handling.
• Limited team size: Only one team member (Rajiv Kumar) is mentioned, raising questions about scalability and execution capacity.
• AI use without clinical validation: The project uses AI tools for development but does not describe how AI will be used in clinical workflows or whether it has been vetted.

Inferred: The product is early-stage and unproven in the market. It may face significant challenges in gaining trust from veterinary professionals and navigating regulatory requirements.

1. What specific veterinary clinics are you planning to engage with, and what feedback have you received?
2. How do you plan to ensure compliance with veterinary privacy regulations (e.g., HIPAA)?
3. What is your go-to-market strategy for clinics?
4. Are there any existing partnerships or pilot programs with veterinary practices?
5. What is the long-term vision for AI integration, and how will it be vetted before deployment?
6. How do you plan to scale beyond a single developer?