New planning source added to the Atlas Launch project.
Living project memory for teams that move faster than their docs
Keep project context flowing as the work changes.
contextflow turns source material into project memory, tracks what changes, and pushes updates to the right people as they happen.
Atlas Launch Changelog
Overview, requirements, risks, and open questions were drafted from the source.
Subscribed teammates and contributors received the context that changed.
Atlas Launch Sources
Initial launch plan, requirements, and open questions.
Decisions and follow-ups from the latest launch review.
Early beta signals grouped by onboarding, identity, and support.
Atlas Launch People
Following requirements, next steps, and open decisions.
Subscribed to source-backed changes and ownership updates.
Receiving concise updates when timing, risk, or direction changes.
Atlas Launch Memory
The beta launch is on track with onboarding and identity as active workstreams.
Owner review is needed before the next launch-readiness checkpoint.
The project needs a clearer owner for beta customer escalation.
What changed, what matters, who needs to know
Why this exists
Every project has a story. Most teams work from data spread across many sources.
Decisions live in meetings. Requirements drift in docs. Risks surface in chat. contextflow gives that moving context one place to settle, starting with a generated project memory and growing into a maintained source of truth.
The product loop
Start a project. Add context. Keep everyone current.
Start a project
Create a home for the work, the questions around it, and the decisions that shape it.
Add sources
Paste notes on the Free plan, or connect documents and richer sources on Pro.
Add people
Include teammates, collaborators, and other contributors who need specific context.
Build project memory
contextflow organizes the important facts into readable Markdown files.
Push useful updates
When source material changes, subscribed people get the context that matters to them.
When the project moves
Pro turns document drift into useful updates.
The Free plan proves the core loop with copied text. Pro is for active work: connected sources can change the project memory, update the change log, and push relevant context to the people who need it.
Role-aware context
The same project change means different things to each contributor.
Teammates
See the decisions, open questions, and next steps that affect their work.
Contributors
Track the source-backed changes, dependencies, and ownership shifts they should know about.
Stakeholders
Receive concise updates when timing, risk, or direction materially changes.
Free vs Pro
Start with a document. Upgrade when the project needs to stay alive.
Free
$0
For turning pasted project context into a basic source-of-truth document.
- One project
- Manual copied-text source input
- Basic generated project document
- Public read link
- Ask questions about the generated document
Pro
$19 per editor / month during beta
For teams that want contextflow to maintain the project memory as work changes, offered as a beta while pricing and usage costs are validated.
- Detailed multi-document project memory
- Discord source ingestion, with more source types coming soon
- Automatic source change detection
- Subscribers, roles, and interests
- Incremental Discord updates, with Slack to come
- Document history and conversation-led improvements
- Additional source connectors beyond Discord
- Slack update delivery
- Organic suggestions for new projects as source material changes
- MCP server for connecting contextflow to AI tools and workflows
Pro is currently a beta. Request access at support@getcontextflow.com.
Pro is currently a beta at $19/editor/month while connector, compute, and ingestion costs are validated. Pricing may change for future customers as usage patterns become clearer.
Questions
Simple enough to try, useful enough to grow into.
Why does the free plan only support manual source input?
It lets people feel the core value immediately: paste messy project context and get a useful project document. Automatic ingestion belongs in Pro because it creates ongoing compute, connector, and notification costs.
What counts as an editor?
Editors manage projects, sources, and subscribers. Readers can view public project documents without being paid seats.
Will there be an Enterprise plan?
Yes, later. Enterprise should focus on SSO, audit logs, advanced permissions, private sources, and custom retention once Pro usage patterns are proven.
How do I know this isn't AI slop?
Fair question. There is no doubt that AI helps us accelerate, and we use it as a tool to get more done. But contextflow did not come from a prompt looking for a product. It came from real pain humans face when project context is spread across too many places: notes, chats, docs, meetings, decisions, risks, and half-finished updates. AI can help execute tasks and draft material. Humans make the decisions, set the philosophy, and decide what is worth building.
How do I get support or delete my data?
Email support@getcontextflow.com for support, account questions, or data deletion requests.
contextflow