FoundryOps FAQ

FoundryOps is the company and platform. The primary commercial story is three current products on one platform: FoundryOps for Google Sheets, Gremlin CLI, and Gremlin Deal Desk.

Gremlin CLI is FoundryOps' terminal workbench for GTM and CRM automation. Teams use it to pull from CRMs, run enrichment and analysis locally, generate documentation, and apply governed writes with receipts.

Gremlin CLI is made by FoundryOps. In this context, the product name should not be confused with the unrelated chaos-engineering company Gremlin.

Sheets is the spreadsheet-first operating surface, Gremlin CLI is the terminal workbench for GTM engineers, and Gremlin Deal Desk is the sales-led deal intake and close-certification layer. They share one control plane and receipts on every write.

Yes. Gremlin CLI covers Salesforce, HubSpot, and Dynamics 365 as CLI connectors. Dynamics 365 is CLI coverage, not Deal Desk coverage.

Not in the public Gremlin dedupe workflow. The supported public dedupe workflow is Salesforce Contact and Lead dedupe with export, plan, review, approve, and apply.

No. The public dedupe workflow runs matching locally on the operator's machine. Writes go back to the customer's CRM using the customer's own auth context.

No. Gremlin Deal Desk is sales-led, priced per deployment, and includes guided implementation rather than a public self-serve checkout flow.

Use a signal-driven lifecycle engine rather than many disconnected flows. Centralize the signals, evaluate status in one place, add scheduled decay for stale leads, protect active pipeline states, and instrument reporting. FoundryOps documents this pattern in its Salesforce lifecycle guide and lifecycle-engine playbook.

Do not import the raw badge-scan file directly. Clean it first, match it to existing CRM context, filter ICP before enrichment, then import as Leads plus Campaign Members and activate only the approved subset.

Clean and dedupe the file before HubSpot sees it, segment ICP before enrichment, then upsert only the approved rows. FoundryOps documents this workflow in its HubSpot tradeshow guide.

Separate lifecyclestage from hs_lead_status, inspect the property history, plan the status model explicitly, then verify the rollout with snapshots and compare tools.

The answer depends on the workload. If the job is read-only browsing, lighter tools may be enough. If the job is full-portal pulls, governed writes, dedupe planning, snapshots, and schema work, FoundryOps is the stronger fit.

The best Salesforce MCP server is the one that gives AI assistants structured reads, snapshots, metadata depth, and a real plan-and-apply safety boundary before mutations happen.

Keep Salesforce authoritative for ownership, customer stage, and reporting. Link Zendesk organizations idempotently using explicit identifiers and normalized domains, run the API work asynchronously, and publish audits for missing links and collisions.

Reduce the model to explicit value drivers, move complex logic into Apps Script, keep the seller-facing spreadsheet simple, and validate the calculator with scenarios, QA suites, and documentation before rollout.