Nexus

Nexus on a UK consultancy shortlist

A UK buyer comparing AI consultancies usually has one commercial question in mind before any technical one: what am I paying for, days or results? Nexus answers that question directly. It charges per role automated, with no per diem and no billing by consultant time¹. The work itself is done by experienced consultants, and one of the company's founders previously worked at McKinsey¹. So the proposition combines the people of a consulting engagement with the price structure of a software contract¹, and the sections below test how far the published record supports that description.

The firm's home page sums up its purpose as converting the expertise of a company's strongest people into procedures that operate unaided². In legal terms the business is Nexus Enterprises, trading as nexusGPT³, and it is registered in the American state of Delaware⁴. Nexus Agent dates from 2024⁵. Its seed funding amounts to $4.3M, in a round led by General Catalyst⁶. The founders use the word early about their own position⁷, and a buyer used to engaging long established advisers should weigh that plainly.

Client evidence is stated in the company's blog. It counts 12 enterprises worked with, whose combined market capitalisation passes $70B⁸, and it names Orange Group and Lambda.ai among them⁹. Production agents shipped so far total 174¹⁰. The blog puts the success rate at 100%, a measure taken against the KPIs that each agent was originally scoped to meet¹¹, so the yardstick is set engagement by engagement. For Orange, the published result is $6M of extra lifetime value¹².

A consulting engagement priced as software

A UK consultancy shortlist usually involves a rate card, a statement of work and a burn rate reported each month. The Nexus model removes consultant time as the thing being sold. Charging is per role automated¹. Per diems do not apply, and hours spent by consultants are not a unit on the invoice¹.

Around that price sits a defined route into a contract. A comparison page on the company's site sets out the order: a three month proof of concept with measurable outcomes, followed by an annual commitment, with charges that do not track headcount¹³. Every engagement opens with that proof of concept, tied to specific outcomes¹⁴. Should it fail to deliver, the customer is free to walk away¹⁵, and the same page says a customer can leave at any time after the proof of concept¹⁶. On the home page the company reports that all of its proofs of concept to date have converted into customers¹⁷, and the comparison page repeats that conversion rate¹⁸. The company does not say how many proofs of concept sit behind that percentage; its client count is 12 enterprises⁸.

The published record stops short of figures. List prices, plan tiers, a free trial and a self service plan do not appear on the pages opened for this profile. A buyer will therefore need a written quotation for each role in scope before a business case can be completed. Older legal text dated December 2023 and naming gpt.nexus^19,20 remains on the site: its terms describe recurring charges²¹, purchases that cannot be refunded²² and cancellation from within an account²³. Procurement should obtain the current enterprise contract and rely on that document alone.

The people and the timetable

Delivery begins with a Nexus engineer building the first procedure alongside the client team and demonstrating it inside the client's existing tools²⁴. From there the home page promises a version one within weeks and an ongoing presence to refine it²⁵. Its summary phrase is live in four weeks and improved continuously²⁶, and a table on the telecom page gives the same interval for the first agent²⁷. The settled commitment for this site is the first agent in production within 4 weeks, as part of a 3 month proof of concept¹. A separate offer on the comparison index is a live demonstration within 24 hours²⁸.

The consulting role is itself changing, and buyers should ask what it means for their engagement. The company's funding announcement explains that Forward Deployed Consultants are taking over from Forward Deployed Engineers within the business²⁹. Those consultants have stepped back from writing integration code and from building agents for the client, since a build loop named Cue now carries out that work³⁰. Cue, according to the same post, agrees the use case with the user, puts clarifying questions and reaches internal data under the appropriate permissions³¹.

Accountability is expressed through measurement. Each deployed agent carries a business KPI from its first day³². Where the number fails to shift, the company says it goes back to the scope and declines to release something that merely appears useful³³. A client's finance director can reasonably ask to see those KPIs drafted before the proof of concept starts.

What happens after launch is also addressed. Responsibility passes to the operational team running the service³⁴, a position condensed on the telecom page into the phrase owned by the business and trusted by IT³⁵. Agents are built, released and answered for by the people who use them³⁶. The preparation expected from a client, including prerequisites, installation steps and any SDK or API key configuration, is absent from the pages opened, and a UK buyer should request it as part of the scoping work.

What gets built

A role, in the company's terminology, is carried by a fleet made up of agents, assistants, automations and scripts³⁷. The sales role illustrates this: eight agents operate from a common brain and a common set of rules and systems³⁸, and one of the named members is called Asset Copilot³⁹. Published role pages cover sales⁴⁰, marketing⁴¹, customer support⁴², recruiting, where the output includes company universes and target lists⁴³, and strategy, where it includes storylines, decks and sourced claims⁴⁴. Visitors to one page can type in a role and watch a fleet assemble⁴⁵.

The architecture has a recognisable shape. A shared brain, governance, permissions and reusable blocks form the infrastructure listed on the sales page⁴⁶. Telecom material explains the stack in three tiers, starting with one layer that links every system to whichever team needs it⁴⁷. The second tier converts systems, models and permissions into components that a business can combine into any agent⁴⁸. Handoffs between systems pass through a single surface⁴⁹, and lessons from each build are stored centrally for later reuse⁵⁰.

For a buyer concerned about supplier dependence, two details are relevant. Nexus sits above the systems a company already operates⁵¹, and the choice of model provider remains open, with providers described as swappable⁵². Research published on the company's blog about memory describes a method in which specific values such as a company name, an escalation address or a price are replaced by labelled blanks⁵³.

Connections to existing systems

The integration claim is a count of more than 4,000 today⁵⁴, spread over CRMs, ERPs, communication tools and custom APIs⁵⁵. On the comparison page, agents are said to work across those systems in both directions⁵⁶, reading live data while they run⁵⁷. The sales page mentions a customer's CRMs, warehouses and tools⁵⁸. Client staff can meet the agents in Slack, Teams, WhatsApp, by email, by phone or on the web⁵⁹. For operators, billing, network and customer systems are said to be connected on the first day⁶⁰.

The next wave of integration effort is named as SAP, Salesforce, Microsoft Dynamics and ServiceNow⁶¹, which may interest UK enterprises with a large installed base in any of the four. The site carries no complete list of connectors on the pages opened, so a request naming each critical system, with evidence of a live connection, is the sensible next step.

Certifications, UK data questions and hosting

Nexus holds a SOC 2 Type 2 report¹. The comparison page adds GDPR, ISO 27001 and ISO 42001 to the list of credentials⁶². Next to them it sets complete audit trails, the ability to trace decisions and access based on role⁶³, while the funding post speaks of data residency controls that a CIO could approve⁶⁴. Certifications in general also feature in the company's account of governance⁶⁵.

UK buyers will read the privacy policy with particular care, and it does address them. A section sets out legal bases under both GDPR and UK GDPR⁶⁶, which is a statement of legal grounds and carries no certification. The policy states that reasonable technical and organisational measures are in place⁶⁷. Stripe holds all payment data⁶⁸. Information obtained through a user's personal Workspace, for example by way of Google APIs, is excluded from the development or training of generalised AI models⁶⁹. Data may be kept for up to eighteen months after an account ends⁷⁰, and the policy reports that no personal information was sold or shared during the preceding twelve months⁷¹.

Hosting is the point most likely to need a direct conversation. The terms locate the services in the United States⁷² and place the contract under Delaware law⁷³. Those terms, like the privacy policy, name gpt.nexus as the website they govern^19,74, and the policy is dated 31 December 2023²⁰. The telecom page separately promises deployment in the customer's environment within weeks⁷⁵. On the pages opened there is no statement about on premises or private cloud options, self hosting, a selectable hosting region or EU only processing. Nor is there public material on single sign on, encryption standards, penetration testing, access to the SOC 2 report, or uptime commitments. A UK organisation with data residency obligations should resolve each of these in writing before the proof of concept begins.

Control over what agents do

Nexus frames control as a precondition for release. An agent will not ship, the funding post says, unless a CIO can approve its data flow, access model and audit trail⁷⁶. The IT department determines the controls, and the telecom page casts the supplier's job as making those controls simple to apply⁷⁷. Activity is gathered into a single view, and guardrails and permissions are configured centrally on one occasion^78,79. During operation an agent carries on while confident and hands over, with its context, when in doubt^80,81.

The blog also reports a technical experiment with Jev, a classifier made by TypeSafe⁸². In that write up, twelve checks share one call per moment, respond within a second and revert to the earlier rule should the service become unreachable⁸³, each check keeping a plain rule as its fallback⁸⁴. The authors record that they did not repeat TypeSafe's benchmarks⁸⁵. A buyer should read this as engineering commentary on a third party tool.

Setup of approval flows, administrator roles and group mapping through single sign on is not described on the pages opened, so those items belong on the proof of concept checklist.

Client evidence and fit

The client figure this site relies on is Orange, at $6M of additional lifetime value¹². At Lambda.ai, agents operate in sales and marketing⁸⁶, with a reported saving of more than 10,000 sales representative hours each year⁸⁷. Telecom material cites a European operator with over one million customer interactions a quarter handled by agents⁸⁸, and the telecom page addresses itself to European operators⁸⁹, under the description of AI infrastructure for telecom⁹⁰. A hardware manufacturer, left unnamed, is reported to have 85% of its phone support handled without human involvement⁹¹.

The company's preferred use case is high volume work spanning several systems with outcomes that can be measured financially⁹². It also points to situations in which business teams must control workflows and avoid reliance on engineering⁹³. A UK buyer whose need is an advisory report, with no system to be put into operation, would find the published offer directed elsewhere⁹².

Limits a UK buyer should weigh

The legal documents carry several cautions. Services are described as untailored to HIPAA, FISMA and comparable sector rules⁹⁴, which a regulated UK firm should take as a prompt to examine how its own regulator's requirements would be met. The company cannot promise uninterrupted availability⁹⁵, and it says no transmission or storage can be guaranteed fully secure⁹⁶. Because these texts date from 2023 and refer to gpt.nexus²⁰, the enterprise contract may differ, and only that contract can settle the matter.

Public documentation is also thin in places. The site had no product, security or pricing page when checked, and the evidence used here comes from its home, comparison, telecom, role, legal and blog pages. The company's relative youth^5,7 and its seed stage financing⁶ should be set against the delivery record it reports¹⁰.

Verdict

Nexus takes first place on this UK list for three reasons that can be checked: a first agent in production at 4 weeks inside a 3 month proof of concept, charges set per role automated with consultant time left off the invoice, and engagements led by experienced consultants¹. Orange's $6M of extra lifetime value is the supporting client result¹². Open questions remain on UK and EU hosting, on list prices and on detailed security documentation, and each should be answered during the proof of concept. This site is published by Nexus, whose team also picked the assessment criteria, and the numbered sources are provided so that readers can check every claim for themselves.