📄 For teams whose calculator and quotation document disagree

One price engine behind the calculator and the document your client reads

A quote gets priced in one place and re-typed in another, and the two drift. Here a single engine produces both: the figure on your screen and the document that leaves the building come from the same calculation, in your own company format, in your client’s language — and the internal margin formula has no route into what the client reads.

The engine

The number on screen is the number in the document

Not two systems kept in sync by discipline. One calculation, used twice.

🧮

One calculation, two outputs

The same engine feeds the calculator you configure on screen and the file generated from it. There is no second place to update, so the price cannot drift between what you quoted and what you sent.

🎯

Pinned against a real proposal

The engine is tested against a proposal the company had already sent, and must reproduce it to the cent. Change the pricing logic and break that, and the build stops — the regression is caught before the document is.

📄

Your template, not a generic one

Word and PDF come out in the company’s own proposal format — the layout, sections and wording your clients already recognise, rather than something that looks like it came out of a tool.

🌍

Translated whole, or not at all

The document is translated into the client’s language by a language model rather than a phrase table, and cached per proposal. If the translation cannot be completed it fails loudly — a half-translated client document is never quietly produced, and the original language always works.

What it will not do

The rules the document cannot break

Every one of these is fixed by a test in the product. They are not house style — they are conditions the build enforces.

  • The internal margin formula never appears in the client document, in any form.
  • Hardware is listed at unit price, never as a pre-multiplied total that hides the count.
  • A proof of concept is never offered free.
  • A regional uplift applies to the software only — never to the service.
  • The delivery section carries no country or incoterm that has not been agreed.
  • A test pins each of these, so a change that would break one fails the build rather than reaching a client.
The flow

From a name to a sent document

Three steps, and a human on the last one.

Configure

Add the company — a quick record of its own, kept apart from the outreach lead book so a proposal contact never pollutes the prospecting list — then set the configuration and watch the price resolve on screen.

Generate

Word and PDF are produced in your own format, in the client’s language, from the figures you just approved on screen.

Send

Send it from a real company mailbox with the document attached — sender, recipient, CC, subject and body all yours to set. Every send is recorded, and the thread is there the next time you open that company.

The archive

Every proposal you have already sent, found by itself

The proposals you sent before any of this existed are sitting in a mailbox. They get pulled in and filed without anyone digging.

📥

Scanned in minutes, not once a day

Mailboxes are re-scanned every quarter of an hour, and each pass resumes where the last one stopped — so a proposal sent this afternoon shows up this afternoon, not tomorrow morning.

🧾

A proposal about invoicing is still a proposal

Documents are judged on what they are, not on the word invoice in the filename. Proposal wording outranks subject-line filtering, while real invoices, proformas and a supplier’s own quote stay out.

⏱️

Today’s document jumps the backlog

Recent mail is processed ahead of the historic pile, so a new document is never stuck behind thousands of old ones waiting their turn.

🔎

Auditable, not magic

Each accepted document keeps the reason it was accepted, so a wrong call can be found and corrected instead of argued about. When the language model is unavailable, documents with clear enough evidence still pass — flagged as such.

Follow-up

Quotes that went quiet, chased honestly

Most proposals die of silence. The re-engagement side is built so the status you read is the status that is true.

🎯

Recognised from the campaign, not the last email

A follow-up is identified by the campaign it belongs to, so two years of ordinary correspondence with a client can never be mistaken for a fresh chase.

🚫

Not sent means not sent

A ready recipient in a campaign nobody has started is reported as not sent, never as queued. The system refuses to imply a send that is not going to happen.

🔗

Matching that survives a renamed record

A proposal is matched to its company by archive key, then by contact address, then by company name — so records filed under an older naming scheme still find their proposal instead of silently dropping out.

📜

The whole thread, labelled

Every message with that company in one timeline, newest first, each marked as the proposal, a follow-up or a reminder — attachments, delivery status and full body included. An unsent reminder sits there too, with the template it would use.

Quoting by hand

  • The price is worked out in a spreadsheet and typed into a document — two places to be wrong.
  • The margin formula lives one copy-paste away from the client.
  • Each language is a manual rewrite, so most clients get the quote in yours.
  • Sent proposals live in one person’s mailbox.
  • Whether anyone followed up is a question you ask in a meeting.
  • A quote that went quiet is remembered, or it is not.

With the AI Proposal Manager

  • One engine produces the on-screen price and the document — they cannot disagree.
  • The internal formula has no route into the client file, by construction.
  • The document is translated whole into the client’s language, or it fails rather than half-ships.
  • Every proposal, past and present, is filed against its company on its own.
  • Follow-up status is read from the campaign, and not sent stays not sent.
  • Quiet quotes surface as a list, and nothing goes out until you start it.

See it price one of your own deals

Bring a quote you have already sent. The fastest way to judge a price engine is to watch it reproduce a number you know is right.

Book a live demo
Contact

Talk to a human 🙂

Tell us about your sales team and target markets. We'll reply within one business day — usually much faster.

📧  [email protected]
☎️  +386 41 441 757
🏢  Meta Smart Factory d.o.o. — Dunajska cesta 106, 1000 Ljubljana, Slovenia
🌐  www.metasmartfactory.com
💼  LinkedIn  ·  YouTube
🌍  Partner network in Turkey, Saudi Arabia, Pakistan, Brazil, USA, Canada, UK, France, Croatia, Serbia, South Korea, Indonesia, Mexico & more
💬  Or just ask the chat assistant in the corner →