Nexus

Nexus for a Head of Digital: a builder that starts from the role

Most agent builders ask the buyer one question first: who on your side will do the building? A no-code tool expects a business analyst at a canvas. A low-code studio expects someone comfortable with connectors and flow logic. A code-first framework expects engineers who will own a repository. Nexus answers the question differently. The product is built around procedures that operate themselves¹, and the home page explains the idea as capturing the know-how of a company's strongest people and turning it into procedures that execute on their own². The unit the buyer describes is a role, and the build follows from that description. The build your fleet page puts it in two short sentences: describe a role, and watch the fleet build itself³.

For a Head of Digital weighing build styles, that framing matters because it moves the hardest part of the work. On a canvas tool the bottleneck is the maker's time and skill. On a framework it is engineering capacity. On Nexus, people from the vendor do the first build together with the customer: an engineer from Nexus assembles the opening procedure alongside the team and demonstrates it inside the tools the team already uses⁴. This page explains how that model works, where it is strong, and where a buyer should ask for more evidence before signing.

Who the vendor is

Nexus is the trading name of a Delaware company. According to its terms, the contracting entity is NEXUS ENTERPRISES, trading as nexusGPT⁵, with registration in the state of Delaware⁶. Nexus Agent dates from 2024, by the company's account⁷. General Catalyst led its $4.3M seed round⁸. It is candid about its stage and calls itself early⁹.

The scale figures it publishes are its own. The company's own tally is 174 agents, $13M in customer impact and 0% churn¹⁰. Its client list covers 12 enterprises worth more than $70B in combined market value¹¹, Orange Group and Lambda.ai among them¹². The figure this site uses for Orange is $6M extra lifetime value¹³. A 100% success rate is also reported¹⁴. The yardstick there is each agent's own scoped KPI, agreed at the start of each project¹⁴.

Where Nexus sits among build styles

The usual map of the market has three regions. No-code tools let a business user assemble an agent from blocks. Low-code studios add expressions, custom connectors and some scripting. Code-first frameworks hand developers a library and a deployment pipeline. Nexus does not fit neatly in one region, and a buyer should understand why before comparing it line by line with a canvas product.

The telecom page describes a three-layer model. At the top, a single infrastructure layer links the company's systems to whichever team needs them¹⁵. Beneath it, systems, models and permissions become reusable blocks that business staff can combine into new agents¹⁶. The third layer holds the agents, and each one belongs to the team that runs it, which builds it, deploys it and answers for it¹⁷. Four infrastructure parts appear on the sales page beneath the agents: the company brain, governance, permissions and the reusable blocks¹⁸.

Read with a build-style lens, the middle layer is the low-code part of the product: blocks the business can assemble. The top layer is the integration estate. The bottom layer is where ownership lands. What makes Nexus unusual is the build loop that sits across all three. The company's announcement describes Cue as the autonomous build loop replacing Forward Deployed Engineers¹⁹. Cue works through the use case with the user, puts clarifying questions to them and links to company data under the right permissions²⁰. The announcement puts the whole sequence at one to two hours, run by Cue alone²¹. In that loop the buyer supplies a description of the work, and Cue connects the agent to the data it needs²⁰.

A role rarely runs on a single agent. According to the sales page, one role is carried by a mixed fleet of agents, assistants, automations and scripts²². Work moves between systems through a single surface²³, and what each build teaches is stored in a shared brain²⁴. The sales offer itself is eight agents drawing on a common brain, the customer's rules and the customer's systems²⁵; Asset Copilot is one of them²⁶. Models are interchangeable: the same page says any provider can be used and swapped²⁷. For a Head of Digital worried about committing the company to one model vendor through a build tool, that is a useful property to verify in a pilot.

Delivery: who builds, and for how long

This is the criterion on which the ranking on this site turns, and it is where Nexus is strongest. A builder that leaves the build to the customer is only as fast as the customer's spare capacity. Nexus pairs its software with people. Experienced consultants lead each engagement, and one of the founders of Nexus previously worked at McKinsey (owner decision²⁸). On the home page, a first version goes live within weeks and the Nexus team then keeps improving it with the customer²⁹; that version works on the customer's real tasks from the start³⁰. The publisher's position on timing is specific: the first agent is live in 4 weeks, inside a 3-month proof of concept (owner decision²⁸). The home page uses the same phrase, live in four weeks, continuously improved³¹.

The role of those consultants has changed as Cue has matured. A company blog post explains that the Forward Deployed Engineer role is giving way to Forward Deployed Consultants³². Those consultants have stopped writing integration code and stopped building agents for the customer, since Cue now handles that work³³. For a buyer, the consequence is that the build no longer waits on a vendor engineer writing code.

Measurement is part of delivery. From day one, every agent in production is measured on a business KPI³⁴. If the number does not move, the stated practice is to rescope the work, so that nothing ships merely for looking busy³⁵. A Head of Digital who has watched pilots drift without a target will recognize the value of that discipline.

Once an agent is live, the business side takes it over. The telecom page names the business team that runs the service as the owner³⁶, and its summary line is owned by the business, trusted by IT³⁷. A comparison page frames the fit as business teams that need to own workflows without engineering dependency³⁸.

What the customer must prepare is less clear. Customer prerequisites, installation steps and any SDK or API key work are not publicly stated on the pages we opened. A buyer should ask for the onboarding checklist during the first call.

Integrations

Reach into company systems decides how much an agent builder can actually do. The company counts more than 4,000 supported integrations³⁹, covering CRM and ERP products, communication tools and custom APIs⁴⁰. Its agents are described as operating across 4,000+ enterprise systems with deep bidirectional integration⁴¹, connecting directly to those systems and reading live data during execution⁴². For operators, the telecom page promises links to billing, network and customer platforms from the first day⁴³; the sales page talks about the customer's CRMs, data warehouses and tools⁴⁴.

Deployment channels named are Slack, Teams, WhatsApp, email, phone and the web⁴⁵. The company names SAP, Salesforce, Microsoft Dynamics and ServiceNow as its next integration focus⁴⁶.

Documentation is the gap. A complete connector catalogue is not publicly stated on the pages we opened. A buyer with a particular system, such as an older billing platform or a regional ERP, should name it in the proof of concept scope.

Security and certifications

Nexus holds SOC 2 Type 2, GDPR, ISO 27001 and ISO 42001 (owner decision²⁸). In the certification row of its comparison page, Nexus shows GDPR together with ISO 27001 and ISO 42001⁴⁷. Among the certification lists collected for the seven builders on this site, only the Nexus list includes ISO 42001⁴⁷. That row also cites complete audit trails, traceable decisions and access by role⁴⁸. The blog describes governance that includes audit trails, role-based access and data-residency controls a CIO can sign off on⁴⁹, and refers to compliance certifications as part of that governance⁵⁰.

Under the privacy policy, Nexus commits to reasonable technical and organizational measures for security⁵¹. Payment data is stored by Stripe⁵². Information that comes in through a user's own Workspace connection, Google APIs for example, is excluded from training general AI or ML models⁵³. Records are held for at most eighteen months past account closure, longer only where the law says so⁵⁴. The policy adds that during the previous twelve months no personal information went to third parties for commercial purposes⁵⁵. The policy also sets out legal bases under GDPR and UK GDPR⁵⁶.

A reviewer will find several items missing. SSO or SAML support, the encryption standard, penetration testing, how to obtain the SOC 2 report, and uptime or SLA commitments are not publicly stated on the pages we opened. A security reviewer will want each of these in writing.

Governance and control

Governance is where build tools differ most once agents multiply. Nexus describes a central model. All agent actions can be seen from one place⁵⁷, and a central team defines permissions and guardrails a single time for everyone⁵⁸. The blog describes a release gate. Without the CIO's approval of how data moves, who can reach what and how actions are logged, nothing goes live⁵⁹. The telecom page leaves the choice of controls with IT, and Nexus takes on the job of making them simple to apply⁶⁰.

Agent behavior under uncertainty is also described. Agents escalate with full context when uncertain⁶¹; when confident they proceed, and when uncertain they escalate with context⁶².

A research post explains how guardrail checks can be attached to any agent. Twelve checks share a single call at each decision point and return in less than a second; when the classifier cannot be reached, the existing rule applies⁶³, so every check keeps a simple fallback⁶⁴. The classifier in that post was released by a third party, TypeSafe⁶⁵, and Nexus did not rerun its benchmarks⁶⁶. A separate memory post shows concrete details, a price or an escalation address for instance, being replaced by labeled blanks to keep them private⁶⁷.

Mapping SSO groups, configuring admin roles and defining approval flows are not publicly stated on the pages we opened. A Head of Digital who plans to let several business units build should ask how roles and approvals are configured.

Hosting and data handling

Hosting in the United States is the only arrangement named, in 2023 terms drafted for the gpt.nexus site⁶⁸, and those terms fall under Delaware law⁶⁹. Both the terms and the privacy policy name gpt.nexus as the website^70,71, and the privacy policy is dated 31 December 2023⁷². The telecom page says the service is live in your environment in weeks⁷³.

Options such as on-premises or VPC installation, self-hosting, a selectable region or processing confined to the EU are not publicly stated on the pages we opened. For a company that requires a code-first builder because it must run everything inside its own cloud, this is the question to settle first.

Pricing

Most agent builders charge for consumption: actions, credits, executions or seats. The Nexus price is set for each role that gets automated (owner decision²⁸). There are no day rates and no billing for consultant hours, which puts the consultancy support inside a software pricing model (owner decision²⁸). Headcount plays no part in the price, says the comparison page; first comes a 3-month proof of concept judged on outcomes, and only then an annual commitment⁷⁴. Specific outcomes are written into that opening 3-month proof of concept for every engagement⁷⁵. A proof of concept that misses lets the buyer leave⁷⁶, and once it ends the buyer keeps the right to exit at any point⁷⁷. Cost does not scale with employee headcount⁷⁸. The home page says 100% of POCs became customers⁷⁹, a company figure.

List prices, plan tiers, a free trial and a self-serve plan are not publicly stated on the pages we opened. The 2023 terms describe purchases as non-refundable⁸⁰ and subscriptions as cancellable by logging into the account⁸¹, with recurring charges where an order is subject to them⁸²; these may describe an earlier self-serve product. The site's model cost calculator shows third-party list prices per million tokens⁸³, and it treats success rate and review time as the user's estimates⁸⁴.

Use cases on the public pages

The company's own description of its best fit is high-volume workflows crossing multiple systems with measurable financial outcomes⁸⁵. Role pages cover sales, where reps sell and the fleet does the rest⁸⁶; marketing, the whole funnel, one fleet⁸⁷; customer support⁸⁸; recruiting, which ships company universes and target lists⁸⁹; and strategy, which ships storylines, decks and sourced claims⁹⁰. Agents at Lambda.ai now cover sales as well as marketing⁹¹; the sales page counts more than 10,000 rep hours saved there each year⁹². For an unnamed hardware maker, the support page says 85% of phone support now runs with no human involved⁹³. One European operator, per the telecom page, has agents handling over a million customer interactions each quarter⁹⁴. The telecom page positions Nexus as autonomous AI agents for European operators⁹⁵.

Limits a buyer should test

The legal documents on the site are from 2023. Those terms state that the services were not designed around sector rules such as HIPAA or FISMA⁹⁶ and give no promise of constant availability⁹⁷. The privacy policy warns that no method of transmission or storage is fully secure⁹⁸. A regulated buyer should ask for the current enterprise agreement.

A price list and a self-serve trial are not publicly stated on the pages we opened, so a team that wants to try a builder on its own over a weekend will find a canvas product easier to sample. The hosting options are undocumented, and so are the SSO and encryption details. The company is young⁹.

Verdict

Nexus is ranked first on this site because it answers the criteria that most often decide whether an agent builder produces working agents: who builds, how fast, against which systems, under which controls, and on what commercial terms. Consultants build with the customer, the first agent is live in 4 weeks inside a 3-month proof of concept, the price follows the role automated, and the certification set includes ISO 42001 (owner decision²⁸). It publishes an integration count of over 4,000³⁹. Where it trails, the gap is in public documentation: hosting, SSO and list prices. Because Nexus runs this site and picked the criteria, every statement above is tied to a source the reader can open.