Product roadmap

In the product today, on every plan except where noted. The WooCommerce and ecommerce suite is included from Pro upwards.

• Core CRM

  Contacts and companies with unlimited custom fields, notes, activity history and full-text search.

• Multi-pipeline Kanban

  Unlimited pipelines with drag-and-drop stages, per-stage win probability and deal ownership.

• Weighted forecasting

  Forecast totals derived from deal value times stage probability, so a pipeline number means something.

• Lead scoring

  Configurable scoring on captured leads so the inbound queue sorts itself before anyone looks at it.

• Round-robin routing

  New leads assigned to an owner automatically rather than waiting for a manager to distribute them.

• Quotes and invoices

  Line items, tax handling, your own numbering scheme, branded PDF export and multiple partial payments per invoice.

• Per-user team email

  Own IMAP and SMTP credentials per user, from-name and HTML signature, templates with merge placeholders, sent log against the contact.

• Calendar and follow-ups

  Follow-up tasks with sub-tasks and overdue surfacing, plus a per-user ICS feed for Google, Outlook or Apple Calendar.

• Automations

  Trigger-and-action recipes on CRM events that create follow-ups, send notifications or fire outbound webhooks.

• Audit log

  A record of who changed what and when, across records and settings.

• CSV and GDPR export

  CSV import and export for contacts, companies and deals, plus a per-contact GDPR export for subject access requests.

• Webhooks

  Register a URL per event to push CRM activity into anything that accepts an HTTP request.

• Read-only JSON API

  Token-authenticated GET endpoints for deals, contacts and companies, for dashboards and BI tools.

• Lead and order intake endpoints

  Token-protected POST endpoints, plus a PHP helper, for capturing leads and orders from any form or storefront.

• WooCommerce order sync

  Idempotent sync on checkout, status change, admin edit and refund, with orders becoming both ledger records and deals, and RFM segments per customer.

• Store dashboard

  Paid revenue, average order value, repeat-purchase rate, refunds, twelve months of revenue history and top products.

• Win-back and checkout recovery

  A daily scan that raises tasks for lapsed customers and unpaid checkouts.

• 35+ currencies and role-based access

  Per-deal currency selection, and access gated by the manage_stillpoint_crm capability with an admin and agent split.

• FluentCRM bridge

  Two-way contact sync with FluentCRM, tags applied on deal won/lost and RFM segment changes, and engagement synced back onto the CRM contact. Works alongside FluentCRM, not instead of it.

• Marketing automation

  Segments, multi-step journeys and campaigns with consent tracking, a suppression list, one-click unsubscribe and a preference centre, sending through SendGrid, Mailgun, Postmark, Amazon SES, capped direct SMTP, or a FluentCRM handoff.

• Reporting and analytics engine

  A report builder, 17 built-in templates, targets, drill-down from summary to record, stage-history tracking and business-mode presets that adapt reporting to how the account is used.

• Work management

  Workspaces, boards and items; projects, templates and dependencies; milestones and a timeline view; recurring items, approvals, time tracking and workload; and public forms that create work items.

• Cross-module automation

  Automations that react across CRM, work and marketing events, with idempotency keys so a retried or duplicate trigger cannot fire the same action twice.

• Service desk — tickets and email piping

  Support tickets created from a shared mailbox over IMAP, Gmail or Microsoft 365 OAuth, or provider inbound webhooks, with threading and database-enforced duplicate protection.

• Service desk — SLA engine and routing

  Response and resolution SLA timers per priority, with breach flags, and rules that route new tickets to the right agent or team.

• Service desk — customer portal and knowledge base

  A branded portal where customers see and reply to their own tickets, plus a searchable knowledge base to deflect repeat questions.

• Service desk — CSAT, incidents and reporting

  Post-resolution satisfaction ratings, incident tracking for wider outages, and service reporting alongside the rest of the reporting engine.

Committed direction, no dates. Each of these is written to be specific about the limitation it removes, because the honest version of a roadmap is a list of things the product cannot do yet.

• Write API

  Create and update contacts, deals, work items and orders over the API. Today the JSON API is read-only and writes must arrive through the intake endpoints; this is what unlocks genuinely two-way integrations, and it is why it sits first.

• Native Zapier and Make app

  A listed app with triggers and actions rather than the generic webhook and HTTP-request pattern that works today. More useful once the write API has landed.

• Multi-store consolidation

  A hub-and-satellite mode so several WooCommerce stores report into one Stillpoint install, with a store identifier on orders and contacts and per-store filtering throughout. Today each licence activation is an independent CRM.

• Consolidated multi-currency reporting

  Convert deal and order values to a base currency, with FX handling, so pipeline, forecast and revenue totals are meaningful across mixed-currency records. Today each record carries its own currency and totals are not converted.

• Full MySQL driver

  Complete MySQL and MariaDB support with a driver picker in settings, for teams whose data outgrows the default SQLite file.

• Granular teams and territories

  Finer-grained permissions beyond today's admin and agent split, so larger organisations can model teams and territories rather than a flat list of agents.

• Guest and client portal access

  A scoped, read-limited view so a client or contractor could see the status of their own work items without full CRM access. There is no portal today.

• Dashboard builder with saved layouts

  Arrange report widgets into a saved, personal dashboard rather than viewing report templates one at a time.

• Scheduled report delivery

  Email a report on a schedule rather than opening it manually. Depends on the send-adapter work already shipped for marketing.

• XLSX and PDF export for reports

  Export a report to a spreadsheet or PDF rather than reading it on screen or pulling it through the JSON API.

• Calendar view for work

  A calendar surface over work items with due dates, alongside the existing board and timeline views.

• Returns, distinct from refunds

  A returns record distinct from a WooCommerce refund, so a physical return and a financial refund can be tracked and reported on separately.

Everything under “Planned” here is genuinely not built, and nothing in the product claims otherwise. What is already shipped — tickets, routing, the customer portal and knowledge base, email piping and the SLA engine — is listed in “Shipped” above, alongside CSAT, incidents and service reporting. This group is only the gap between what the service desk does today and what it does not do yet.

• Live chat

  A widget-based live chat channel into the service desk. Nothing exists today; tickets currently arrive by email or the customer portal.

• WhatsApp

  Planned via an authorised WhatsApp Business API provider, not an unofficial or scraped integration. Not built yet.

• SMS

  Planned as a ticket channel through an SMS gateway provider. Not built yet.

• Voice / call logging

  Planned so a phone call can be logged against a ticket. There is no call handling or logging in the product today.

• AI assistance for agents

  Planned: ticket summaries, draft-reply suggestions and classification, with a human always reviewing and sending. Stillpoint has no AI features today, and none of this is being built to send a reply unsupervised.

• Importers for SupportCandy, Zendesk and Freshdesk

  Planned data importers so a migration does not mean re-keying every historical ticket by hand. Not built yet.

• Business-hours response-time medians

  Planned reporting refinement so a response-time median can be calculated against configured business hours rather than the raw clock. Today's reporting uses wall-clock time.

• Support cost per ticket

  Planned once a cost input exists to calculate against — for example agent hourly cost. There is currently no cost figure to attach to a ticket, so this cannot be reported yet.

• One-click erase / anonymise, including message bodies

  Planned workflow to erase or anonymise a requester's data in one action, including redacting message bodies in historical tickets. Today's GDPR export is per-contact but there is no one-click erase covering ticket message content.

Things we are investigating. These may change shape substantially or never ship at all, and none of them should influence a purchase decision.

• MCP server for AI assistants

  We are investigating an MCP server so assistants could query and update the CRM directly. Nothing exists today, and it depends on the write API landing first.

• Cohort analysis

  We are investigating cohort-style reporting — grouping customers or deals by start period and comparing behaviour over time — as an extension of the reporting engine, not a promise of a delivery date.

• Anomaly detection

  We are looking into flagging unusual movements in reporting metrics automatically. This is early-stage thinking, not a committed feature.

• Critical path for projects

  We are investigating whether a critical-path view on top of dependencies and milestones is worth the complexity it adds to work management.

• Real-time collaborative updates

  We are exploring live, multi-user updates on boards and items. Today changes save and refresh normally rather than streaming between open sessions in real time.

• Gantt drag-to-resize

  We are investigating direct drag-and-resize editing on the project timeline view. Today the timeline is a read view of dates set on the item; it is not yet an editing surface.

• Inventory analytics

  We are looking into stock-level and inventory reporting drawn from WooCommerce. Nothing exists today, and it is a distinct effort from the order and revenue reporting that is already shipped.

• Guest and client portal, deeper access

  Beyond the scoped read-only access under investigation in Next, we are exploring what a fuller client-facing portal would need before it could be trusted with real client interaction.

• Two-factor authentication and SSO

  Under investigation for larger teams. Today access rides on the WordPress login, so site-level 2FA plugins already cover part of this.