Pipeline value by stage
Count and value for every stage of the pipeline you are looking at, in your org default currency.
Every deal, the stage it is in, and how long it has been sitting there. Drag it forward when it moves. The board is the record, not a picture of one.
Unlimited deals and unlimited users. MIT licensed, self-host it anywhere.
Not a dashboard that reads the pipeline once a night. Deals sit in columns, you drag them, and the change is written the moment you let go.
This is the whole list. BottleCRM does not ship win-rate modelling, conversion funnels or cycle-length reporting, so this page does not claim them.
Count and value for every stage of the pipeline you are looking at, in your org default currency.
The sum of every open deal multiplied by its own win probability.
Days on the current stage per deal, against the expected days you set on that stage.
A count in the header, and a filter that narrows the list to only the deals that have stalled.
Revenue and deal-count targets per person, with a team leaderboard.
Narrow by owner, stage or date and the count and both totals recompute for that slice, not for the page you are looking at.
The source is public. Read the pipeline code before you trust a word on this page.
Yes. Every organisation starts with one pipeline holding six stages: Prospecting, Qualification, Proposal, Negotiation, Closed Won and Closed Lost. An admin can rename, add, reorder and remove stages, and add more pipelines, in Settings on the web app or the phone. Each stage is open, won or lost, and every pipeline keeps at least one of each. Wins are counted by that kind rather than by name, so calling your won stage "Signed" does not break the dashboard or your goals.
Yes. New business and renewals, or one pipeline per product line, each with its own stages. The board and the list switch between them. The board moves a deal between stages of its own pipeline; moving it to another pipeline is done from the deal itself.
Each deal records when it last changed stage, so the days it has spent where it is are always known. An admin can give each open stage an expected number of days and an earlier warning. Past the warning the deal is marked past expected; at one and a half times the expected days it is marked stalled. A stage with no days set never flags. You can filter the list down to just the stalled deals rather than hunting for them.
Moving it into a won stage needs a close date and an amount, and records who closed it. From there, one click on the deal page creates a draft invoice with the deal's line items, account and contact already on it, on the web or the phone. You can also raise an estimate from any deal before it closes.
Owner and tags on the board itself. The list view runs considerably more, including stage, currency, close date and the stalled subset. Switching between board and list keeps the filters both layouts can honour, so you do not silently lose a filter by changing the view.
Yes. A deal belongs to an account, carries its own line items, and holds comments, attachments and a full change history. Tasks can be pinned to it. It is one database, not a pipeline tool bolted onto a contact list.
No per-seat fee, no deal cap, no trial clock. Host it yourself, or let RunCode run it.