Two local dependencies, and only one was obvious

Published September 2, 2026Updated September 3, 2026

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 […]

In this series · Part 15 of 34

1Dynamics 365 CRM: API integration + change-control repo 2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts 3Turning a sales-intelligence export into a clean CRM data model 4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time 5Your SEO health now lives as a dashboard inside the CRM 6Contact form duplicate detection now reads the request, not just the address 7Marketing list members now show engagement and account fit 8Campaign responses now create leads behind a confirmation step 9Three CRM automations passed their tests without running the code that had just changed 10A signature defect that three mailboxes agreed was not there 11Asking whether a partner is involved, instead of inferring it 12Choosing what runs the AI layer in the CRM sales process 13A read-only CRM endpoint for scoring outside the desktop 14Why a corrected email signature kept sending the old one 15Two local dependencies, and only one was obvious 16Filing a generated document to the record automatically 17The rehearsal that guards every process change had been failing silently 18An email step in the sales process can now be excused, not only sent 19A one to one email from a lead left the engagement record blank 20One meeting that served two process steps, recorded as two 21A setting that stored correctly, read back correctly, and was never in force 22Generating a product catalogue from one canonical file 23Three date fields that existed on every row, and had never once been written 24Unused, unreferenced, and still not safe to delete 25A measure that could not record early 26A sales automation that runs as itself, not as an administrator 27A stage change that was refused, and reported as a success 28An Email Validation Gate for Campaign Sends in the Authgnosis CRM 29Marketing List Membership and Campaign Frequency Caps in the Authgnosis CRM 30A Send Guardrail for Unsubscribe Links in the Authgnosis CRM 31Automated Bounce Handling for Campaign Email 32Nurturing Cadence Automation and an Email Send Gate in the Authgnosis CRM 33A Hard Stop on Calendar Invites from AI Agents in the CRM 34Bounced Campaign Email Now Updates the CRM on Its Own

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

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.