SharkzPro

Company: SharkzPro

Self-reported basis: The description is entirely self-reported and unverified; it originates from a Devpost submission for the OpenAI 2026 hackathon. No independent evidence of revenue, customers, or traction exists beyond what the author states.

What the company appears to be: SharkzPro is a product designed to help security operations managers schedule guards, track certification compliance, and maintain audit readiness. It was built using AI tools (Codex, ChatGPT) during a hackathon and includes a redesigned interface for key components like compliance dashboards, scheduling calendars, and guard profiles.

What changed: The project was redesigned using OpenAI's Codex to improve usability in three core areas: compliance tracking, shift scheduling, and guard profile views. The redesign focused on making it easier for operations managers to see who is compliant, scheduled, and what needs attention at a glance.

Single most important open question: Is there evidence of real-world usage or adoption beyond the hackathon context? The description states that the product was shipped to a live team managing 50 guards, but no further traction data is provided.

The description states that SharkzPro helps security operations managers:

• Schedule guards across shifts and sites
• Track certification and training compliance for each guard
• Maintain an audit trail ready for review

It also states that the product was redesigned using Codex to improve three key areas:

1. Compliance dashboard (certification/training status at a glance)
2. Scheduling calendar (shift assignment across guards and sites)
3. Guard profile records

These features are described as being restructured to allow managers overseeing dozens of guards to see critical information quickly, without manual digging through spreadsheets.

Inference: The product appears to be a SaaS or web-based tool for managing guard scheduling and compliance in security operations — likely aimed at small-to-medium-sized security companies or teams.

The description states that SharkzPro was “redesigned this week with Codex” to make guard compliance and scheduling “actually usable” for security operations managers. It also says the product had “underlying scheduling and compliance features,” but the interface made day-to-day use slow.

Claim: The tool is positioned as a solution to inefficiencies in manual spreadsheets and outdated UIs in security operations management.

Inference: The positioning evolved from an existing product with basic functionality to one that improves usability through AI-driven redesign, based on feedback from real users.

The description states:

• The tool is for “security operations managers”
• It was built with input from a manager running a company with 50 guards
• The user needs to track dozens of guards across shifts and sites
• The interface should be usable during shift changes

Inference: The primary customer is a security operations manager overseeing a team of multiple guards, likely in a small-to-medium-sized company.

Not evidenced. The description does not mention pricing, monetization, or business model details.

The description states:

• Built with: Codex, ChatGPT, Next.js, Supabase, TypeScript, Netlify, Namecheap
• Used Codex to drive a full redesign across three core UI areas
• The team made key product decisions themselves (e.g., what information to prioritize)
• Redesigned components without breaking existing functionality

Inference: The tool is built on modern web stack and leverages AI for UI rewrites, but the delivery approach was iterative and user-centered.

The description states:

• The product was shipped to a live team managing 50 guards
• It was redesigned during a hackathon (OpenAI Build Week)
• An operations manager who deals with 50 guards daily can now see compliance and scheduling information much faster than before

Inference: There is evidence of real-world use in a live environment, but no data on adoption, retention, or revenue.

Not evidenced. The description does not mention competitors or market positioning beyond the general category of guard scheduling and compliance tools.

1. No traction or revenue evidence: The product is described as being used by a live team, but no data on adoption, usage, or monetization is provided.
2. Hackathon origin: The project was built in a short timeframe (a week) and may not reflect long-term product maturity or scalability.
3. Single founder: The team size is listed as 1, which raises questions about execution capacity.
4. Unverified claims: The description makes strong claims about usability improvements but does not provide metrics or user feedback beyond one person’s experience.

1. What is the actual usage volume of the tool in the live environment?
2. How many security operations teams are currently using SharkzPro?
3. Is there a plan to monetize this product, and if so, what is the pricing model?
4. How did you validate that the redesign addressed real pain points, and not just assumptions?
5. What are the technical challenges in scaling the AI-driven UI redesign approach?
6. Are there any legal or compliance issues related to handling guard data or certifications?