Skip to content
Fonsent

Why it is called Fonsent

The name joins two words, and each one is a rule the product has to keep.

· 2 min read · Fonsent

The name joins the Latin fons, source, with consent. Those are the product’s two promises, and we wanted them in the one word people would say most often.

Fons: where a value came from

A CRM fills with values nobody can account for. When software writes them, there are more of them, and they all look equally sure of themselves.

So the first rule is about origin. Every value Fonsent writes from an email, a meeting or a transcript is stored with the exact sentence it came from. The database checks the quote against the source and refuses a value that has none. No quote, no change: if the source doesn’t state the value, nothing is proposed.

The second rule is about leaving. Nothing customer-facing leaves unless a person approved that exact message, and it leaves at most once. An agent can’t approve a draft; only a person can. An approval covers exactly what you saw, so if the content changed after you opened it, the approval is refused.

Why put constraints in a name

Most product names promise a result. This one names two things the product must not do: write a value it can’t source, or send something nobody approved. A constraint is easier to check than a result. You can open any value and look for the sentence. You can open any sent email and look for the approval.

A name is also a promise you repeat every time you say it. If Fonsent ever shows a value without a source, the name is the first thing that will be wrong. We would rather carry that risk than a name that asks nothing of us.

Who makes it

Fonsent is made by Stead Technologies LLP, a product strategy, design and engineering studio in Bengaluru, India. About Fonsent.

Start with your own records.

Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.

Early access. No payment details are asked for.