Investor update

Safari Writer

1 / 1 Press ←/→ to navigate Press S for speaker notes Press O for overview

Investor presentation draft · repo snapshot 2026-03-08

Safari Writer: product progress, remaining work, and go-to-market path

A retro-styled writing environment built with Python + Textual, combining editor, proofreader, mail merge, print/export, and Safari DOS file management.

Current state

Core product is working. The biggest job now is polish, completion, and positioning.

Pitch framing

We are selling disciplined progress on a differentiated niche product, not vapor.

Executive summary

  • Product exists today: editor, formatting, proofreader, mail merge, print/export, and Safari DOS all have real implementation.
  • Validation signal: current test suite passes at 586 tests from a fresh make test run.
  • Spec maturity: most core specs are largely implemented; the major untouched area is the AI chat spec.
  • Best near-term use of capital: finish polish and workflow gaps before expanding into ambitious AI features.
  • Market story: retro UX + practical writing workflows + terminal-native simplicity gives us a clear niche.
  • Recommendation: fund a focused push to turn a promising 0.1 product into a reliable v1 wedge.

What Safari Writer is building

Product thesis

  • Modern spiritual successor to AtariWriter with a Textual terminal UI.
  • "What you see is what you mean" editor model: formatting is explicit and visible.
  • Designed for focused writing, editing, light publishing, and structured document workflows.

Target users

  • Retro-computing enthusiasts who want a real tool, not just an emulator.
  • Writers and technical users who prefer keyboard-first, low-distraction interfaces.
  • Developers and documentation teams who benefit from plain-text and syntax-aware workflows.

Evidence base: README, pyproject, TODOs, and spec set in spec\*.md.

What is done now

Core editor

  • Main menu and editor flows
  • Search and replace
  • Block operations
  • Inline style codes

Document workflows

  • Global format screen
  • ANSI preview
  • Markdown export
  • PostScript export

Data + support tools

  • Proofreader module
  • Mail merge data + injection
  • Safari DOS standalone module
  • Recent file and project plumbing
Change log shows 0.1.1 work added on 2026-03-08
Pyproject package version is still 0.1.0
Latest shipped feature area: file type awareness + syntax highlighting

What is not done yet

High-value completion work

  • Mid-document global format overrides
  • Manual dictionary creation in proofreader
  • Double-column rendering in preview and PostScript
  • Safari DOS conflict-resolution and progress flows

Still-open product gaps

  • Undo remains an obvious UX gap called out in BUGS.md.
  • Some Safari DOS list navigation and filtering features remain open.
  • Cross-platform polish and edge-case handling still need concentrated effort.
  • The ELIZA-style AI chat spec exists, but implementation has not started.

The strongest investor story is "finish and harden the product" before "add every future concept."

How the specs are coming along

Spec area Status Investor read
Core editor / keyboard / global format / CLI / demo mode Largely done Core product shape is established.
Inline formatting / proofreader / mail merge / print Partly done Useful today, but still needs workflow polish and edge-case completion.
Safari DOS Functionally strong, UX incomplete Good strategic differentiator if polished.
File type awareness Done Fresh signal that velocity is real.
AI chat / ELIZA-RAG Spec only Potential upside, but should not anchor the next milestone.

Estimated completion is repo-based inference, not a formal earned-value model.

Challenges that remain

Product polish

Undo, save flows, prompts, and edge-case UX still need tightening to meet modern expectations.

Rendering complexity

Preview, Markdown, and PostScript outputs must stay aligned as formatting features expand.

Cross-platform behavior

Windows terminal quirks and file-system differences make QA and support more demanding.

Scope discipline

There is a risk of spreading effort across AI, DOS polish, and editorial features all at once.

Bottom line: the project's main risk is not vision failure; it is finishing quality-critical details fast enough.

Why this product can win

  • Differentiated UX: retro identity is memorable and marketable.
  • Practical utility: proofreader, mail merge, and export make it more than nostalgia.
  • Terminal-native: fits technical and keyboard-first audiences well.
  • Focused positioning: it does not need to beat Microsoft Word at everything.
  • Spec discipline: unusually detailed specs reduce product drift.
  • Local-first story: offline, lightweight, and installable with simple Python tooling.

What sort of LLM bots we should hire next

1. QA triage bot

  • Reads specs, TODOs, and BUGS
  • Turns gaps into reproducible test cases
  • Best ROI for finishing work cleanly

2. Textual UX bot

  • Specialist in keyboard flows and TUI ergonomics
  • Focus on prompts, menus, layout, and affordances
  • Key for Safari DOS and editor polish

3. Print/rendering bot

  • Owns preview / Markdown / PostScript alignment
  • Reduces regressions in layout logic
  • Supports higher-confidence output features

4. Documentation / demo bot

  • Creates docs, scripts, walkthroughs, and release notes
  • Improves onboarding and investor/customer demos
  • Useful immediately

5. Growth copy bot

  • Writes landing pages, launch posts, and email sequences
  • Tunes positioning by audience segment
  • Supports market discovery without huge agency spend

Wait on this one

  • Do not lead with an "AI chat bot builder" bot yet.
  • The AI chat spec is rich, but it is a second-stage investment.
  • Finish product readiness first, then expand intelligently.

Market fit: where the wedge is

Best initial segments

  • Retro-computing and digital minimalism communities
  • Technical writers and developer-documentation users
  • Writers who want a local-first, distraction-light environment

Good reasons they may buy in

  • Distinctive writing experience they can feel immediately
  • Practical export and proofreading capabilities
  • No cloud dependency and a straightforward install path
Best thesis: Safari Writer is not mass-market office software; it is premium-fit software for users who care about focused writing and characterful tools.

Competition and positioning

Category Examples Why Safari Writer still matters
Mainstream word processors Microsoft Word, Google Docs Safari Writer competes on focus, identity, local-first use, and keyboard-first simplicity.
Plain-text / markdown editors Obsidian, Typora, VS Code Safari Writer adds retro differentiation, built-in proofing, and document-printing flavor.
TUI editors Vim, Neovim, Helix, nano Safari Writer is friendlier for non-programmer writers and has a stronger guided workflow model.
Retro references AtariWriter, ST Writer, emulators Those establish lineage; Safari Writer makes the idea usable on modern systems.

How we should be marketing this

Lead with the vibe, close with utility

Use retro visuals and terminal aesthetics to earn attention, then prove the product solves real writing tasks.

Demo-first content

Short videos and GIFs showing edit -> proofread -> export -> mail merge will outperform feature lists.

Community channels

Retro computing circles, Python/Textual communities, indie writing spaces, and developer-productivity audiences.

Positioning line

"A modern retro word processor for people who want focus, keyboard speed, and character."

  • Build a polished demo document pack
  • Collect user quotes early
  • Publish roadmap discipline, not endless feature promises

Recommended next milestone plan

Milestone 1

  • Undo and save-flow fixes
  • Proofreader dictionary completion
  • Safari DOS prompt and conflict polish

Milestone 2

  • Double-column rendering and print confidence
  • UI interaction tests for key flows
  • Packaging and release discipline cleanup

Milestone 3

  • Public-facing docs and demo assets
  • Early adopter recruitment
  • Decision gate on AI chat investment

The investor take

Safari Writer looks investable as a disciplined niche software play: a differentiated product with real implementation, a clear roadmap, and a sensible path to finish, package, and test market demand.

Reasons to lean in

  • Real code, real tests, real shipped capability
  • Distinctive brand and user experience
  • Clear use for AI assistance in execution

What investors should watch

  • Can the team close polish gaps quickly?
  • Can the product earn love from its first niche community?
  • Can roadmap discipline beat feature temptation?

Source basis for this deck

  • README.md for product description and current feature framing
  • TODO.md, TODO_files.md, and BUGS.md for completion and gap tracking
  • CHANGELOG.md and pyproject.toml for release and packaging context
  • spec\*.md, spec\ROADMAP.md, and spec\PRIOR_ART.md for scope, ambition, and competitive lineage
  • make test run on 2026-03-08 confirming 586 passed

Competition and marketing recommendations include informed strategic judgment on top of repository evidence.