Skip to content
Fonsent

What we left out, on purpose

Five things a CRM with an agent in it usually has, and why Fonsent doesn’t.

· 2 min read · Fonsent

A product is also the list of things it declines to do. These five are deliberate, and each one costs us something.

A meeting recorder

Fonsent doesn’t record meetings. It reads the transcripts and calendar files you import. A recorder in every call changes how people talk, and it makes the CRM a party to conversations nobody chose to share with it. You decide which transcripts come in.

Sending without a person

Nothing customer-facing leaves unless a person approved that exact message. In a sequence, a person approves each message; enrolling a contact approves nothing. This is slower than letting outreach run. It is also the difference between an email you sent and an email that was sent in your name.

A forecast that commits for you

Commit is never a default. A rep sets it on the deal. And the forecast never hides data quality: deals with no ARR or no deal type are counted and named, not treated as zero. A number that looks complete because the gaps were dropped is worse than a number with its gaps showing.

Trackers

The app serves its own fonts and loads no third-party trackers. This website sets no advertising cookies and loads no third-party scripts. We would like to know which pages people read. We don’t need to know who they are to find out.

Borrowed proof

Fonsent holds no security certification and has not had an independent audit, and this site says so on its security page. There are no customer logos here because it is in early access and there are none to show. Where a logo wall would sit, the home page lists four rules the database enforces. Those you can test yourself.

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.