Questions about Shuntline
Short answers to what architects, CRM owners and marketing ops ask first. Everything here is also in the pages above, in more depth.
What is a reverse-CRM experience?
It moves users and records upstream. People start from their enterprise data in Snowflake, land in one governed space, Shuntline Hub, where they view, analyze or ask Snowflake CoWork, then go down to the solution that does the job: a Shuntline solution on Snowflake, or a specialized app such as Salesforce or a CDP, which receives only what it needs to engage. Reverse ETL already made the warehouse the starting point for marketing, building audiences there and activating them in ad, email and CDP tools; a reverse CRM applies the same logic to the CRM's users and records. Shuntline Hub → · Read the essay: The Reverse CRM →
What is Shuntline?
Upstream CRM records on Snowflake, in two moves. CRM Insights detects which entities in Salesforce are referentials rather than workplaces, why they should leave and what moving them saves. Solutions give them a home: adaptable applications (lead management, opt-in and consent, campaign referential and UTM, or custom ones on the same skeleton) installed as Snowflake Native Apps in your own Snowflake account, sold as a fixed-fee monthly subscription.
What does "upstream CRM records" mean?
Records that exist before and around the CRM rather than inside it: the lead as it arrived, the consent a person gave, the campaign that was defined once for the whole group. They are cross-company referentials, worked mostly by automation and read far more often than written, which is the opposite of what a system of engagement like Salesforce is built for.
Does Shuntline replace Salesforce or the CRM?
No. The CRM keeps the work it is good at: accounts, opportunities, the conversations of a sales team. Shuntline takes the referentials out of it, hands the CRM what it needs (for example the converted opportunity, never the raw lead) and lets the warehouse join the rest.
Where does Shuntline run and who hosts it?
In your Snowflake account: the applications are Snowflake Native Apps installed from the Snowflake Marketplace, their records live in hybrid tables, their screens are Streamlit, and the warehouse is the referential they read from and write to. Nothing is hosted by Shuntline. A hybrid design with AWS, Google Cloud or Azure alongside Snowflake can be studied on demand.
How do the solutions connect to marketing platforms?
By reverse ETL. Audiences are built in the warehouse from leads, consent and campaign codes, then pushed to Marketing Cloud or other downstream solutions, which execute. Attribution comes back as a join on the campaign code rather than a reconciliation.
What is CRM Insights?
An automated audit of your Salesforce org, delivered by Shuntline. It detects the entities that should not belong in a system of engagement, explains why, and prices the seats, automations and integrations they carry, attributed to the users who touch them. The findings stay on that machine by default; turn on sharing and they are published to your own Snowflake account or AWS S3 bucket, so every team reads the same evidence.
Is Shuntline limited to the solutions listed?
No. The catalogue grows wherever the pattern applies, and a custom solution can be co-designed on the same skeleton (a Snowflake Native App with hybrid-table records, a Streamlit console, a rules engine and agent tools) for any entity the audit surfaced. Some of those custom solutions surface here, in the catalogue, once the record proves common enough; others stay private to the customer who asked for them, delivered with their source code.