Sales pipeline with IA assitant

If your leads live in a spreadsheet, a mailbox and somebody's memory, Sales Pipeline AI gives them one home inside the Drupal admin you already use: a Kanban board per sales process, a profile for every lead, and the numbers that show where deals stall.

The day you install it, a pipeline called Sales pipeline is waiting under Administration » Sales pipelines with four columns: New, Contacted, Qualified and Proposal. Add a lead, drag it across, and the funnel starts counting. None of that needs an account anywhere.

What you get

• A board you drag, and a history you never write. Cards show name, company and value with call and email links; every move is stored as a stage transition, so the analytics build themselves.
• Outcomes with a value. Drop a card on the Won, Rejected or Lost shelf and the deal closes with its amount summed; the overview shows each pipeline's last 7 and 30 days.
• Funnel, flow and list. Count, value and conversion per column, a Sankey diagram of forward and backward moves, and a table under one filter bar.
• Columns you shape from the board. Rename, pick an icon and colour, insert a column anywhere, reorder; a column with cards cannot be deleted.
• A lead profile that tells the whole story. Contact fields edit inline, an awareness level runs from unaware to most-aware, and a timeline collects calls, emails, chats, meetings, notes and files (private attachments up to 20 MB). Leads take extra fields through Field UI.
• Actions and buying signals. Typed tasks (email, lead magnet, call, meeting, WhatsApp, SMS, task) with due date, attachment and a mandatory flag; signals with a weight and a progress bar.
• Import in minutes. CSV import with a downloadable template, an Orphans tab for leads in no pipeline, and a dialog that moves a lead to another pipeline.
• A team that sees its own work. Every lead has a setter, a closer and an agent; users in the shipped sales role (ventas) see only their leads and pipelines; the owner hears of an action due, a stalled lead, a deal won and a weekly summary.

How it works

Everything is a Drupal content entity: pipelines, stages, leads, placements, actions, activities, signals and stage transitions. A lead can sit in several pipelines, one stage per placement, and an outcome closes it there; the funnel and flow views are read straight from those records.

The overview at /admin/sales-pipeline-ai lists your pipelines; from it you open a board at /admin/sales-pipeline-ai/pipeline/{slug} and its funnel, flow, list and Adjust pipeline screens. With the optional service connected, the AI buttons ask the suite's gateway for a playbook, stored on the stage, a suggestion, stored on the lead, or a list of ideas you turn into actions or signals.

Free, and what the optional service adds

The CRM is complete without any external account: everything listed above works on the bundled pipeline, heuristic signal labels, owner notifications and the Spanish translation included.

Three things need the optional Central Connect AI service: the AI features (playbooks, suggestions, the ideas dialog and AI-written labels for signals from inbound activity), pipelines beyond the bundled one, and the CSV export of leads. The service is operated by Tangram Consulting, the sponsor, or by any provider exposing the same API. You connect your site explicitly from the SDK settings page; until then no lead data leaves it, and the module only asks the SDK whether a subscription exists.

A locked feature never leaves you on a broken screen: an extra pipeline opens on a page that says so and leads you back, AI buttons carry a short notice, and the CSV export answers access denied until you connect.

Use cases

• An agency selling websites and support. One pipeline from first contact to proposal, with the Won shelf as the month-end report.
• A small in-house sales team. Setters qualify and hand over to closers; each rep sees only their leads, the owner sees the funnel.
• Leads that arrive from everywhere. Import the old spreadsheet, log the calls, and let the chatbot's closed conversations land on the timeline.

Getting started

1. Install with Composer and enable the module; the SDK comes with it.
2. Grant administer sales pipeline ai and manage sales pipelines to whoever owns the process, and view sales pipeline ai leads, edit sales pipeline ai leads and move sales pipeline ai leads to the team.
3. Open Administration » Sales pipelines (/admin/sales-pipeline-ai), click the bundled pipeline and use each column's gear to rename it and pick its icon and colour, or the + between columns to insert one.
4. Add leads from the Add lead dialog or import a CSV at /admin/sales-pipeline-ai/import.
5. Give your reps the shipped sales role, mark each as setter, closer or agent and add them to the pipeline pools.
6. For AI, more pipelines or the export, connect the site on the SDK settings page; the AI switch is at /admin/sales-pipeline-ai/settings.

Requirements

• Drupal 11.1 or newer, and the PHP version it requires (8.3).
• Core modules: User, Field UI, Views, File, Options and Text.
• Central Connect AI SDK (required); Multi-Role AI Chatbot (optional).
• An account on the Central Connect AI service for AI, extra pipelines and the export.
• composer require drupal/sales_pipeline_ai

Privacy and security

• Leads, activities, actions, signals and transitions are content entities in your database; the module's settings hold only the AI switch and the upgrade URL; the only other shipped configuration is the sales role.
• Leads stay until you delete them; there is no automatic purge.
• Attachments live in the private file system and are served only to users allowed to see that lead.
• Every write from the board is a POST with the CSRF request token; card moves are flood-limited to 60 per minute; dialogs check that ids belong to the lead on screen.
• Administration and pipeline-management permissions are restricted access; manage sales pipelines can create team accounts, so grant it with care.
• Once connected, an AI request leaves only when you press an AI button or log an inbound activity with the AI switch on, and carries the data of that lead and its stage, nothing from other leads. The module has no HTTP client and stores no AI provider key.
• Emails to a lead use your site's mail system; notifications stay in your notification centre.

Part of the Central Connect AI suite

The suite's free admin modules share one header, one notification centre and one connection to an optional AI service.

• Central Connect AI SDK: the required base; header, icons, dialogs, the notification bell and the gateway this module calls for AI.
• Multi-Role AI Chatbot: its closed or escalated conversations become chat activities on the matching lead.
• Web Health Status: reads this module's lead and pipeline counters for its dashboard.

Similar projects and how this one differs

• CRM models contacts, contact methods and relationships as a general-purpose base; no stages, outcomes, board or funnel.
• RedHen CRM manages contacts, organisations and their relationships for nonprofits; no sales process with columns and conversion figures.
• CRM Core is a contact and activity framework; it offers no Kanban board or pipeline analytics.
• View kanban bootstrap turns any view into a drag-and-drop board; no lead model, outcomes, funnel or team scoping.
• Pipedrive sends contacts and deals to the Pipedrive service; here the pipeline and the leads stay inside Drupal.
• Salesforce Suite synchronises Drupal entities with Salesforce; here Drupal is the CRM, not a mirror of one.

Development

Parts of this module were written with the assistance of AI-based coding tools, as required by the policy on the use of AI when contributing to Drupal. All the code has been read, corrected, tested and is maintained by the human maintainer listed below, who takes full responsibility for it.

Maintainers and sponsor

Maintained by pedroromán. Development is sponsored by Tangram Consulting, which also operates the optional service. Issues, ideas and contributions are welcome in the issue queue.