Skip to content
Docs menu

Venom Funnel

A sales pipeline on top of Venom People. Move deals through stages on a board, link the people involved with their context cards, track products, goals and the weighted forecast, and let agents do the same over MCP.

View .md

Venom Funnel is the pipeline for deals, at /funnel. It is built on Venom People: the people on a deal are People, the company is a People company, and what you do on a deal lands on your own people as interactions. g d opens it from any app, and ⌘K finds deals by title, company or the people on them (type deals:).

It is a port of the open-source Funnel CRM onto Venom's organisation, members, Tasks and bell, with Funnel's tested report maths unchanged. Every member of an organisation has it, and every role can change deals today, billing and viewer included. Agents use it through the workspace MCP server and REST API.

The board

Each stage of the pipeline is a column with its deal count, value and weighted value (value × the stage's probability). Cards show the title, value, company, the people on the deal, how long it has sat in the stage and the expected close. A card gets a warning mark once it has been in an open stage longer than the stage's stale after days.

When a person on the deal is one of your own People contacts, the card and the list row show their seniority mark, warmth dot and country, as in the People list; a colleague's contact shows none of these. n now · m ever next to the company is how many people you can see in People there now, and how many ever (alumni included); it opens /people?company=… with exactly the "ever" count, and Only where they work now there shows the "now" count. The deal's page shows the same link under its company.

  • Drag a card to another stage, or within a stage to reorder. Dropping it into a lost stage asks why (optional).
  • Keyboard: arrows move between cards, Shift + arrows (or H J K L with Shift) move the card, W marks it won, X lost, Enter opens it, C makes a new deal, / searches, V switches between board and list.
  • A deal's status follows its stage: entering a won or lost stage closes it (with a close date), entering an open stage reopens it. Every stage entry, including creation, is kept in the deal's history.
  • Each deal has its own page at /funnel/deals/<id>, with its people, products, activities and history.

A card also shows one short line of your own, when there is one: your intro ask on the deal ("Intro asked (Priya, 3d)", "Intro agreed (Priya)", "Intro drafted (Priya)"; the most advanced open one) and your next calendar meeting with someone on it. Nobody else sees that line on your board.

The list shows the same deals in a table. Filter by owner, status, Intro asks (My open intro ask: deals with a draft, asked or agreed ask of yours) and a select-type custom field, and save the current filters as a view, personal or shared with the organisation.

On a phone

On a screen narrower than 640px the board shows one stage at a time. A row of stage tabs at the top gives each stage's name, deal count and value; it stays in view while you scroll, and the tab you pick is kept in the address, so going back from a deal returns to the same stage. To move a deal, tap ⋯ on its card and pick the stage (Won and Lost included; Lost still asks why). There is no dragging on a phone.

The filters fold behind the Filters button (it shows how many are on), the search box takes the full width, and + makes a new deal. The list shows one row per deal (title and value, then stage, company and last change) instead of the table. On a deal's page the stages scroll sideways in one row, with Won and Lost below them.

Create a deal from a person or a company

On a person's or a company's page in People, Create deal opens the new-deal dialog with the person linked and the company filled in. Both pages list that person's or company's deals.

To create many at once, pick people in the People list or in Reach and choose Add to pipeline. It takes only your own people; a colleague's contact shared with you is skipped and the message says so. You get one deal per person ("Grab — Ana") or one per company holding everyone picked there ("Grab — Ana and 2 more"), in the pipeline and open stage you pick. Create a consulting pipeline makes one with the stages Target, Reached out, In conversation, Proposal, Won and Lost. People who already have an open deal in that pipeline are skipped, and in per-company mode a company's open deal takes the new people in. Seen by starts at your team when you are in one; the title names the person, so everyone who can see the deal sees that name. Undo archives the deals it created and takes the people it added off an existing company deal, leaving everyone else on it.

A deal

A deal has a title, a value and currency, a stage, an owner (a member), a company, an expected close date, a source, notes and custom fields. Its page shows:

  • Notes at the top, the full width of the page (and of a phone's screen), with markdown drawn as headings, lists, tables and links. Edit opens a large editor; long notes start folded with Show all. An agent that writes notes through funnel_deal_update lands here.
  • People involved, each with their People context card when the person is yours. Add a person by searching.
  • Products: lines from the catalogue or free text, with quantity and discount. When a deal has lines its value is their total (each line rounded to the minor unit, as in Funnel); without lines you type the value.
  • To-dos: a to-do is an issue in Venom Tasks, assigned to the deal's owner and linked back here.
  • Activity: log a call, meeting, email, message or note. It shows on the deal for everyone who can see the deal, and is also written as an interaction on each person of the deal that you know yourself, so your context cards stay current. Nothing is ever sent to anyone. An entry's markdown is drawn the same way as the notes.
  • Stage history with who moved it and when.

Intros and meetings

These parts of a deal's page are yours alone; anyone else who opens the deal sees their own, or nothing.

  • Intros: your intro asks on the deal, connector → target, with the state, its age, the next nudge and the same buttons as My asks (send with a channel button or through Venom, They agreed, Introduced, Declined, Drop, Link to deal). The section is hidden when you have none. Ask for intro, next to People, starts one: someone on the deal or a name you type, then who of your people can introduce you. When an ask on the deal becomes introduced, the target joins the deal's people and the activity gets one "Intro made" row. The stage is not moved.
  • Next meeting: your next meeting from your connected calendars or bookings with someone on the deal in it (matched and confirmed, not a "Possibly …?"), or a booking made for the deal, with its time, title and place.
  • Meetings in the activity: meetings logged on your own people on the deal since a month before it was created, in person with a place, from your calendar, from Granola or from How did it go?, show in the activity, marked Only you. One you log from the deal itself is an ordinary activity already. See People meetings.

Who sees what

A deal is visible to everyone in the organisation or to one of your teams (the members of the teams above it see it too, as in People: who sees what); its owner and its creator always see it. The people on a deal keep People's rules: you see a linked person only if you may see that person (you know them, or they were shared with your team or the organisation). For the rest you see a count of private contacts, and searching a deal by a hidden contact's name does not find it. You cannot link someone else's private person. A context card, notes and interactions are only ever shown to the member who owns the person. The reports and goals count the deals you may see.

A to-do on a deal is a Tasks issue, so it goes to a Tasks team: the deal's team when it is one, otherwise your first Tasks team.

The org's webhooks (Settings → Webhooks) carry deals visible to everyone in the organisation: funnel.deal.created, funnel.deal.updated, funnel.deal.stage_changed (the stage and status before and after, so won and lost show here) and funnel.deal.archived, with the id, title, value, currency, pipeline, stage, status, owner and company. Never the notes, the lost reason, custom fields or the people on the deal. A team-only deal is never sent; a deal moved from the organisation to a team sends one funnel.deal.updated with its id and visibility: "team" only. Outreach sends no org webhook events: an enrollment is about a person's private contact.

Forecast and reports

/funnel/reports (Funnel's maths, ported with its tests):

  • Forecast by expected close month: pipeline, weighted (value × stage probability), commit (deals at 80% or more) and best case (40% or more). A close date in the past counts in the current month; deals without a date are their own row.
  • Conversion by stage: of the deals that entered each stage in the period, how many went on.
  • Win rate by month, the sales cycle (days from created to won), velocity (days per stage) and lost reasons.
  • Team: won value and win rate per owner, and each owner's open pipeline.
  • Goals: a target for won value, deals won, new deals or activities logged, for the month or quarter, for the organisation or one member, with the pace against the share of the period gone and a forecast (won so far plus the weighted open deals due in the period).

Reports use the pipeline's main currency; deals in another currency are counted and left out of the sums. Pick the range (30 days, 90 days, 12 months, year to date), the pipeline and whose deals.

Settings

/funnel/settings: pipelines and stages (type open, won or lost; probability; stale after days; order), the product catalogue, custom deal fields (text, long text, number, money, date, select, multi-select, checkbox, URL, email), and the importer.

A new organisation gets one pipeline, Sales: Lead, Qualified, Demo, Proposal, Negotiation, Won, Lost. A pipeline always keeps at least one won and one lost stage; a stage that holds deals cannot change type, and archiving it moves its deals to another stage of the same type.

What is not here

Funnel's web forms are not ported; capture leads with Venom Forms and link the person. Funnel's notifications are the Venom bell, its tasks are Tasks, and its API keys are Venom API keys.