Launch Plan · crafter-station/text0

Launch brief

Pricing recommendation

$20/month starter plan for individual users; it is low-friction for indie founders and knowledge workers who want to try reference-aware autocomplete without an enterprise procurement cycle.

Outreach target

The first 50 users should be solo founders, product managers, technical writers, and startup operators at 1–50 person teams who already live in Notion, Linear, and GitHub and who draft specs, updates, or docs daily. Trigger moments: they are overwhelmed by scattered context, need faster first drafts, are building with AI tools already, or want a writing assistant that can pull from their existing work artifacts instead of a blank prompt. Prioritize people who use Next.js/Vercel, ship frequently, and care about privacy or local-first experimentation, since Ollama support and the current editor stack will resonate there.

First week

First-week rollout

Day 1

Positioning + product packaging

Audit app surface in app/page.tsx, app/(protected)/home/page.tsx, and app/(protected)/docs/[doc_id]/page.tsx to identify the one primary user flow: create doc -> add references -> autocomplete/chat.
Write a clear product promise around "absurdly smart (and personal) autocomplete" using supported features from README: smart autocomplete, chat with content, reference-aware suggestions, voice I/O, zen mode, and integrations.
Pick 1–2 launch personas from the existing integrations signal: Notion-heavy operators, PMs using Linear, and founders/docs writers using GitHub references.
Confirm that local-dev Ollama support from commit 791b9a0 is a differentiator for privacy/local testing and include it in the launch angle.

Day 2

Landing page and onboarding

Rewrite app/page.tsx hero copy to emphasize reference-aware writing, not generic AI writing.
Add a single CTA above the fold: "Start writing with Text0" or equivalent sign-in action tied to Clerk sign-in flow in app/(auth)/sign-in/[[...sign-in]]/page.tsx.
Surface the strongest trust proof from repo signals: MIT license, 446 stars, Discord community, and supported integrations (GitHub, Linear, Notion).
Create a short onboarding checklist in the UI pointing users to new-doc, reference selector, and integration setup (app/(protected)/home/new-doc.tsx, app/(protected)/docs/[doc_id]/text-editor/reference-selector.tsx).

Day 3

Core activation fixups

Verify the first-run path from home page to editor loads cleanly and does not depend on optional integrations.
Check the key APIs used for activation: app/api/completion/route.ts, app/api/chat/route.ts, app/api/references/route.ts, and app/api/uploadthing/route.ts.
Add or refine empty states in the editor sidebar components: ai-chat-sidebar.tsx, ai-chat-trigger.tsx, model-selector.tsx, and voice-transcription.tsx so first-time users understand what to do.
Test local dev with Ollama support and document the minimal setup in README or .env.example for fast trial by contributors and users.

Day 4

Proof assets and demo creation

Record 3 short demo clips/gifs: autocomplete in editor, chatting with a referenced doc, and syncing a source from Notion or Linear.
Capture screenshots of the main loop: landing, home/recent files, and document editor using existing public assets (public/landing.png, public/autocomplete.png, public/home.png).
Write a launch thread and a concise demo script that describes the difference between Text0 and standard AI editors: it uses user-provided references for context.
Prepare a public demo document or sample workspace seeded with GitHub/Linear/Notion references to show the product works end-to-end.

Day 5

Distribution prep

Update README.md to include a crisp feature list and a "Why Text0" section anchored to current repo features, not future roadmap items.
Create a changelog or launch note that mentions the new Ollama local development support from 791b9a0 and the existing integrations.
Prepare direct outreach copy for founders, indie hackers, and ops teams who already keep notes in Notion or tasks in Linear.
Set up tracking for sign-ups, doc creation, reference attachment, and first autocomplete usage using existing analytics hooks (@vercel/analytics).

Day 6

Launch outreach

Post the product demo to Discord first, using the existing Discord invite presence in README and app/components/PleaseStarUsOnGitHub.tsx.
Submit to Indie Hackers, Product Hunt, and relevant Next.js/Vercel communities with the "personal autocomplete" angle and local Ollama support.
Send targeted DMs/emails to the first 50 likely users from your network: writers, startup operators, and AI tool builders using Notion/Linear/GitHub daily.
Ask for one specific action: try the hosted app at www.text0.dev, create one doc, and connect one reference source.

Day 7

Ship + iterate

Monitor onboarding drop-off in the first session and fix the largest friction point in the sign-in -> new doc -> reference attach path.
Triage any blocker bugs around editor loading, hydration, or integrations; prioritize issues similar to recent fixes in recent-files, delete dialogs, and hydration errors.
Publish a follow-up post with one concrete user quote or workflow screenshot and ask for feedback on the next improvement from open issues (#29, #23, #21, #14).
Make one visible improvement from launch feedback, even small, to keep momentum and show shipping velocity.

Messaging

Landing page messaging

Headline

Text0: the personal AI editor that writes with your references

Subhead

Autocomplete, chat, and rewrite inside one Next.js editor that can use your docs, GitHub, Linear, and Notion context.

CTA

Start writing with Text0

Feature line

• Smart autocomplete powered by AI • Chat with your content • Reference-aware suggestions from GitHub, Linear, and Notion • Voice input/output and zen mode • Local development with Ollama support for private testing

Channels

Distribution channels

Discord community

Rank 1

Highest intent because the repo already points users to Discord and existing contributors/community can amplify the launch quickly.

Product Hunt

Rank 2

Best fit for a polished AI productivity tool with a clear demo and a strong hook around personal autocomplete.

Indie Hackers

Rank 3

Indie founders already have the pain point of drafting docs and product updates from scattered references.

Next.js / Vercel communities

Rank 4

The stack signal (Next.js, Vercel, AI SDK) makes it easy to attract builder-minded early adopters.

Direct outreach to Notion/Linear/GitHub power users

Rank 5

The integrations are already in the product, so users with these tools are the fastest path to activation.

Metrics

Success metrics for day 7

50 activated signups (account created + first doc opened)
20 users connect at least one reference source or sample workspace
10 users complete at least one autocomplete or chat action in the editor
5 public posts or shares mentioning Text0 from launch channels
At least 3 qualitative user quotes confirming the reference-aware workflow is useful

Shared with Git Pitcher

This webpage is a public artifact generated from a repository. Git Pitcher turns repos into Repo Reads, Audits, and Build Packs you can actually use with an AI coding agent.

Analyze your own repo →Generate a Build Pack →