Launch HN: Introducing Prized (YC S26)

Empowering Non-Technical Teams to Create Secure Internal Tools

Prized is thrilled to announce our official backing by Y Combinator (S26). Our mission is simple: enable non-engineer staff to build the internal tools they need without compromising system security.

Wait weeks for a Jira ticket to be picked up by engineering $\rightarrow$ Build it yourself with AI.

---

🛠️ How It Works: From Prompt to Production

Instead of writing complex SQL or Python, users describe their needs in plain English. Admins maintain control by approving connectors and scoping data visibility once, ensuring that AI-generated tools never overreach.

The Workflow

Example Prompt: "Build a customer lookup for support. Search by name, email, or order #, with orders and open tickets in one view."

The AI Execution Process:

• Read from Salesforce
• Wrote 14 configuration files
• Ran 2 security checks
• Completed 12 logic steps
• Status: Done

---

💼 Versatile Use Cases Across the Org

Prized allows different departments to solve their own bottlenecks:

• Support Ops: Customer lookup tools for rapid ticket resolution.
• Finance: Reviewing refunds and managing risk flags with full audit trails.
• Rev Ops: High-level billing dashboards tracking $\text{MRR}$, subscriptions, and churn.
• Operations: Stockroom management to flag SKUs below the reorder point and update counts inline.

---

📊 Deep Dive: The "Renewal Desk"

To demonstrate the power of Prized, consider a Renewal Desk built on Salesforce, Postgres, and Zendesk.

Current Health Metrics:

• At-Risk ARR: $173\text{k}$ (which is $\approx 6\%$)
• Open Renewals: $28$
• Open Tickets: $37$ (representing $9\%$ of total)

Upcoming Renewal Forecast:

Account Detail View:

---

🛡️ Enterprise-Grade Security

Your team is already using AI, but Prized makes it safe. We replace blanket database access with a granular permission model.

1. Admin-Approved Connectors: Tools only touch production systems that have been explicitly cleared.
2. Strict Scoping: Every tool operates under its own specific role and grant list.
3. Comprehensive Auditing: Every single action is logged.

Sample Audit Log

Below is a representation of the workspace.log tracking tool interactions:

{
  "security_policy": {
    "default_access": "deny_all",
    "scope_level": "role_based",
    "audit_enabled": true
  }
}

Ready to start? [Sign in] | [Get started] | [Pricing]