Platform overview
This is where the architecture story now lives: what the internal CRM does, what the public layer does, and how the two stay cleanly separated.
Built for staff who need relationship memory, submission review, private notes, and publishing controls.
Staff can track organizations, keep internal context private, review submissions, and decide exactly what is exposed publicly.
Searchable discovery without leaking the private operating context behind the scenes.
The directory supports search, filtering, and public profile claims so organizations can be found without touching the CRM.
Public web data can be indexed, staged, normalized, and reviewed instead of bypassing curation.
Scraped and imported records are meant to flow into a review lane first, keeping quality control with staff instead of dumping raw internet data straight into production.