# Spiich — Agentic sales platform that keeps HubSpot, Attio, Pipedrive or Salesforce updated from chat, voice and meetings.

> Source: The Agents Index — https://theagentsindex.com/spiich (structured, researched, re-verified)
> Facts last verified: 2026-09-15

Spiich is an agentic sales platform that sits on top of an existing CRM (HubSpot, Attio, Pipedrive or Salesforce) and updates it from chat, voice and recorded meetings. Background agents run on schedules, CRM events or webhooks to prospect, qualify and enrich records.

| Fact | Value |
| --- | --- |
| Website | https://spiich.ai |
| Price | from €149/month |
| Free trial | Yes |

A free trial runs before a workspace subscribes; the vendor publishes neither its length nor its credit allowance. It needs a work email address (personal domains are refused) and a connected CRM, and when it ends with no subscription every page redirects to Settings > Billing.

## What it does

**Done-for-you service** · No — You license software and run it yourself: signup is self-serve in four steps, and the vendor's people only appear for Salesforce field mapping during onboarding or to build a custom integration on request.

> Signup is self-serve and takes four numbered steps.
> — https://spiich.ai/help/getting-started/create-your-spiich-workspace · Create your workspace guide, paragraph under 'Sign up with a work email'

## How much it does unattended

**Runs autonomously** · Yes — Background agents fire on schedules, CRM events or webhooks and complete the job unattended; in chat it also runs multi-step work end to end without approving each step.

> You describe the job once in plain language, decide when it should fire and what it is allowed to touch, and it runs by itself from then on.
> — https://spiich.ai/help/background-agents/background-agents-overview · What background agents are, opening paragraph

**Multi-agent** · Partly — The assistant can fan research out to parallel sub-agents, but those helpers are read-only and stateless, so several agents do not jointly write or coordinate a task.

> For broad research it can hand work to sub-agents that run in parallel and stream their progress into the chat. Those sub-agents are deliberately read-only
> — https://spiich.ai/help/chat-and-voice/what-spiich-does-on-its-own · 'What it does without asking' section, second paragraph

**Agent permissions** · Partly — Wide latitude with named stop conditions: it will not overwrite a populated CRM field it was not told about, act across a batch, or destroy a file without asking first.

> Overwriting a CRM field that already has a value. If you tell it explicitly to change a field, it changes it. If it would have to overwrite something you did not mention, it asks first.
> — https://spiich.ai/help/chat-and-voice/what-spiich-does-on-its-own · 'What it stops and asks about', first bullet

## Which models it runs on

**Model choice** · No — The only choice a user makes is how hard the assistant thinks (Fast, Balanced or Expert), with no model picker and no provider named in the product documentation.

> The tier chip in the composer sets how much reasoning a message gets. Your choice is remembered for the next message.
> — https://spiich.ai/help/chat-and-voice/chat-basics · Chat basics, 'Fast, Balanced and Expert' section

_Not established: Claude, GPT, Open models_

## Where you use it

**In a browser** · Yes — The hosted web app at app.spiich.ai is the full product, joined by a Chrome side panel, a macOS/Windows recorder and iOS and Android apps.

> Spiich runs in four places: the web app, a Chrome side panel, a desktop recorder and a mobile app.
> — https://spiich.ai/help/apps/which-app-to-use · Which Spiich app to use, summary line at the top

## Whose machine it runs on

**Self-hosted** · No — Hosted only, on the vendor's managed EU cloud; even its MCP client refuses servers on private or internal networks, so nothing runs on your own infrastructure.

> Spiich is hosted entirely within the EU on managed, enterprise-grade cloud infrastructure.
> — https://spiich.ai/trust · Trust centre FAQ, 'Where is Spiich hosted?'

**Open source** · No — Proprietary: the terms reserve every intellectual property right to the vendor and forbid reverse engineering, with open-source code appearing only as third-party dependencies.

> Spiich retains all rights to the Services including, without limitation, all intellectual property rights and know-how related to the Services
> — https://spiich.ai/terms · General terms and conditions, section 11.1 Intellectual Property

## What it costs to run

**How it meters** · Yes — Two meters at once: a per-user seat price plus a workspace credit balance drawn down per enrichment, briefing, agent run and generated table cell.

> Spiich meters the work its agents do in credits. Every workspace has one credit balance, and each thing the assistant does on your behalf draws from it.
> — https://spiich.ai/help/workspace/credits-and-usage · Credits and usage, opening paragraph

**Free tier** · Partly — A free trial starts at signup and needs a work email and a connected CRM, but no standing free plan exists and pages redirect to billing once it lapses.

> There is no separate plan step for Google sign-ups; your trial starts automatically once the company name is saved.
> — https://spiich.ai/help/getting-started/create-your-spiich-workspace · Create your workspace, 'Signing up with Google'

**API access** · Partly — You can drive an agent from your own stack through a generated webhook endpoint with HMAC-SHA256 signing, but no general public API is documented and the terms forbid programmatic extraction of output.

> A Webhook agent starts when an outside service posts JSON to a private URL Spiich generates for it.
> — https://spiich.ai/help/background-agents/agent-triggers · Triggers and schedules, 'Webhook trigger' section

**MCP server** · No — MCP runs one way only: Spiich consumes tools from customer-hosted servers, and publishes no MCP server of its own for another agent to query.

> Spiich supports the Model Context Protocol (MCP) as a client: point Spiich at a customer-hosted MCP server and its agents can use those tools and data sources alongside the standard integrations.
> — https://spiich.ai/ai-instructions · AI Instructions page, Integrations section, MCP paragraph

**Bring your own key** · Partly — You may bring your own enrichment provider key (Lusha, Wiza, Apollo, FullEnrich or Lemlist), but not your own model keys, inference endpoint or cloud.

> While a key is connected, enrichments run on that provider's credits instead.
> — https://spiich.ai/help/workspace/credits-and-usage · Credits and usage, 'Bring your own enrichment provider'

## Buying it for a team

**A company can buy it** · Yes — Sold to a company: one workspace with an admin who invites the team, self-serve checkout at signup, and invoice or custom-contract arrangements handled by the vendor.

> Some companies are set up on an invoice arrangement by the Spiich team instead of self-serve checkout.
> — https://spiich.ai/help/getting-started/create-your-spiich-workspace · Create your workspace, 'Invoice billing'

**Seat model** · Yes — One non-transferable licence per end user, priced per user per month, with Recorder and Task View granted as extra per-person seats an admin adds to the subscription.

> Each end user must have an individual license. The Subscriber shall assign each of its end users with an individual and specific license, which may not be shared, transferred or otherwise used
> — https://spiich.ai/terms · General terms and conditions, section 2.9

**Pooled budget** · Yes — One credit balance for the whole workspace, divided by optional team budgets and personal caps, with the stricter of the two winning on every action.

> Credits belong to the workspace, not to a person. Team budgets and personal caps are how you divide them up.
> — https://spiich.ai/help/workspace/credits-and-usage · Credits and usage, Limits, first bullet

**Admin controls** · Yes — Per-agent switches gate email, Slack, enrichment and table writes, Proposal mode stages every CRM change for review, and admins choose which CRM objects the agent may touch.

> Everything that leaves Spiich or spends money is off until you turn it on, per agent, in the form.
> — https://spiich.ai/help/background-agents/agent-permissions · What an agent is allowed to do, opening paragraph

**Audit log** · Partly — Agent runs, credit charges and each chat step are logged and readable in-app, but no admin-action audit log or log export is documented; CRM changes rely on the CRM's own trail.

> Agent activity logged and monitored for anomalies
> — https://spiich.ai/trust · Trust centre, 'How we protect your data', Monitoring & resilience

**Single sign-on** · No — Email and password plus OAuth for connected tools is all that exists today; SAML and OIDC are described as in progress, and two-factor is the only extra control.

> Not yet. We support email and password plus OAuth for connected integrations. SSO via SAML and OIDC is in progress and not currently available.
> — https://spiich.ai/trust · Trust centre FAQ, 'Does Spiich support SSO (SAML/OIDC)?'

## What happens to your code

**Opt out of training** · Yes — Nothing to opt out of: the contract and the trust page both state customer content is never used to train models, with zero-retention terms at every provider.

> Spiich will not use Subscriber's content to train AI models unless separately agreed.
> — https://spiich.ai/terms · General terms and conditions, section 11.3

**Data residency** · Yes — EU only for production data, application, database, inference and backups, with the single stated exception of unattributed web-search queries sent to US providers.

> All customer production data is stored and processed within the EU. The only exception is agent web search, which sends tenant-unattributed queries to US providers with zero data retention.
> — https://spiich.ai/trust · Trust centre, 'Data residency' section

**Getting out** · Partly — Export exists but is not self-serve: data is available for 30 days after termination through support or the DPA, and Tables has no export button at all.

> Customer data is available for export for 30 days after termination. After that window it is deleted, except for copies in routine backups
> — https://spiich.ai/trust · Trust centre FAQ, 'What happens to your data if you stop using Spiich?'

**Certifications** · Yes — ISO/IEC 27001:2022 certified with a named certificate and scope, plus CASA Tier 2 and a GDPR data processing agreement; SOC 2 is only a roadmap item.

> Spiich is ISO 27001 certified. Our certification is to ISO/IEC 27001:2022 under certificate 110826-1, issued in August 2026 by an accredited third-party certification body.
> — https://spiich.ai/trust · Trust centre FAQ, 'Is Spiich SOC 2 or ISO 27001 certified?'

## Provenance

Every fact above comes from the vendor. Nothing here is independently corroborated yet.

## Coverage elsewhere

None recorded. Every fact above comes from the vendor and is not independently corroborated yet.

## What changed

- 2026-09-15 — Capabilities · Commercial terms · Free tier · Price

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent Spiich, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth.

Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.