Skip to content

feat: add productization plan and web UI scaffold#23

Merged
abrichr merged 5 commits intomainfrom
feat/productization-mvp
Mar 19, 2026
Merged

feat: add productization plan and web UI scaffold#23
abrichr merged 5 commits intomainfrom
feat/productization-mvp

Conversation

@abrichr
Copy link
Member

@abrichr abrichr commented Mar 19, 2026

Summary

  • Add comprehensive productization plan at docs/PRODUCTIZATION.md covering market context ($4.7B AI code assistant market), competitive analysis, hybrid pricing model (Free/Pro/Team tiers), 6-week MVP roadmap, go-to-market strategy, technical architecture evolution, and unit economics
  • Create Next.js web app scaffold at apps/web/ with landing page, task submission form, and job detail page -- the first step toward a web-based entry point alongside the existing Telegram bot
  • Update monorepo config (turbo.json, .gitignore) for Next.js support

Details

Productization Plan

  • Pricing: Free ($0, 3 tasks/mo, public repos), Pro ($29/mo, 20 tasks), Team ($99/mo, 100 tasks)
  • MVP Roadmap: Week 1-2 GitHub App, Week 2-3 Web UI, Week 3-4 Stripe billing, Week 4-5 multi-tenant queue, Week 5-6 sandboxing
  • Unit economics: $0.50-5.10 COGS per task, selling at $5-15, 50-90% gross margin
  • GTM: Target small dev teams (2-10 engineers), wedge with bug fixes and dependency updates

Web UI Scaffold (apps/web/)

  • Landing page (/) with features, pipeline diagram, language support table, pricing tiers, and open-source CTA
  • Task submission (/new) with repo URL, task description, branch, advanced options (max loops, budget cap)
  • Job detail (/jobs/[id]) placeholder for real-time status via Supabase Realtime
  • Server actions for secure Supabase job insertion (service role key stays server-side)
  • Supabase client helpers for both server and browser contexts
  • Tailwind CSS with custom wright color palette

Test plan

  • Review docs/PRODUCTIZATION.md for completeness and accuracy
  • Verify apps/web/ builds: pnpm install && pnpm --filter @wright/web build
  • Verify landing page renders correctly: pnpm --filter @wright/web dev
  • Verify task submission form validation (empty fields, non-GitHub URLs)
  • Confirm turbo and pnpm workspace configs properly include the new app
  • CI passes (lint, test, build across all packages)

Generated with Claude Code

Add comprehensive productization document covering market analysis,
pricing model (Free/Pro/Team tiers), MVP roadmap (6 weeks), technical
architecture evolution, go-to-market strategy, and unit economics.

Create Next.js web app scaffold at apps/web/ with:
- Landing page with features, pricing, and language support sections
- Task submission form connected to Supabase via server actions
- Job detail page scaffold for real-time status tracking
- Supabase client helpers (server + browser)
- Tailwind CSS styling with custom Wright color palette

Also update turbo.json for .next/ build outputs and .gitignore for
Next.js artifacts.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@abrichr
Copy link
Member Author

abrichr commented Mar 19, 2026

Review

The productization doc and Next.js scaffold look good overall. However, CI is failing because pnpm-lock.yaml was not updated after adding apps/web/package.json:

ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/apps/web/package.json

To fix: run pnpm install locally on this branch, then commit the updated pnpm-lock.yaml.

Not merging until CI passes.

abrichr and others added 4 commits March 18, 2026 21:27
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@abrichr abrichr merged commit bd56e54 into main Mar 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant