GITNUXSOFTWARE ADVICE
Mental Health PsychologyTop 10 Best Writers Block Software of 2026
Top 10 Writers Block Software ranking with criteria for journaling support, AI chat tools, and mental health apps like Wysa and Woebot.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Wysa
Stateful prompt orchestration tied to a structured conversation schema via API and automation events.
Built for fits when teams need workflow automation for writing anxiety with API-driven state control and governance..
Woebot
Editor pickClinician-configured, state-driven conversation flows with constrained step paths for consistent intervention execution.
Built for fits when mental-health style writing workflows need strict conversation schemas and controlled escalation paths..
MindDoc
Editor pickLinked mind-map nodes that generate document views for planning-to-draft continuity and consistent exports.
Built for fits when writers need structured mind-map to document workflow with governed collaboration..
Related reading
Comparison Table
The comparison table maps Writers Block software across integration depth, data model design, and automation plus API surface. It also captures how each tool handles provisioning, RBAC, audit log coverage, and configuration and extensibility. The goal is to show concrete tradeoffs in schema alignment, admin governance controls, and operational throughput.
Wysa
AI journalingAn AI journaling and self-guided mental health app that supports guided check-ins, emotion tracking, and reflective prompts designed to reduce writer’s block in writing workflows.
Stateful prompt orchestration tied to a structured conversation schema via API and automation events.
Wysa can capture user inputs, categorize writing stress signals, and drive stepwise interventions that depend on prior session context. The data model supports provisioning of conversational flows and tracking progress across sessions, which matters for teams that need consistent outcomes. Integration depth shows up in the ability to connect external systems to conversation state and intervention outcomes through an automation and API surface.
A tradeoff appears in configuration effort, since deeper automation and custom routing require more schema-aligned setup. Wysa fits when a team needs measured throughput across many sessions and wants admin governance with RBAC-style access boundaries and an audit log trail for critical events. Writers or internal health ops teams can use it to route users into specific exercises while preserving context continuity.
- +Conversation state and progress tracked as structured data for consistent interventions
- +Automation and API surface supports routing based on context and outcomes
- +Governance controls include RBAC-style access boundaries and event traceability
- +Extensibility through configurable prompts and workflow definitions tied to state
- –Deeper customization requires careful schema-aligned configuration
- –Custom workflow logic can increase operational overhead for small teams
clinical ops teams
Route writers by risk signals
More consistent stepwise care
product integration teams
Sync writing sessions with tools
Higher workflow throughput
Show 2 more scenarios
security and governance
Control access and review events
Reduced access and audit risk
RBAC-style permissions and audit log coverage support admin governance for sensitive session data.
behavior change program owners
Provision CBT writing routines
Improved adherence to routines
Configurable exercises depend on session context to guide users through structured cognitive tasks.
Best for: Fits when teams need workflow automation for writing anxiety with API-driven state control and governance.
More related reading
Woebot
CBT chatbotA chatbot-based self-guided mental health tool that provides interactive CBT-style exercises and prompts intended to help users overcome cognitive blocks during writing.
Clinician-configured, state-driven conversation flows with constrained step paths for consistent intervention execution.
Woebot fits teams that need writers-block-like intervention flow control rather than generic chat. The data model ties conversation state to a finite set of therapeutic steps, which reduces free-form drift during high-stakes interactions. Integration breadth shows up through channel connectivity and workflow hooks that emit events for downstream logging, reporting, and escalation.
A key tradeoff is limited extensibility compared with platforms that expose a full prompt graph, so custom logic usually stays within supported configuration boundaries. Woebot works well for use cases where a consistent conversational schema must run at predictable throughput and where admin governance must control what content and steps are reachable.
- +Conversation state schema constrains steps and reduces free-form responses
- +Configurable intervention flows support consistent clinical messaging
- +Event output supports downstream logging and operational reporting
- +Automation structure supports repeatable throughput under steady traffic
- –Extensibility is constrained versus full custom workflow graphs
- –API surface is narrower than purpose-built automation studios
Behavioral health operations teams
Standardize intake and coping prompts
Consistent guidance across channels
Digital clinical programs
Run controlled conversation automations
Fewer off-path interactions
Show 2 more scenarios
Customer success analytics teams
Monitor intervention outcomes
Actionable visibility for admins
Woebot emits workflow events that can be tied to reporting and operational dashboards.
Safety and compliance leads
Govern reachable guidance content
Governed automation behavior
Woebot configuration controls conversation reachability to keep outputs aligned with approved steps.
Best for: Fits when mental-health style writing workflows need strict conversation schemas and controlled escalation paths.
MindDoc
CBT workbookA mental health journaling and CBT-style workbook platform with self-assessments and structured exercises that can feed writing prompts when ideation stalls.
Linked mind-map nodes that generate document views for planning-to-draft continuity and consistent exports.
MindDoc centers on a node-and-link data model where each mind map element becomes an editable unit inside a writing workflow. Document views keep structure consistent while edits propagate across the map, which reduces drift between planning and drafting. Collaboration features include shared workspaces and revision history, and role-based access supports governance for writing teams. Export options let teams move from structured drafts to formats for downstream editing and publishing.
A tradeoff appears in automation depth since high-throughput, multi-system pipelines depend on the available API endpoints and webhook behavior rather than fully configurable internal jobs. MindDoc fits well when writers need traceable planning-to-draft continuity for recurring deliverables like campaign briefs, SOPs, or client proposals. Teams with strict admin policies benefit most when RBAC and auditability align with internal review gates before documents are exported.
- +Node-based data model keeps planning and drafting synchronized
- +Revision history supports review workflows with traceability
- +Collaboration around shared maps reduces copy-paste drift
- +Exports convert structured writing artifacts into deliverable formats
- –Automation breadth can lag teams needing complex multi-step pipelines
- –Deep governance depends on available RBAC granularity and audit log coverage
- –Extensibility constraints may limit bespoke content generation flows
Content operations teams
Convert campaign briefs into drafts
Faster handoff to editors
Technical writers
Draft SOPs from structured outlines
Lower inconsistency across versions
Show 2 more scenarios
Agile project teams
Track requirements through deliverable drafts
More consistent change reviews
Requirement nodes link across plans and document exports for review cycles.
Enterprise knowledge teams
Govern shared templates across teams
Controlled authorship and access
RBAC and workspace controls restrict map edits and manage shared drafting assets.
Best for: Fits when writers need structured mind-map to document workflow with governed collaboration.
BreeZy
AI assistantAn AI mental health journaling companion that generates reflection prompts and coping exercises to support consistent writing output when blocked.
API-driven draft generation with configurable prompt and template workflows for repeatable content cycles.
BreeZy pairs writers block workflows with content generation controls aimed at reducing dead ends during drafting. It integrates with common authoring and productivity surfaces, while maintaining a structured data model for prompts, drafts, and revisions.
Automation features map inputs to outputs through configurable templates and recurring workflows. A documented API and extensibility points support integration depth for teams that need provisioning, RBAC alignment, and audit-friendly operations.
- +Structured data model for prompts, drafts, and revision artifacts
- +Configurable templates for repeatable writing workflows across projects
- +API surface supports automation that can drive draft generation
- +Integration targets common authoring and productivity tooling
- –Workflow configuration can require careful schema alignment across teams
- –Automation throughput may bottleneck if generation steps are chained
- –Governance relies on external process when RBAC and audits are strict
- –Complex multi-step prompt logic can be harder to maintain over time
Best for: Fits when teams need writers block tooling plus API-driven automation to control draft generation at scale.
MindNode
ideation mappingCross-platform mind-mapping for structured ideation with keyboard-first capture, templates, and export options that support repeatable writing and planning workflows.
Mind map to outline export that preserves branching structure when translating ideas into draft text
MindNode turns writing into a node-based mind map that can be exported into outlines and drafts. The core capability is converting branches into structured text while maintaining visual context for ideation and revision.
Integration depth is limited to third-party connection points rather than a full automation and workflow API surface. Automation and extensibility depend mainly on export formats and external integrations rather than provisioning, RBAC, or schema-driven data exchange.
- +Node-to-outline flow keeps ideas connected during drafting and revision
- +Export formats support downstream writing workflows outside the mind map
- +Cross-device access supports ongoing capture and refinement of concepts
- +Keyboard-first editing supports fast restructuring during ideation
- –Limited automation controls reduce hands-off operations for writing at scale
- –Public API and data schema options are not a primary extension mechanism
- –Admin governance controls like RBAC and audit logs are not a focus
- –Integration breadth can lag compared with tools built for workflow orchestration
Best for: Fits when individuals or small teams want visual drafting structure with minimal automation requirements.
Obsidian
knowledge graphLocal-first knowledge base with Markdown and a graph data model that supports writing workflows, automation via community plugins, and integration through local APIs.
Plugin API for custom commands, views, and event-driven automation over a Markdown-backed link graph.
Obsidian fits writers and knowledge workers who want local-first note storage plus fast personal automation via plugins. The data model centers on Markdown files, folder structures, and link graphs, so integrations map directly onto readable text.
Its extensibility comes from a plugin API, with options to automate indexing, templates, and custom commands without needing a separate service. Administrative governance and RBAC controls are limited because content is primarily managed on a device or via external sync methods.
- +Markdown file data model keeps content portable and inspectable
- +Plugin API supports custom commands, views, and automations
- +Link graph and backlinks update from local indexing
- +Template and snippet workflows reduce repetitive writing setup
- –No built-in RBAC or org-level admin governance for teams
- –Audit logs and retention controls depend on external tooling
- –Automation uses plugins, so reliability varies by plugin quality
- –Cross-team collaboration needs separate sync or workspace processes
Best for: Fits when an individual or small group needs local-first writing with plugin-based automation and Markdown-compatible exports.
Scrivener
project writingProject-centric writing workspace with manuscript structure, research organization, and customizable templates that map directly to draft and revision states.
Project Binder with Compile targets maps structured manuscript sections into consistent export formats.
Scrivener focuses on document structure and authoring workflows instead of browser-first collaboration. Its core capability is a metadata-driven project binder that supports scenes, draft versions, and research material in one data model.
Export and formatting features map project sections into compile targets for print and eBook outputs. Automation and integration are limited to built-in workflows and platform-level extensibility rather than a governed API or RBAC layer.
- +Project binder keeps scenes, drafts, and research under one structured container
- +Metadata and targets drive consistent compilation across print and eBook outputs
- +Cross-platform desktop workflow supports long-form drafting with local file control
- +Extensibility via scripts and plugins supports tailored authoring automations
- –No documented enterprise API surface for provisioning or external system integration
- –Limited automation controls outside the app compared with integration-first writer platforms
- –Collaboration and governance features like RBAC and audit logs are not core strengths
- –Automation runs largely within desktop workflows, reducing deployment throughput
Best for: Fits when solo writers or small editorial workflows need a metadata-centered drafting workspace.
Roam Research
graph notesGraph-backed note system with database-like relationships, bidirectional linking, and automation via APIs and integrations for sustained writing iteration.
Block-level, bidirectional graph linking that turns writing into a traversable schema.
Roam Research combines a graph-based writing space with bidirectional links between notes, blocks, and pages. Its core workflow centers on capturing ideas as blocks, then building schemas through link structure rather than rigid forms.
The data model is accessible through export and structured note conventions, which supports downstream automation. Integration depth is strongest through extensible workflows that rely on consistent identifiers and block-level addressing.
- +Block-level graph model maps writing structure to relationships
- +Bidirectional links support navigation and knowledge refactoring
- +Exports enable migration and external processing pipelines
- +Extensibility through automation scripts and developer-facing surfaces
- –Schema enforcement is weak compared to database-backed writers
- –Automation depends on stable block addressing conventions
- –Granular admin controls are limited for multi-user governance
- –Audit logs and RBAC depth are not suited for strict compliance
Best for: Fits when writers need graph-driven linking and exportable data for automation, not rigid form workflows.
Notion
schema workspaceComposable workspace with relational databases, page templates, and an integration API that supports writing pipelines with schemas, permissions, and automation workflows.
API support for blocks and pages, combined with database properties, enables structured draft automation and repeatable review states.
Notion supports writer workflows through database-driven pages, inline comments, and granular access controls that map well to draft, review, and revision states. The data model centers on pages, properties, relations, and templates, which lets writing systems stay consistent across projects.
Notion automation and extensibility rely on a documented API plus webhooks via third-party connectors, which supports integration depth for content ops and publishing pipelines. Admin and governance controls include workspace settings, role-based access, and audit logging for key actions.
- +Database properties model outlines, status, and targets with reusable templates
- +Relations link research, drafts, and citations across large writing systems
- +API and rich block schema enable programmatic edits and retrieval
- +RBAC-based sharing supports per-page permissions and team collaboration
- –Automation depends on external services for complex multi-step workflows
- –Write throughput can slow when syncing large hierarchies via API
- –Schema changes across connected databases require careful migration planning
- –Governance controls are less granular than dedicated content governance tools
Best for: Fits when writers need database-backed status tracking with integrations that coordinate edits, review, and publishing.
Coda
automation docsDoc-and-table automation platform where writing is stored in tables and docs with formulas, roles, and an API surface for workflow integration.
Coda tables and relations inside docs let writing workflows use a controlled schema for automation and API updates.
Writers Block teams that need a structured, spreadsheet-like editor with automation lean on Coda for document-to-app modeling. Coda’s data model centers on tables, relations, and typed columns embedded inside docs, which supports editorial workflows with schema control.
The automation surface uses formulas and a growing set of integrations, plus a documented API for programmatic updates, webhooks, and sync patterns. Governance comes through workspace roles, permissions, and audit visibility for changes that affect collaboration.
- +Doc-first data model with tables, relations, and typed columns
- +API supports programmatic read and write for external workflow systems
- +Automation via formulas, scheduled updates, and integration triggers
- +RBAC-style permissions at workspace and document levels
- –Schema changes can require careful migration to avoid broken references
- –Automation logic can become hard to reason about across large docs
- –Audit and governance granularity may be insufficient for strict admin teams
- –Performance tuning is needed for high-throughput table operations
Best for: Fits when editorial and workflow teams need structured documents, schema control, and API-driven automation.
How to Choose the Right Writers Block Software
This buyer's guide covers nine writing-workflow tools that address writers block through structured prompts, conversation state, and schema-driven planning artifacts. It focuses on integration depth, data model control, automation and API surface, and admin governance across Wysa, Woebot, MindDoc, BreeZy, MindNode, Obsidian, Scrivener, Roam Research, Notion, and Coda.
Readers get concrete decision criteria tied to named mechanisms like API-driven state control in Wysa, clinician-configured constrained flows in Woebot, and database-driven draft states in Notion and table-driven schema in Coda.
Writers block workflow systems that store state, prompts, and revisions in a governed data model
Writers Block software turns ideation stalls into repeatable interventions by binding prompt logic to stored writing state, then writing that state back into a traceable format. These systems typically reduce dead ends by routing users through structured steps or by converting ideas into exportable planning artifacts like mind-map nodes and document views.
Wysa represents an automation-first approach where structured conversation data tracks progress and drives API-triggered interventions. Woebot represents a step-constrained conversational model where message flows are configured to constrain paths and keep outputs reviewable.
Evaluation checklist for integration depth, schema control, and governance-ready automation
Integration depth matters because writers block workflows rarely live in isolation. Teams need automation hooks that read state, call prompts or generation steps, and write results back into systems that track drafts and reviews.
Data model control and admin governance matter because the same prompt and revision logic must behave consistently across users. Tools like Wysa and Notion emphasize state and schema surfaces that support configuration, RBAC-style access boundaries, and audit visibility.
API-driven state and prompt orchestration
Wysa ties stateful prompt orchestration to a structured conversation schema exposed through an API and automation events. BreeZy pairs an API surface with configurable prompt and template workflows that map inputs to draft-generation outputs.
Conversation flow schemas that constrain execution paths
Woebot uses clinician-configured, state-driven conversation flows that constrain step paths to keep interventions consistent. This reduces free-form divergence compared with tools that rely mainly on exports or local plugin logic.
Typed data models for planning-to-draft continuity
MindDoc uses a node-based data model where linked mind-map nodes generate document views for planning-to-draft continuity. Notion uses database properties, relations, and templates so draft and review states remain consistent across pages.
Automation throughput with reviewable event outputs
Woebot emphasizes event output that supports downstream logging and operational reporting for steady throughput. Wysa also records governance-oriented event traces that make it easier to audit state transitions during interventions.
Admin governance controls for access boundaries and audit traceability
Wysa includes governance controls with RBAC-style boundaries and audit-oriented event records. Notion adds workspace and content activity audit logging plus role-based access that supports per-page permissions.
Extensibility mechanisms with integration breadth
BreeZy exposes a documented API and extensibility points aimed at automation pipelines. Obsidian relies on a plugin API for custom commands, views, and event-driven automation over a Markdown-backed link graph, which trades enterprise governance for local extensibility.
Pick the right writers block tool by matching workflow state, schema control, and governance needs
Start by defining where writers block state should live. If intervention steps must track progress across a conversation and drive automation calls, Wysa and Woebot are built around state schemas that support repeatable execution.
Next, map required integration and governance to the tool's data model. Notion and Coda treat writing as database-like structures with an API and permissions, while MindDoc and Roam Research prioritize exportable structured artifacts and graph or node continuity.
Choose the state model that matches the intervention style
For conversation-led interventions, select Wysa for stateful prompt orchestration tied to a structured conversation schema or Woebot for constrained, clinician-configured message flows. For planning-led interventions, select MindDoc for linked mind-map nodes that generate document views or Roam Research for block-level bidirectional graph linking that acts as a traversable schema.
Validate the automation and API surface needed for integration
For API-driven draft generation and automation mapping, select BreeZy or Wysa because both emphasize an API surface that drives generation and prompt workflows. For schema-driven edit and retrieval in a larger system, select Notion for blocks and pages via API plus webhooks through connectors or Coda for programmatic reads and writes using its API alongside formulas and triggers.
Confirm schema control and revision traceability requirements
If revision history and planning synchronization must be preserved, select MindDoc because it keeps node-based planning aligned with document views and revision history. If teams need explicit status tracking across large writing systems, select Notion for database properties, relations, and templates tied to draft and review states.
Check governance depth for multi-user operations
For RBAC-style boundaries plus audit-oriented traces for intervention state, select Wysa or Notion. If strict admin governance like compliance-grade RBAC and audit granularity is required, treat Obsidian, MindNode, and Scrivener as weaker fits because admin governance and audit log controls are not core strengths in those tools.
Decide whether low-friction local automation is enough or enterprise orchestration is required
If local-first authoring with plugin-based automation is the priority, select Obsidian because content remains in Markdown files with a plugin API over a link graph. If a deployment needs controlled throughput for repeatable pipelines, select Woebot for constrained message flows or BreeZy and Wysa for API-driven prompt and draft generation at scale.
Writers block tool fit by workflow intent, governance needs, and integration scope
Different writers block workflows require different state models and governance controls. Teams focused on automation and state tracking typically need tools like Wysa, Woebot, Notion, or Coda.
Individuals and small teams focused on structured ideation without heavy admin governance often prefer MindNode, Obsidian, Roam Research, or Scrivener.
Workflow automation teams that need API-driven state control
Wysa fits because it records writers block sessions as structured conversation data and orchestrates prompts through API and automation events. BreeZy also fits when generation cycles must be driven by configurable templates and API-driven draft generation.
Mental-health style interventions that must follow constrained conversational paths
Woebot fits because it uses clinician-configured, state-driven message flows with constrained step paths. This structure supports consistent intervention execution and reviewable outputs under steady traffic.
Editorial and operations teams that want database-backed draft and review states
Notion fits because database properties, relations, and templates enable repeatable review states across pages and support API-based programmatic edits. Coda fits when the team wants doc-and-table modeling with typed columns and an API for workflow integration.
Writers who need planning-to-draft continuity through structured artifacts
MindDoc fits because linked mind-map nodes generate document views and keep planning synchronized with revision history. MindNode fits when the goal is mind map to outline export that preserves branching structure with minimal automation needs.
Solo writers who prioritize local-first notes and plugin automation
Obsidian fits because its Markdown file data model and plugin API support custom commands and event-driven automation over a local link graph. Scrivener fits when long-form drafting needs a project binder with metadata and compile targets rather than API-driven orchestration.
Pitfalls that break writers block workflows when state, schema, or governance are mismatched
Most failures come from choosing a tool whose data model and automation surface cannot carry the intervention logic across users. Another common failure comes from underestimating how governance and audit visibility interact with multi-user workflows.
Tools that prioritize local authoring or export formats can still help, but they often do not provide the same RBAC and audit depth needed for operational delivery.
Assuming export-only mind maps can replace schema-driven state control
MindNode and Scrivener can preserve structure through exports and compile targets, but they do not prioritize API-driven state orchestration or constrained step execution. Wysa and Woebot handle state and step routing as first-class inputs to automation.
Under-scoping governance for multi-user intervention histories
Tools like Obsidian and Roam Research emphasize local graphs and exports, so RBAC-style admin governance and audit log depth are not core strengths. Wysa and Notion provide RBAC-oriented boundaries and audit visibility for key actions and state transitions.
Building multi-step pipelines on constrained workflow graphs without checking extensibility limits
Woebot constrains paths for consistent messaging, so extensibility beyond its structured flows is narrower than tools with broader workflow graphs. BreeZy and Wysa provide more room for configurable prompt and template workflows tied to stored state.
Treating schema changes as harmless when typed structures and relations drive automation
Coda and Notion rely on schema-like structures through typed columns or database properties and relations. Schema changes can require careful migration planning or broken references, so workflows should be validated for migrations before broad rollout.
How We Selected and Ranked These Tools
We evaluated writers block tools by scoring features, ease of use, and value using concrete capability signals tied to each product’s stated mechanisms. Features carried the most weight, while ease of use and value each contributed a smaller share, and the overall rating reflects that weighting across the set. We used criteria like API and automation surface coverage, whether the product’s data model exposes state in a usable schema, and whether admin and governance controls provide traceability and access boundaries for multi-user operation.
Wysa separated from lower-ranked options because it combines stateful prompt orchestration with a structured conversation schema exposed through an API and automation events. That combination most directly improved features scoring and operational integration control by making intervention steps and progress inspectable and routable as stored state.
Frequently Asked Questions About Writers Block Software
Which Writers Block tools expose an API or workflow automation surface for stateful conversation control?
How do Woebot and Wysa differ in their underlying data model for writing support workflows?
What tool types fit teams that need governed collaboration with an audit log and role-based access controls?
Which tools support data migration most directly because their core data model is already structured?
What is the tradeoff between graph-based tools like Roam Research and structured form tools like Woebot?
Which option best supports mind-map to document workflows without losing structural context?
When teams need RBAC-aligned integrations for editor workflows, which tools are most consistent?
Which tool supports local-first writing automation and what limitation comes with that approach?
Which common failure mode occurs when exports or identifiers are inconsistent, and which tools reduce it?
Which tool fits a scenario where the writing workflow is driven by spreadsheet-like tables and typed schemas?
Conclusion
After evaluating 10 mental health psychology, Wysa stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Mental Health Psychology alternatives
See side-by-side comparisons of mental health psychology tools and pick the right one for your stack.
Compare mental health psychology tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.