Salesforce¶

Purpose¶

#1 CRM for customer use and integration. The majority of eco|monetize™ target customers run on Salesforce, so it's both a source of data (via integrations) and a deployment target for customer-facing tooling like EcoTask.

How we use it¶

Customer integration target — ICP enrichment data shows top prospects overwhelmingly use Salesforce + Slack + Microsoft 365 (per Jordan's memory + Apollo enrichment patterns)
EcoTask deployment — custom package deployed to customer Salesforce orgs as part of the Revenue OS offering. Active project per Jordan's memory project_salesforce_deployment_pain.md
Metadata generation — scripts at /Claude/archive/production-snapshot/ reference salesforce-metadata generators (generate_metadata.py, generate_ecotask_metadata.py)
Internal CRM — secondary to Monday.com for internal ops but primary for customer records tied to the integration

Setup & credentials¶

Developer org + production org (TBD). Credentials in 1Password. No MCP server installed — API access via direct integration.

Owner¶

code.platform — as the owner of the integrations surface in v1.2 (absorbed code.integrations role). Code.platform handles EcoTask build + deploy.

[[monday-com]] — internal CRM primary (different role)
[[hubspot]] — secondary CRM
[[apollo-io]] — prospecting into Salesforce-using accounts
[[code.platform]] — integration owner
Active issue: EcoTask deployment pain (Track 7 + Track 8 priority per Jordan's memory)

Notes¶

EcoTask deployment pain — Jordan's memory flags: "EcoTask deploy burned 45-60 mins, profile issues, still didn't fully work. Needs: SFDC module version inventory, zero-click install automation, QA agent to recreate + validate."
Existing scripts for SF metadata generation in archived production snapshot
Salesforce integration is the primary path for customer onboarding