Case study · SoberSphere · Our own business
We built and use Substrate with the SoberSphere portal to record engagement, support follow-up, and keep CRM reporting connected to the underlying activity.
In operational use as of October 2026. Built for our own venture.
Explore custom CRM & pipeline systems ↗The business need
SoberSphere needed to connect investor outreach with activity in its information portal.
Sending a message was only the first step. We needed to record entries and document requests, associate activity with outreach records where possible, and make it available for follow-up and reporting.
The system had to distinguish an issued access code from a visitor’s self-entered details. It also needed a durable activity record when an alert failed or a reporting job was delayed.
The working system
A simplified view of the implementation. No investor records or private materials are shown.
Issued access codes connect grants to contact records, channels, and outreach batches.
The portal records entries, document requests, and contact submissions in Substrate.
Activity alerts help identify engagement that may warrant a conversation.
A separate reporting process reconciles stored activity into the CRM.
Attribution reflects the access method used. An assigned code identifies its grant; a typed name or email is self-reported. A document request is an activity signal, not proof that its contents were read.
Why it was built this way
An alert is useful when someone needs to act promptly. The stored activity is what reporting can check later. Keeping those roles separate means a missed notification does not have to erase the underlying record.
Substrate holds the activity history. The CRM receives a usable view of that history through a separate reporting process.
What we learned
The recorded activity let us distinguish sending outreach from getting someone into the portal. It gave us a basis for reviewing the handoff between a conversation and the material sent afterward.
The system supports that decision; it does not make the sales conversation happen or establish why every recipient did not enter.
Operating the system
Using the system exposed practical issues, including expired access codes and delayed reporting runs. Those incidents informed the operating requirements: explicit expiry management, checks on failed entries, and a way to reconcile reports from stored activity.
A working workflow includes maintenance and verification as well as its visible interface.
What transfers to another business
Contact records, source attribution, activity history, follow-up alerts, and reporting can support many kinds of pipeline.
SoberSphere uses gated access because this workflow includes private materials. A sales, referral, onboarding, or recruiting pipeline may start with a public form or an existing record and need no gate at all.
See the broader CRM & pipeline use cases ↗We’ll look at what you need to track, which decisions it should support, and whether existing software or a custom build is the appropriate solution.
Discuss your workflow ↗