Tosven is in pilot. Early access conversations are open for the first companies. Apply

CRM and sales

The CRM that shares a database with your ledger

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.

1
database for the deal, the quote, the invoice and the journal entry
0
integrations between a won deal and its invoice
2
distinct signatures for a discount above 20 % in the default policy
Weekly
forecast snapshots, append-only, compared week over week

Sales and finance read the same customer record

Read the documentation

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

The pipeline board, with money that is real

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

Everything a sales organisation runs on

01

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.

02

Weighted forecast

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.

03

Deal 360

One screen per customer: identity, contacts, open deals, decision makers, receivables, the chain from deal to payment, a single timeline and the next step.

04

Contacts, companies, roles

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.

05

Activities and tasks

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.

06

Versioned quotes

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.

07

Signed discount approval

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.

08

Quote to invoice

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.

09

Consent and erasure

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

Three sales days, step by step

01

A won deal becomes a journal entry

Nordlys AB accepts the third version of an annual maintenance quote. Sample data.

  1. 09:12Antti KorhonenSends QUO-2026-0142 v3 to Sanna Lind. The document is frozen and hashed at send.
  2. 11:40Sanna LindOpens the link, types her name, confirms her authority and accepts v3.
  3. 11:41Antti KorhonenMoves OPP-2026-0412 to Won. The close date is set to today and the stage history is written.
  4. 13:05Sara NyströmConverts the accepted version into draft invoice INV-2026-0418. Each line points to its quote line.
  5. 13:20Sara NyströmPosts the invoice. JRN-2026-01284 is written and Nordlys AB changes from prospect to customer.
02

A discount that needs two signatures

A draft quote for Harju Tekniikka Oy carries a 22 % line discount, above the 20 % threshold. Sample data.

  1. 08:50Antti KorhonenSaves the draft. The screen states that sending needs two signatures before he tries.
  2. 08:51Antti KorhonenRequests approval. The approval card is bound to the hash of this exact draft.
  3. 09:30Elina KoskinenSigns. She did not write or edit the draft, so her signature counts.
  4. 10:15Mikko LehtonenSigns as the second, distinct approver. Any later edit would make the card stale.
  5. 10:20Antti KorhonenSends v1. The quote number is allocated at send and the deal amount follows the quote.
03

An overdue invoice, followed up without a spreadsheet

An invoice to Vesta Logistics Oy is 16 days overdue with 18.600,00 € open. Sample data.

  1. 07:58Collections agentProposes reminder 1 of 3 for INV-2026-0397, with the full letter and the reason on the card.
  2. 08:05Elina KoskinenReads the letter and the payment history on the card, then signs it.
  3. 08:06Collections agentRechecks the open balance and sends the reminder to the live billing address.
  4. 10:42Antti KorhonenSees the reminder on the customer timeline and logs a call with the buyer on the same record.
  5. 10:50Antti KorhonenRecords a promise to pay by 21.10.2026. Reminders pause until that date.

Sample data

Pipeline and deal 360

Stage rules live in the database, not in a training deck

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.

  • Deals past their stage threshold are marked stagnant, with the days shown
  • Signals: silent decision maker, close date moved twice, overdue invoice
  • Receivables on the deal screen read from the ledger, or show no access
  • Row ownership and time-limited sharing for teams that need it
Forecast

A forecast you can compare with last week and with the books

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.

  • Probability comes from the stage, with a logged override per deal
  • Manager adjustments sit beside the rep's figures and never replace them
  • Converted totals name the exchange rate source and its date
  • Pipeline and forecast are verified measures in Lens, per currency
Quotes and approvals

What the customer received never changes

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.

  • Binding offers and non-binding estimates are separate document kinds
  • Margin is shown only when every priced line has a cost, never guessed
  • The link records that the page was opened. There is no tracking pixel
  • Loosening an approval rule takes effect after 24 hours, not at once
Consent and erasure

The compliant path is the default path

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.

  • An opt-out is lifted only by that person's new consent, not by a note
  • Prospects come up for review after 24 months, former customers after 36
  • Erased addresses stay as salted hashes so they are never contacted again
  • People are not scored. Company signals are rules with stated reasons

In the field · IT services and software company

From first meeting to paid invoice in a project business

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.

With separate tools

  • Deal amount in the CRM, real amount in the latest quote document
  • Discount approved in an email thread nobody can find at audit time
  • Finance retypes quote lines into the invoicing system
  • Sales learns about an overdue invoice from the customer

In Tosven

  • Sending the primary quote sets the deal amount, with provenance
  • Approval is a signed card bound to the exact draft that was sent
  • Accepted lines convert into a draft invoice and keep their link
  • Overdue invoices and reminders appear on the customer timeline

A working day

Sample data
  1. 08:00Antti Korhonen opens his deals. Two are stagnant in Proposal and one decision maker has been silent for 12 days.
  2. 09:30Elina Koskinen signs a discount approval for Harju Tekniikka Oy. The card shows the triggered rule and the draft hash.
  3. 11:40Sanna Lind at Nordlys AB accepts QUO-2026-0142 v3 through the link. The deal moves to Won.
  4. 13:20Sara Nyström converts the accepted version and posts INV-2026-0418. The journal entry is written in the same step.
  5. 16:00Mikko Lehtonen reads the forecast. Commit grew by 48.000,00 € since Monday and the view names the deal behind it.

Status

Where it stands today

Live in pilot
  • Leads, companies, contacts with dated roles, deals, activities and tasks
  • Pipelines with stage history, probabilities, exit criteria and loss reasons
  • Versioned quotes, customer link acceptance and signed discount approval
  • Conversion of an accepted quote to a draft invoice: full, partial or advance
  • Weighted forecast with weekly snapshots, targets and attributed adjustments
  • Consent gate, retention review, erasure and Collections agent reminders
On the way
  • Sales agent in production. Today sales signals run as deterministic rules
  • Product catalogue, price lists and sales orders with delivery
  • Email and calendar capture, and company registry enrichment
  • Pipeline inspection: what changed since a date, with a waterfall
  • Forecast against invoiced revenue as a standard view in Lens
  • Recurring billing, payment links and a customer portal for documents

Frequently asked

Questions and answers

hello@tosven.com

How is this different from connecting a CRM to an accounting system?

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.

Can we define our own pipelines, stages and fields?

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.

How does a customer accept a quote?

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.

What do agents do in sales today?

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.

How are consent and erasure requests handled?

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

Be among the first companies.

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.