Nerd holds how your company does a job: the steps, the source each fact has to come from, what the document must contain, and which approval it needs. The assistant your team already uses asks Nerd, and follows it.

Which assistants does Nerd work with?

Any assistant that can add a remote connector. Today that is Claude, ChatGPT, Microsoft 365 Copilot and Gemini Enterprise, and it is the same Nerd and the same address in each one. On a business or enterprise plan your workspace administrator is the one who adds it.

Nerd works with the internal teams responsible for getting a deal right: sales, deal desk, RevOps, pricing, operations, and finance. It is most useful when answering one request means checking several systems, documents, and approval rules.

Is Nerd customer-facing?

No. Nerd works behind the scenes, inside the assistant your team already uses. It has no inbox, no chat presence and no way to reach a buyer. Your team remains the customer-facing voice.

What work does Nerd handle?

Nerd starts with quote work. It holds the steps a request goes through, the source each fact has to come from, what the output must contain, and which approval it needs before it goes out. The same shape covers the next job a company decides to teach it.

How is Nerd different from a CRM copilot or a general agent builder?

A copilot helps inside one product. A general agent gives you tools to build with. Nerd keeps the deal-desk workflow consistent across every assistant conversation: the same procedure, the same sources, the same approvals, whoever is asking and whenever they ask.

Can Nerd fit our deal-desk workflow?

That is the setup rather than a customisation project. Someone records how your team already does the job, reviews the playbook Nerd proposes from it, and publishes it. Different fields, pricing sources, documents, roles and approval paths are what a playbook is for.

What if our data and process are messy?

That is normal. Product specs may sit in PDFs, prices in spreadsheets, and exceptions in someone's head. Nerd holds the rule for which source wins and what to do when two disagree: ask, stop, use once, or propose a correction. You do not need a data migration before finding value.

How do we get started?

Create a workspace, connect Nerd to the assistant your team uses, and turn one real workflow into a reviewed playbook. There is no card to set up. If your company runs its assistant on a business or enterprise plan, adding a connector is something the workspace administrator does, so bring them in early.

Will Nerd act without our approval?

Nerd takes no action at all. It answers questions about how your company does the job. Your own assistant does the reading and writing, under each person's existing permissions, and a person still approves anything that commits.

Get in touch and we will give you a number for a team your size. We are setting pricing with the first teams using Nerd, so there is nothing published yet, and nothing to commit to before you have seen it work.

Our assistant already remembers how we work. Why do we need Nerd?

Your assistant remembers you: your wording, your habits, what you asked it last week. What it cannot know is how your company does the job, because that was never in your conversation. Nerd holds the company layer, so the steps, the sources and the approvals are the same whoever is asking. The two do not compete. Your own memory stays yours, and the playbook is shared.

What is a deal desk in your assistant?

A deal desk in your assistant is the repeatable work behind a quote, done by the assistant your team already uses, to rules your company wrote down: which sources to consult, what the output has to contain, and what must come back to a person before it goes out.

The distinction matters because it is more than a chatbot. A chatbot answers from whatever it can find, and two people asking the same question get two answers. A deal desk works to a procedure, and the procedure belongs to the company rather than to whoever typed the prompt.

How Nerd works

Nerd holds what your company published: the steps, the source each fact has to come from, the document and wording requirements, and which approval a request needs and where it has to be raised. Your assistant asks Nerd how this company does the job, then does the reading and the writing itself, under each person's existing permissions. Nerd does not connect to customer source systems, hold customer source-system credentials, or price quotes. It serves published guidance without running a model of its own.

The rules that make it trustworthy

Three. A model never authors a price; the playbook names the system the number comes from. Nothing commits; a person approves, in your own system, and Nerd holds no record that they did. And one person's way of working never becomes company policy: a change proposed from a real exception is published by a leader, or it is not published at all.

Why now

Teams already work in an assistant like Claude or ChatGPT every day. What they do not have is any way to make it answer the same way for everyone, which is a question about company knowledge rather than about the model.

How you start

Start with one repeatable workflow. Record how it is done today, review the playbook that comes out of it, publish it, and use it on the next real request. Expand once the first one is right.