Build /how-we-built-scribe public page — case study & portfolio piece

[taha-abbasi]

Overview

Build a public page at tryscribe.co/how-we-built-scribe showcasing the Scribe build story as a polished case study.

Dual purpose:

1. Portfolio piece for job applications (immediate: Founding Full-Stack Engineer role via G2i recruiter Juliana)
2. Pitch material for investors/partners

Content Source

JOURNEY-PITCH.md is the single source of truth. All data comes from there.

Page Sections

1. Hero

• Headline contrast: "1 CTO. 9 Working Days. ~$200/month in AI tokens."
• Subline: What would traditionally require an 8-person team, $350K-$600K, and 3.5-5.5 months
• Use Scribe visual language — quill accent, dot pattern, floating article cards (from marketing.html)

2. The Numbers (Proof Bar style)

• 9 working days
• 17 releases (v0.1.0 → v0.9.6+)
• 1 Software Architect/CTO
• ~$200/mo AI tokens

3. What Was Built (Feature list)

Full production SaaS: auth, onboarding, AI content generation, job queue + worker, blog engine (4 layouts), image pipeline (DALL-E → CDN), dashboard CRUD, email notifications, mobile responsive, SEO, MongoDB + Vercel + AWS infra, EC2 deployment, CI/CD, monitoring

4. The Traditional Equivalent: Resource Cost

• 8-role salary table with annual salary + fully loaded monthly cost
• Why 14-22 weeks breakdown (low end vs high end reasoning)
• Why $350K-$600K math ($107K-$130K/month × timeline)
• What it doesnt include (recruiting fees, tooling, opportunity cost)

5. What We Actually Spent

• 1 CTO using agentic orchestration
• 9 working days
• ~$200/mo AI tokens
• Lean infra leveraging AWS Startup Credit Grants

6. Tech Stack

Visual badges/pills: Next.js, TypeScript, MongoDB, AWS (EC2, IAM, Organizations), Vercel, Claude Opus, DALL-E 3, GitHub Actions

7. Day-by-Day Build Log

Timeline/cards for each of the 9 working days with version tags and bullet points

8. Version History Table

All 17 versions from v0.1.0 to v0.9.6+

Design Requirements

• Static HTML at platform/public/how-we-built-scribe.html (same pattern as marketing.html)
• Scribe branding: Playfair Display headings, Inter body, cream/amber/ink palette
• Reuse visual components from marketing.html: proof-bar stats, card styles, section layouts, quill accents, dot patterns, feature cards
• Case study feel, NOT a blog post
• Mobile responsive
• OG meta tags for link previews (title, description, image)
• Nav link back to tryscribe.co
• Footer consistent with marketing page

URL Routing

• Add redirect/rewrite in Next.js middleware or config so /how-we-built-scribe serves the static HTML
• Same pattern as existing /marketing.html serving