Multiplayer by default
Bring teammates and agents into the same operational conversation.
- Roles and permissions
- Shared timeline
- Assignment
- Organization context
THE MULTIPLAYER AI PLATFORM FOR ENTERPRISE
Bring your team, company knowledge, and connected tools into one shared workspace. Specialized AI agents execute the work, people review the evidence and correct decisions, and approved workflows become reusable capabilities across the enterprise.
Build once. Improve together. Reproduce everywhere.
Felipe Matias opens an investigation and passes Contract CTR-2026-0417 to the Revenue Assurance agent. The agent queries CRM, billing, contracts, and email, collects the exports, and assembles an evidence bundle of 12 findings (3 critical), which travels to João Víctor. João opens the supporting files, corrects the renewal-date assumption, and the agent recalculates. An approval request goes to Felipe, who approves; Revenue_Assurance_Report.docx is generated and the workflow is reproduced across Finance, Legal, and Operations. Every document in the diagram opens into a full preview.

Felipe Matias
Operations Director
Revenue Assurance Agent
Specialist agent · AI

João Víctor
Financial Analyst

Felipe Matias
Operations Director
Revenue Assurance Agent
Specialist agent · AI

João Víctor
Financial Analyst
Felipe Matias opens an investigation and passes Contract CTR-2026-0417 to the Revenue Assurance agent. The agent queries CRM, billing, contracts, and email, collects the exports, and assembles an evidence bundle of 12 findings (3 critical), which travels to João Víctor. João opens the supporting files, corrects the renewal-date assumption, and the agent recalculates. An approval request goes to Felipe, who approves; Revenue_Assurance_Report.docx is generated and the workflow is reproduced across Finance, Legal, and Operations. Every document in the diagram opens into a full preview.
Building with Speco
Adapt Imóveis
tday.com
Adapt Imóveis
tday.com
Adapt Imóveis
tday.com
Adapt Imóveis
tday.comIn Speco, a conversation can contain people, agents, tools, evidence, approvals, generated files, and operational history. When the work succeeds, the whole process can be shared and reproduced — not buried inside one person's chat history.
THE MULTIPLAYER ROOM
Bring teammates, specialized agents, company data, and tools into one shared room. Review the evidence, correct assumptions, approve the outcome, and preserve the workflow for the next team.
Felipe Matias opens a new investigation. The Revenue Assurance agent and João Víctor join the room. The agent queries CRM, billing, contracts, and email evidence, then creates twelve findings and flags three critical. João opens the evidence and corrects an assumption — the renewal date is January 2027, not October 2026 — and the agent recalculates. Felipe approves the result, the room generates Revenue_Assurance_Report.docx, and the workflow is saved for the next team.
AI does not work alone here. People direct it, correct it, and approve it.
WHAT THE PRODUCT DOES
Bring teammates and agents into the same operational conversation.
Agents work with databases, company systems, documents, spreadsheets, and approved integrations.
Review what happened, fix assumptions, approve outcomes, and preserve the operational record.
Turn successful work into shareable and reproducible agent capabilities.
Produce professional DOCX, PDF, XLSX, and CSV files, structured data, and system updates.
FROM CONVERSATION TO COMPANY CAPABILITY
Every stage keeps a person in the loop. Nothing becomes a decision without someone approving it, and nothing worth repeating stays trapped in one person's history.
Start with the real task, files, context, and desired outcome.
Invite teammates and the right specialized agents into one shared room.
Agents query systems, inspect data, transform files, and execute approved tools.
See the evidence, assumptions, progress, and generated outputs before they become decisions.
Humans fix missing context or incorrect assumptions, and the agent applies the correction.
Opening evidence, commenting on findings, and validating or rejecting them ship today. In-thread correction that immediately re-runs the agent is in development.
Finalize reports, analyses, documents, and updates with human control.
Save the successful conversation as a reusable agent workflow for the next person, team, or organization.
When an agent workflow succeeds, your organization can share it, version it, and reproduce it for another team without rebuilding the process from scratch.
Configuration travels. Credentials never do.
Corrected by João Víctor
Approved by Felipe Matias
João VíctorFinancial AnalystFinance· reconnects own tools & data
SamuelLegal AssistantLegal· reconnects own tools & data
RafaelHR ManagerHR· reconnects own tools & data
Felipe MatiasOperations DirectorOperations· reconnects own tools & data
MaxSoftware EngineerEngineering· reconnects own tools & dataDestination teams reconnect their own integrations. Each branch runs independently — on its own data, under its own approvals.
PEOPLE
Speco is built for the roles that have to answer for a number after it ships. Every run ends the same way: a named person opens the evidence, corrects what is wrong, and approves what is right.

Felipe Matias
Operations Director

João Víctor
Financial Analyst

Max
Software Engineer

Rafael
HR Manager

Samuel
Legal Assistant
In every Speco run, the amber step is a person.
REAL FOOTAGE
No mockups in this section — both players run recordings of Speco producing real files and a real specialist agent being built, end to end.
15 seconds inside a Multiplayer AI workflow
RUNNING IN PRODUCTION
REVENUE ROOM
Every figure is detector-computed and reconciled. Open a finding to see the formula, the inputs, and the source records it came from — then mark it valid or send it back.
APPROVALS
Generated files sit in a review state until a named person approves them. Rejections carry a note, and both outcomes are written to the audit record.
REPRODUCTION
Reproducing an agent clones its safe configuration only. Private organization data stays isolated and connection secrets are never copied — the destination team reconnects its own.
BUILT AND RUNNING IN PRODUCTION
Speco's Revenue Assurance Agent connects company data, runs deterministic detectors, persists findings, shows evidence, and brings analysts into the same review room.
Production-verified demonstration using a persisted synthetic dataset.
Northwind Freight
$36,000
Formula
(active_seats - billed_seats) * unit_price_cents * months50 unbilled seats × $60.00 × 12 months
ULTRADOC PIPELINES
Speco agents do not stop at an answer. They assemble structured data, apply organization templates, run document pipelines, request human review, and generate professional files ready for real operations.
Complete UltraDoc pipelines are included with Enterprise.
Legal case package
case-package.pdf
MTR-2026-118
Financial analysis workbook
leakage-model.xlsx
ACC-1042
Executive revenue report
Revenue_Assurance_Report.docx
run_8fa2c1
Insurance renewal priority
renewal-priority.csv
POL-4471-A
WORKFLOWS
Example workflows, not customer deployments. Each one keeps the specialist in control of the judgment and gives the agent the assembly.
Legal teams
Specialized agents assemble, verify, and format case material while your lawyers keep every judgment call.
Lawyers remain in control while specialized agents assemble, verify, and format the work. Speco does not exercise legal judgment.
Example workflow
Financial groups
Connect billing and CRM records, reconcile inconsistencies, and produce reports analysts can actually check.
Analysts can inspect formulas, evidence, and assumptions before approving any result.
Example workflow
Insurance companies
Surface patterns across policy, claims, engagement, and commercial data so account teams can act on the strongest ones.
Agents surface patterns while humans validate the commercial context. Speco does not make underwriting decisions.
Example workflow
Operations and consulting
Run the same high-value engagement again without rebuilding the process from scratch each time.
Every deliverable passes a named reviewer before it leaves the room.
Example workflow
CONTROL
What follows is what Speco does today. We do not list certifications we do not hold.
Organization-isolated data
Each organization's data, agents, and connections are scoped to that organization.
Role-based permissions
Owner, admin, and member roles govern who can change what.
Auditable activity
Operational events are recorded and reviewable.
Human approvals
Generated outputs can require explicit sign-off before they are final.
Connection-level access
Agents reach systems through connections your organization configures.
Reproduction without copied credentials
Sharing an agent moves configuration, never secrets or organization data.
Reviewable evidence
Findings carry their formulas, inputs, and source references.
Organization-owned billing
The company owns the plan, the seats, and the usage.
Speco does not currently hold SOC 2, ISO 27001, HIPAA, or PCI certification, and does not claim to.
ENTERPRISE
Employees use free Speco accounts and join through an organization invitation. Access, agents, knowledge, billing, permissions, and usage belong to the organization — not to each employee's personal subscription.
Manages billing, the plan, and organization settings.
Manages teams, members, and workflows where permitted.
Participates in authorized work — runs agents, reviews evidence, approves outcomes.
Creates a free Speco account and joins through the organization's invitation.
PRICING
Start free. Pay when your organization scales.
Free
Free/ forever
Explore the platform. Build your first AI agent.
Starter
$20/ per month
Build and share unlimited AI agents with a small team.
Growth
$100/ per month
Scale reusable AI agents across a growing organization.
Enterprise
Starting at $500/month + usage
Deploy specialized AI workers and complete document and operational pipelines across your enterprise.
Need more than the listed capacity? Contact the Speco team
The same prices worldwide — every plan is billed in USD.
Invited employees use free Speco accounts
Organization access is provided by the company's plan. Nobody on your team needs a personal subscription to participate.
Unlimited agents does not mean unlimited compute
Paid plans do not cap how many agents you create. Execution, model usage, storage, and premium tools remain governed by your plan's included capacity and applicable usage billing.
| Capability | Free | Starter | Growth | Enterprise |
|---|---|---|---|---|
| Organization members | 1 | 5 | 25 | 100 |
| Unlimited agents | Not included | Included | Included | Included |
| Shareable agents | Not included | Included | Included | Included |
| Reproducible agents | Included | Included | Included | Included |
| MCP endpoints | Not included | Not included | Included | Included |
| Human approvals | Included | Included | Included | Included |
| Audit logging | Not included | Not included | Not included | Included |
| Revenue Assurance Agent | Not included | Not included | Not included | Included |
| UltraDoc pipelines | Not included | Not included | Not included | Included |
| Advanced evaluations | Not included | Not included | Included | Included |
| SSO / SAML | Not included | Not included | Not included | Included |
| Priority support | Not included | Not included | Included | Included |
A shared environment where people and specialized agents work on the same task together. Agents use your systems and data, people review the evidence and approve outcomes, corrections improve the work, and a successful conversation can be saved as a capability the organization reuses. The alternative — everyone running their own private chats — leaves nothing behind.
No. A chatbot returns an answer to one person and the context disappears. In Speco the work is owned by the organization: agents call approved tools against your data, outputs are real files, a named person approves them, the activity is recorded, and the whole workflow can be reproduced for another team without rebuilding it.
No. Employees create free Speco accounts and join paid organizations through invitations. Their access comes from the organization's plan.
Paid plans do not impose a count limit on agent objects. Execution, model usage, storage, and premium tools remain subject to your plan's included capacity or usage billing — unlimited agents is not unlimited compute.
Yes. You upload documents and configure connections to systems such as billing records, CRM accounts, contract stores, and data warehouses. Agents reach those systems through connections your organization sets up, scoped to your organization.
Today you can open the evidence behind any finding, comment on it, validate or reject it, and approve or reject generated files with a note — all of which is recorded. Correcting an assumption in-thread and having the agent immediately recalculate is in development, and it is labelled as a preview wherever we show it.
An authorized team can recreate an approved agent's configuration and start from it. Reproduction copies configuration and provenance only — private organization data is not copied and connection credentials are never transferred. The destination team reconnects its own integrations.
DOCX, PDF, XLSX, CSV, PPTX, and structured JSON, plus updates written back to connected systems. Complete UltraDoc document-generation pipelines are included with Enterprise.
Enterprise is priced "Starting at $500/month + usage" and includes 100 organization members by default. Custom capacity is available through sales.
None yet, and we will not claim otherwise. What exists today is organization-isolated data, role-based permissions, auditable activity, human approvals, connection-level access control, and reproduction that never copies credentials. If a certification is a requirement for you, talk to us about timelines rather than assuming.
Build specialized agents, connect company context and tools, review the work with your team, and reproduce what works across the organization.
Felipe Matias opens a revenue investigation. The Revenue Assurance agent queries billing and CRM records and returns twelve findings. João Víctor reviews the evidence and corrects an assumption; the agent recalculates. Felipe approves the result, the agent generates Revenue_Assurance_Report.docx, and the workflow is reproduced to three other teams.