Go to Market¶

Operational source:

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\go-to-market

This page mirrors the detailed operational tracking for this track so the deployed wiki shows the same score tables as the source TRACKING.md.

Last updated¶

2026-04-29

Scoring model¶

This track uses milestone and feature scorecards.

Score guide:

100 means complete, validated, and stable for current scope
90-99 means strong and working, but still carrying meaningful gaps
75-89 means materially working, but still missing important completeness
50-74 means real foundation exists, major parts are still absent
below 50 means early, partial, or mostly planned

For this non-code track, 100 requires completed deliverables plus active source proof that the milestone is currently usable.

Evidence sources reviewed¶

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\go-to-market\MASTER_PLAN.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\04_Marketing and Outreach\Presentation_trials\competition_short.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\04_Marketing and Outreach\Presentation_trials\competition_detailed.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\contact_workflow
D:\02_Code\45_merged_macos_colabui_dfmanim
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\01_RapidDraft\04_Technical_Architecture\CAD_Drive_Collaboration_Mode.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\00_Meta\Decision_Log.md

Current overall score¶

Go to Market overall score: 67 / 100

Why the score is not higher: The asset base is rich, especially for pitches and company-tailored decks, and the product now has a simpler shareable wedge in CAD Drive collaboration. The score is not higher because the current pilot pipeline, outreach workflow, and post-share feedback loop are still not centrally governed. The live app is closer to shareable because app.rapiddraft.ai is now the intended Stytch-gated entry point and hosted DraftLint is available, but the trusted-recipient list and feedback loop still need operating discipline.

Milestone scorecard¶

Milestone	Score / 100	Current state	What it helps achieve	Main remaining gap
1. Canonical product narrative	74	Working	Keeps the product story coherent across competitions and pilots.	CAD Drive collaboration is the default near-term wedge, but the Core-vs-Studio long story still needs discipline.
2. Competition and application assets	82	Strong	Provides ready material for incubators and competitions.	Still needs one current source-of-truth list.
3. Pilot pipeline	62	Foundation exists	Moves the company from pitch-only to customer traction.	The immediate trusted-share group can start feedback, but prospects and status are still not centrally tracked.
4. Company-tailored materials	76	Strong	Makes outreach and pilot discussions more credible.	The asset library is distributed.
5. Outreach operations	38	Early	Supports repeatable customer contact and follow-up.	Workflow exists in fragments, but no mature operating loop is declared.
6. Current traction readiness	58	Partial	Converts assets into a repeatable founder motion.	CAD Drive can now be shared with a small trusted group on `app.rapiddraft.ai`, with Stytch access and hosted DraftLint available. Feedback capture, follow-up, and the queued public-surface cleanup still need a tight loop.

Feature scorecard¶

Feature track	Score / 100	What it helps achieve	Current note
Positioning	76	Gives the company a differentiated story.	The default near-term story is now clearer: CAD Drive collaboration first, Expert/DFM depth second.
Pitch system	81	Supports competitions and investor-facing communication.	One of the strongest parts of the track.
Pilot targeting	66	Helps prioritize customer conversations.	There are real pilot materials and now a shareable collaboration trial on the intended app domain, but central tracking is still light.
Outreach workflow	38	Makes founder outreach repeatable.	Current workflow is still fragmented; today's trusted-share loop should become the first governed feedback loop.
Application readiness	82	Keeps the company ready for competitions and programs.	Strong asset coverage already exists.
Proof and credibility assets	78	Makes the product feel real to external audiences.	Many tailored decks exist, and CAD Drive now gives the story a live product surface instead of only deck evidence.

Current headline assessment¶

Go to Market is not starting from zero. There is already a substantial pitch and pilot asset base, and CAD Drive collaboration is now real enough to create external feedback. The lower score comes from operational fragmentation, not lack of material.

Active rollout updates¶

This week's go-to-market motion should be intentionally narrow: share CAD Drive with a few trusted people, ask them to perform one collaboration loop, and capture what fails or confuses them.

Late-day rollout context: use app.rapiddraft.ai as the link, not pilots.rapiddraft.ai. Recipients must exist in Stytch before magic-link sign-in works. DraftLint is available through the hosted IONOS gateway with 20/minute and 100/month scan limits, so the feedback ask can include one drawing scan if the recipient has a suitable PDF/PNG/JPG. The production UI cleanup that hides internal Batch Mode, Design Review, and pinned standards is pushed but still queued in Railway, so avoid over-reading the current launcher if it still exposes internal surfaces.

Highest-value next actions¶

Pick 3-5 trusted recipients for today's CAD Drive share, add/confirm them in Stytch, and record owner, email, status, and feedback notes in one place.
Send a focused ask: open/upload a model, share a link, add a pinned comment, reply, upload a new version, optionally run one DraftLint drawing scan, and tell us what felt unclear.
Turn the responses into a one-week blocker list for Collaboration, not a broad roadmap.
After the trusted-share loop, create one pilot pipeline view with current status and top targets.

Related wiki material: The refined RapidDraft targeting method now lives in RapidDraft_Refined_Search_Loop.md, and the current ranked output lives in RapidDraft_Refined_Targets.md.

Sources¶

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\go-to-market\MASTER_PLAN.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\go-to-market\TRACKING.md