DrawX GTM — Summary

Auto-generated index — AI synthesis unavailable this run: Bedrock invoke failed for eu.amazon.nova-pro-v1:0: aws: [ERROR]: An error occurred (AccessDeniedExc

• README.md
• assets-checklist/assets.md
• competitive/competitor-map.md
• content/copy-bank.md
• content/generated/2026-07-03.md
• content/viral-bets.md
• launch/pre-launch-instrumentation-audit.md
• launch/week-1-plan.md
• positioning/differentiators.md
• positioning/positioning.md
• use-cases/use-cases.md

DrawX — GTM (private)...

Go-to-market strategy, positioning, and launch material for DrawX (AI diagramming: a GitHub repo or a sentence → an editable draw.io diagram you own; $5/mo Pro; now with a public API + MCP server).

Access: This is a private repo. Read access = being a collaborator. That's the security model — GitHub auth, no bypassable password pages. Ask the owner to add you as a collaborator.

Start here

• SUMMARY.md — auto-generated 2-minute overview (refreshed by Claude/Bedrock on every change). Read this first.

Contents

Hosting

The rendered, access-gated site is hosted on Vercel (private repo → Vercel auto-deploys on every push). GitHub Pages isn't used (it needs a paid plan for private repos, and a public repo would expose these strategy docs). Build: npm run build:site → site/index.html (see vercel.json).

Access is gated by a client-side code prompt (ACCESS_CODE env var, hashed at build). Honest caveat: this is friction for a non-technical partner, not hard security — the content is static HTML. Fine for internal reference; we can layer real auth later.

Automation (runs on GitHub Actions)

• refresh-summary — on any .md change, regenerates SUMMARY.md via Amazon Nova Pro on AWS Bedrock (eu.amazon.nova-pro-v1:0 — the model actually available on our account; Claude is marketplace-blocked here). Fails soft to a plain index.
• daily-content — daily cron drafts X/LinkedIn/Reddit/blog ideas into content/generated/YYYY-MM-DD.md for human review before posting.
• Both need the AWS_BEARER_TOKEN_BEDROCK repo secret. Vercel redeploys automatically when these commit.

Editing

Just edit the markdown and push. Summary + site refresh automatically. Keep positioning/pricing consistent with the locked docs — don't re-litigate; operationalize.

DrawX — Marketing Asset Checklist (with status)

Every asset referenced across strategy docs, with honest status. Update status as produced. Status legend: ❌ not started · 🟡 in progress · ✅ done

Core demo assets

• ❌ 30-second screen-record: sentence → diagram → edit → PPTX export
• ❌ <3-min Loom full walkthrough
• ❌ 5–6 before/after screenshots (spaghetti vs DrawX clean) of the same systems
• ❌ "Point it at [famous repo]" verified-correct example set (3–5 repos)

Web / SEO

• ✅ OG / social share image — dynamic on-brand card at app/opengraph-image.tsx (1200x630, next/og)
• ✅ Positioning-aligned metadata (title/description/OpenGraph/Twitter) in app/layout.tsx; /pricing + /about in sitemap/robots
• ❌ Web manifest (PWA) — still pending, low priority
• ✅ Landing page headline aligned to locked positioning ("generated from your code — and fully yours to edit")
• ✅ Enterprise landing page BUILT — full marketing site at / (hero, how-it-works, features, use-cases, comparison, FAQ, CTA, footer) on feature/landing-enterprise. Light, on-brand, motion-rich.
• ✅ /pricing and /about pages built
• ✅ /upgrade page rebuilt on-brand (was off-brand dark gradient)
• ✅ Comparison: on-landing table + standalone /compare/{eraser,gitdiagram,lucidchart,mermaid} pages (honest framing, SEO metadata, sitemap)
• ❌ AlternativeTo listing (external — submit when launching)

Launch surfaces

• ❌ Product Hunt: copy, gallery images, maker comment
• ❌ Show HN post (builder story + honest limitations)
• ❌ Console.dev submission
• ❌ Reddit question-format first post + comment targets list

Accounts / infra (Day 0 blockers)

• ❌ Reddit account
• ❌ LinkedIn presence/page
• ❌ X account
• ❌ Sending email (transactional vs marketing split — decide; Resend currently in-app invites only)

Proof / social

• ❌ First named customer quote
• ❌ First case study (after 5–10 dev wins)
• ❌ Traction numbers for pitch

DrawX — Competitive Map & "Why not X"

Distilled from ../../DrawX-Strategy/atlas.html (36-competitor primary-source atlas). Use for comparison pages, Reddit/HN replies, and sales objection handling. Keep claims accurate.

The lanes

"Why not X" one-liners (for replies/FAQ)

• "Why not just GitDiagram?" — Great for a quick Mermaid sketch. DrawX gives you an editable .drawio you own and keep refining, plus PDF/URL/chat inputs and PPTX export.
• "Why not Eraser?" — Eraser locks you into its DSL/tool. DrawX outputs native draw.io XML — edit it anywhere, forever.
• "Why not Lucidchart AI?" — Lucidchart is heavyweight and proprietary. DrawX is dev-native, repo-aware, and $5/mo.
• "Why not write Mermaid myself?" — You can — and import it. DrawX generates the first 90% and lays it out cleanly so you're not fighting spaghetti.

Positioning vs the field (one line)

DrawX is the only tool that is repo-aware + multi-input + editable & owned (draw.io) + (soon) generates HLD/LLD + design docs, at an indie-friendly $5/mo.

TODO (assets)

• Public comparison pages: DrawX vs GitDiagram / Eraser / Lucidchart / Mermaid (source material above).
• AlternativeTo listing.

DrawX — Copy Bank (reusable, on-message)

Pull from here for landing page, PH, social, emails. All consistent with locked positioning + $5/mo.

Taglines (pick per surface)

• Turn your repo — or one sentence — into an editable architecture diagram you own.
• Architecture diagrams that match your code. Generated, editable, yours.
• Stop redrawing diagrams by hand every sprint.
• Not a screenshot. Not Mermaid spaghetti. A real draw.io diagram you own.

Landing hero (draft — aligns to locked positioning)

H1: Your architecture diagram, generated from your code — and fully yours to edit. Sub: DrawX turns a GitHub repo, a PDF, a URL, or a single sentence into an editable draw.io diagram. No lock-in, no spaghetti. $5/mo. CTA: Generate your first diagram free →

Elevator (30s)

DrawX is an AI diagramming tool for developers and architects. Point it at your GitHub repo or just describe your system, and it generates a clean, accurate architecture diagram — as a real draw.io file you can edit and own forever. Most AI tools hand you a screenshot or a locked-in format that's wrong and goes stale. DrawX gives you something you can actually keep using. Free to start, $5/mo for 50 generations.

Product Hunt one-liner

Repo or sentence → editable draw.io architecture diagram you own. Multi-input (repo/PDF/URL/chat), exports to PNG/SVG/.drawio/PPTX. $5/mo.

Outbound openers (warm)

• Dev: "Saw you shipped/inherited [project]. I built a thing that turns a repo into an editable architecture diagram in a couple minutes — would a 30-sec clip be useful for your README?"
• Architect: "You mentioned redrawing architecture diagrams every sprint — I'm building DrawX to generate them from the code and keep them editable in draw.io. Worth a look?"

Boilerplate (about)

DrawX is an AI-powered diagramming tool built on the draw.io engine. It generates accurate, editable architecture diagrams from your codebase, documents, or a single prompt — so your diagrams match reality and stay yours.

DrawX GTM — generated drafts · 2026-07-03

Auto-generated by Amazon Nova Pro on the daily cron. Human review required before posting. Grounded in this repo's positioning + copy-bank + use-cases — no external claims.

X (Twitter) Drafts

1. Builder Story Angle (230 chars): "Just inherited a complex codebase? DrawX turns your GitHub repo into an editable draw.io architecture diagram in minutes. No more redrawing from scratch. Try it free: [link] #buildinpublic"

2. Before/After Angle (220 chars): "Tired of messy Mermaid diagrams? See the difference: [link to image] DrawX generates clean, editable architecture diagrams from your repo or a simple sentence. Free trial available."

3. Hot Take on Stale Diagrams (235 chars): "Architecture diagrams that don't match your code are worse than none. DrawX ensures your diagrams stay accurate and editable. Point it at your repo and see the magic. $5/mo Pro for 50 generations."

LinkedIn Drafts

1. For Architects (680 chars): "Architects: Ever spent hours redrawing diagrams to match the latest code changes? DrawX automates this pain. Simply point it at your GitHub repo or describe your system, and get a fully editable draw.io diagram that you own. No more fighting with Mermaid or locked-in formats. Our multi-input tool supports GitHub, PDFs, URLs, and even chat descriptions. Export to PNG, SVG, .drawio, or PPTX for stakeholder-ready presentations. Try it free, then $5/mo for Pro features. Let’s keep your diagrams accurate and up-to-date."

2. For Founders/CTOs (650 chars): "Founders and CTOs: Your architecture diagrams should match your code, not gather dust. DrawX generates accurate, editable diagrams from your GitHub repo or a simple sentence. Ideal for onboarding, documentation, and stakeholder presentations. Multi-input support (GitHub, PDF, URL, chat) ensures flexibility. Export to PNG, SVG, .drawio, or PPTX. Free to start, $5/mo for Pro. Keep your team aligned with reality, not outdated drawings."

Reddit Comment-Style Drafts

1. For r/programming (480 chars): "Ever wished your architecture diagrams could stay in sync with your code? DrawX generates editable draw.io diagrams from your GitHub repo or a simple sentence. No more redrawing or dealing with ‘spaghetti’ layouts. Try it out and see the difference. [link] It’s free to start with a $5/mo Pro option for more generations and features."

2. For r/devops (490 chars): "Struggling to keep your architecture diagrams up-to-date? DrawX might be the solution. It turns your GitHub repo into an editable draw.io diagram, so you don’t have to redraw every sprint. Supports multiple inputs like PDFs, URLs, and chat descriptions. Export to various formats including PPTX. Give it a try for free, then upgrade to Pro for $5/mo. [link]"

Long-Form Idea

Blog/Essay Title: "The Silent Killer of Tech Projects: Outdated Architecture Diagrams and How DrawX Can Help"

Outline:

1. The Problem:
   • Discuss the common issue of architecture diagrams becoming outdated and the impact on projects.
2. The DrawX Solution:
   • Explain how DrawX generates accurate, editable diagrams from various inputs.
3. Real-World Applications:
   • Share case studies or examples of how DrawX has helped teams keep their diagrams up-to-date.

DrawX — Content & Viral Bets

"Extreme bounds" ideas + the safe core. Each bet: the hook, why it could travel, and the risk. Golden rule for dev communities: 7:1 value-to-mention. Lead with the artifact, not the pitch.

The repeatable core (do every week)

• Before/after pair: "ChatGPT/Mermaid spaghetti" vs "DrawX clean editable diagram" of the same system. Single image, instantly legible. The format that wins on X/Reddit.
• "Point it at this repo →" demos: pick a well-known OSS repo, post the generated editable diagram. The artifact does the selling.

Viral bets (ranked by upside × shareability)

1. "I fed [famous OSS repo] to an AI and got an editable architecture diagram" (Show HN / X thread). Upside: HN/dev audience loves repo teardowns. Risk: must be accurate — a wrong diagram of a known repo gets torn apart. Mitigation: only post repos where output is verified correct.
2. "Your architecture diagram is already out of date" — the drift essay (LinkedIn/blog). Names the pain everyone feels; positions DrawX as the fix. Upside: architect/eng-lead resonance. Risk: low; mostly upside.
3. 30-second screen-record: sentence → diagram → edit → export to PPTX. Upside: shows the whole loop fast; reusable everywhere (X, PH, landing hero). Risk: low.
4. "Watch an AI Solution Architect design an HLD + LLD from a one-paragraph brief" (when G3 ships). Upside: genuinely novel; could define a category. Risk: HIGH if quality is "spaghetti" — gate behind the validation loop being done. Do NOT post until output is clean.
5. Public "diagram any repo people drop in the comments" live thread. Upside: high engagement, builds proof. Risk: throughput + accuracy under fire; needs a human reviewing each before posting.
6. Comparison/teardown: "I tried 5 AI diagram tools on the same repo." Upside: ranks for comparison search; honest if we lose some rounds (builds trust). Risk: must be fair.

Channel notes

• Reddit: r/SideProject, r/indiehackers (promo-friendly); r/softwarearchitecture, r/devops, r/ExperiencedDevs, r/dataengineering, r/Database (strict — comment-first, value 7:1). F5Bot keywords: "diagrams go stale", "draw.io ai", "mermaid alternative", "lucidchart alternative".
• HN: Show HN with the builder story + a live link + an honest "what it can't do yet."
• X: #buildinpublic before/after images; the 30s loop video.
• LinkedIn: the drift essay + architect one-liner; warm intros first.

Hard guardrails (no fuck-ups)

• Never claim a TO-BUILD feature as live (Architect Co-Pilot, FinOps, sync). See ../positioning/differentiators.md.
• Never post an inaccurate diagram of a known system. Accuracy IS the brand.
• Disclose you're the maker when posting your own tool.

Pre-Launch Instrumentation Audit — 2026-07-02

Ran before any launch push (per week-1-plan "instrument before posting"). Every claim below is code-verified, not assumed. Verdict: funnel + margin + SEO are launch-ready. One domain-of-record decision for the founder to confirm.

1. PostHog funnel events — ✅ ALL WIRED

Every funnel step has a real call site (not just a definition in lib/analytics/track.ts):

Server-side subscription lifecycle events (subscription_started/renewed/cancelled/...) fire from the DodoPayments webhook via trackServer() (awaited/captureImmediate so they survive serverless freeze).

Caveat: all no-op unless NEXT_PUBLIC_POSTHOG_KEY is set in prod — confirm it's set in Vercel before launch (that's the only gap between "coded" and "capturing").

2. Cost vs $5/mo margin — ✅ HEALTHY (credit-costs are the throttle)

Prices (lib/ai/pricing.ts, per 1M tokens): Flash $0.50/$3.00 · Pro $2.00/$12.00 · Ultra $5.00/$25.00. Default mode is Flash everywhere.

The real protection is the credit-cost design: Pro plan = 50 credits/mo; a Pro-mode gen costs 2 credits, a full Ultra architect run costs 4. So a $5 user physically can't run more than ~12 full Ultra architect runs or ~25 Ultra chat gens per month.

No underwater scenario. Margin holds even before payment-processor fees are considered.

3. OG / share images + SEO — ✅ PRESENT (week-1 "missing OG" note was stale)

• app/opengraph-image.tsx — dynamic 1200×630 PNG with alt text (Next.js auto-wires into OG images).
• app/layout.tsx — full metadata: metadataBase, title template, description, keywords (incl. HLD/LLD), openGraph block, twitter: summary_large_image.
• app/robots.ts + app/sitemap.ts present.

Founder decision (not a bug): app SEO/sitemap/robots use app.getdrawx.com; the API OpenAPI spec + GTM copy use getdrawx.com. Fine if that's the intended app-vs-marketing split. If share links should resolve to the marketing site, update SITE_URL in app/layout.tsx. No code change made — confirm the domain of record first.

Launch-readiness verdict

Funnel, margin, and SEO are ready. The only true pre-launch to-dos are operational, not code:

1. Confirm NEXT_PUBLIC_POSTHOG_KEY is set in Vercel prod (else no events capture).
2. Confirm the domain-of-record for share links (app. vs bare getdrawx.com).
3. (Parked) Gemini key — Flash/Pro degraded until replaced; fallback masks it.

DrawX — Week-1 Launch Plan

Operationalizes Sunday 3 (../../Sunday3-GTM/). Tracker: ../../Sunday3-GTM/drawx-gtm-tracker.csv. Status carried from Sunday 3: built & ready, NOT yet posted. Accounts NOT yet created.

Day 0 — unblock (must happen first)

• Create 4 accounts: Reddit, LinkedIn (or use personal), X, sending email. (Blocker — nothing posts until done.)
• Set up F5Bot alerts: "diagrams go stale", "draw.io ai", "mermaid alternative", "lucidchart alternative".
• Record <3-min Loom walkthrough + 30-sec X demo (see ../assets-checklist/).
• Confirm landing headline matches locked positioning (see ../content/copy-bank.md).
• Fresh-account onboarding click-through (no crash, <5 min to first diagram).

This week — outreach (from Sunday 3 drafts)

• Send 5 warm/cold emails (drafts in Sunday3 deck): warm friend, ex-colleague, indie hacker, architect (LinkedIn), VP Eng (hiring signal).
• 10 LinkedIn DMs using the keyword recipe ("architecture diagram" + "out of date", "draw.io frustrating", "solution architect C4").
• Reddit: 5 value-comments/day on grounded threads (7:1 rule); one question-format post.
• Submit to Console.dev (devtools newsletter, reviews betas).
• Reach 3 partners: doc platforms (Docusaurus/GitBook/Mintlify), GitDiagram (complement), Console.dev.
• Post PRIMARY content: Show HN builder story. Backups: LinkedIn drift essay, X before/after.

The one test this week

Does the shareable "repo → editable diagram" moment create pull (comments, DMs, signups) where devs already hang out? Success bar: 5+ real responses (reply/DM/signup/call) in 7 days. 0 → change message/targeting/positioning.

Measurement (instrument before posting)

• Confirm PostHog funnel events fire: signup → first generation → quota_exhausted → upgrade_viewed → checkout → paid.
• Langfuse: measure real per-generation cost vs $5/mo margin (50 gen/mo). Flag if margin is thin.
• Daily: log every touch in the tracker CSV.

Demo-day assets (parallel, not week-1 blocking)

• OG/share image + manifest (currently missing — SEO/share).
• Product Hunt copy + gallery + maker comment.
• First named quote / case study (after 5–10 dev wins).

DrawX — Differentiators (real, ranked)

Honest framing: differentiators marked PROVEN exist in code today. Those marked TO-BUILD / TO-VALIDATE are bets, not claims. Never market a TO-BUILD item as shipped.

1. Editable draw.io output you OWN — PROVEN (moat)

Competitors hand you images or proprietary DSLs: GitDiagram → Mermaid + static images; Eraser DiagramGPT → its own DSL; Lucidchart/Composer → proprietary. DrawX hands you raw .drawio XML you can edit forever in the world's most-used diagram engine. This is the survivor moat.

2. Multi-input ingest in one product — PROVEN

Chat, GitHub repo (8 auto-detected diagram types), PDF (large docs), URL, image → one product. Rivals are narrow single-input tools.

3. Stakeholder-ready exports incl. PPTX — PROVEN

PNG, SVG, native .drawio, and PPTX (slide + deck) are wired. Few AI diagram tools export to PowerPoint.

4. "No spaghetti" layout quality — TO-BUILD (P0 moat)

The cross-category complaint about every AI diagram tool is "vague/inaccurate/spaghetti." Closing this with deterministic layout rules (drawio-skill: edge geometry, adaptive spacing, semantic palette) + a VLM validation loop is the single highest-leverage moat. Partially scaffolded (/api/validate-diagram); not complete.

5. Generated HLD + LLD + design doc from one brief — TO-BUILD (Architect Co-Pilot v1)

No competitor produces an editable draw.io HLD and LLD and a design document from a single business brief. Today our HLD/LLD are static templates. Making them generated is net-new in the market.

6. Lives where developers already work (MCP) — TO-BUILD

A branded DrawX MCP server puts diagram generation inside Claude/Cursor/VS Code. Distribution-as-differentiation.

7. Diagrams that stay in sync with code — FUTURE wedge

repo→diagram exists; the unsolved hard problem is keeping it synced as code changes. Whoever solves drift wins the "diagrams rot" pain at its root. North-star research bet.

What is NOT our moat (correction, verified)

GitHub→diagram is the HOOK, not the moat. GitDiagram (MIT, 15.7k★) owns that search intent. Our moat is editable + accurate + all-in-one + (soon) generated architecture.

DrawX — Positioning (locked)

Verified against ../../Sunday3-GTM/index.html and product code (2026-06-26). Do not re-litigate positioning, ECPs, motion, or pricing — these are locked. Operationalize them.

Positioning statement (locked, Sunday 3)

For developers and architects who need a system diagram that actually matches their code, DrawX is the AI diagramming tool that turns your GitHub repo — or one sentence — into a fully editable draw.io diagram you own, unlike hand-drawing in draw.io or AI tools like Eraser that either rot the second code changes, or hand you inaccurate output you can't fix.

One-sentence motion

We turn a developer's GitHub repo or a single sentence into a fully editable draw.io diagram they own — devs discover it on Reddit & HN, share the output, and pull their team in. ($5/mo, self-serve.)

Target (Early-Customer Profiles, not broad ICP)

• Primary wedge — indie hackers & senior devs who just inherited/shipped a codebase and need an architecture diagram for README/docs/onboarding, and resent how fast it goes stale. Lives on Reddit, HN, X #buildinpublic, Indie Hackers. Self-onboards <5 min, pays $5 personally, no procurement.
• Secondary bet — solution/software architects at 20–200-person companies who must keep diagrams matching reality for stakeholders and hate redrawing every sprint. Reached via LinkedIn + warm intros. HLD/LLD willingness-to-pay is UNVERIFIED — treat as a hypothesis to test (this is what Architect Co-Pilot v1 validates).

Channel one-liners (locked)

• Dev (Reddit/HN/X): "Point it at your repo, get an editable architecture diagram you actually own — not a screenshot, not Mermaid spaghetti."
• Architect (LinkedIn/email): "Stop redrawing architecture diagrams by hand every sprint. Generate them from the code, edit in draw.io, keep them yours."

Pricing (live, code-verified)

• Free: 5 generations/month.
• DrawX Pro: $5/mo ($12 anchor shown), 50 generations/month, Flash/Pro/Ultra modes, all exports, cancel anytime.
• Legacy beta_unlimited ($1.99 one-time) grandfathered only.
• ⚠️ Older strategy docs say $9–12/mo + $5 founder — stale. Code shipped $5 flat.

DrawX — Use Cases (who, pain, value, what they build)

Maps each segment to concrete jobs-to-be-done. "Now" = works today in code. "Near future" = on roadmap (G3/G5).

A. Indie hacker / senior dev (PRIMARY wedge)

• Pain: Inherited/shipped a codebase; needs an architecture diagram for README/docs/onboarding; hates that it goes stale and that hand-drawing in draw.io is slow.
• Value: Point at repo (or type a sentence) → editable, owned architecture diagram in <5 min.
• Builds now: System architecture, sequence, ERD, infra, dependency, CI/CD, network, class diagrams from a repo; exports to README/docs/slides.
• Near future: Re-sync diagram when code changes; one-click "explain this repo" doc.

B. Solution / software architect (SECONDARY bet — validate)

• Pain: Must keep HLD/LLD matching reality for stakeholders; redraws by hand every sprint; decisions undocumented.
• Value (now): Generate diagrams from code/brief, edit in draw.io, own them.
• Value (near future — Architect Co-Pilot v1): Business brief → clarifying Qs → HLD + LLD + design doc (overview, components, data model, trade-offs, risks, NFRs). Accelerates architecture planning and documentation.
• Most complex thing it can help with (near future): Take an ambiguous business requirement and produce a coherent, consistent, editable multi-level design with rationale — the work a junior-to-mid architect does in days, in minutes, with a human in control.

C. Product / program folks (sub-product opportunity, G5)

• Pain: Need workflow diagrams + a real design/PRD doc + to get artifacts into Notion/Confluence/Jira/GitHub.
• Value: Mini "workflow + design-doc" tool with connectors; AI drafts the workflow and doc, they refine, then push to their stack.

D. Startups & "vibe coders" (north-star vision, G5)

• Pain: Can't afford a senior solution architect; coding agents produce code without architectural judgment; cloud bills creep; deployments are scary.
• Value (vision): An on-demand virtual AI Solution Architect that designs, guides coding agents, watches cloud cost (FinOps architect — continuously finds savings without disrupting prod, user stays in control), and can assist deployment. Each persona ships only after the prior proves value. v1 is the HLD/LLD/doc slice — everything else is explicitly later.

Reality guardrail

A/B work in code today. C/D are roadmap. Marketing leads with A (proven), introduces B as the new capability we're shipping, and frames C/D as vision — never as available.