NeverWrite NeverWrite

Your knowledge base, made smarter.

q3-launch-plan.md
AI Review
Launch notes.md •
client-discovery.md
fieldwise-approval-flow.excalidraw
Clients / Fieldwise / Launch

Fieldwise Q3 launch plan

Launch objective

Position Fieldwise's new analytics workspace as the clearest way for operations teams to spot delivery risk before it becomes a client issue. The launch should generate qualified demo requests while giving existing customers a concrete reason to upgrade.

Approved scope

Northstar will deliver the launch narrative, landing page, product announcement, three customer emails, and sales enablement copy. Paid media, video production, and product UI changes remain outside this engagement unless approved in writing.

Working sequence

Aug 18–29: finalize message and landing-page draft. Sep 1–5: client review and legal approval. Sep 8–12: build, QA, and sales handoff. Sep 16: publish and monitor the first-week conversion report.

Decisions needed this week

Confirm the primary audience, approve the proof-point hierarchy, and name one Fieldwise owner for legal and product sign-off. Without a single approval path, the launch date is at risk.

Risk watch

The product metrics are still being validated. Use the approved range in public copy until Finance confirms the final figures. Keep customer examples anonymous until the reference permissions are signed.

Integrated Terminal
~/Documents/Northstar-Studio $
git status --short
M Clients/Fieldwise/Launch/q3-launch-plan.md
?? Clients/Fieldwise/Launch/launch-checklist.md
2 AI changes pending review
$ _
New chat
Review the Q3 launch plan. Keep the scope firm, make the approval path explicit, and do not change the client promise without support from the discovery notes.
The plan is well grounded. The main gap is operational: the scope is clear, but the team needs one named approval path before the review window starts. I can tighten that section and add a small handoff checklist.
Apply those as a review. Keep every edit pending until Maya approves it.
New Turn11s
Reading linked context
Drafting review
I clarified the approval gate in q3-launch-plan.md and created a reusable checklist for the final handoff. The customer-facing claim remains unchanged.
Edited q3-launch-plan.md+8-3
@@ -16,4 +16,5 @@ q3-launch-plan.md
1616 ## Decisions needed this week
17- Confirm the primary audience, approve the proof-point
18- hierarchy, and name one Fieldwise owner for legal and
19- product sign-off.
17+ Confirm the primary audience and approve the
18+ proof-point hierarchy. By August 29, Fieldwise names
19+ one approval owner who coordinates Product, Legal,
20+ and Revenue sign-off. Northstar starts build only
21+ after that owner confirms the final scope.
Preparing pending changes
Two reviewable changes are ready. Nothing has been applied to the workspace yet.
Edits (2)+20-3
q3-launch-plan.md+8-3
launch-checklist.md+12-0
Download free View on GitHub
Local-first vault Notes stay in a folder on your computer.
Review every AI edit Accept, reject, or refine before anything lands.
Your keys, your models Connect the AI you already pay for.
Apache 2.0 Open source. Free to use. No lock-in.
Control

AI that asks before it writes

Agents can draft, restructure, and research across your notes. Every edit lands as a reviewable change — accept, reject, or refine one step at a time. Nothing is silently rewritten.

Align Q3 targets in proposal.md and add the incident checklist to runbook.md. Apply as a review — do not write straight into the vault.
Preparing input
Drafting response
Tightened the targets paragraph and drafted the incident checklist. Both land as reviewable edits — nothing is written until you accept.
Edited proposal.md+2-1Open
14- Q3 targets need revision
14+ Q3 targets aligned with pipeline
1515  Owner: GTM ops · review Friday
Applied the edit to proposal.md and runbook.md. Review when ready.
Edits(2)+7-1
Review
proposal.md+2-1
runbook.md+5-0

Message Claude — @ to include context, / for commands

Accept Editsopus
Privacy

Your files never leave your desk

NeverWrite opens a folder on your machine. No cloud vault, no account, no telemetry. AI is only used when you attach content or start a session — with the providers you choose.

TeamVault

~/Documents/TeamVault
Workspace

One place for writing, research, and review

Markdown notes, PDFs, tables, terminals, and multiple AI sessions side by side. Clip web research into your vault. Keep client work and internal docs in the same professional editor.

Clients / Fieldwise

Q3 proposal

Scope, timeline, and ownership for the Fieldwise rollout. This document is the working draft GTM shares with legal before the Friday review.

Executive summary

Fieldwise Enterprise is ready for a phased deployment across two business units. Coverage sits at 2.1× pipeline, with primary risk concentrated in legal review cycles.

Q3 targets need revision

Q3 targets aligned with pipeline. Owner: GTM ops · review Friday.

Deliverables

  • Executive summary for leadership
  • Pipeline targets by segment
  • Owner handoff and escalation path
  • Security & data-residency appendix

Timeline

Kickoff in week of July 7. Pilot complete by end of August. Full production cutover scheduled for the first week of September, pending legal sign-off.

Ownership

AreaOwner
CommercialGTM ops
SecurityPlatform
LegalCounsel

Clients/Fieldwise/proposal.md · plaintext Markdown · local

Align Q3 targets in proposal.md and tighten the executive summary from the brief. Apply as a review — do not write straight into the vault.
09:16
Preparing input
Reading q3-brief.pdf
Drafting response

Tightened the targets paragraph and drafted the executive summary from q3-brief.pdf. Nothing is written until you accept.

Edited proposal.md+2-1Open
14- Q3 targets need revision
14+ Q3 targets aligned with pipeline
1515  Owner: GTM ops · review Friday

Applied the edit to proposal.md and runbook.md. Review when ready.

Edits(2)+12-3Review
proposal.md+8-2Open
runbook.md+4-1Open

Message Claude — @ to include context, / for commands

Accept Editsopus
How it works

Three steps. Full control.

No onboarding maze. No cloud account. Start with a folder and keep humans in the loop.

01

Open a folder

Point NeverWrite at a vault on your computer. Your notes stay as normal files you already own.

02

Write and collect

Capture notes, research, and web clips. Organize with tags, links, and search that stays local.

03

Ask AI, then approve

Let agents draft and reorganize. Review every change before it becomes part of your knowledge base.

Built for SMEs

Knowledge work without the cloud tax

Designed for teams that need serious writing tools and AI help — without giving up ownership of their documents.

Founders & small teams

Document decisions, product notes, and hiring plans without shipping internal knowledge to a SaaS vault.

Consultants & agencies

Keep client research private. Clip sources, draft proposals with AI, and approve every line before it leaves the vault.

Ops & knowledge owners

Maintain SOPs and runbooks as Markdown. Let agents suggest updates — you ship only what you review.
Download

Download NeverWrite

Free for macOS, Windows, and Linux. No account required.

macOS Universal Apple Silicon + Intel Windows x86_64 Most PCs Windows ARM64 Snapdragon, Copilot+ PCs Linux x64 AppImage Intel, AMD Linux ARM64 AppImage ARM Linux devices Linux x64 .deb Intel, AMD Debian/Ubuntu Linux ARM64 .deb Debian, Ubuntu ARM Linux x86_64 RPM Fedora and RPM-based distros Linux AArch64 RPM ARM RPM-based distros

Free, open source, no account required.

Bring your own AI

Use the models you already pay for

NeverWrite connects to your existing AI subscriptions and keys. No middleman markup — you choose the model, you control the spend.

Codex

Strong for structured drafts and technical writing.

Claude

Natural long-form writing and careful reasoning.

OpenCode

Terminal-native agent with provider settings in-app.

Kilo

Open-source agent for planning and vault work.

Grok

Native Grok ACP with official CLI detection.

More providers are on the roadmap. Requested runtimes ship as ACP compatibility lands.

FAQ

Common questions

Is NeverWrite free?

Yes. NeverWrite is open source under Apache 2.0. Download and use it with no subscription, paywall, or account. It grows through contributions from its community.

Where is my data stored?

On your machine. Notes and chat histories stay local unless you explicitly send content to an AI provider or another tool you choose. You can also store your folders in a synced location such as OneDrive, Dropbox, Google Drive, or a similar service.

Do I need an API key?

For AI features, use keys or subscriptions from providers such as OpenAI, Anthropic, Kilo, or Grok. You connect directly to them — no middleman. You control which models run and what you spend.

Can AI change my notes without permission?

You decide. Agent permissions are configurable, and edits go through review so you can accept or reject changes before they stick.

What platforms are supported?

macOS, Windows, and Linux — including AppImage, Debian/Ubuntu .deb, and RPM packages on supported systems.

Your folders. Made smarter.

Free, open source, no account required. Download NeverWrite and keep your team's knowledge on your machine.

Download free View on GitHub