Pipeline and stages
Several pipelines, each with ordered stages, a probability, a forecast category, a stagnation threshold and up to five exit criteria. Every stage move is recorded and cannot be skipped.
CRM and sales
Customers runs the full sales cycle: leads, pipeline, forecast, quotes, approvals and follow-up. A won deal becomes an invoice and a journal entry in the same system, with no integration in between.
Most companies run sales in one system and invoicing in another, then spend the month end explaining why the two disagree. In Tosven the company a salesperson works on is the same counterparty the accountant invoices. Its name and business identifiers are stored once. Open receivables, average payment days and the last invoice appear on the deal screen for anyone with the right to see them.
The depth is what a sales director expects from an enterprise CRM. Leads convert into companies, contacts and deals. Pipelines have stages, probabilities and exit criteria. Quotes are versioned, approved and accepted through a customer link. The forecast is weighted, categorised and frozen every week. What changes is the end of the chain: the accepted quote becomes a draft invoice, and posting it writes the journal entry.
Customers
Each column is a stage with its own probability and forecast category. Totals are shown per currency and never mixed. A card in Won is not the end of the story: it carries the invoice that was posted from it.
Sample data · pipeline board
Several pipelines, each with ordered stages, a probability, a forecast category, a stagnation threshold and up to five exit criteria. Every stage move is recorded and cannot be skipped.
Categorised and weighted totals per quarter and per currency, side by side with won revenue and the target. Manager adjustments carry an author, a date and a reason.
One screen per customer: identity, contacts, open deals, decision makers, receivables, the chain from deal to payment, a single timeline and the next step.
People are linked to companies with dated roles, so a job change is a new row and history stays intact. Each deal names its decision maker, champion, user and blocker.
Calls, meetings, emails, notes and tasks attach to several records at once: the company, the person and the deal. Nothing is logged twice and nothing is orphaned.
A sent version is frozen and hashed. A change is a new version. The customer accepts through a link by typing a name and confirming authority, bound to that exact document.
Policy rows per company decide when a discount or margin needs one or two signatures. The approval card is bound to the draft, and the author of a draft never signs it.
An accepted version converts into a draft invoice in full, by line and quantity, or as an advance. Invoiced quantity per line is derived from posted invoices, never typed.
Marketing consent is checked per country before any send, and an opt-out survives merges and conversions. Retention reviews go to a person. Erasure states what was removed and what the law keeps.
In practice
Nordlys AB accepts the third version of an annual maintenance quote. Sample data.
A draft quote for Harju Tekniikka Oy carries a 22 % line discount, above the 20 % threshold. Sample data.
An invoice to Vesta Logistics Oy is 16 days overdue with 18.600,00 € open. Sample data.
Sample data
A stage move is checked against its exit criteria. Losing a deal requires a reason from a closed list. Winning sets the close date. Every move writes a history row that no tool, import or agent can bypass. The 360 view then puts that history next to activities, audit entries, tasks, invoices and payments in one timeline.
The forecast groups open deals by quarter, currency and category, and shows the categorised and the weighted total side by side. A snapshot is frozen every Monday. The week-over-week view names each deal that is new, grew, shrank, moved in, moved out, was won or was lost. Because invoices live in the same database, forecast and invoiced revenue can be compared to the cent.
A quote is an offer with a deadline, so a sent version is frozen with its hash and its rendered document. The customer link shows those exact bytes. Acceptance is refused after the validity date and on a superseded or withdrawn version. Discount rules are evaluated in the database, and send is refused until every triggered rule has its signatures.
Every marketing send passes a gate that reads the suppression list, contact blocks and the rule of the recipient's country. If the gate is closed, the send button is inactive and states why. Retention periods raise a review for a person, they do not delete. Erasure removes CRM data and keeps what bookkeeping law requires, and says which is which.
In the field · IT services and software company
An IT services and software company sells a mix of projects, maintenance contracts and advance-billed work. Deals run for months and change shape on the way. In a setup with separate tools, the salesperson keeps the deal in the CRM, the quote in a document, the approval in an email thread and the invoice request in a message to finance. Each handover is a retyping step, and the forecast is a spreadsheet nobody fully trusts.
In Tosven the same deal moves through all of it. The quote has versions, and the version the customer accepted is the one finance converts, in full or as a 30 % advance. The sales director sees which accepted work is still uninvoiced, because invoiced quantity is derived from posted invoices. The CFO sees a forecast frozen weekly and the receivables of every account the team is selling to.
Works with
The CRM company is the ledger counterparty. Accepted quotes become draft invoices, and posting writes the journal entry.
Team chatEach customer has a shared room, opened from the customer view, next to the team's internal channels.
Analytics and reportingOpen pipeline, weighted forecast, won revenue and target are verified measures, per currency, with drill-down.
Status
There is nothing to connect. The company in the pipeline and the counterparty on the invoice are one record with one set of identifiers. Quote lines carry over to invoice lines by reference, receivables on the deal screen are read from the ledger at that moment, and permissions and the audit trail are shared. No sync job exists that could fall behind.
Yes. Pipelines and stages are configured per company, with probabilities, forecast categories, stagnation thresholds and exit criteria. Extra fields on companies, contacts and deals, and entirely new record types, are defined in Builder. A type defined there gets its form, list, permissions and agent tools from the same definition, and follows the same access rules as the rest of the CRM.
The customer receives a link to the frozen document. On that page they type their name, confirm that they may act for the company, and accept or decline. The acceptance is bound to the hash of that version and is refused after the validity date. Where a deal needs more assurance, the seller records a manual acceptance with evidence attached.
The Collections agent is in production: it proposes payment reminders on a fixed ladder, a person signs each card, and it charges no fees or interest. Sales signals such as a silent decision maker or a slipping close date are produced by deterministic rules and shown with reason and evidence. A Sales agent that drafts follow-ups and quote versions is on the roadmap. Agents propose. They never sign a discount.
Consent and opt-outs are stored as evidence rows with source, channel and text version. The marketing gate reads them before every send and again at execution. When a retention period ends or a person asks, a reviewer decides to keep, pseudonymise or erase. The erasure screen lists what was removed and what remains because accounting records must be kept, with the legal basis named.
Early access
Tosven is in pilot. Tell us about your company and the tools you use today in a few sentences, and we will say plainly whether it is a fit.
sales@tosven.com · No card details and no commitment.