Outmarket says it has raised a $34.5 million Series B led by SignalFire, a round that comes only months after its $17 million Series A and signals continued investor appetite for AI tools that sit inside insurance agencies rather than beside them. TechCrunch reported the planned funding announcement on September 28, 2026, while Outmarket’s own release said the company has already broadened its workflow product and reached more than 300 agency customers. The evidence supports a clear story: insurance AI is moving from generic document automation toward operational software for the people who quote, bind and service policies.

The company’s pitch is built around a simple bottleneck. Vishal Sankhla, Outmarket’s CEO and co-founder, told TechCrunch that most insurance is still sold through human agents and that the work remains heavily manual, especially in commercial lines. Those policies can involve a large range of coverage types and custom paperwork, which means brokers and account managers spend time reading contracts, matching terms and filling out forms. That is the job Outmarket is trying to compress with AI.

According to Outmarket’s press release, the platform connects to agency management systems and combines structured data with unstructured policy, contract and client records. The new Certificates workflow is the best example of how that works in practice. Outmarket says the tool reads a client contract or lease, extracts insurance requirements, checks them against existing policies, flags gaps and produces the completed certificate with the proper holders and endorsements attached. In other words, the software is not just drafting language; it is acting as a control layer between agency records and the final document that goes to a customer, landlord or carrier.

That matters because certificates are one of the most routine and error-sensitive tasks in an agency. A missed requirement can create errors-and-omissions exposure, while slow turnaround forces staff to stop higher-value work to chase paperwork. If Outmarket’s system works as described, the practical benefit is shorter turnaround, less rekeying and fewer mistakes in documents that often must be issued quickly. Outmarket says early customers are issuing certificates in minutes and seeing fewer errors, but those performance claims come from the company itself rather than independent testing.

The funding round also suggests the company is trying to scale beyond a single workflow. Outmarket says it now has over 300 agency customers, including more than 25% of the top 100 insurance agencies, and that it recently surpassed 10,000 active users. Those are vendor-reported adoption numbers, not independently verified market-share data, but they point to a product that has found a real use case inside a conservative industry. The company also says it plans to extend capabilities to carriers later this year, which would matter because the value of these systems rises when agencies and insurers can move information without manual handoffs.

The distinction between a workflow tool and a decision-maker matters for agencies evaluating it. The release describes software that checks certificate requirements against policy data and flags gaps, while the agency still owns the insurance advice and final document. A useful deployment test would compare the same team’s certificate turnaround, correction rate and escalations before and after adoption. The cited sources give vendor adoption claims, but no independent before-and-after study of those outcomes.

The limit is equally important. Outmarket appears strongest where work is repetitive, document-heavy and tied to an agency management system. It is less clear how far the same model goes when source documents are incomplete, requirements conflict or human judgment is the deciding factor. That boundary is what will determine whether Outmarket becomes a useful point tool for agency operations or a broader intelligence layer for insurance distribution.

Sources: TechCrunch; Outmarket AI / PR Newswire

Watch whether agencies publish measurable certificate turnaround times and error reductions after AMS-connected workflows go live, because those operational numbers will show whether the product is saving time or just shifting work.