Shipping Faultrix: What I Learned Building an AI SaaS From Zero in 5 Months
## What I Built
[Faultrix](https://faultrix.com) is an AI-powered construction quality control SaaS. A building inspector uploads photos of a construction site; Faultrix analyzes them and generates a legally compliant ÖNORM B 2110 technical report — with SHA-256 evidence chain, DSGVO compliance, AES-256 encryption — in under 1 minute.
I built it solo, from zero to production, in 5 months. Coming from a pure research background (diffusion models, OOD detection at JKU Linz), here's what surprised me about the gap between AI research and AI product.
The Tech Stack and Why
Frontend & Backend: Next.js 14 App Router with TypeScript. React Server Components make the AI streaming UX straightforward. TypeScript caught enough bugs early that the extra setup was worth it on day 1.
Database & Backend logic: Convex. Real-time reactive queries, serverless functions, and built-in file storage. For a solo developer building a data-intensive SaaS, Convex's all-in-one approach beats stitching together Supabase + separate serverless functions.
Authentication: Clerk. Complete auth in 2 hours including organization management and webhooks to Convex. The opportunity cost of building auth yourself in 2025 approaches infinity.
File storage: Cloudflare R2. S3-compatible API, zero egress fees, and edge distribution. For image-heavy SaaS this is a meaningful cost difference at scale.
AI layer: OpenAI API (GPT-4o + Vision). The construction defect analysis uses vision + structured output extraction to produce JSON that maps to the ÖNORM report schema.
Payments: Stripe. 45 minutes to working checkout, webhooks handled, subscription management done.
Security: SHA-256 evidence hashing on every uploaded image (makes the report legally defensible), AES-256 encryption at rest for all documents.
The Hardest Part Wasn't the AI
I expected the AI part to be hard. It wasn't. The GPT-4o vision API is remarkably capable at identifying construction defects when given a well-structured prompt and output schema.
The hard parts: - ÖNORM compliance: The Austrian standard for construction technical documentation is not AI-friendly. Getting the output to match the exact required section structure, terminology, and formatting took 3 weeks of iteration with real building inspectors. - Evidence chain: A report is legally defensible only if you can prove the photos weren't altered. The SHA-256 pipeline sounds simple but the UX of surfacing it without confusing users is non-trivial. - Pricing: "How much should AI-generated ÖNORM reports cost?" has no obvious answer. I interviewed 12 building inspectors and construction companies before landing on a pricing structure.
What Research Background Actually Transfers
Transfers well: - Systematic experimentation (prompt engineering is just hyperparameter tuning with words) - Evaluation rigor — I built proper test suites for the AI outputs before shipping - Understanding model limitations — knowing when to trust GPT-4o and when to flag for human review
Does not transfer: - Product intuition — researchers optimize for correctness; users optimize for "does this save me time" - Distribution shift in production is a UX problem, not just a model problem - You cannot ablate your way to product-market fit
One Thing I'd Tell a Research-to-Product Engineer
The first version of Faultrix had a beautiful, fully accurate AI analysis pipeline and a terrible UX. Users churned because the interface required 8 steps to upload photos. The AI was irrelevant — the UX was the product.
Ship the simplest version that delivers the core value (in Faultrix's case: "upload photos → get report"). Then add sophistication. Do not add sophistication before you have users.
Try it at [faultrix.com](https://faultrix.com). If you're in construction or building inspection in the DACH region, I'd love your feedback — ahmed.mo.0595@gmail.com.
Frequently Asked Questions
What is Faultrix and what does it do?
Faultrix is an AI-powered construction quality control SaaS. Building inspectors upload photos of a construction site, and Faultrix analyzes them and generates a legally compliant ÖNORM B 2110 technical report in under 1 minute with SHA-256 evidence chain and DSGVO compliance.
What tech stack does Faultrix use?
Next.js 14 App Router with TypeScript, Convex for database and backend logic, Clerk for authentication, Cloudflare R2 for file storage, OpenAI API (GPT-4o + Vision) for AI analysis, and Stripe for payments.
What was the hardest part of building Faultrix?
The hardest part was not the AI but achieving ÖNORM B 2110 compliance. Getting the output to match the exact required section structure, terminology, and formatting took 3 weeks of iteration with real building inspectors.