Before Authgnosis approaches a prospective client, it scores that company against a detailed ideal customer profile, so outreach only goes where the services and Marissa Wright's experience are a reasonable fit. This build doubles as a proof of concept for the enterprise sales and customer lifecycle automation work, where the aim is that a salesperson stays in the browser the CRM already lives in.
- The client-fit score combines what a company does, read from its website, with its size, read from the CRM. Reading the CRM needed a database connection that exists only on one desktop, so answering a fit question meant leaving the browser where the CRM lives, getting the answer elsewhere, and coming back.
- A read only endpoint now serves that lookup over an authenticated connector, so the check runs in the browser session alongside the CRM. It offers one operation and no general query, so a surface that can score a company cannot do anything else with the CRM.
- Fixing CRM access alone would not have been enough. The scoring also called a local script to gather website evidence, so it would have failed on its first action before reaching the CRM at all. It now falls back to fetching the pages itself and collecting the same named signals. Confirmed by scoring a company end to end from a browser session.
- Running both evidence paths against the same company exposed a defect in the preferred one. The script reported navigation labels where the pricing tiers should have been, and missed the sales button beneath each tier. Those are the signals the fit rubric arbitrates on.