The roadmap is curated, not crowdsourced. Customer audits, support patterns, and operator hours weigh heaviest. Items can ship earlier than estimated, slip a quarter, or move down for capacity reasons. We update this page as work moves between columns.
Drag deals across stages with amounts, close dates, and next steps. Per-column counts and totals show what is real and what is stuck without rebuilding a report.
A focused workspace for working leads visually with status filters and a side-by-side detail panel. Capture interest, assign owners, qualify, and convert without touching a list view.
Per-stage layouts, required fields, success criteria, checklists, and stage-scoped quick actions on a path bar across the top of the record. New reps follow the play; veterans move faster with guardrails.
Admin-published one-click record actions, available globally and per-stage on the path bar. Compress repeated work into shortcuts your team uses every day.
Tailored apps with their own navigation items, pages, default landing, and per-app record layouts. Same org, separate experience for sales, support, and ops.
Compose record pages from built-in components — record header, field form, related list, activity timeline, comments, attachments, approval actions, email thread, data table, metric cards, rich text, checklists — plus tenant-authored custom components.
Sequenced approval chains with entry conditions, approver types (user, role, manager, queue), unanimous flags, lock-on-submit, recall permissions, and final or step-level actions. Manager sign-off before quotes leave the building.
Tenant-authored JavaScript that runs on BEFORE_* and AFTER_* record events, sandboxed in V8 isolates with org-scoped SDK access, governor limits, and per-org concurrency caps.
Reusable server-side modules callable as sdk.modules.<name>() from triggers, jobs, and endpoints. Org-scoped resolution keeps tenants isolated.
Tenant-defined HTTP routes mounted at /api/{orgSlug}/*. Membership-bound, code-defined, and gated by the same org-scoped SDK as triggers and jobs.
Cron-driven background jobs in per-org BullMQ queues. A misbehaving job can only saturate its own queue — never another tenant’s.
Author component bundles in-browser with an SFC compiler, served per-org from a stable bundle URL. Drop them onto record pages from the page builder.
Define objects with API names, custom fields, lookup, and master-detail relationships. On deploy, RidgeCRM creates a real Postgres table with FK indexes — reportable, queryable, and first-class to the API.
In-app hub for triggers, classes, endpoints, jobs, and components, with a recent-runs panel. Every isolate run is captured with surface, reference id, status, error message, and duration.
A support-oriented workspace for cases, tied to the same accounts your sales team uses. Post-sale work starts with context.
Structured proposals from a product catalog with totals, tax, and discount. Status flows draft → in review → approved → presented → accepted, linked to opportunities so quoting stays inside the deal.
Every call, email, task, comment, and status change on a record in one chronological feed. Walk into any conversation with full context.
A unified call and email feed across an account, contact, or lead. Stop hunting through two systems to reconstruct what was said.
Trello-style kanban project boards for ad-hoc and cross-functional work, parallel to the opportunity pipeline. Members, columns, tasks, and per-task activity.
Per-record uploads to S3-compatible storage, scoped per organization, surfaced as a related component on record pages. Contracts, screenshots, and call notes live with the record.
Send from inside a record, threaded inbox view, inbound webhook ingestion, open and click tracking pixels, and tracking-link rewriting. The full email loop without leaving the CRM.
A bottom-right phone panel powered by Twilio: dial pad, inbound and outbound states, call timer, mute, hold, hang up, and call disposition logging tied back to the record.
Fifteen field types including formula, validation rules with And/Or/Not DSL, page layouts, and record types. Model your industry without filing a vendor ticket.
Export any list view or report run to CSV for offline analysis or migration. Mapped CSV import is partially shipped via the API; the polished file-upload and field-mapping UI is queued for the import column.
Tabular, summary, and matrix reports with filters, grouping, charts, date presets, and CSV export. Reports run over standard objects and deployed custom objects. Dashboards composed from report-backed widgets via a builder UI.
Org-scoped API with JWT bearer auth covering CRM CRUD, approvals, attachments, list views, reports, email send and tracking, telephony, custom objects, and platform triggers.
Automation rules can call external URLs on record events alongside update field, create record, send email, and send notification actions. Integrate RidgeCRM into your existing stack over HTTP.
Filterable activity log with action, object, user, and date filters; per-entry view of old and new values, IP, and user agent. The data layer for field history already lives here.
Role-based access with per-profile object and field permissions. Sales sees pipeline, support sees cases, finance sees quotes — you decide field-by-field.
Reusable message library tied to merge fields and activity context, organized by category. Reps follow up consistently without rewriting the same email.
Cross-object search across accounts, contacts, leads, opportunities, and cases ranked by relevance. Quick-navigate to the record you need without rebuilding a list view.
Saved filters, column choices, sorting, inline cell editing, and bulk delete, owner change, or field updates. Scope to org or mine, set defaults, and pin views your team uses every day.
Convert a qualified lead into an account, contact, and opportunity in one flow. Linkbacks captured on the lead so the conversion trail stays visible.
An isolated org clone for developing and testing changes — triggers, layouts, automations, custom objects — before promoting to production. No separate sandbox exists today; this is the next big platform piece.
The internal calendar at /app/tasks/calendar ships today. Two-way sync with Google Calendar and Microsoft 365 is in flight so CRM events stay aligned with the calendars your team already lives in.
Subscribe individuals or groups to saved reports. Daily, weekly, or monthly snapshots delivered before the meeting starts — reports and dashboards already exist; recurring delivery is what is queued.
Weighted close-date rollups by owner, team, and segment. The forecastCategory field is on the opportunity model today; the rollup view is what is being built.
iOS and Android with offline cache for accounts, contacts, tasks, and pipeline. Field reps can keep working without signal.
Draft follow-up emails, summarize record activity, and suggest next steps inline. Grounded on your records, not a generic LLM guess.
In-product proposal signing without bouncing into another tool. Status flows back to the opportunity automatically.
The inbound email webhook stores messages today; auto-creating cases, matching to existing accounts, and routing to the right queue is what is queued. Fewer tickets get lost in shared inboxes.
Response and resolution timers per case priority. Visible countdowns and breach alerts so commitments do not slip quietly.
A per-record field-history tab. Underlying old/new value capture is already in the audit log today; this exposes it inline on the record page so close-date debates settle with evidence instead of memory.
Issue tokens with granular object and field permissions. Give integrations only the access they need — nothing more.
Ship repeated implementation patterns as reusable packages instead of one-off custom work. Versioned, installable, and auditable.
A scoped portal where end customers can submit cases, view status, and access invoices. Read-only first, then progressive trust.
Lists, sends, and attribution back to opportunities. We are deciding how deep to go before this overlaps existing marketing automation tools.
A Twilio-based CTI panel ships today with dial pad, dispositions, and call logging. “Native” here means first-party recording, transcription, and softphone ownership. Likely a partner integration before native ownership.
Geographic and account-rule routing for inbound leads and ownership. Only worth building if customers are running multi-territory teams.
Org-level base currency with per-deal currency and rate snapshots. Forecasting in one number even when you sell in many.
Conversational support inside the CRM with case fallback. Open question is whether this should be a partner or a first-party surface.
First-class connectors for Power BI, Tableau, and Looker so analysts can model RidgeCRM data alongside billing and product warehouses.
Tell us what your team keeps working around. The audits and improvement queues from real customers are the strongest signal we have for what to build next — and the fastest way onto the roadmap.
Managed CRM for growing B2B service businesses.