Executive Summary
Protectron is an EU AI Act compliance platform that I designed and built from the ground up in 72 hours. The project addresses a critical €4.5 billion market gap: while enterprise compliance solutions cost €50,000-200,000 annually, startups and SMBs building AI products have no affordable options to achieve regulatory compliance.
This case study documents the complete product design journey—from identifying the market opportunity through deep research, conducting user interviews, designing comprehensive user flows, and building a production-ready platform with a developer SDK, compliance dashboard, and 28 pages of marketing and documentation content.
Key Outcomes:
- Complete SaaS platform with risk classification, document generation, and audit trails
- Python and TypeScript SDKs with LangChain, CrewAI, and AutoGen integrations
- 78,000+ words of content across landing pages, documentation, and resource guides
- Production-ready infrastructure with EU data residency and GDPR compliance
- Pricing model starting at €99/month (10-50x cheaper than alternatives)
1. The Problem
Market Context
The EU AI Act is the world's first comprehensive AI regulation, affecting every company that develops, deploys, or uses AI systems serving European users. Enforcement began in February 2025, with full high-risk requirements taking effect in August 2026. Non-compliance carries penalties up to €35 million or 7% of global revenue.
Through extensive research using Claude for deep analysis and conversations with AI developers, I identified four critical pain points:
Pain Point 1: Prohibitive Costs
Enterprise solutions like Credo AI and Holistic AI cost €50,000-200,000 annually. Consulting engagements run €30,000-100,000 per project. For a Series A startup or SMB, these costs are prohibitive—often exceeding their entire compliance budget.
Pain Point 2: Overwhelming Complexity
The EU AI Act spans 400+ pages of dense regulatory text with 113 specific requirements for high-risk AI systems. Most teams lack the legal expertise to interpret requirements, the technical knowledge to implement them, and the time to manage ongoing compliance.
Pain Point 3: No Starting Point
Companies don't know where to begin. Is their chatbot high-risk? What documentation is required? Who is responsible—legal, engineering, or product? The regulation creates anxiety without providing clear action steps.
Pain Point 4: Continuous Burden
Unlike one-time certifications, EU AI Act compliance is ongoing. New AI systems require assessment, documentation must stay current, and audit trails need continuous capture. Static consulting deliverables become outdated immediately.
2. Research & Discovery
Methodology
My research combined quantitative market analysis with qualitative user research to validate the opportunity and define the product direction.
Deep Research with AI
I leveraged Claude's deep research capabilities to analyze the complete EU AI Act regulation, map all 113 requirements for high-risk systems, identify enforcement timelines and penalties, and understand the competitive landscape. This AI-assisted research compressed what would typically take weeks into hours.
User Interviews
I conducted conversations with AI developers, CTOs, and compliance officers to understand their pain points firsthand. Key insights emerged:
"We lost a €800K enterprise deal because we couldn't answer basic questions about EU AI Act compliance. The procurement team walked away."
— CTO, Series A HR Tech Startup
"I was told to 'figure out AI compliance' with no budget, no resources, and no idea where to start. I've been Googling for three months."
— Compliance Officer, Mid-Market SaaS
Key Finding: No self-service, affordable EU AI Act compliance platform existed for SMBs and startups. This validated the massive market opportunity.
User Personas
Based on my research, I defined three primary personas:
Sarah — Head of Legal at AI Startup
- Company: Series A-B AI startup, 30-100 employees
- Pain: Enterprise deals stalling over compliance questions
- Budget: Can expense €99-299/month without approval
- Urgency: HIGH — losing deals to compliance gaps
Marcus — CTO at Growing SaaS
- Company: B2B SaaS, 50-500 employees with AI features
- Pain: Deployed AI features, worried about liability
- Budget: Engineering budget, can justify €299-999/month
- Urgency: MEDIUM-HIGH — enterprise customers require proof
Elena — Compliance Officer at Mid-Market
- Company: 500-2000 employees using multiple AI tools
- Pain: Told to 'figure out AI compliance' with no resources
- Budget: €5K-20K annual compliance budget
- Urgency: HIGH — regulatory pressure from leadership
3. Solution Design
Design Principles
Based on my research findings, I established four core design principles that would guide every decision:
1. Self-Service First
Users should be able to achieve compliance without calling sales, booking demos, or hiring consultants. The product must guide them through the entire journey.
2. Immediate Value
Users need to see value within the first 10 minutes. A free risk assessment quiz provides instant classification and requirements without requiring payment.
3. Developer-Friendly
For AI agent builders, compliance must integrate into their existing workflow. SDKs that work with popular frameworks (LangChain, CrewAI) enable 'compliance as code.'
4. Affordable Transparency
Clear pricing starting at €99/month, no hidden fees, no multi-year contracts. Users can start small and scale as their AI portfolio grows.
4. User Experience Design
Information Architecture
I designed the information architecture to support two distinct user journeys: the marketing/conversion flow and the product/dashboard flow.
Marketing Site Structure
- Landing Page Value proposition, problem/solution, pricing, CTAs
- Feature Pages Deep dives on each module (Risk Classification, Document Generation, etc.)
- For Compliance Teams Persona-specific messaging and use cases
- For AI Agent Developers Technical focus with SDK integration guides
- Resources EU AI Act guides, compliance checklists, case studies
- Developer Documentation SDK quickstart, API reference, framework guides
Dashboard Structure
- Dashboard Home — Compliance score, recent activity, system overview
- AI Systems — CRUD for managing AI systems with risk classification
- Requirements — Per-system checklist with progress tracking
- Documents — Library of generated and uploaded compliance docs
- Evidence — Centralized evidence management linked to requirements
- Audit Trail — Real-time feed of AI agent events (for SDK users)
- Reports — Audit package generation and compliance reports
- Settings — Organization, team, billing, API keys
Primary User Flow: First-Time User to Compliance
I mapped the complete journey from discovery to achieving compliance:
Stage 1: Discovery User lands on homepage, sees value proposition, clicks 'Start Free Risk Assessment'
Stage 2: Risk Assessment Quiz 10-minute questionnaire (no account required) with questions about AI system purpose, data types, decision impact, and EU presence
Stage 3: Results & Gate Instant risk classification with visual breakdown. Email gate to receive full requirements list.
Stage 4: Account Creation Simple signup (email/password), quiz results auto-imported into new account
Stage 5: Dashboard Aha Moment User sees their AI system already created with risk classification, compliance score (typically low), and clear next steps
Stage 6: Work Through Requirements Guided checklist experience with document generation prompts for missing items
Stage 7: Achieve Compliance Dashboard shows 'Compliant' status, user can generate audit report and display certification badge
Dashboard Design
The dashboard design prioritizes clarity and actionability. The main dashboard shows a compliance score prominently, with a clear breakdown of which systems need attention and what requirements are incomplete.
Key Design Decisions:
- Compliance score as north star metric always visible, updates in real-time
- System-centric navigation users manage compliance per AI system, not globally
- Progress indicators everywhere visual feedback on completion status
- Contextual help tooltips explaining EU AI Act requirements in plain language
- Empty states that guide never leave users staring at blank screens
5. Technical Implementation
Database Architecture
I designed a multi-tenant database schema with Row Level Security (RLS) ensuring complete data isolation between organizations. Key tables include:
- organizations — Company accounts with subscription tiers and usage limits
- ai_systems — Individual AI systems with risk classification and metadata
- ai_system_requirements — Per-system requirement tracking linked to EU AI Act articles
- documents — Generated and uploaded compliance documents with versioning
- evidence_files — Uploaded evidence linked to specific requirements
- audit_events — Immutable audit trail from SDK integration
- audit_logs — Platform activity logging for compliance
SDK Development
A key differentiator for Protectron is the SDK for AI agent developers. I designed and documented SDKs for Python and TypeScript with native integrations for popular frameworks:
Python SDK
The Python SDK uses callbacks to automatically capture LLM calls, tool invocations, agent decisions, and human oversight events. A single line of code enables compliance logging:
callback = ProtectronCallback(system_id='my-agent')
Framework integrations include LangChain (agents, chains, LCEL), CrewAI (multi-agent crews), AutoGen (conversation tracking), and custom Python applications.
TypeScript SDK
The TypeScript SDK provides the same capabilities for Node.js and edge deployments, with special support for the Vercel AI SDK.
6. Content Strategy & Execution
SEO Strategy
Every page was designed with search intent in mind:
- Primary keywords targeting high-volume terms ('EU AI Act compliance', 'AI compliance platform')
- Long-tail keywords for specific intents ('LangChain compliance SDK', 'AI audit trail')
- Resource guides targeting educational queries ('what is high-risk AI', 'Article 12 requirements')
- Comprehensive meta descriptions and schema markup for each page
7. Results & Impact
What Was Built
In 72 hours, I designed and built a complete compliance platform:
- Fully functional landing page with conversion-optimized design
- Complete dashboard with risk classification, requirement tracking, and document generation
- Python and TypeScript SDKs with framework integrations
- REST API with authentication, rate limiting, and webhook support
- Database schema with multi-tenant architecture and RLS
- 28 pages of production-ready content
- Integration guides for LangChain, CrewAI, and AutoGen
- Case studies demonstrating real-world value
8. Reflections & Key Learnings
What Worked Well
AI-Assisted Research & Development
Using Claude for deep research compressed weeks of regulatory analysis into hours. The AI could parse 400+ pages of EU AI Act text and help me map requirements to product features systematically. Similarly, Claude Code enabled rapid iteration on the codebase.
Design-Led Development
Writing comprehensive PRDs before coding meant I built the right thing the first time. The user flows were clear, the information architecture was sound, and edge cases were considered upfront.
Developer-First Approach
Designing the SDK alongside the dashboard ensured the product worked for both compliance teams and engineering teams. This dual-persona approach expanded the addressable market.
Challenges & How I Addressed Them
Regulatory Complexity
The EU AI Act is genuinely complex. I addressed this by creating plain-language explanations alongside technical requirements, building contextual help into the dashboard, and designing the risk assessment to guide users through classification without requiring legal expertise.
Two-Sided Value Proposition
Protectron serves compliance teams (non-technical) and developers (technical). I addressed this by creating distinct user journeys, separate feature pages, and ensuring the SDK documentation was isolated from compliance documentation.
Trust in a Compliance Context
Users must trust that Protectron accurately represents EU AI Act requirements. I addressed this by including Article references throughout the product, maintaining transparency about the platform's role (tool, not legal advice), and designing audit trails with cryptographic integrity.
Key Takeaways
- Market gaps create opportunities: The absence of affordable EU AI Act compliance tools wasn't an oversight it was an opportunity waiting for someone to build the solution.
- AI accelerates everything: From research to content creation to code generation, AI tools made a 72-hour build feasible. This is the new standard for product development.
- Comprehensive documentation enables speed: The time invested in PRDs paid dividends during development. Clear specs meant less rework and fewer decisions during implementation.
- Design for both personas: Products serving both technical and non-technical users must acknowledge these differences explicitly in IA, content, and features.
- Compliance is continuous: The best compliance tool is one that makes ongoing compliance effortless, not one that generates a one-time report.
9. Conclusion
Protectron demonstrates what's possible when you combine deep research, thoughtful design, and modern development tools. In 72 hours, I created a complete SaaS platform addressing a €4.5 billion market gap with a landing page, dashboard, SDK, API, and 78,000+ words of content.
The project showcases my ability to identify market opportunities through research, design comprehensive user experiences, architect technical solutions, and execute across the full product stack. From user personas to database schemas, from marketing copy to API documentation, every aspect was considered and delivered.
Most importantly, Protectron solves a real problem. As AI regulation expands globally, companies need accessible compliance tools. By democratizing EU AI Act compliance, Protectron enables startups and SMBs to build AI responsibly without enterprise budgets or expensive consultants.