Respell

Name: Respell
Brand: Respell

AI Native

Respell is a no-code platform that builds multi-step agent-style automation workflows called Spells by combining large language model calls, application integrations, human-in-the-loop review steps, and optional API execution.

Est 2022|Valuation $20M|Raised $4.7M|8 Ref Customers

LinkedIn 2K|Web traffic 6K|FTEs 3

MarketsWorkflow Automation

Published Oct 9, 2026

01Common complaints

1) If a stable, long-term standalone platform is required - The vendor previously announced a standalone shutdown and team transition. Unless current status and continuity guarantees are validated, avoid net-new adoption based on the standalone product. 2) If procurement requires a large corpus of verified customer reviews - Publicly surfaced review volume was limited in the materials reviewed; organizations that require extensive third-party review evidence should consider alternatives. 3) If mature iPaaS governance is a default requirement - For organizations needing established enterprise governance patterns out of the box, consider enterprise-focused iPaaS providers. 4) If Salesforce-native agent functionality is the primary requirement - Given the team transition, evaluate the acquiring vendor's native agent platform for integrated capabilities within that ecosystem.

Deal disqualifiers (poor fit)

Strict requirement for on-premise deployment or documented data residency guarantees not present in public materials
Procurement processes requiring extensive third-party review validation and referenceability when such evidence is limited
High sensitivity to vendor lifecycle risk given the prior team/product transition

Current limitations acknowledged by the vendor

Integration references in vendor materials indicate continued work on connector coverage and depth.

Product continuity limitation

The vendor's prior announcement of a standalone shutdown and team transition indicates a significant roadmap and support pivot.

Security/compliance gaps (public documentation)

Absence of public documentation for ISO 27001/27017/27018, HIPAA, and PCI DSS in the materials reviewed
Data residency and specific hosting options were not documented in public materials

02Why they buy

Differentiators (based on product materials)

A workflow model called "Spells" that combines multi-step logic, LLM calls, app triggers/actions, and human review steps in a unified builder
Support for combining app integrations with LLM-driven decision or synthesis steps and optional API execution
Vendor-stated SOC 2 Type II compliance posture and security-focused messaging (vendor assertions to be validated by procurement)

Where competitors have clear advantages

Zapier: integration breadth and ecosystem maturity
Workato/Nintex/UiPath: enterprise automation track record and governance capabilities
The acquiring vendor's agent platform: tighter native integration with that vendor's ecosystem, which may be beneficial for organizations already invested there

03Field reports

Important note on review availability

Standard review platforms did not show a substantial corpus of end-user review quotes in the materials captured for this report. Coverage on major review platforms appeared limited.

Given the limited footprint on review platforms, this section relies primarily on vendor-published materials, product documentation, third-party directories, and automated site trust assessments. These sources have different evidentiary value than verified end-user reviews.

Available vendor assertions

The vendor has made claims about workflow volume and customer reach in its own blog and marketing materials; these assertions were not accompanied by independently verifiable methodologies in the sources reviewed.
Product documentation explains the concept of "Spells" as workflows composed of steps and describes manual and trigger-driven spell types.

Common themes inferred from product materials and directories

Emphasis on multi-step agent-style workflows rather than single prompt chains
A stated set of integrations (the vendor materials referenced a large integration set; details on depth and coverage require validation)
Security-oriented messaging including SOC 2 Type II and controls for PII and prompt-injection prevention, as presented by the vendor

Observations from third-party signals

Third-party listings and site-trust scanners provided mixed signals about product continuity and site trustworthiness; these are signals to consider in procurement evaluations but are not direct indicators of product quality or performance.

Why customers may choose or leave

There was limited independent customer testimony in the materials reviewed to determine precise reasons for adoption or churn. The vendor's announced transition is a likely driver of churn or migration for some customers, but it is an organizational lifecycle event rather than a purely product-quality issue.

Vendor-published outcomes

The vendor has published assertions of operational outcomes and usage volumes. The captured materials did not include named customer references, independent verification, or detailed case study methodologies.

Third-party case studies

No third-party case studies specific to this product were located in the reviewed materials.

Critical evaluation: The absence of named reference customers and independently verifiable ROI metrics increases procurement risk. If the product or its successor is under consideration, request reference customers, an ROI model with assumptions, and examples of production-grade workflows demonstrating guardrails, approvals, and auditability.

04Best fit

Company sizes

Small and medium businesses through mid-market organizations appear to be primary targets based on product design and pricing posture.
Enterprise adoption is possible but depends on governance, security controls, and procurement processes.

Likely strongest verticals

Sales and revenue operations (lead research, outreach, enrichment)
Marketing operations (content workflows)
Recruiting and people operations (candidate research and screening workflows)

Roles/personas

Decision makers: Heads of Operations, RevOps leaders, and IT leads responsible for governance
End users: operations analysts, sales operations analysts, marketing operations staff

Qualification criteria (good fit)

Organizations with numerous repeatable "knowledge plus action" workflows (for example: research → decision → system update)
Willingness to standardize processes and implement approvals and guardrails
Need for a combination of app triggers/actions and LLM-based reasoning

05The pitch

What the product does (objective value proposition)

Respell is a no-code platform for building multi-step agent-style automation workflows, called "Spells." These workflows can combine: - large language model (LLM) calls (with support for multiple models) - application integrations (triggers and actions) - human-in-the-loop review steps - optional API execution to run workflows programmatically In practical terms, Respell is presented as a tool to convert repeatable business processes (research, outreach, data enrichment, content creation, CRM updates, etc.) into automated workflows that incorporate LLM reasoning rather than solely transferring data between applications.

Target market and market positioning

Respell targets: - operations teams (Ops / RevOps / Sales Ops / Growth) seeking workflow automation with LLM reasoning - business teams that want low- or no-code automation extending beyond standard integration platforms - startups and mid-market companies seeking agent-like workflows without building custom infrastructure It is positioned as an "agentic workflow orchestration" product, related to iPaaS/BPM/RPA categories and distinct from single-turn chatbot builders.

Get a comprehensive analysis of Respell including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 9, 2026

01Common complaints

If a stable, long-term standalone platform is required

The vendor previously announced a standalone shutdown and team transition. Unless current status and continuity guarantees are validated, avoid net-new adoption based on the standalone product.

If procurement requires a large corpus of verified customer reviews

Publicly surfaced review volume was limited in the materials reviewed; organizations that require extensive third-party review evidence should consider alternatives.

If mature iPaaS governance is a default requirement

For organizations needing established enterprise governance patterns out of the box, consider enterprise-focused iPaaS providers.

If Salesforce-native agent functionality is the primary requirement

Given the team transition, evaluate the acquiring vendor's native agent platform for integrated capabilities within that ecosystem.

Deal disqualifiers (poor fit)

Strict requirement for on-premise deployment or documented data residency guarantees not present in public materials
Procurement processes requiring extensive third-party review validation and referenceability when such evidence is limited
High sensitivity to vendor lifecycle risk given the prior team/product transition

Current limitations acknowledged by the vendor

Integration references in vendor materials indicate continued work on connector coverage and depth.

Product continuity limitation

The vendor's prior announcement of a standalone shutdown and team transition indicates a significant roadmap and support pivot.

Security/compliance gaps (public documentation)

Absence of public documentation for ISO 27001/27017/27018, HIPAA, and PCI DSS in the materials reviewed
Data residency and specific hosting options were not documented in public materials

02Why they buy

Differentiators (based on product materials)

A workflow model called "Spells" that combines multi-step logic, LLM calls, app triggers/actions, and human review steps in a unified builder
Support for combining app integrations with LLM-driven decision or synthesis steps and optional API execution
Vendor-stated SOC 2 Type II compliance posture and security-focused messaging (vendor assertions to be validated by procurement)

Where competitors have clear advantages

Zapier: integration breadth and ecosystem maturity
Workato/Nintex/UiPath: enterprise automation track record and governance capabilities
The acquiring vendor's agent platform: tighter native integration with that vendor's ecosystem, which may be beneficial for organizations already invested there

03Field reports

Important note on review availability

Standard review platforms did not show a substantial corpus of end-user review quotes in the materials captured for this report. Coverage on major review platforms appeared limited.

Available vendor assertions

The vendor has made claims about workflow volume and customer reach in its own blog and marketing materials; these assertions were not accompanied by independently verifiable methodologies in the sources reviewed.
Product documentation explains the concept of "Spells" as workflows composed of steps and describes manual and trigger-driven spell types.

Common themes inferred from product materials and directories

Emphasis on multi-step agent-style workflows rather than single prompt chains
A stated set of integrations (the vendor materials referenced a large integration set; details on depth and coverage require validation)
Security-oriented messaging including SOC 2 Type II and controls for PII and prompt-injection prevention, as presented by the vendor

Observations from third-party signals

Third-party listings and site-trust scanners provided mixed signals about product continuity and site trustworthiness; these are signals to consider in procurement evaluations but are not direct indicators of product quality or performance.

Why customers may choose or leave

There was limited independent customer testimony in the materials reviewed to determine precise reasons for adoption or churn. The vendor's announced transition is a likely driver of churn or migration for some customers, but it is an organizational lifecycle event rather than a purely product-quality issue.

Vendor-published outcomes

The vendor has published assertions of operational outcomes and usage volumes. The captured materials did not include named customer references, independent verification, or detailed case study methodologies.

Third-party case studies

No third-party case studies specific to this product were located in the reviewed materials.

04Best fit

Company sizes

Small and medium businesses through mid-market organizations appear to be primary targets based on product design and pricing posture.
Enterprise adoption is possible but depends on governance, security controls, and procurement processes.

Likely strongest verticals

Sales and revenue operations (lead research, outreach, enrichment)
Marketing operations (content workflows)
Recruiting and people operations (candidate research and screening workflows)

Roles/personas

Decision makers: Heads of Operations, RevOps leaders, and IT leads responsible for governance
End users: operations analysts, sales operations analysts, marketing operations staff

Qualification criteria (good fit)

Organizations with numerous repeatable "knowledge plus action" workflows (for example: research → decision → system update)
Willingness to standardize processes and implement approvals and guardrails
Need for a combination of app triggers/actions and LLM-based reasoning

05The pitch

What the product does (objective value proposition)

Respell is a no-code platform for building multi-step agent-style automation workflows, called "Spells." These workflows can combine:

large language model (LLM) calls (with support for multiple models)
application integrations (triggers and actions)
human-in-the-loop review steps
optional API execution to run workflows programmatically

In practical terms, Respell is presented as a tool to convert repeatable business processes (research, outreach, data enrichment, content creation, CRM updates, etc.) into automated workflows that incorporate LLM reasoning rather than solely transferring data between applications.

Target market and market positioning

Respell targets:

operations teams (Ops / RevOps / Sales Ops / Growth) seeking workflow automation with LLM reasoning
business teams that want low- or no-code automation extending beyond standard integration platforms
startups and mid-market companies seeking agent-like workflows without building custom infrastructure

It is positioned as an "agentic workflow orchestration" product, related to iPaaS/BPM/RPA categories and distinct from single-turn chatbot builders.

Get a comprehensive analysis of Respell including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →