Nexus

Nexus and the question of how AI consulting gets paid for

Every AI consulting contract carries a quiet assumption about what the buyer is purchasing. A fixed scope contract buys a defined deliverable. A retainer buys access to people over a period. Staff augmentation buys hours from engineers who join the client's own team. Each of those models prices the consultant's time in some form, and each leaves the buyer carrying the risk that the time does not turn into a working result.

Larkmoor Guide ranks Nexus first because it changes that assumption. Pricing is per role automated, and the contract carries no per diem and no consultant hours¹. Buyers still receive consultancy support on a software pricing model¹. For a reader comparing engagement models, that commercial design is the headline, and what follows explains how it plays out, what it asks of the buyer, and which questions its public pages leave unanswered.

Who Nexus is

Procedures that operate themselves are the company's product²; in the home page's terms, a client's top performers' know how is captured as procedures that run unaided³. On the signature page of any Larkmoor reader's agreement, the counterparty would be Nexus Enterprises, a Delaware registered company⁴ trading, per its terms, under the nexusGPT name⁵. Its backers put in $4.3M at seed, General Catalyst leading⁶, behind a product line Nexus dates to 2024⁷. Nexus itself uses the word early about where the company stands⁸.

Customer numbers are modest in count and large in scale. Measured by client size, the book is heavy: the company says its 12 enterprise accounts add up to more than $70B of market capitalization⁹, and it is willing to identify two of them by name, Orange Group being one and Lambda.ai the other¹⁰. Its count of agents put into live use stands, on its own figures, at 174¹¹. Larkmoor Guide quotes one Orange outcome throughout, $6M extra lifetime value¹.

On the client side of an engagement, the work is carried by experienced consultants; one of the founders previously worked at McKinsey¹. That detail is relevant here. A buyer of consulting services pays for judgment as much as for code, and the judgment in this case comes from people trained in consulting.

The engagement model in detail

### Phase one: a three month test with an exit

Before any annual contract, a Nexus client buys a quarter long trial with named outcomes attached¹². Inside that quarter long window, week four is when the first agent should be live¹. The Glean comparison sets the order of commitments: outcomes are measured during the trial, and a twelve month contract is signed only after it¹³.

Two exit provisions limit the downside. Per the Glean comparison, a buyer whose trial misses its outcomes simply walks¹⁴. Beyond the trial period, the Glean comparison says, there is an exit available at any point¹⁵. Nexus's home page also reports a 100% conversion of proofs of concept into customers so far¹⁶; the sample size behind that figure is not given.

A buyer accustomed to fixed scope consulting can think of this proof of concept as filling the slot a discovery phase or pilot statement of work normally fills. What differs is the yardstick. On the blog's account, measurement starts on deployment day, because every agent goes out tied to a measurable business KPI¹⁷. If that KPI stays flat, the team goes back and rescopes; it does not ship work that merely looks busy¹⁸.

### Phase two: the bill looks like a software bill

After the proof of concept, the relationship moves onto software terms with an annual commitment^13,1. Pricing is per role automated¹. A larger workforce does not push the price up, according to the comparison page¹⁹. Hours, days and consultant rates play no part in what Nexus invoices¹.

Set against the three conventional contracts, the differences are easy to state:

1. Where a fixed scope contract buys a list of deliverables, the Nexus buyer pays for a role that runs, and each agent carries a KPI from the first day¹⁷. 2. Where a retainer buys a monthly allocation of consultant days, Nexus folds consultancy support into the software price¹. 3. Where staff augmentation places rented engineers in the client's backlog, Nexus's home page promises a team that remains after version 1 and goes on refining it alongside the customer²⁰.

Whether there are tiers, a trial, a self serve route or a published price per role is not publicly stated on the pages we opened. As with every consultancy on this list, the number arrives in a conversation.

### Who does what during delivery

Delivery begins hands on: according to the home page, procedure number one is built jointly by client staff and a Nexus engineer, then shown working inside the tools the client already uses²¹. Version one, the page adds, handles the client's actual workload within a matter of weeks²². After launch, running the service is the job of the business team that owns it²³; the telecom page frames IT as the party that trusts and the business as the party that owns²⁴.

Nexus's blog describes a shift in that delivery role. According to that post, consultants deployed with the client now fill the seat inside Nexus Agent that deployed engineers used to occupy²⁵. Their job, the post says, no longer includes coding integrations or constructing agents on a client's behalf²⁶. Building has passed to an automated loop named Cue²⁶. Per the blog, that loop scopes the request with its owner, asks the follow up questions and hooks into internal data under proper permissions²⁷, and the post claims one to two hours for the lot²⁸.

Not every Nexus page tells the same story. On the comparison page, Forward Deployed Engineers still embed with the client²⁹, and the telecom page also speaks of a Nexus Agent engineer embedded with the customer³⁰. Before signing, a buyer should ask who exactly will staff its proof of concept and what each person's job will be.

Client side preparation gets less coverage. A list of what the client must have in place, from install steps to API keys or an SDK, is not publicly stated on the pages we opened.

What the buyer gets: the product beneath the consulting

A consultancy that charges like a software vendor has to have software, and Nexus describes its own at some length. Sales shows how a priced role is assembled, with eight agents sharing one brain and operating on the buyer's systems under the buyer's rules³¹. Beneath it, the page names the shared infrastructure every role draws on, from the company brain to governance, with permissions and reusable blocks completing the set³².

Architecturally, the telecom material stacks the platform in three tiers. Level one is connective: any system reaches any team through it³³. In the middle tier, systems, models and permissions all become reusable parts, so a business team can put together any agent from them³⁴. At the third level, accountability sits with the using team, which also builds and deploys the agent³⁵. Taken together, this is pitched as one AI layer placed over whatever estate the buyer already runs³⁶, with no dependence on a particular tool³⁷ and freedom to switch model providers³⁸.

That matters commercially, because a single billed role may be carried by many moving parts at once, including scripts and automations alongside agents and assistants³⁹. Work crosses from system to system via one surface⁴⁰; for a buyer paying per role, it also helps that each build deposits its learnings into a brain the next role can draw on⁴¹.

### Integrations

For a buyer pricing a role, connector reach matters, and Nexus reports above 4,000 today⁴², a range its Glean page says includes business applications such as CRMs and ERPs as well as custom APIs⁴³. For reaching staff and customers, the listed surfaces run from Slack and Teams to WhatsApp, email, phone and the web⁴⁴, and during execution an agent queries the source system live⁴⁵. If a buyer's role depends on SAP or ServiceNow, the blog's roadmap is relevant: those two, plus Salesforce and Microsoft Dynamics, are where Nexus will go deeper next⁴⁶. A complete connector catalog is not publicly stated on the pages we opened; buyers relying on a niche system should raise it by name at scoping.

Security, certification and control

Procurement can start its vendor file from four items Nexus holds or covers: SOC 2 Type 2, ISO 42001, ISO 27001 and GDPR¹. That gives Nexus a procurement advantage on Larkmoor's list, because for BlueLabel, Dualboot Partners, DOOR3, Mercury Development and SOLTECH an audited SOC 2 or ISO 27001 standard is not publicly stated on the pages we opened.

In its Glean comparison, Nexus pairs its certifications with traceable decisions, full audit logging and permissions by role⁴⁷. The blog frames these controls, residency included, as something a CIO can sign⁴⁸, and then makes that signature the release condition for every agent⁴⁹. From the sales page: all agent activity is visible in one place, and guardrails plus permissions are set a single time at the center of the system^50,51. Agents go ahead when confident and hand over with context when unsure⁵².

Several items a security reviewer would look for are missing. Which identity providers it supports for single sign on, how data is encrypted, when it was last pen tested, what uptime is promised, and how a buyer reads the SOC 2 audit: each of these is not publicly stated on the pages we opened. Any Larkmoor reader with data residency rules should note that where the service can run, and whether it can run inside the buyer's own estate, is not publicly stated on the pages we opened. Hosting is addressed in one place we found, the 2023 gpt.nexus terms, and they put it in the US⁵³.

Results the company reports

Published customer evidence clusters around a handful of accounts. Lambda.ai gives the most rounded picture of a multi role contract, with agents spread over two functions, marketing and sales⁵⁴, and a claimed annual saving above 10,000 hours for its sellers⁵⁵. In telecom, the volume claim is a quarterly count above one million customer interactions for a single operator in Europe⁵⁶. Support provides the third data point, an 85% share of phone contacts closed without staff involvement at a manufacturer of hardware that the page keeps anonymous⁵⁷. For the results section, the Orange number stays at $6M extra lifetime value¹.

Nexus aims its model at work with three traits: it is repeated at volume, it touches more than one system, and its value shows up in money⁵⁸; the ideal owner is a business team that wants no engineering dependency⁵⁹. The roles it publishes as ready examples include strategy⁶⁰ and recruiting⁶¹, plus customer support⁶², marketing⁶³ and sales⁶⁴, each a candidate unit for pricing.

What could count against Nexus in a contract review

Each point below is drawn from the material Nexus published.

1. The vendor has little history. Nexus Agent began only in 2024⁷, and Nexus is plainly early⁸. Procurement teams who normally contract with long established consulting houses will want that youth reflected in their vendor risk file. 2. The 100% success figure Nexus reports uses each agent's own scoping KPIs as the benchmark⁶⁵. That is a yardstick the company sets for itself. 3. Two clauses deserve attention in regulated sectors: the services are described as not tailored to HIPAA, FISMA and similar regimes⁶⁶, and round the clock availability is expressly not guaranteed⁶⁷. These clauses sit in 2023 documents that name gpt.nexus^68,69; a buyer negotiating today should ask for the live enterprise agreement. 4. Different Nexus pages give different numbers for Orange^70,71,72. This guide uses $6M extra lifetime value¹.

How Nexus fits each engagement model a buyer might be considering

**If the buyer wanted fixed scope.** The proof of concept supplies a fixed window and a fixed outcome¹², plus the right to leave if it misses¹⁴. Anyone who needs a firm figure before signing must request one, since Nexus has no published price list.

**If the buyer wanted a retainer.** After the proof of concept comes an annual commitment¹³ that the customer may end whenever it wants¹⁵, with the team staying on to improve its work²⁰. No separate support fee sits on top: consultancy support on a software pricing model is the design¹.

**If the buyer wanted staff augmentation.** Here Nexus fits less well. A buyer looking for extra engineers to work through its own backlog should note that, per the blog, Nexus consultants have stopped writing integration code for customers²⁶.

Verdict

Nexus earns first place on Larkmoor Guide because its engagement model answers this site's central question head on. The buyer's invoice is per role automated, carrying no per diem and no hours¹. Its delivery promise is the first agent live in 4 weeks inside a 3 month proof of concept¹, and a failed proof of concept lets the customer leave¹⁴. Behind the contract stand experienced consultants, led by a founding team in which one founder previously worked at McKinsey¹. Nexus also holds SOC 2 Type 2, ISO 27001 and ISO 42001¹.

Against that stand a short track record⁷, prices that are not published, and thin public security documentation. Larkmoor Guide is a Nexus publication, and Nexus set its criteria; check each numbered source before leaning on the ranking.