Chamelio

What it is

Chamelio is a platform for in-house legal teams that puts contract negotiation, a contract repository, request intake, and an AI agent on top of one shared record of the company’s own contracts, templates, playbooks, and negotiation history. The vendor calls it a “legal intelligence platform”. Buyers should read it as an AI-native replacement for a CLM: redlining against playbooks in Microsoft Word, automatic metadata extraction into a repository, intake and approval routing through Slack, Microsoft Teams, and Salesforce, and dashboards on legal workload.

The design choice that matters is statefulness. Most legal AI tools review each contract in isolation. Chamelio stores what the team has already agreed to and uses that record for the next review. When a sales rep asks in Slack for an NDA with a new vendor, the agent fills in the intake from the request, checks past deals with that counterparty, applies the playbook to score the risk, and routes the task to the right attorney with a memo. After signature it extracts terms and can trigger downstream actions, such as notifying finance about payment terms. Signing itself runs through DocuSign; Chamelio has no native e-signature.

The company was founded in 2024 and is based in New York. Its three founders came from the operator side, not from legal tech: CEO Alex Zilberman co-founded AnyVision, where he was COO; COO Gil Banyas was AnyVision’s general counsel, with 15 years in legal; CTO Gal Lellouche founded an AI company that Sage acquired. Funding: $10M before the Series A (a $5.7M seed led by Work-Bench, announced 27 January 2026, on top of an Emerge pre-seed), then a $26M Series A led by Entrée Capital on 22 September 2026, with Work-Bench, Emerge, and Bright Pixel Capital participating. That makes roughly $36M in total.

Why it shows up in Legal Ops stacks

• It consolidates point tools. One vendor covers Word redlining, the repository, intake, and workflows. For a legal team of two to fifteen people that bought a review tool, a CLM, and an intake form separately and now reconciles three sources of truth, that is the pitch.
• Migration is a product feature, not a services project. An AI-powered CLM Migrator moves contracts and metadata out of the incumbent system. The vendor says it takes days rather than months. That removes the most common reason teams stay on a CLM they dislike.
• The business stays in its own tools. Requesters work in Slack, Teams, or Salesforce and never log into a legal portal. The vendor lists 40+ integrations, including DocuSign, DocuSign CLM, Google Drive, HubSpot, and NetSuite.
• Traction among technology companies. About 100 teams at the seed; “hundreds” of customers and 4x ARR growth since the seed at the Series A. Named customers include Wiz, monday.com, Socure, AppsFlyer, Fiverr, Global-e, Cellebrite, and Lightricks. One Work-Bench case study reports about 15% more contracts completed with flat turnaround and no extra headcount. These are vendor and investor figures and have not been audited.

Pricing reality

There is no public price list. Chamelio sells through a demo, and there is no pricing page on the site. The Capterra listing gives a starting price of $6,000 per year on a usage-based model and says a free trial is available. That is the only published anchor. Third-party review sites put scaling teams at $12,000–18,000 a year and full legal departments at $25,000–45,000 plus implementation. Those bands come without a source, so treat them as a guess at the shape of the curve, not a quote.

For comparison, Vendr transaction data puts the average SpotDraft contract near $25,000 a year, and Ironclad deals usually start around $50,000. Chamelio’s published entry point is well below both. Whether the gap survives at 15 seats with migration included is the question to put to sales. Get three things into the order form: what counts as a usage unit (contracts, users, or agent runs), whether the CLM migration is included or billed as services, and the renewal cap. A company with 4x ARR growth and fresh funding will want to reprice in year two.

Best for

General counsel and legal ops leads at venture-backed technology companies with 2–15 lawyers. The fit is a team that negotiates a high volume of commercial paper (NDAs, MSAs, DPAs, vendor agreements), receives requests through Slack or Salesforce, and has either outgrown a patchwork of point tools or wants to leave a legacy CLM without a six-month re-implementation.

Not for you if you are a law firm: Chamelio is built for in-house teams. Not for you if you are a global enterprise with procurement-led contracting across thousands of suppliers and heavy ERP integration; Icertis or Sirion are built for that governance load. And not for you if you need native e-signature, a public API, or an MCP server. None of the three is published today.

Alternatives — and when to pick them instead

• Ironclad: the mid-market-to-enterprise CLM leader by installed base. Pick it when you need proven, configurable workflow depth and have the budget and the quarter it takes to implement.
• DocuSign IAM: the largest agreement platform by footprint. Pick it when signing volume drives the program and you want the CLM from the vendor that already holds your envelopes.
• SpotDraft: the closest head-to-head in the mid-market, with $92M raised. Pick it when you want a more mature product, Vendr pricing data to negotiate against, and a larger reference base.
• Ivo: the fastest-growing entrant in AI contract review, with a $55M Series B in January 2026. Pick it when review and redlining is the whole job and you already have a repository you are happy with.
• LegalOn: pick it when the bottleneck is review throughput on cross-border paper and you want prebuilt attorney playbooks rather than playbooks generated from your own history.
• GC AI: pick it when you want a broad in-house legal assistant at a transparent per-seat price and don’t need a repository or workflow engine.

Watch-outs

• Young vendor, fast growth. Founded in 2024 and scaling from about 100 to hundreds of customers in eight months. Support, onboarding, and the product roadmap can all bend under that load. Guard: ask for a named onboarding lead, a written migration timeline with acceptance criteria, and two reference customers who went live in the last 90 days.
• The “legal intelligence” is only as good as the history you migrate. Playbooks and risk scores draw on your past contracts. A thin or messy repository produces confident but generic output. Guard: during the pilot, check extraction accuracy on 50 of your own executed contracts before you let the agent auto-route or auto-approve anything.
• The autonomy boundary is configurable, so it can be set wrong. The vendor promotes autonomous handling of routine agreements with lawyer oversight as an option. Guard: start with auto-approval off, allow it only for one agreement type (such as inbound NDAs on your own paper), and review a weekly sample of what the agent decided.
• Security details sit behind the trust center. The site confirms SOC 2 Type II, encryption in transit and at rest, and hosting on AWS and GCP. It does not name the model providers or data regions. Guard: get the subprocessor list, the LLM providers, the data residency, and a no-training commitment written into the DPA.
• No public API or MCP server. Integrations are vendor-built connectors. Guard: if you plan to pull contract data into your own warehouse or an AI agent, make an export path (bulk and scheduled) a contractual requirement before signature.