Sales Pipeline

Know Where Each Sales Opportunity Stands

Free for 5 in total Unlimited with Sales €19.99/month

See which opportunities are moving forward, review the conversation before you follow up and keep proposals close to the deal.

Add your first prospect

Free account, no card needed.

A Prospect card's menu listing the stages it can move to

SALES PIPELINE

Pick up the next conversation with context

A client asks for a quote. You need to know what happens next.

Record the opportunity, keep track of what you discussed and move it through the stages of your sale. When different kinds of work follow different steps, give each its own board.

Make the stages yours

Name and order stages for each pipeline, and set what the team must record when it advances a Prospect along each path.
Work the board

See Prospects as cards, drag them between stages and keep their order clear within a stage.
Keep the details together

The Prospect stays connected to its project, activity and the proposals and billing work that follow.

A CLEAR NEXT STEP

Agree on what the team needs before moving a deal

Advancing a Prospect along a path can ask for a note, a result or a report filed from one of your report forms (a Reports pack feature). The team records what happened before the deal moves on, while each sales process keeps its own paths.

Separate processes

Keep a different path for each kind of sale instead of forcing every opportunity onto one board.
Record what changed

The move and the information supplied with it become part of the Prospect's history.

From interest to the work you sell

Capture the opportunity

Add a Prospect by hand, from a helpdesk conversation or from a request through your Enlivy price calculator, with its source and project. Set an intake stage first so requests land on the board.
Choose the right pipeline

Work it on the board that matches the sales process and move through the stages that apply.
Keep the record

Log calls, meetings and outcomes. Download a current Prospect brief when you need a portable view of the deal.
Continue after the win

Use connected proposal and billing records rather than copying the opportunity into another tool.

DUPLICATE REVIEW

Compare possible duplicates before combining them

Possible duplicates appear with match signals and a confidence level for your team to review. Compare the records, choose the Prospect to keep and decide which fields survive. The merged record keeps the connected activity and proposals. Some conflicting identities, projects or won and lost outcomes block the merge; a completed merge cannot be undone.

Review before merging

Candidate ranking helps you find overlap, while a person makes the final decision.
Keep the commercial history

Related activities and proposals move with the record that is absorbed.

PORTABLE DEAL CONTEXT

Take a current Prospect brief into the next conversation

Download the Prospect brief from its action menu when you need a portable summary. Check the current record before sharing the file outside your workspace.

API Reference

Prospect Management from the API

Wire your lead capture, CRM, and sales automation straight into Enlivy. The Prospects API lets you work with your sales pipelines: create leads from any source, move them through configured stages, and log each touchpoint.

The examples below cover listing and filtering Prospects, creating a lead, moving it through configured stages, and recording activities such as calls and meetings. The API also exposes boards, duplicate review and merge, and a downloadable brief.

Pull your pipeline into any dashboard or sync job. Query prospects with pagination, filter by stage, owner, source, or date range, and full-text search by name, company, or email. Expand related records such as the current stage and the assigned team member.

GET/organizations/<organization_id>/prospects

curl -G 'https://api.enlivy.com/organizations/<organization_id>/prospects' \
  --data-urlencode 'page=1' \
  --data-urlencode 'limit=20' \
  --data-urlencode 'source_type=inbound' \
  --data-urlencode 'include=organization_prospect_stage,assigned_organization_user' \
  --data-urlencode 'include_meta=navigation' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";

const query = new URLSearchParams({
  page: "1",
  limit: "20",
  source_type: "inbound",
  include: "organization_prospect_stage,assigned_organization_user",
  include_meta: "navigation",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospects?${query}`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
  },
}).then((response) => response.json());

Retrieve a single prospect with everything attached to it: contact details, source attribution, budget, current pipeline stage, and lifecycle timestamps such as qualified, won, and lost.

GET/organizations/<organization_id>/prospects/<prospect_id>

curl -G 'https://api.enlivy.com/organizations/<organization_id>/prospects/<prospect_id>' \
  --data-urlencode 'include=organization_prospect_stage,assigned_organization_user' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const prospectId = "<prospect_id>";

const query = new URLSearchParams({
  include: "organization_prospect_stage,assigned_organization_user",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospects/${prospectId}?${query}`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
  },
}).then((response) => response.json());

Capture a lead from any source: a landing page, an ad campaign, an outbound list, or your own app. Send a person, a company, or both, tag where it came from, and drop it straight onto your pipeline.

POST/organizations/<organization_id>/prospects

curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/prospects' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "first_name": "Jane",
  "last_name": "Doe",
  "company_name": "Acme Studio",
  "email": "jane@acme.example",
  "source_type": "inbound",
  "source_channel": "website",
  "source_campaign": "summer-launch",
  "summary": "Requested a demo from the pricing page.",
  "budget": "5000",
  "budget_currency": "EUR"
}'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";

const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospects`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    first_name: "Jane",
    last_name: "Doe",
    company_name: "Acme Studio",
    email: "jane@acme.example",
    source_type: "inbound",
    source_channel: "website",
    source_campaign: "summer-launch",
    summary: "Requested a demo from the pricing page.",
    budget: "5000",
    budget_currency: "EUR",
  }),
}).then((response) => response.json());

Update a prospect’s contact details, owner, budget, summary, or lifecycle state (qualified, disqualified, won, lost). You only send the fields you want to change.

PUT/organizations/<organization_id>/prospects/<prospect_id>

curl -X PUT 'https://api.enlivy.com/organizations/<organization_id>/prospects/<prospect_id>' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "summary": "Budget confirmed, decision expected next week.",
  "budget": "8000",
  "budget_currency": "EUR"
}'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const prospectId = "<prospect_id>";

const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospects/${prospectId}`, {
  method: "PUT",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    summary: "Budget confirmed, decision expected next week.",
    budget: "8000",
    budget_currency: "EUR",
  }),
}).then((response) => response.json());

Move a prospect along a configured stage path. Each advance records who performed it and can include an outcome, note, and linked report. The advance also appears on the prospect timeline.

POST/organizations/<organization_id>/prospects/<prospect_id>/advance

curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/prospects/<prospect_id>/advance' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "organization_prospect_stage_path_id": "stage_path_id_here",
  "outcome": "Qualified, budget and timeline confirmed.",
  "description": "Moved from New to Qualified after the discovery call."
}'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const prospectId = "<prospect_id>";

const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospects/${prospectId}/advance`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    organization_prospect_stage_path_id: "stage_path_id_here",
    outcome: "Qualified, budget and timeline confirmed.",
    description: "Moved from New to Qualified after the discovery call.",
  }),
}).then((response) => response.json());

Record a touchpoint on a prospect: a call, a meeting, an email, a note. Activities build the prospect’s timeline and give your team a shared, chronological history of every interaction.

POST/organizations/<organization_id>/prospect-activities

curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/prospect-activities' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "organization_prospect_id": "prospect_id_here",
  "title": "Discovery call",
  "description": "Walked through pricing and the onboarding timeline.",
  "outcome": "Positive, sending a proposal next week.",
  "activity_at": "2026-07-03 15:30:00"
}'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";

const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospect-activities`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    organization_prospect_id: "prospect_id_here",
    title: "Discovery call",
    description: "Walked through pricing and the onboarding timeline.",
    outcome: "Positive, sending a proposal next week.",
    activity_at: "2026-07-03 15:30:00",
  }),
}).then((response) => response.json());

Read the activity feed across your organization. Expand each entry with the Prospect it belongs to, the team member who performed it, and any linked report or stage transition.

GET/organizations/<organization_id>/prospect-activities

curl -G 'https://api.enlivy.com/organizations/<organization_id>/prospect-activities' \
  --data-urlencode 'page=1' \
  --data-urlencode 'limit=20' \
  --data-urlencode 'include=organization_prospect,performed_by_organization_user' \
  --data-urlencode 'include_meta=navigation' \
  -H "Authorization: Bearer $ENLIVY_API_TOKEN" \
  -H 'Accept: application/json'

const baseUrl = "https://api.enlivy.com";
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";

const query = new URLSearchParams({
  page: "1",
  limit: "20",
  include: "organization_prospect,performed_by_organization_user",
  include_meta: "navigation",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/prospect-activities?${query}`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`,
    Accept: "application/json",
  },
}).then((response) => response.json());

Where it fits

Know Where Each Sales Opportunity Stands

Pick up the next conversation with context

Agree on what the team needs before moving a deal

From interest to the work you sell

Capture the opportunity

Choose the right pipeline

Keep the record

Continue after the win

Compare possible duplicates before combining them

Take a current Prospect brief into the next conversation

Prospect Management from the API

Part of these setups

Works together with

Start with the part you need.