Go to Market¶

Operational source:

/Users/adeelyj/Library/CloudStorage/OneDrive-Personal/100_Knowledge/203_TextCAD/01_Product_Project_Management/00_Project_Management_n_skills/01_tracks/go-to-market

This page is the local wiki mirror of the operational MASTER_PLAN.md and TRACKING.md.

Last updated¶

2026-06-18

Current overall score¶

Go to Market overall score: 72 / 100

The score moves from 67 to 72 because June materially improved the external proof surface: Theegarten-specific follow-up, architecture/local-AI framing, bilingual website direction, and concrete pilot next steps. The score is still capped because the pilot pipeline is not yet one governed view, website branch/deploy truth still needs discipline, and RapidCRM scheduled outreach has a known reliability gap.

Current posture¶

The current external story has two related motions:

live product proof around CAD Drive, Agent, Drawing Analysis/DraftLint, and Expert workflows
customer follow-up proof around Theegarten-Pactec, controlled local/private AI, and a release-check pilot path

Milestone scorecard¶

Milestone	Score / 100	Current state	Main remaining gap
Canonical product narrative	78	Working and sharper	Core-vs-Studio and app-vs-website language still need discipline.
Competition and application assets	82	Strong	Needs one current source-of-truth list.
Pilot pipeline	69	Real but distributed	Needs one governed view of prospects, status, owner, next action.
Company-tailored materials	84	Strong	Asset library remains distributed across website, wiki, pilot folders.
Outreach operations	44	Early with reliability plan	RapidCRM send-only worker/status cleanup not implemented yet.
Current traction readiness	68	Improving	Feedback capture, CRM reliability, and pipeline governance need a tight loop.

Feature scorecard¶

Feature track	Score / 100	Current note
Positioning	81	Stronger after Theegarten release-check and controlled local/private AI framing.
Pitch system	82	Strong, but should be refreshed against current Theegarten proof.
Pilot targeting	72	Real assets exist; central status tracking is still light.
Outreach workflow	44	RapidCRM exists but scheduled-send reliability needs the planned fix.
Application readiness	82	Strong asset coverage.
Proof and credibility assets	84	Website, Theegarten wiki, local-AI architecture, CAD Drive, DraftLint, Agent proof.

Active updates¶

2026-06-18 - Website, Theegarten follow-up, and CRM reliability refresh¶

The website repos now contain Theegarten follow-up and broader site polish work. The local wiki has Theegarten and local-AI supporting pages. The RapidCRM reliability plan documents a send-scheduling failure mode and the required send-only worker/status/monitoring fix.

2026-06-08 - Theegarten follow-up page becomes the lead customer asset¶

https://rapiddraft.ai/theegarten-pactec is the immediate customer-facing follow-up asset. It should explain RapidDraft as the engineering review layer, keep local/private AI behind a controlled backend boundary, avoid overclaiming about autonomous release, and present an 8-12 week pilot path.

2026-05-26 - Website branch reconciliation preserved the non-Google NDA flow¶

The website reconciliation plan keeps the Netlify form capture plus local PDF NDA/LOI path and avoids reintroducing the Google Docs/Drive NDA path.

Highest-value next actions¶

Create one pilot pipeline view with target, owner, status, next action, asset link, and last contact.
Verify live website branch/domain state before sending or referencing pages.
Use the Theegarten follow-up page as the immediate customer asset.
Implement the RapidCRM scheduled-send reliability plan before scaling outbound.
Refresh pitch/application assets against the current release-check/local-AI/product-proof story.

Sources¶

Operational GTM master plan and tracker.
01_tracks/go-to-market/plans/260526_rapiddraft-website-branch-reconciliation/README.md
01_tracks/go-to-market/plans/260608_theegarten-follow-up-architecture-page/README.md
01_tracks/go-to-market/plans/260617_rapidcrm-scheduled-send-reliability/README.md