Knowledge Base

Every user-facing release in DealJourney, in plain English. Dates are the day the release went out.

The essentials for a brand-new workspace: set up your company profile, invite the team, learn the dashboard, shape your pipeline, and bring your data across.

Opportunities are how DealJourney tracks every potential deal: the money, the people, the timeline, and the full history of every interaction from first conversation to signed contract.

Leads capture early interest before you know there's a real deal. Keeping them in their own funnel, rather than mixed into the pipeline, gives you a clean top-of-funnel view and prevents your forecast from being polluted by speculative demand.

Contacts are the people you sell to. Customers are the organisations they belong to. Every email, call, meeting, and note lives on a timeline attached to both, so the full relationship history is always one click away.

Recurring revenue is a first-class concept in DealJourney. Subscriptions drive MRR, ARR, churn, and retention reports. Invoices, whether generated natively or mirrored from a connected accounting system, close the loop between a won deal and the money arriving.

Tickets handle customer support, onboarding requests, and any other tracked conversation. Every ticket is linked to the customer and contact it's about, so whoever replies has the full history in context.

DealJourney ships with built-in report suites for sales, revenue, customers, activity, and marketing (when enabled), plus Explore and custom reports. A shared header controls period, comparison, user scope, currency, and exports, so every tab speaks the same language.

DealJourney's workflow engine runs on the classic trigger, condition, action model. Every run is logged, so you can debug a misbehaving rule and prove the ones you care about are firing.

DealJourney connects to the accounting, email, calendar, and communication tools your team already uses, and exposes a full public REST API plus webhooks for everything else.

Tenant admins shape the workspace for the rest of the team: who sees what, which fields exist, how pages are arranged, and what changes are recorded. The audit trail captures every material change server-side.