The active foundation
Our own GTM brain holds company context, skills, decisions and outputs in Baalda. Claude Code and Codex support scoped research, drafting and checks against that context. People own the decisions and review work that spends money or reaches a buyer.
Email and Google Calendar support conversations and meetings. Google Ads, LinkedIn Ads and Meta sit in client-owned accounts for the relevant delivery work. Client billing and permissions stay with the client.
We are building our own CRM and outbound operations. The options below are not a claim that every named product is active internally, and this page does not rate tools that have not been tested.
Choose by the job
| Job | Active foundation or client system | Options to evaluate | Decision that comes first |
|---|---|---|---|
| Company context and repeatable AI work | GTM brain in Baalda, Claude Code and Codex | Additional models as a job needs them | Approved context, proof and human review |
| Pipeline and relationship ownership | Client’s CRM | CRM-native capability first; HubSpot, Salesforce or Attio where appropriate | Identity, lifecycle, ownership and the one pipeline definition |
| Paid campaign execution | Client-owned Google Ads, LinkedIn Ads and Meta | Supported platform connectors | Conversion goal and value model |
| Enrichment | Depends on the client’s verified stack | Native data, Apollo, Clay or specialist providers | Which missing field changes the next action |
| Orchestration | Job-specific; native automation where sufficient | n8n or another supported connector | Failure handling, permissions and maintenance owner |
| Outbound sending | Client-specific decision | Appropriate sending platform and mailbox setup | Eligibility, suppression, delivery health and sales capacity |
| Contact verification | Client-specific decision | SendSure or another verification provider | Validity checks and the limits of verification |
| Search and source-gap research | Search results, AI answers and primary sources | Dedicated visibility tooling when the sample warrants it | Buyer question set and reproducible evidence |
No affiliate links or paid placements are used here. Commercial relationships belong beside the recommendation, not hidden in a footer.
SendSure disclosure
Vijay is involved in SendSure, a separate email verification and deliverability product. That relationship makes it especially important to show fit, limits and alternatives. Naming SendSure is not an independent comparison or a recommendation that it must be used in every engagement.
Verification can help detect address problems. It cannot guarantee inbox placement, buyer interest or lawful outreach. Evaluate it against the same sample and outcome definition as any alternative.
A smaller stack can be the better stack
Before adding a tool, ask whether the CRM or existing system can do the job reliably. Then test the missing capability. Include data coverage, error handling, exportability, cost at the expected volume and who maintains it.
A connector that saves an operator ten minutes and creates an unowned failure queue may be a bad trade. A tool should earn its place through a useful output and a manageable dependency.
How a Pick earns publication
Picks follow recorded evaluations in four jobs: enrichment, orchestration, sending and deliverability, and search and content operations. Each review must show the task, sample, alternatives, what was tested, failures, limits, costs checked on the review date and the decision.
There are no scored Picks at launch. We publish them when we have a test record worth a buyer’s trust. This page is the current stack map, not a substitute for those evaluations.
The evaluations behind the Picks
The job-based Picks record what was tested, what was checked in current documentation and what still needs a live account trial. Our October source-capture work used Firecrawl on seven named public pages. That is a specific research trial, not a claim that every provider in the stack has been tested or connected.
Read the enrichment Pick, orchestration Pick, sending and deliverability Pick and search and content Pick for the sample and limits.
Publication and source record
Published on GTMhub: . Last reviewed: .