Apply to Register Here

Founded in 2015, Activant is a global investment firm with $1.5 B AUM that partners with high-growth founders and teams that are transforming commerce.

Activant

We’re always looking to learn about new perspectives, new research, and new ideas.

Get in touch

Disclaimers & Terms of Use

Privacy Policy

323 Railroad Avenue
Greenwich, CT 06830
USA

Greenwich

New York

Berlin

Constantia Uitsig Wine Estate
Spaanschemat River Road
Cape Town 7806
South Africa

Cape Town

Activant is a research-led growth firm that invests in relentless founders

Featured Companies

Read past issues

Monthly Newsletter

Browse Research Library

Research

Perspectives

Home

Activant is a research-led global investment firm that partners with high-growth companies.

We partner with founders who have won their initial battles and are ready for the next challenge.

We typically invest when two things come together. First, the company has the potential to achieve escape velocity and transform an entire industry. Second, we believe the founders can lead the company through hyper growth, and our support can significantly increase the probability of this success. 

The critical time window to escape competitors and transform an industry is not open for long.

That’s why after we invest, the real work begins.

About

We only partner with a few founders per year. But when we do, we’re fully committed.

Our portfolio

Companies

Read our investment rationales and market perspectives.

A team built to support and advise yours.

We invest behind insights.

View all research

Founders who aspire to build something bigger than themselves chose to partner with us at their most critical point.

Team

A born and raised Texan, Julius holds a passion for ecosystem-changing technology. Having worked as both a software engineer and an investor, he aims to provide tangible technical value to operators that he feels is sorely lacking in the overall industry. All too often, the narrative outstrips the technical conversation, and by understanding what it is founders are building, Julius believes that he can provide increased leverage to them as they grow. 

In his free time, Julius keeps up to date on the latest NLP research and algorithmic trading strategies.

"I joined Activant to help add technical expertise in a traditionally finance-dominated world. Activant has this incredible ability to bring people from different fields together and working to invest in truly disruptive companies. For me personally, I can’t wait to work with founders shaping the future."

Application Programming Interfaces (APIs), the digital conduits that allow different software systems to “talk” to one another, are the unsung heroes of digital commerce in a world where the number of connections between entities is increasing exponentially. 

Businesses today use nine times more individual software tools than they did five years ago

  and complexity is only increasing. Maintaining these myriad integrations and the constant upgrades to each is a major challenge, particularly if engineering teams need to deal with each connection individually. Differences in time formats, currencies, accounting or reporting nomenclature, and a host of other nuances can make managing APIs at scale a headache.

There are solutions to this, and markets thrive when aggregators enable simple connections, much like 

 did with its universal API for fintech companies to connect to user 

” is an abstraction layer that handles communication with many different APIs and backend data models. Companies only need to build one integration – to the unified API provider — and it then manages the complexities of multiple API connections. Exhibit 1 illustrates the simple difference that a unified API offers for developers.

: changes to APIs can lead to downtime if the individual connections are not aligned, resulting in breakages

: fixing these breakages is often an inefficient process consuming expensive developer capacity

Accessing new integrations and data points

: access is possible to all the API integrations a Unified API solution has built

: Unified APIs offer significant time and resource savings, allowing more rapid prototyping and new product launches.

The case for Unified APIs is compelling and we expect the market to expand over time as API-first businesses proliferate.

We estimate that companies spend more than $50 billion annually in the U.S. alone on maintaining external-facing APIs. Our estimates include (1) the number of companies that use external API integrations, (2) the number of API integrations per company, and (3) the average annual maintenance spend per API. Based on our interactions with industry experts and practitioners, we conservatively estimate that companies have an average of four external API integrations, and that maintaining these costs approximately $620 per API per annum. Exhibit 2 summarizes the results of our market sizing analysis.

Victory Matibiri, CEO and Co-Founder, Mansa

Estimated Unified APIs Market Size

In our market study, we differentiated the players based on the time it took to integrate their solutions and the degree of customization of data fields possible. The Activant Market Map is shown below.

One of the benefits of the segmentation approach used is the alignment with the broader market of solutions addressing the pain points of building, maintaining and orchestrating APIs. Each quadrant in the market map represents a unique approach to API integration.

 do what the name suggests: they unify APIs. These tools are generally faster to integrate as they only need to process a single set of API documentation. Unified APIs apply a data normalization technique that standardizes API fields across software vendors. The more coverage a business has across vendors, the more participation it can expect.

 solutions help internal development teams build individual API connections in a low-code fashion. Relative to Unified APIs, these tools generally require more engineering hours to build but are ideal for scenarios where a high degree of customization in the data being pulled is required. These tools do not apply a data normalization technique.

Integration Marketplaces as a Service (iMaaS) 

solutions focus on the distribution of integrations and enable SaaS companies to provide APIs to their customers in the form of a marketplace. In the same way, a traditional marketplace helps organize and showcase products a business can sell, an integration marketplace is an effective platform to showcase all the apps an SaaS can integrate with.

uses company resources to build and maintain APIs. The resources required ultimately depend on the complexity of the integration, which includes factors such as the number of end-points to connect, the amount of data being pulled, and security requirements. Costs can vary from $10-$100K+ per integration.

Importantly, many of the companies that we have located on the market map offer iPaaS, iMaaS, and Unified API solutions. It is not a one-size-fits-all world and customers have the luxury of choosing a combination of the solutions depending on their specific needs. Simple solutions will win. Less friction is likely to result in more commerce.

It’s still early days, despite the clear need for a ‘middleware’ layer to help manage the complexities of multiple API integrations. We believe that tomorrow’s winners will be those that offer solutions with 

 to allow teams to pull customized data listings. Additionally, we think the use of Large Language Models (LLMs) to automate the construction of API integrations into their common data layers will become table stakes. This may decrease the cost per integration and has the potential to expand industry margins – which is likely to increase industry competition. Whatever the future holds, there’s definitely change coming to the status quo.

Activant’s conviction in the bright future for unified API solutions is summarized in our thesis map below.

, a first mover in the use of LLMs. The company recently unveiled 

 to provide LLM-built API integrations to customers.

, a solution powering the credit decision engines of top tier banks and FinTech companies that integrates with 19 accounting solutions and 16 commerce platforms. Lenders can quickly assess, for example, the size and quality of incoming payments to their customers by comparing contract details against invoices in accounting platforms.

, a market leader offering integration with 200+ Human Resource Information Systems (HRIS). Providers of 401(k) plans, HR technology, and fintech solutions can integrate with an employer’s HRIS system to streamline employee onboarding, track payrolls, update benefit deductions, and manage other core HR and compliance functions

, which offers its customers broad and deep solutions across disparate use cases in CRM, accounting, logistics, and the like, allowing them the option to build fast, then deep. A unified API allows customers to instantly set up real-time read-and-write integrations, and when it’s time to build more complex processes, customers can leverage Alloy’s Embedded iPaaS.

, a first mover in building the category across Africa, which allows fintech firms to read and write across 17+ African commerce, banking, accounting, and payments platforms.

At Activant, we’re excited to watch this market evolve. If you’re building in the space, have a different perspective, or enjoyed the piece, 

The information contained herein is provided for informational purposes only and should not be construed as investment advice. The opinions, views, forecasts, performance, estimates, etc. expressed herein are subject to change without notice. Certain statements contained herein reflect the subjective views and opinions of Activant. Past performance is not indicative of future results. No representation is made that any investment will or is likely to achieve its objectives. All investments involve risk and may result in loss. This newsletter does not constitute an offer to sell or a solicitation of an offer to buy any security. Activant does not provide tax or legal advice and you are encouraged to seek the advice of a tax or legal professional regarding your individual circumstances.

This content may not under any circumstances be relied upon when making a decision to invest in any fund or investment, including those managed by Activant. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by Activant. While taken from sources believed to be reliable, Activant has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation.

Activant does not solicit or make its services available to the public. The content provided herein may include information regarding past and/or present portfolio companies or investments managed by Activant, its affiliates and/or personnel. References to specific companies are for illustrative purposes only and do not necessarily reflect Activant investments. It should not be assumed that investments made in the future will have similar characteristics. Please see “full list of investments” at https://activantcapital.com/companies/ for a full list of investments. Any portfolio companies discussed herein should not be assumed to have been profitable. Certain information herein constitutes “forward-looking statements.” All forward-looking statements represent only the intent and belief of Activant as of the date such statements were made. None of Activant or any of its affiliates (i) assumes any responsibility for the accuracy and completeness of any forward-looking statements or (ii) undertakes any obligation to disseminate any updates or revisions to any forward-looking statement contained herein to reflect any change in their expectation with regard thereto or any change in events, conditions or circumstances on which any such statement is based. Due to various risks and uncertainties, actual events or results may differ materially from those reflected or contemplated in such forward-looking statements.

Building connections

Unified APIs

We are hardly the first to claim a new technology is poised to upend work as we know it. With every wave of innovation comes a chorus of such pronouncements, many of which turn out to be hyperbole. Technology may make our jobs easier, but most of the time, the core of what we do remains fundamentally the same. 

But spend five minutes on ChatGPT, or any comparable Large Language Model (LLM), and it’s clear: it’s different.

The reason is simple. Most technologies help us accomplish tasks. They’re tools, a means of making us more productive. AI, on the other hand, can think (or at least, provide the appearance of thinking). It’s like having another knowledge worker on the payroll.

Activant Perspective 1: LLM-enabled software will autonomously accomplish highly complex tasks.

This is the beauty (and threat) of LLMs: they can do work we thought would long be the purview of humans.

Given this, one could be forgiven for worrying their job will soon be automated away by an AI. In the short term, this will lead to dislocation. 

But technological revolutions are never zero-sum – in fact, they’ve always been accretive.

 As workers adapt, they become more productive, and the companies they work for can do more with less. Some stop there, to be sure, but most businesses opt to invest the gains back into their infrastructure and people. In the end, revenues go up, and the economy grows.

That said, we’re still in the very first days of this cycle – and critically, of the technology itself.

Activant Perspective 2: LLMs alone are not enough to achieve Perspective 1.

Case in point: a large language model can’t complete most tasks on its own. After all, an LLM is merely a dense set of attention networks; essentially, statistics on a massive scale. Yes, they can engage in human-like “thought,” but to generate real value from any of these models, a human would have to integrate them into actual workflows – and make use of their decision-making prowess.

For example, imagine that you hired someone to lay bricks. You could lead them to a stack of bricks and explain where and how you want them laid. They could perfectly understand your instructions. Yet, understanding isn’t enough – the worker needs to be able to, well, lay bricks.

In this case, they need to have more than just cognition – they need to have arms, legs, and physical strength. Furthermore, they need a memory to recall how you wanted each of the bricks to be arranged, and a way of correcting any errors so they don’t cause the eventual structure to fail.

Put another way, if LLMs are to extend beyond mere Q&A, they need (1) a suite of Tools to actually impact the real world, (2) memory repositories to remember what actions they’ve taken, and (3) auto-critique algorithms to error correct along the way.

When all these components come together, an “Agent” is born.

 An Agent is orchestration software that combines an LLM with memory, tools, and auto-critique algorithms.

 An Agent is a highly advanced bot that can complete work that has been assigned to it in natural language.

Though still in their infancy, Agents are poised to fundamentally reshape the way we work. They will become natural extensions of your organization and complete day-to-day tasks – akin to hiring more employees. They’ll help you get work done, even collaborate with others on your behalf. Eventually, they’ll be able to work together, breaking down tasks into atoms of work able to be handled by a full “office” of Agents, some of which orchestrate, while others specialize.

The result is why this time is different: working together, Agents will be able to handle increasingly complex tasks, replacing knowledge workers in a variety of fields.

 As they do, what it means to work – and to lead – will change drastically, as both will increasingly depend on a mix of human and human-like capital.

Activant Perspective 3: Agent Teaming is the future of autonomously completed, complex work – 

Few have sketched a path from where we are today, to the autonomous knowledge workers of the future. But that future is closer than you’d think, and one for which you almost certainly want a roadmap. To learn more about how this transformation will unfold, and how you can best position yourself within it, read on.

The Agent Ecosystem {2}

The Agent Ecosystem of the future has four key components:

provide “conscious thought” within AI Agents and have been trained on text data,

external APIs to facilitate task completion and Agent interaction with the real world,

 includes various data storage mechanisms to retain and recall information, and

the ability to correct mistakes when completing tasks.

To better understand the components, we imagine how each one might erode a job we know quite well: that of an analyst at Activant (sorry, John). Among many other things, we often rely on our analysts to create market maps, which requires them to:

Find companies that exist in that industry,

Compare these companies qualitatively, and

Place them on a 2-dimensional grid according to this comparison.

Until recently, this was almost inconceivable as a task for machines. Now, let’s explore how we’d put our “Agent Analyst” to use.

AI Agent Ecosystem

1. Understanding the Industry (and the Task) – Large Language Models

For our Agent Analyst to understand the task at hand, it requires the capacity to comprehend instructions stated in natural language. While LLMs provide that ability, they come in many different shapes and sizes (literally). For that reason, here we outline a basic framework for evaluating LLM providers, including both foundational model providers and companies offering Fine-Tuning as-a-Service (FTaaS

When comparing foundational models, the number of parameters in a model is often a good approximation of output quality. As a rule of thumb, the more parameters a foundational model has, the better its performance across different benchmarks, 

such as reasoning, web browsing, or even game playing

. Although fine-tuning a model can boost its performance on a particular task, larger models with more parameters tend to have better generalization skills – making them more useful.

As seen below, model sizes are increasing on an exponential basis with base 2, and although not pictured, model performance is similarly increasing – just not at the same rate.

Foundational Models Size Map

At the heart of any LLM lies its architecture: a blueprint dictating how various attention heads and layers are organized. Then, there are the "weights" — numeric values assigned to parameters in the neural network, refined and adjusted through training to enhance performance. Training involves feeding data into the model, allowing it to learn and make predictions, and then adjusting the weights based on its accuracy. It's through this process, often requiring substantial computational resources, that the model obtains its ability to understand and generate human-like text.

, “openly” share their architecture, weights, and sometimes even their training methodologies. This approach not only reveals the intricacies of their design but also democratizes access, allowing enterprises, researchers, and even enthusiasts to build upon, refine, or entirely repurpose these models for their own applications.

Conversely, some entities opt for a more guarded approach. Closed-source models, such as GPT-4 by OpenAI, often protect the details of their architecture, weights, or training processes, presenting them as somewhat of a black box. Instead of allowing direct model access, they employ APIs as intermediaries, thereby controlling and often monetizing the interaction between the end user and the model.

Foundational Models

“Provider Modality” relates to the data type a provider offers models for. This includes various transformations such as text-to-video, text-to-text, text-to-image, and image-to-text, among others. Companies that operate in just one domain are labeled as “Uni-Modal”; by contrast, “Multi-Modal” companies provide models spanning multiple domains. As Agents continue to evolve, we expect a growing emphasis on modality in LLM models, as those able to perform more diverse tasks and offer easier integrations will have a distinct advantage in the marketplace.

While Agents will no doubt depend on the 

, we actually expect most Agents to remain agnostic to the specific LLM they use. 

Today, OpenAI, Google, and Anthropic dominate the industry, but this is hardly set in stone. If anything, the next few years will see considerable competition, with whoever invests the most in R&D in a constant arms race. Given this uncertainty – and the promise of better models always around the bend – it’s hard to imagine Agents relying on a single provider. From an investment perspective, backing one LLM provider is essentially a vote of confidence in its R&D team, but past performance is not (necessarily) indicative of future results.

Having understood the industry (and the task), the Agent Analyst now needs the ability to search for companies. In other words, the Agent Analyst needs a Tool.

Tools are snippets of code that foundational models can use to create, modify, and utilize external resources in order to execute tasks they couldn’t otherwise complete on their own.

Most Tools are problem specific. In this case, all the Agent Analyst needs is a connection to Google, or SerpAPI, a prominent wrapper for Google’s Search API. Unsurprisingly, other tasks will require different Tools. Game this out, and you quickly arrive at the need for Toolkits and Tool Aggregators. As tasks become more complex, Agents will rely on not one, but a variety of Tools to accomplish a single objective. Through Aggregators, Agents will be able to access the resources they need, programmatically, and as those needs arise.

AI & LLM Tooling Companies

Single Tools refer to companies or services that specialize in just one function, such as searching the internet, booking a flight, or creating realistic voice audio files. While these offerings do have certain strengths, integrating them into a Toolbox, and thus into Agents, is often cumbersome. Notably, in prominent Agent libraries

, Toolboxes need to be set up before an Agent itself is even initialized. 

This means if there's a need to integrate additional Tools later – for example, if an Agent encounters a new task that requires a Tool outside of its preset toolkit – the Agent would have to initialized all over again.

 Given these considerations, embedding Single Tools into an Agent's workflow can be quite labor-intensive and time-consuming.

AI Agent Tooling

By contrast, Tool Aggregators offer Toolboxes-as-a-Service (TaaS). Theoretically, aggregators can compile an infinite number of Tools and distribute them via a single, unified API. In practice, they typically provide Tools that have been identified by an Agent as required to complete a given task. If an Agent requires determines it needs additional tools, however, it can access them without restarting.

 companies could provision Tools and/or provide tool-building functionality for Agents. As long as they offer an API, Agents can leverage these solutions as they do Tool Aggregators, integrating (and even custom-building) Tools into their workflows on the fly.

Many LCNC platforms have existed prior to the advent of LLMs and already have large libraries of powerful, ready-built Tools to draw upon. Several companies, including 

, have begun offering Agents-as-a-Service (AaaS), using these libraries to jump ahead of competitors, many of which are starting from scratch. Others may choose to offer APIs to facilitate quick adoption within the Agent Ecosystem and more reliably maintain their market share.

Because of their ease of integration and use, we believe Tool Aggregators and API-based LCNC platforms are the best positioned to take advantage of this new Agent ecosystem

. As platforms like LlamaIndex and Relevance AI grow, Agents will be able to dynamically access a vast library of toolsets without needing to update their structure or code – increasing both their functionality and value.

As our Agent Analyst has progressed, it has gained the capability to discern tasks and search for companies. However, identifying a company means nothing if an Agent can’t remember it for later use. To facilitate this, Agents require a dedicated memory component that can store companies and their associated descriptions.

Memory

Over the years, the software industry has seen a multitude of data-structure innovations, from traditional SQL-based relational tables to modern streaming services like Kafka. Yet, to truly grasp the intricacies of Agent development and the depth of virtual cognition, it's helpful to draw parallels with human memory.

At a high level, human memory is split into three core categories: sensory memory, short-term (or working) memory, and long-term memory.

In humans, sensory memory can be thought of as the direct inputs from our various senses — taste, smell, sight, touch, and hearing. These are perceived subconsciously, processed then filtered for relevance. Similarly, in the realm of Agents, 

sensory memory captures the responses generated from the Tools they employ.

 Research in neuroscience and psychology reveals that of the countless sensory inputs humans encounter every moment, only about 5% ascends to conscious awareness, courtesy of various attention mechanisms. Our neural framework efficiently filters out redundant and useless sensory data, elevating only important information for conscious processing. The sensory memory of an Agent operates on similar principles, 

sieving through vast data while retaining only what's significant.

For example, to store the names and descriptions of any relevant companies it finds, our Agent Analyst might choose to create a vector database. To do that, the Agent could use the 

 API and receive a specifically formatted JSON response directly. Though the Agent could use the LLM to parse that JSON response, it would be far more efficient for the Agent to use the Pinecone Tool from 

 and receive a pre-processed Python dict. In many ways, this is analogous to how our subconscious mind pre-processes data before it needs to be consciously thought about – i.e. you don’t have to process the shoe touching your foot when you’re using your finger to touch your phone because your subconscious brain filters the shoe sensation out.

Over time, we believe that sensory memory will include the ingestion of many different data types,

 from unstructured data files (such as docx, pdf, epub, or recordings) to semi-structured datasets (such as messages and CRM data). 

As of today, it is unclear to us if “sensory” processing should or could be handled at the Tool level,

 like it is in the above Pinecone example, because we don’t know if Tool Aggregators will provide a standardized API for these tools – or if it’s even possible to have a standardized API across all conceivable Tools. What we do believe as a result of our work is that the quality of Agent-handled sensory memory will be highly correlated with the quality of the Agent itself.

Having processed inputs on the subconscious level, Agents are left with the inputs which require conscious thought. In humans, conscious thoughts reside in working or short-term memory. When we actively think about a topic, we do not consciously remember the context for the thought in our “memory,” but it is nevertheless remembered. In fact, our short-term memory is believed to have the capacity of about seven items

 and lasts for 20-30 seconds. For Agents, using the context windows defined by LLMs to store short-term memory is the default solution of most Agents we see today, and we don’t see that changing. As context windows increase in length and new techniques for prompt engineering solve existing constraints, the context window will be an even more effective location for short-term memory.

Interestingly, most short-term memory will be forgotten after a certain time threshold, especially after corresponding actions are finished. Though some of this information may be transitioned into long-term memory (which we discuss below), most of an Agent’s short-term memory will not be useful after a task is completed. Therefore, short-term memory data can be stored in the context and does not require the same complex storage techniques long-term memory does.

In the context of our Agent Analyst, short-term memory can be thought of as remembering the larger task at hand (i.e., creating a market map) when deciding what smaller task (i.e., finding a company) needs to be accomplished next. In practice, this information will largely live inside the context window of the LLM API call – and while it’s essential for the Agent to complete a task, we believe that there is little opportunity for investment in short-term memory due to the limited additional infrastructure required to build it.

Once subconscious and conscious memory is in place, an Agent Analyst will need some way of saving information for longer periods than the immediate task at hand. This is where long-term memory comes into play.

In humans, long-term memory is finite, due to the limited capacity of the brain. As a result, we have developed two primary mechanisms to retain knowledge: repetition and adrenaline. For obvious reasons (i.e., they can use ACID databases), Agents lack this capacity constraint. Instead, they are limited by the amount of memory that they could conceivably “know” how to access. For example, if our Agent Analyst was integrated into our Drive and needed to search for the PowerPoint example of our Market Map, the size of the context window would limit the number of folders that it could select from in its search.

In our view, connections to long-term memory repositories are no different than Tools, in that they are blocks of code that can be executed and return a response.

Over the next decade, we believe that the entire ecosystem of data management will grow even faster than it has historically because of increased Agent data utilization. Agents will be able to build pipelines from company data, leverage it in their own processes, and integrate outside data into existing workflows. The total spend on databases and database management solutions doubled from $38.6B in 2017 to $80B in 2021

. As the Agent ecosystem grows, the demand for data stores will increase even more rapidly, making the volumes of unstructured company data – which today sits untouched – significantly more valuable.

We’ve listed a handful of data structures, and the impact we anticipate from Agents, below:

AI Agent Use Case w/r/t Databases

4. Placing Company Logos – Auto-Critique

Our Agent Analyst has successfully understood the industry, used a search Tool to find all the companies within it, and saved them in a database for future output. As a final step, we need the Agent to place the logos of each of those companies onto an Activant Market Map – fully understanding the significance of each company’s position. Naturally, this will involve a Tool that enables the Agent to create graphs. In the short term, this Tool will likely be some wrapper around Our Agent Analyst has successfully understood the industry, used a search Tool to find all the companies within it, and saved them in a database for future output. As a final step, we need the Agent to place the logos of each of those companies onto an Activant Market Map – fully understanding the significance of each company’s position. Naturally, this will involve a Tool that enables the Agent to create graphs. In the short term, this Tool will likely be some wrapper around Matplotlib

 but in the long term, this will undoubtedly be an integration into PowerPoint.

Plotting logos, of course, is the easy part of the challenge; understanding where to place a logo in a subjective 2-dimensional plane is the truly complex task. It requires iterations, constant comparisons to other companies, and perhaps even outside input from the Activant team. 

Therefore, the Agent needs a mechanism for critiquing itself. We call this Auto-Critique.

While we foresee potential challenges - like defensibility - this remains a vital component of the ecosystem with several approaches underway: (A) Prompt Engineering, (B) Human-In-The-Loop, and (C) Auto-Critique.

Self-Critique

 Prompt Engineering is the process of forming and refining natural language statements and questions to achieve an optimal outcome from an LLM.

In practice, LLMs are only capable of comprehending and responding to inputs that fit within a defined context window. For example, GPT4’s context window is about eight thousand tokens – meaning only about seven thousand words can be provided as context at any one time.

 In order to maximize the utility of the model, a prompt engineer could write shorter and more effective prompts.

In our view, prompt engineering is likely a temporary solution, one we expect the industry to shift away from as LLMs improve in terms of task comprehension and context window size (though the timeline for this shift remains uncertain). Meanwhile, existing businesses in this domain have a chance to pivot their business model, leveraging their current distribution to tap into emerging opportunities.

Human-In-The-Loop Critique refers to the use of humans to validate that Agents are accurately processing and reasoning through tasks.

Human-In-The-Loop Critique is just what it sounds like: leveraging humans to correct or modify the reasoning of LLMs. Currently, developers use this method when building Agents, as they want visibility into their inner workings. 

Because it requires that people scale linearly with compute resources, it will likely be unsustainable in the long term.

 Auto-Critique refers to the autonomous use of LLMs to check and modify Agent reasoning about a task.

Humans often make decisions in multiple steps: starting with an initial judgement, then assessing its consequences, and evaluating alternatives. Throughout this process, we add new information, remember past experiences, and take note of what others have done. We call this “thinking it through,” and LLMs perform a similar process when refining their own outputs. Like the brain, they begin with a rough first pass – a digital gut instinct, one might say – before iterating to either expand on that conclusion or critique it.

Auto-Critique is an autonomous process that allows Agents to improve and amend their own output by reflecting on past responses and errors, all without human intervention.

 To do this, Agents draw on new input from a variety of sources, including external Tools, other Agents, affiliated LLMs, and heuristic functions. Once they arrive at a sufficient result (governed by predefined metrics for evaluating self-reasoning), a stop condition is granted, allowing Agents to finalize their output.

Teaming: The Rise of the Planet of the Multi-Agent Systems

So far, we’ve focused largely on the mechanisms and potential of standalone Agents. However, to fully appreciate the potential of this nascent sector, we must also look at the collective strength of Agent Teaming, otherwise known as Multi-Agent Systems (MAS). Within the framework of a MAS, the power of individual Agents is not merely aggregated – it’s amplified, boosting the overall effectiveness of the system in a multiplicative and potentially exponential manner.

Tool Aggregators

Multi-Modal Data Stores

A Technical Guide for Founders & Operators Building Agents

Towards the AI Agent Ecosystem

Since their introduction more than 50 years ago, Transportation Management System (TMS) software has grown to become a mission-critical component enabling the worldwide movement of goods. Your most recent grocery haul and new home exercise equipment, along with your business’ purchase of everything from office supplies to raw materials and inventory was made possible by a TMS. Over the years, TMSs have grown in size and scale, and have permeated all of the steps in the supply chain. 

Yet despite their ubiquity, we believe that today’s TMSs simply aren’t enough. 

They are old and legacy, don’t serve the mid-market or smaller customers efficiently, are missing key features, and often create more pain points and clumsy workarounds than the number of business problems they solve.

 – largely because compelling new logistics tech companies are entering the market. In this article, we offer an overview and history of the category, as well as two frameworks to understand the 

 of TMSs and how to think about the emerging vendors. Throughout our research, we asked ourselves: 

does a next generation TMS even need to be a TMS at all?

Some of today’s most compelling new vendors might offer their own TMS or TMS-like features but are agnostic as to whether you use them for that or not. Their real value-add is sitting on top of existing TMS systems and leveraging data created to offer compelling new insights and actions.

What is a TMS, and why should we even care what generation we’re on? 

A TMS is a software platform that tracks the physical movement of goods from point A to point B

 – everything from planning which carrier to use and at what rate, to tendering and executing the shipment, to tracking the load’s progress, to settlement and analysis after delivery.

Why the next generation TMS won't be a TMS at all

The Future of Transportation Management Systems (TMS)

Activant’s resident technical expert. Brings his engineering background to finding and partnering with founders and their teams.

Office

Hometown

Residence

Julius
Stener

Investment Team

Office

Hometown

Residence

Research

Office

Hometown

Residence

Julius Stener

Investment Team

Office

Hometown

Residence

Research

Julius
Stener