Before you start

Cosa works on the data your deals already produce — call transcripts, email threads, CRM activity. There is no migration project and no playbook to configure first. You need exactly one thing to begin: a real deal with at least one substantial source, ideally a call transcript. If you do not record calls, an email thread or pasted notes work too; the intelligence will simply carry more ASSUMED tags until richer sources arrive.

Step 1: Connect your tools

Cosa ships with five native connectors. Connect whichever ones your team actually uses:

  • Close — syncs calls, emails, meetings, notes, SMS, and tasks from your leads, including full email and call bodies.
  • HubSpot — syncs calls, emails, and deals.
  • Gmail — syncs email threads via Google OAuth (a standard consent popup; no password sharing).
  • Granola — syncs meeting notes and transcripts via API key.
  • Google Meet — syncs meeting transcripts from Google Drive via OAuth.

Close, HubSpot, and Granola connect with a pasted API key or token; Gmail and Google Meet use a one-click Google consent flow. Credentials are encrypted at rest. Once connected, syncs pull new activity in automatically and de-duplicate against what has already been ingested — nobody on the team uploads anything manually. The full connector and tooling detail lives in integrations and MCP.

You do not need all five. One good source is enough to start; each additional connector deepens the evidence on every deal it touches.

Step 2: Drop in a transcript

Pick a real deal — ideally one that is live and slightly murky, because that is where the output is most instructive. If your connectors are syncing, the transcripts and threads are already flowing in. If not, paste a transcript directly.

The pipeline runs in about 60 seconds. If the source material is thin, Cosa does something deliberately unusual: it pauses and asks you targeted questions instead of inventing answers. A couple of multiple-choice prompts — company name, rough deal economics, the main problem — and the run continues. That pause is the honesty system working, not a setup failure.

Step 3: Read your first deal intelligence

The first output is a structured view of the deal, and every claim in it is tagged FOUND (taken from a source, traceable to the line), ASSUMED (AI inference, flagged for verification), or CALCULATED (derived, formula shown). Expect five things:

  1. 1.A Business Case built from what the prospect actually said — the problem, the current way of working, the value at stake, with an overall confidence grade.
  2. 2.Decision Gate status — where the buyer is across the 7 Decision Gates, based on what was said rather than what the CRM stage claims. Gates the buyer never addressed are marked as not mentioned, not guessed.
  3. 3.A stakeholder map — everyone surfaced in the sources, with role, sentiment, and influence, each field carrying its own verified-or-inferred marker.
  4. 4.Buying signals and risks — what is pulling the deal forward and what is quietly blocking it.
  5. 5.A recommended next action — the single highest-impact move, given the gate status.

The first thing most users notice is the ASSUMED tags — places where they had been treating an inference as a fact. That discomfort is the product working. The methodology behind the gate model is documented in the methodology.

Step 4: Confirm your first action

Cosa proposes; you decide. The recommended action might be a follow-up email built only on FOUND metrics, a pre-call brief for the next meeting, or a champion kit your contact can forward internally. Review it, adjust whatever reads wrong, and confirm — only then does it execute through your connected tools. Nothing is ever sent or written on your behalf without that confirmation. This human-in-the-loop step is permanent design, not a beginner mode.

What week 1 looks like

  • Day 1: Connect tools, run your first deal, read the intelligence, confirm one action. Most teams find at least one materially wrong assumption about a live deal on day one.
  • Days 2–3: Run your three to five most important active deals. Compare gate status against your CRM stages — the disagreements are your real pipeline review.
  • Days 4–5: Work the loop on a live deal: pre-call brief before the meeting, sharper conversation in it, one-click follow-up collateral the same day. This is the rhythm that compresses deal cycles.

No learning curve stands between connecting and benefiting — the identify-and-engage value works from day one. Reference points: Rayqua's founder Marc went from zero sales experience to a structured sales process in week 1; HASE+CO, a 140-employee DACH Mittelstand company, was paying from week 2 and closed 2 high-ticket deals (EUR 850K average transaction value) within 6 weeks. For plans, see pricing.