Frequently asked questions
Why does a sales tool ship a CLI?
For the same reason developer tools do: scriptability, automation, version control, and integration into existing workflows. A CLI lets a GTM engineer build a workflow once and run it in CI, on a cron, or as part of a larger orchestration layer.
Who actually uses a CLI for sales work?
GTM engineers, technical RevOps leads, and the engineering-savvy half of RevOps teams. Frontline SDRs and AEs don't use it directly. They consume the outputs through their normal tools.
What can you do with the Landbase CLI that you can't do in the UI?
Build composable pipelines (score → enrich → export → push to CRM in one command), run scheduled jobs, version-control your ICP definitions, and integrate with internal tooling like dbt or Dagster.
Is a CLI overkill for a 5-person GTM team?
Sometimes yes. The CLI's value scales with workflow complexity. A team running one motion through one CRM doesn't need it. A team running three motions across multiple tools sees outsized value.
How is the Landbase CLI different from a Python SDK?
The CLI is for one-shot commands and shell scripting; the SDK is for embedding Landbase in a larger application. Most teams use both. CLI for ad-hoc work and SDK for production pipelines.
.png)
.png)