PIPELINES
Sales pipeline software that keeps the numbers honest
Boards with per-pipeline URLs and swimlanes, drag reconciled by row version, quotes built from line items, approvals frozen at ask time, and a share portal the buyer opens without a login.
Boards
As many pipelines as you run, each with its own URL.
A raise funnel, a bid-team funnel, and a renewals board are different processes, so they get different boards. Every pipeline has a URL you can bookmark and send, swimlanes split a board by a second dimension, and bulk actions move a whole selection at once. The deals grid puts every deal from every pipeline in one table when you need the wide shot.
- Per-pipeline URLs: the board you are looking at is a link
- Swimlanes and bulk actions for working many deals at once
- Drag is optimistic and reconciled by row version: your card moves instantly, and a conflicting edit from a teammate is caught instead of silently overwritten
The deal workspace
One screen per deal: activity, email, and intelligence.
Opening a deal should not mean opening five tabs. The workspace puts the activity timeline, the email thread, and the intelligence view (call insights that cite the exact utterance they came from) behind tabs, with a summary rail keeping value, stage, and owner in sight the whole time. Products, line items, and quotes live on the deal, so the value you see is built from what you are actually selling.
- Activity, email, and intelligence tabs beside a persistent summary rail
- Products and line items roll up into quotes on the deal
- Comments with mentions and files, kept where the context is
Process that holds
Discipline built into the board, not bolted on.
Four mechanisms that keep a pipeline meaning what it says.
Stage-entry requirements
A stage can require fields before a deal enters it: no value, no Negotiation; no close date, no Contract. The gap is stopped at the door of the stage instead of discovered in the forecast.
Approvals that snapshot the ask
When someone requests approval, the numbers are frozen at ask time. The approver decides on what was actually asked, and a later edit to the deal cannot quietly rewrite what was approved.
Win and loss are outcomes, not colors
Closing a deal records an outcome, not just a stage change. Won and lost feed the win/loss reporting, velocity, and forecast views in analytics, so the post-mortem has data instead of memory.
A share portal for the other side
Every deal can open a token-gated, brandable share portal: the people on the buying side follow a link, under your brand, with no login and no account. What you chose to share is all they see.
Why most sales pipeline software rots into a to-do list
Boards fail in two quiet ways. The first is drift: stages stop meaning anything because nothing enforces them, values go stale because nothing derives them, and within a quarter the board is a decorated task list. The second is concurrency: two people touch the same deal, the last write silently wins, and nobody notices until the numbers disagree with the meeting.
Ishara treats both as design problems. Stage-entry requirements and approvals give the board teeth, quotes built from products and line items keep the value derived from something real, and every drag is optimistic in the interface but reconciled by row version on the server. If a teammate changed the deal while your card was in the air, the conflict is caught and resolved against the current row, not papered over.
Worked example: the edited ask
A rep requests approval on a 480,000 QAR quote at a 12 percent discount. While the request sits with the approver, the rep adds a line item and the quote becomes 610,000. In sales pipeline software that approves "the deal", the approver just signed off on numbers they never saw. Ishara snapshots the ask: the approval on record binds to 480,000 at 12 percent, exactly what was reviewed.
A deal is a full record, not a card
Deals are objects on the same kernel as everything else, so a deal carries typed fields, saved views, and automations like any other record. That is what makes the workspace possible: email threads match to the deal, call intelligence lands its cited insights on it, and the summary rail is reading live fields, not a cached card. The board is one view of the record, and the object CRM page covers what the record itself can do, provenance and honest multi-currency totals included.
When you want to test how the board holds up, the seeded workspace in the app comes with pipelines already populated: drag a few deals, ask for an approval, and open the share portal on one.
Frequently asked questions
Can I run more than one pipeline?
Yes. Each pipeline is its own board with its own URL, swimlanes, and bulk actions, and the deals grid shows every deal across all pipelines in one table. A raise funnel and a bid-team funnel can run side by side with different stages.
What happens when two people move the same deal at once?
Drag is optimistic, so your card moves instantly, but the server reconciles every move by row version. If a teammate changed the deal in the meantime, the conflict is detected and resolved against the current row instead of one edit silently overwriting the other.
What does the deal share portal show the buyer?
Whatever you choose to share, on a brandable page gated by a token: the person on the other side follows the link and sees it under your brand, with no login and no account to create. Access is carried by the token in the link itself.
Stop working the market blind.
The investors, the tenders, and the signals are in Ishara from day one. You bring the deals.
Free to start · 32,822 investors on day one · Qatar tenders live, more markets on the way