top of page

Outmarket Series B Arrives Four Months After Its Prior Round

Sep 29
13 min read

Outmarket raised a $34.5 million Series B only four months after announcing its previous round, an unusually fast return to investors. The Outmarket Series B follows a $17 million Series A and turns a routine funding story into a test of demand for insurance workflow automation.

SignalFire led the new round. Fika Ventures, Permanent Capital Ventures, TTV Capital, and Dash Fund also participated, according to the company’s funding announcement. The same announcement says more than 300 agencies and 10,000 users now use Outmarket.

The company is not trying to replace insurance brokers with a general-purpose chatbot. It wants to automate the document-heavy work surrounding quote comparisons, policy checks, proposals, certificates, loss runs, and account setup.

That distinction matters. Insurance agencies operate across carrier portals, agency management systems, email, spreadsheets, and document repositories. Automating work across those systems demands more than generating plausible text.

The funding therefore sets up a clear contest. Outmarket is betting that a broad insurance automation platform can become the operating layer for agency work. The opposing view favors narrower tools, existing agency systems, and human review around each consequential decision.

The Outmarket Series B Follows Rapid Agency Adoption

The speed of the financing matters more than the round’s size.

Outmarket announced its $17 million Series A on May 13, 2026. That financing brought its reported total funding to $21.7 million and followed a $4.7 million seed round.

The company returned with its Series B in September, about four months later. Outmarket’s founders said they had not expected to raise again so soon.

They attributed the decision to customer adoption after the Series A. Existing customers reportedly expanded the product across more teams, business lines, and workflows. Additional agencies also began using it in daily operations.

Outmarket reported more than 250 agency partners when it announced the Series A. Its latest disclosure raises that figure above 300 agencies. That represents at least 50 additional agencies, although the company has not published a precise comparison date or customer cohort.

The startup also says its customers include more than one-quarter of the 100 largest United States brokers. It did not identify every broker or disclose how extensively each one uses the platform.

Those qualifications are important. Customer counts can include organizations with very different seat totals, contract values, and deployment depths. A limited team pilot does not carry the same weight as adoption across an entire brokerage.

Still, a second institutional round within four months is a meaningful signal. Investors typically require evidence that new capital can accelerate an opportunity rather than simply extend a runway.

The new round also changes the scale of Outmarket’s financial position. Combining the previously reported $21.7 million with the Series B implies roughly $56.2 million in announced funding.

That figure should not be confused with revenue or valuation. Outmarket has not publicly disclosed either metric for the new round.

The Series B was led by SignalFire, which also participated in the Series A. The other named investors returned as well, suggesting existing backers increased their exposure after observing recent adoption.

That pattern offers stronger support than a round composed entirely of new investors. Existing investors had access to private operating information before making another commitment.

However, financing remains an investor judgment, not independent product validation. The round does not establish that Outmarket’s software performs every workflow more accurately than competing products or experienced agency staff.

The evidence available to the public remains mostly company-reported. The original Series B coverage confirms the financing and its focus on automating insurance paperwork.

Outmarket’s May announcement provides a useful baseline. That Series A record identified Permanent Capital Ventures as the lead investor and listed SignalFire among the participants.

The lead role changed in the Series B, but the investor group remained largely consistent. That continuity supports Outmarket’s account of a fast follow-on round driven by operating momentum.

It also raises the stakes. With more capital and higher expectations, the company must now convert reported adoption into durable, repeatable usage.

Insurance Paperwork Is the Product Opportunity

Outmarket is targeting the repetitive work around insurance advice, not the relationship itself.

A commercial insurance account can generate a dense trail of submissions, quotes, policies, endorsements, loss histories, certificates, emails, and renewal documents. Staff must move information among systems while checking whether details remain consistent.

That work is tedious, but it is not trivial. A missed exclusion, incorrect limit, or outdated document can affect the client’s understanding of its coverage.

Outmarket says its platform handles quote comparisons, policy checking, coverage analysis, benefits comparisons, certificates, loss runs, and agency management system setup. Its Proposal Builder reportedly produces thousands of client proposals each month.

A proposal builder turns policy and quote information into a document that a broker can present to a client. The underlying task involves gathering details, normalizing different carrier formats, and displaying meaningful differences.

Policy checking presents another opportunity. Agency employees often compare an issued policy with the coverage requested or quoted, looking for discrepancies that require attention.

Loss runs summarize an insured organization’s claims history. Brokers use them during submissions, renewals, and negotiations, but obtaining and organizing those documents can require repeated follow-up.

These examples explain why insurance automation attracts investors. Many tasks involve reading, comparing, extracting, and transferring information, all areas where current AI systems can assist.

They also explain why insurance presents a harder challenge than ordinary office writing. The source material contains specialized terms, inconsistent layouts, and legally significant details.

Outmarket’s product strategy treats these workflows as connected parts of one platform. Its founders argue that agencies want a system covering a broad surface of daily work, not isolated AI features.

The company says its software connects with existing agency management systems, commonly called AMS platforms. An AMS stores customer, policy, carrier, activity, and document information for an agency.

This integration-first approach recognizes an operational reality. Most established brokerages cannot abandon their core systems simply because a new AI interface offers better document analysis.

Outmarket must work around those systems, read their data, and return usable results without disrupting existing records. Integration quality therefore becomes as important as model quality.

The latest funding announcement also introduced Certificate Hub. A certificate of insurance summarizes selected policy information for a third party requesting evidence of coverage.

Certificates are common in construction, property management, logistics, and vendor relationships. A business might need one before entering a jobsite or beginning work for a client.

The workflow appears repetitive because many requests use familiar forms and policy details. Yet certificates can create errors-and-omissions exposure when staff mishandle requirements, endorsements, holders, or coverage information.

Outmarket says Certificate Hub will automate parts of that process. The announcement does not provide enough detail to determine which steps remain subject to human approval.

That unanswered question sits at the center of the broader opportunity. Agencies want relief from administrative work, but they cannot delegate accountability along with the data entry.

The best deployment model will likely separate routine extraction from consequential judgment. Software can prepare comparisons and draft documents, while licensed professionals resolve ambiguity and approve client-facing conclusions.

This division would make AI a capacity tool rather than an autonomous broker. It could let experienced staff spend more time advising clients and less time moving data.

Broad Platforms Are Challenging Point Solutions

Outmarket’s main competitive bet is breadth across agency workflows rather than dominance in one narrow task.

Insurance technology has no shortage of specialized products. Different vendors target submissions, renewals, policy checking, carrier appetite, commissions, accounting, certificates, and client communication.

A point solution concentrates on one workflow. It can offer deeper controls for that task, but every additional product creates another integration, login, data transfer, and vendor relationship.

Outmarket is pursuing the opposite model. It wants agencies to use one platform across proposals, comparisons, checking, certificates, and related operational work.

That approach can compound value if each workflow improves the next one. Information extracted during a quote comparison might support a proposal, policy check, or renewal review later.

A shared data layer can also reduce repeated document processing. The same account information should not require fresh extraction every time a different team begins a task.

However, breadth creates its own product burden. A platform covering many workflows must support different lines of business, carrier formats, agency procedures, permissions, and review standards.

The company also competes with established agency management systems. Those vendors already sit near critical records and can add AI features without asking customers to adopt another operating layer.

Applied Systems, Vertafore, and other insurance software providers have longstanding agency relationships. Their installed position offers distribution, proprietary context, and integration advantages.

Specialists present a different challenge. Quandri, for example, focuses heavily on renewal automation and describes workflows that analyze policies, identify risks, and support client outreach.

The companies do not overlap perfectly. Outmarket emphasizes commercial insurance workflows and a broad product surface. Quandri emphasizes automated renewal work, particularly in personal lines.

That difference illustrates a basic buyer decision. An agency can select the broadest platform available, or it can assemble focused products around its highest-friction workflows.

Broad platforms promise fewer handoffs. Focused vendors can argue that their narrower systems go deeper, require less manual initiation, or better match a particular book of business.

Outmarket’s founders have criticized what they characterize as point solutions presented as full insurance platforms. That is a company position, not an independent market verdict.

The competitive evidence will come from customer behavior. Agencies will reveal whether they consolidate workflows within Outmarket or keep specialized alternatives beside it.

The answer might vary by brokerage size. A large organization can support several specialized products, internal integrations, and dedicated technology teams.

A smaller agency may prefer one vendor that handles multiple tasks. It has fewer resources for configuring, monitoring, and reconciling a collection of tools.

Large brokerages also bring demanding security, governance, and audit requirements. Winning an initial team can be easier than securing an enterprise-wide deployment.

That makes Outmarket’s claim about top brokers noteworthy but incomplete. The critical issue is not simply whether a broker appears on the customer list.

Investors and competitors will watch how many departments, users, and workflows each customer activates. Expansion within existing accounts would support the platform thesis more strongly than logo growth alone.

Retention matters too. Insurance workflows repeat across renewals, endorsements, and certificates, giving software vendors an opportunity to become deeply embedded.

The same repetition makes replacement disruptive. Once an agency configures integrations and review procedures, changing vendors may require extensive retraining and validation.

Outmarket’s rapid fundraising gives it resources to pursue that embedded position. Competitors still have room to challenge the company on workflow depth, automation levels, accuracy, or implementation demands.

The Mechanism Depends on Integration and Review

The valuable mechanism is controlled workflow automation, not unrestricted text generation.

A general AI model can summarize a policy, but an agency platform must do much more. It needs to locate the correct documents, identify relevant fields, compare versions, and preserve account context.

It must also connect an output to the appropriate customer, policy period, carrier, and workflow. A fluent answer attached to the wrong account would create more work, not less.

That requirement favors products built around structured workflows. The system needs defined inputs, approved data sources, validation rules, user permissions, and an escalation path.

Outmarket’s platform appears designed around those operational boundaries. The company describes connections among agency management systems, carrier portals, repositories, email, and spreadsheets.

The practical workflow might begin with document ingestion. Software extracts policy details, organizes them into a common structure, and flags missing or inconsistent information.

A comparison layer can then identify differences among quotes or between requested coverage and an issued policy. The platform can draft a client proposal from those structured findings.

A human reviewer remains responsible for interpreting ambiguous language and confirming recommendations. The software saves time by preparing the evidence and focusing attention.

This process offers more defensible value than asking a chatbot open-ended questions about coverage. It limits the model’s role and keeps decisions inside a traceable workflow.

Traceability is essential in insurance. An agency must know which document supported an output, who reviewed it, and what changed before information reached a client.

The latest announcement does not publish Outmarket’s accuracy rates, exception rates, or review requirements. It also does not identify the models used for individual features.

That absence does not mean the system lacks controls. It means public reporting cannot yet establish how those controls operate across products and customer environments.

Product evaluations should therefore examine the full workflow. A high extraction score provides little comfort if users cannot trace the result or catch an exception.

Buyers should also distinguish between time saved during document preparation and time added during verification. Automation only improves capacity when total effort falls without unacceptable risk.

Outmarket says its products fit the way brokers already work. That claim will depend on configuration demands, integration reliability, and the number of exceptions requiring manual resolution.

Legacy data presents another challenge. Agency records can contain inconsistent naming, incomplete fields, duplicated accounts, and documents stored outside the expected location.

AI does not automatically repair those conditions. It can misread the environment faster if the underlying information remains poorly governed.

The platform approach offers one potential answer. A shared data layer can normalize information and preserve context across several workflows.

It also concentrates risk. When one platform participates in proposals, checking, certificates, and account setup, a faulty integration can affect several processes.

That tradeoff makes governance part of the product rather than an administrative afterthought. Agencies need permissions, logs, version history, and clear responsibility for every automated action.

The strongest implementations will likely use risk-based automation. Low-risk extraction and drafting can proceed quickly, while unusual or consequential cases receive human review.

Certificates illustrate this model. Software can retrieve policy information and prepare a document, but exceptions involving endorsements or unusual requirements need escalation.

The opportunity is not complete autonomy. It is a system that reduces repetitive work while making the remaining human decisions clearer and better documented.

What the Funding Numbers Do Not Prove

The Outmarket Series B validates investor interest, but it does not settle accuracy, economics, or long-term adoption.

The company has disclosed agency counts, user counts, top-broker penetration, and proposal volume. Those figures show activity, yet they leave several important questions unanswered.

Outmarket has not publicly disclosed annual recurring revenue, customer retention, deployment costs, or the proportion of users active during a typical month.

It has also not published comparative accuracy data for policy checks, quote analysis, or certificates. Buyers therefore need their own tests using representative documents and exception cases.

Customer references can provide useful evidence, but published testimonials tend to feature successful deployments. They rarely show abandoned pilots or teams that kept older processes.

The platform’s breadth adds another uncertainty. A customer counted as an Outmarket agency might use one feature heavily while ignoring the rest.

That outcome could still support a viable business. It would provide weaker evidence that Outmarket is becoming a comprehensive operating layer.

The speed between rounds can be interpreted in more than one way. It may reflect unusually strong demand and an opportunity to invest ahead of competitors.

It can also reflect investor urgency before the market resolves. Private financing often prices expected growth rather than established profitability.

The latest round included repeat investors, which strengthens the adoption narrative. Yet those investors share an incentive to present the company’s trajectory positively.

Independent validation should come from measurable operating results. Useful indicators include renewal rates, workflow expansion, processing time, exception frequency, and verified error reduction.

Risk becomes especially important when automation touches client-facing insurance documents. An incorrect comparison can distort a purchasing decision.

A flawed policy check can miss a discrepancy. A certificate can create confusion when it appears to promise coverage that the underlying policy does not provide.

These risks do not argue against automation. Manual processes also produce errors, delays, and inconsistent records.

The relevant comparison is controlled automation against the real human process, not against an imaginary process with perfect accuracy.

Agencies should evaluate where the software reduces risk and where it creates new failure modes. The answer can differ across workflows.

Document extraction might offer an immediate benefit because every result remains visible for review. An automated client communication carries greater risk if it leaves without approval.

The same distinction applies to system actions. Drafting an AMS entry differs from committing that entry automatically.

Outmarket must demonstrate that its controls scale with adoption. A pilot involving expert reviewers can succeed even when the workflow would strain under thousands of daily transactions.

The company also faces implementation risk. Each brokerage has its own document conventions, carrier relationships, service structure, and appetite for automation.

A platform can either force standardization or absorb local variations. The first approach creates organizational resistance, while the second increases product complexity.

Security and confidentiality remain central. Insurance agencies hold sensitive business, personal, claims, and policy information.

Customers need clear answers about data retention, model training, access controls, incident response, and vendor oversight. A broad platform increases the amount of information entrusted to one provider.

None of these issues invalidates the funding thesis. They define what Outmarket must prove after raising capital faster than most enterprise software companies revisit the market.

The company’s public adoption numbers have moved quickly. Its next challenge is making usage depth, reliability, and customer outcomes equally visible.

Three Signals Will Define Outmarket’s Next Stage

The next evidence should come from account expansion, measurable workflow results, and competitive responses.

The first signal is expansion inside existing agencies. Outmarket says customers have added teams, business lines, and workflows since the Series A.

Future disclosures should make that claim easier to evaluate. Seat growth, workflow adoption, or customer retention would show whether the platform becomes more valuable after initial deployment.

Expansion would strengthen Outmarket’s broad-platform thesis. Flat usage inside a growing customer list would suggest the product remains a collection of useful but limited tools.

The second signal is evidence from Certificate Hub and other consequential workflows. Outmarket introduced the certificate product alongside the Series B announcement.

The launch gives the company a concrete opportunity to demonstrate its operating model. Agencies will want faster handling without weaker review or documentation.

Useful evidence would include processing times, exception rates, approval patterns, and independently verified error outcomes. These measures matter more than the number of documents generated.

Strong results would support the argument that Outmarket can extend from analysis into operational execution. Frequent exceptions or heavy review requirements would weaken the promised capacity gains.

The third signal is how established vendors and specialists respond. Insurance software companies already possess customer relationships, workflow data, and core-system access.

They can add comparable AI features, deepen integrations with specialist partners, or bundle automation into existing products. Each response increases pressure on an independent platform.

Specialists can also sharpen their positioning. They may offer deeper automation for one renewal, certificate, or policy-review process.

Outmarket must prove that shared context across workflows delivers more value than best-in-class tools assembled separately. Funding gives the company time to build that case, but not exclusive access to the opportunity.

The broader market supports continued investment in insurance AI. Industry financing data showed AI-native companies captured a substantial share of insurtech funding during early 2025.

Capital is increasingly flowing toward products that automate core work rather than merely digitizing distribution. That trend gives Outmarket favorable timing and more competition.

For insurance buyers, the right response is neither automatic enthusiasm nor blanket resistance. The financing should prompt a closer look at which workflows already consume avoidable staff time.

Agencies can start by choosing a representative process and measuring its current cost, turnaround time, exception rate, and error history. They can then compare those results with a controlled automation pilot.

Human approval should remain explicit wherever an output affects coverage interpretation or a client commitment. Logs and source documents should remain available after every automated step.

The Outmarket Series B is significant because it arrived before the previous round had become old news. Investors are betting that insurance agencies are ready to move from experiments into daily AI-assisted operations.

The next few months should reveal whether adoption becomes deeper, not merely broader. Watch the workflows customers expand, the evidence Certificate Hub produces, and the features competitors release.

If Outmarket can document sustained usage and controlled accuracy, its fast fundraising will look like preparation for a genuine platform shift. If not, the round will remain an impressive bet on demand that still requires operational proof.

Give every agent the context to do better work

Connect your agents to the knowledge, decisions, and history already organized in remio.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page