TrustRun — Automation Trust Score Before You Scale
Demoing an automation is easy. Trusting it with real customer data is terrifying. TrustRun runs your Zapier or Make workflow in shadow mode, compares outputs against a live baseline, and gives you a trust score before you flip the switch.
Difficulty
intermediate
Category
Business Automation
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
Validated by Real Pain
— sourced from real community discussions
Automation is easy to demo but hard to trust in production — teams currently run workflows in parallel manually and do spot-checks in spreadsheets to verify outputs before scaling.
What is it?
Automation teams waste hours manually spot-checking workflows before scaling — the 'run it in parallel and pray' method. TrustRun connects to Zapier or Make via webhook, intercepts test runs, compares outputs against expected results using Claude for semantic diff, and builds a trust score across 100+ runs. Below 90% confidence, it blocks promotion to production and fires a Slack alert with the exact failing step. Teams get a dashboard showing error rates, output drift, and a green/red deploy gate. Buildable now because Zapier and Make both expose webhook and API access, Claude handles semantic comparison, and Supabase stores run history cheaply.
Why now?
Zapier Teams revenue crossed $100M ARR in 2024 and the ecosystem has thousands of agencies running critical workflows with zero native validation tooling — the pain is validated and the webhook APIs are stable and free to use.
- ▸Shadow-mode webhook proxy that captures live workflow outputs without affecting production runs.
- ▸Claude-powered semantic output diff that flags when results drift from expected values, not just exact mismatches.
- ▸Trust score dashboard showing pass rate, error clusters, and a deploy gate per workflow.
- ▸Slack alert with exact failing step JSON diff when trust score drops below configurable threshold.
Target Audience
Automation agency owners and RevOps teams running 10+ Zapier or Make workflows, roughly 80,000 teams globally paying for Zapier Teams plans.
Example Use Case
A RevOps manager at a 50-person SaaS has 12 Zapier workflows handling lead routing. Before TrustRun, they ran parallel tests for two weeks manually. Now they get a trust score in 24 hours and deploy with confidence.
User Stories
- ▸As a Zapier agency owner, I want to see a trust score for each client workflow before promoting it to production, so that I stop getting 2am Slack messages about broken automations.
- ▸As a RevOps manager, I want to get a Slack alert when a workflow output starts drifting from expected values, so that I catch data corruption before it hits our CRM.
- ▸As an automation consultant, I want to share a trust score report with my client, so that I can justify the go-live decision with evidence instead of gut feel.
Done When
- ✓Webhook ingestion: done when a POST to the provided webhook URL appears as a new run row in the dashboard within 5 seconds.
- ✓Trust score: done when after 20+ runs the dashboard displays a percentage score with a green/amber/red status ring.
- ✓Slack alert: done when trust score drops below the configured threshold and a Slack message appears with the failing run's diff within 60 seconds.
- ✓Billing: done when clicking Upgrade opens Stripe checkout, payment succeeds, and the workflow limit increases immediately without page refresh.
Is it worth building?
$49/month x 30 teams = $1,470 MRR at month 3. $99/month x 150 teams = $14,850 MRR at month 9. Math: cold outreach at 4% conversion to paid trial, 70% trial-to-paid.
Unit Economics
CAC: $80 via LinkedIn DM outreach at 5% conversion. LTV: $1,188 (12 months at $99/month). Payback: 1 month. Gross margin: 88%.
Business Model
SaaS subscription
Monetization Path
14-day free trial then $49/month Starter (5 workflows), $99/month Pro (unlimited workflows, team seats).
Revenue Timeline
First dollar: week 3 via beta upgrade. $1k MRR: month 3. $5k MRR: month 7. $10k MRR: month 12.
Estimated Monthly Cost
Claude API: $35, Vercel: $20, Supabase: $25, Resend: $10, Stripe fees: $20. Total: ~$110/month at launch.
Profit Potential
Full-time viable at $8k-$15k MRR with low churn due to workflow dependency lock-in.
Scalability
High — add n8n support, Slack app, and enterprise SSO for upmarket expansion.
Success Metrics
Week 2: 5 beta teams connected. Month 2: 20 paying teams. Month 4: 80% month-2 cohort retained.
Launch & Validation Plan
Post in r/zapier and r/n8n asking if people manually verify workflows before scaling. DM 15 Make agency partners from the Make partner directory offering free beta.
Customer Acquisition Strategy
First customer: DM 20 Zapier-certified consultants on LinkedIn offering 60-day free access in exchange for a 30-minute feedback call. Ongoing: sponsor r/automation weekly thread, submit to Zapier app marketplace blog roundups, SEO targeting 'workflow testing automation'.
What's the competition?
Competition Level
Low
Similar Products
Datadog monitors infrastructure not workflow logic. Statuspage shows uptime not output correctness. n8n's built-in error view only catches hard failures, not semantic drift.
Competitive Advantage
First tool specifically for workflow trust validation — Zapier and Make have zero native trust scoring, and generic monitoring tools do not understand automation output semantics.
Regulatory Risks
GDPR: workflow payloads may contain PII — must offer data masking option and EU data residency note in privacy policy.
What's the roadmap?
Feature Roadmap
V1 (launch): webhook proxy, trust score, Slack alert, Stripe billing. V2 (month 2-3): n8n support, PDF trust report export, team seats. V3 (month 4+): custom scoring rules, Zapier app listing, API access for CI/CD pipelines.
Milestone Plan
Phase 1 (Week 1-2): webhook ingestion, Claude diff, trust score dashboard ships. Phase 2 (Week 3-4): Stripe billing, Slack alerts, deploy gate live. Phase 3 (Month 2): 5 paying beta customers, n8n support added.
How do you build it?
Tech Stack
Next.js, Claude API, Supabase, Resend, Zapier Webhooks, Make Webhooks — build with Cursor for backend logic, v0 for dashboard UI
Suggested Frameworks
-
Time to Ship
2 weeks
Required Skills
Webhook ingestion, Claude API semantic diff, Supabase RLS, Next.js dashboard.
Resources
Zapier Developer Platform docs, Make API docs, Anthropic Claude API, Supabase quickstart.
MVP Scope
app/page.tsx (landing + hero), app/dashboard/page.tsx (workflow trust scores), app/api/webhook/route.ts (webhook proxy ingestion), app/api/compare/route.ts (Claude diff call), lib/db/schema.ts (Drizzle schema for runs and workflows), lib/claude.ts (semantic diff helper), components/TrustGauge.tsx (score ring UI), components/RunTable.tsx (run history table), seed.ts (demo workflow runs), .env.example (required env vars).
Core User Journey
Paste webhook URL into Zapier -> run workflow 10 times -> see trust score appear on dashboard -> configure deploy gate -> upgrade to Pro.
Architecture Pattern
Incoming webhook -> Supabase run log -> Claude API semantic diff -> trust score computed -> Postgres updated -> Slack alert fired if below threshold.
Data Model
User has many Workflows. Workflow has many Runs. Run has one DiffResult. DiffResult has a trustScore float and a failureReason string.
Integration Points
Zapier Webhooks for workflow event capture, Make Webhooks for Make workflows, Claude API for semantic diff, Supabase for run storage, Resend for alert emails, Stripe for billing.
V1 Scope Boundaries
V1 excludes: native Zapier app listing, n8n support, team collaboration, custom scoring rules, mobile app.
Success Definition
A paying automation agency finds TrustRun via Reddit, connects their first workflow without founder help, and renews after month one.
Challenges
Distribution is the hard problem — automation teams do not google for 'workflow validation tools' so inbound SEO is slow. Direct outreach to Zapier agency partners and Make partner directory is the only realistic fast channel. Churn risk: teams scale workflows then stop using the validator, so usage-based nudges are critical.
Avoid These Pitfalls
Do not try to build a native Zapier app on day one — webhook proxy is faster to ship and equally powerful. Do not score trust on fewer than 20 runs or you will give false green signals that destroy credibility. Finding first 10 paying customers will take longer than building — budget 3x more time for outreach than development.
Security Requirements
Supabase Auth with Google OAuth, RLS on all run and workflow tables, payload masking option for PII fields, rate limiting 100 req/min per webhook endpoint via Vercel Edge middleware.
Infrastructure Plan
Vercel for Next.js frontend and API routes, Supabase for Postgres and auth, Sentry for error tracking, GitHub Actions for CI on main branch deploys.
Performance Targets
100 DAU and 2,000 req/day at launch. Webhook ingestion under 300ms. Dashboard load under 2s. No caching needed at v1 scale.
Go-Live Checklist
- ☐Security audit complete.
- ☐Payment flow tested end-to-end.
- ☐Sentry error tracking live.
- ☐Vercel monitoring dashboard configured.
- ☐Custom domain with SSL set up.
- ☐Privacy policy and terms published.
- ☐5 beta users signed off.
- ☐Rollback plan: revert Vercel deployment documented.
- ☐Launch post drafted for r/automation and r/zapier.
First Run Experience
On first run: dashboard shows 3 seeded demo workflows with pre-populated run histories and trust scores of 94%, 71%, and 100%. User can immediately explore the trust score UI, view a simulated failing run diff, and test the deploy gate toggle. No real webhook required to understand the product.
How to build it, step by step
1. Define Drizzle schema for Workflow, Run, DiffResult entities in lib/db/schema.ts. 2. Scaffold Next.js app with Supabase client and RLS policies via Supabase dashboard. 3. Build POST /api/webhook route that stores incoming run payload to Supabase. 4. Build lib/claude.ts that sends two run payloads to Claude and returns a semantic similarity score. 5. Build GET /api/workflows/[id]/score route that aggregates trust score from last 100 runs. 6. Use v0 to generate TrustGauge ring component and RunTable component. 7. Build dashboard page showing all workflows with trust scores and deploy gate status. 8. Add Slack webhook call when trust score drops below user-configured threshold. 9. Add Stripe billing with $49 and $99 plans gated by workflow count in middleware. 10. Verify: paste test webhook URL, fire 20 test payloads, confirm trust score updates and Slack fires on a bad run.
Generated
June 5, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.