WORK

Products we built, launched and still run.

Our portfolio starts with our own products. ScopeCrafters and ContentVo are live AI SaaS products with paying plans, built by Cyphorux on the same stack and process we use for client work. Each case study covers the problem, the architecture, what we cut, and what we learned.

WHY OUR OWN PRODUCTS

Proof you can click, not logos.

Agency portfolios are hard to verify. A logo wall doesn't tell you who did the work, what the work was, or whether the thing still runs. We'd rather show products you can open right now, sign up for, and judge yourself.

Running our own products also keeps us honest about the parts of software that only show up after launch: billing edge cases, AI cost per user, prompts that drift, pages that don't get indexed. Every one of those lessons goes into client work before it becomes a client's problem.

Both products were built by the founder, Hamza Bashir, who also built AI agent and omnichannel support infrastructure serving more than 500,000 customers for a national highway operator. The products are where we try ideas first. Client engagements get the versions that worked.

SHARED FOUNDATIONS

What both products have in common.

  1. 01

    Model output is untrusted input

    Both products request structured output from the AI model and validate it before it's saved or shown. A response that doesn't match the schema is rejected rather than rendered.

  2. 02

    Authorization lives in the database

    Every table has Postgres row-level security tied to the signed-in user or workspace. An application bug can't leak one customer's data to another.

  3. 03

    Webhooks own billing state

    Plans change only when the billing provider's signed webhook says so. That is why moving both products from Stripe to Polar was a contained change.

  4. 04

    One deploy target

    Next.js route handlers on Vercel, Supabase for data, auth and storage. No separate API service, no queue, no worker fleet until the product needs one.

  5. 05

    Growth is built into the codebase

    Free tools, programmatic pages from typed data, comparison hubs, sitemaps, structured data and llms.txt ship with the product, not as an afterthought.

CHANGELOG

Milestones, from the commit history.

Dates below come from each product's git history, not from memory. They show how quickly a focused scope moves when the out-of-scope list is respected, and what happens after launch: most of the work is billing, hardening and growth, not new features.

  1. Jun 15, 2026ScopeCrafters: first commit. Magic-link auth, schema and Stripe Checkout the same day.
  2. Jun 17, 2026ScopeCrafters: billing migrated from Stripe to Polar as merchant of record.
  3. Jun 18, 2026ScopeCrafters: electrical and plumbing trades plus a referral system ship, making four trades in total.
  4. Jun 21, 2026ScopeCrafters: three free calculators, competitor pages and an about page with founder details.
  5. Sep 21, 2026ContentVo (then ContentFlow): first commit, with brand analysis and image generation.
  6. Sep 27–28, 2026ScopeCrafters: programmatic templates and directory pages; thin state pages gated and unbacked rating markup removed.
  7. Sep 29–30, 2026ContentVo: quota bypasses closed, annual billing and referrals added, billing moved to Polar.
  8. Oct 2, 2026ScopeCrafters: calculators released as embeddable widgets for link earning.
  9. Oct 4, 2026ContentVo: renamed from ContentFlow and moved to contentvo.com.
  10. Oct 7, 2026ContentVo: guides, comparison and tool pages expanded to 1,200+ words each.
RELATED SERVICES

Want something similar?

Each case study maps to a service. If you're planning an AI-native product like ScopeCrafters, start with AI product development. If you need a SaaS MVP that can take payments on launch day like ContentVo, start with SaaS MVP development.

Build something like this.

Tell us about the product you want to build. We'll reply with honest questions about scope, timeline and fit.

SSttaarrtt  aa  pprroojjeecctt