Sales Pipeline
Know where each lead stands
See which leads are moving, read the last conversation before you follow up, and send the proposal from the lead's page.
Add your first leadFree account, no card needed.
SALES PIPELINE
Follow each lead from the first request to the proposal
Someone asks for a quote. You need to know what you discussed and what comes next.
Add each lead, note what you discussed and move the lead through your sales stages.
-
Make the stages yours
Name and order the stages of each pipeline. Choose what your team must record before a lead moves to the next stage.
-
Work the board
Each lead is a card. Drag it to the next stage and order the cards within a stage. When a teammate moves a card, your open board shows the move too.
-
Keep the details together
Open a lead to see its project, its activity, its proposals and the tasks linked to it.
A CLEAR NEXT STEP
Decide what your team records before a lead moves on
Moving a lead to the next stage can ask for a note, a result or a report form. Report forms need the Reports pack. Each kind of sale keeps its own stages.
-
Separate pipelines
Keep a pipeline for each kind of sale instead of one board for everything.
-
Record what changed
The move and what your team wrote with it stay in the lead's history.
From the first request to the proposal
-
Add the lead
Add a lead by hand, from a CSV file or, with the Helpdesk pack, from a conversation. Requests from the price calculator on your website arrive as leads, each with a proposal, once you choose the stage they land in.
-
Choose the pipeline
Put the lead on the pipeline for that kind of sale, and move it through the stages that apply.
-
Keep the record
Log calls, meetings and outcomes. Download a PDF brief of the lead before your next meeting.
-
Send the proposal
Write a proposal for the lead, or check the one the price calculator made, and send it from the lead’s page. When you make the lead a client, you continue from the accepted proposal to the contract and invoices without typing the deal again.
DUPLICATE REVIEW
Compare duplicate leads before you merge them
Enlivy lists possible duplicates, with what matches and how likely a match is. You compare the two leads, choose the one to keep and pick which details stay. The lead you keep takes over the activity and proposals of both. Some conflicts block a merge, and a merge cannot be undone.
-
Review before merging
Enlivy ranks the likely duplicates. A person decides whether to merge them.
-
Keep the sales history
Activity and proposals move to the lead you keep.
A BRIEF FOR THE NEXT MEETING
Take a PDF brief of the lead to your next meeting
Download the brief from the lead's menu, in the list or on its card. It shows the stage, pipeline, source, budget, owner, summary and activity, with your branding. Enlivy makes the PDF when you download it, so download it again after the lead changes.
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.
/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.
/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.
/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.
/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.
/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.
/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.
/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
Part of these setups
Each page follows one way of selling and shows what your client does, which features you use and what they cost.
- Sales teams Core A pipeline for each way you sell, with your own stages. You review possible duplicate leads before you merge them. See the setup
- Agencies and studios Optional Adds a pipeline for new leads from your price calculator, with your own stages and a brief for each call. See the setup
- Course authors Optional Adds a pipeline for leads from DMs, forms and webinars, shared with your team. See the setup
Works together with
- Products Build a reusable catalog of everything you sell, services or goods, with pricing, units, tax settings, and descriptions set once. Every product is ready to add to a proposal or invoice.
- Proposals Put the work, the price and the payment terms in one proposal. Your client accepts it from the email, and the contract and first invoice use the same price.
- Helpdesk Website chat, client portal messages and email from your connected mailbox arrive in shared inboxes. Your team assigns and answers them, and reviews email from unknown senders.
- Tasks Keep your team's work beside the invoices, leads and projects it concerns. Tasks are included for every organization at no extra charge, with no limit on the number of tasks.
- Data Export Choose the period and the record types, and download one archive for your accountant, with a summary spreadsheet for each type if you want one. Free on every plan.
- MCP Connect Claude, ChatGPT, Cursor, or another MCP-compatible assistant to work with your invoices, contracts, and pipeline, within your own permissions.