Before you say yes to a prospect, settle the question “does our product support this?” in the code: put it to Claude with the Everyone profile, and let the status of the answer set what you promise. That is how pre-sales technical questions get an answer without waiting for an engineer. Verified can be repeated; Backend only is never self-service; Not found is a probable no, not a proven one.
What follows is for salespeople, pre-sales and sales leaders. The tool is DeployIt, an MCP server that answers questions about your product from your company's repositories, and says what each answer is worth.
Why is “does our product support this?” the riskiest question in a deal?
Because it arrives mid-call, and the true answer is in the code. A salesperson has three options, none of them good: say yes from memory, promise to come back and lose the momentum, or message an engineer who is busy elsewhere.
The yes from memory is the expensive one. It is rarely a lie: the feature exists, roughly. What memory drops is the limit: a format, a ceiling, a step only your own team can perform. Nobody notices during the call; the customer does at onboarding, after signing.
What does an answer from the code look like?
An example, labelled as one. The prospect's finance team wants to export its invoices alone, every month.
A prospect wants their accountants to export invoices to CSV themselves. Does our product support this?
The product can produce a CSV export of invoices: the export exists on the server.
No screen leads to it. Nothing in the interface lets a customer start the export themselves.
Three things came back: what exists (the export), what does not (a way for the customer to start it), and what the answer is worth (its status). A yes from memory would have sold a button that is not there.
The first time, the investigation takes 20 to 60 seconds, which is long in a live call. Ask the predictable questions before the meeting: the same question, in the same words and without context, then comes back at once as long as the code has not changed.
Pre-sales technical questions: what does each status let you promise?
Every answer about the code carries one of four statuses, defined in Reading an answer. In a deal, each one becomes a sentence you may say and a line you may write.
| Status | What it means | What you tell the prospect | What you do with it |
|---|---|---|---|
| Verified | Confirmed in the code. You can repeat it. | The answer, limits included. | It goes into the proposal as stated. |
| Backend only | The product can do it, but no screen leads there. | “The product can do it; it is not something you do yourself from the interface.” | Never promise it as self-service. The product team says whether, and how, it can be offered before anything is written. |
| Not found | Searched for without being found: most likely absent from the product. It is not proof. | “I don't believe we support it. I will confirm.” | Count it as a no to qualify the deal; have the product team confirm before it becomes a written no. |
| Inconclusive | The investigation didn't get there. | “I will come back to you on this point.” | Ask again “in depth” if your profile allows it, or hand it to someone with the Developers profile. |
Verified also covers “partly”
A verified answer is not always a yes. In the sales example on our home page, a prospect wants invoices in several currencies, and the verified answer is “partly”: each invoice carries a single currency, set when it is created, while the same customer can receive invoices in different currencies. That sentence is the promise. Nothing wider.
Backend only is the status that hurts deals
“The product can do it” is true, and it sounds like a yes. The prospect hears self-service. The status says less: the capability is in the product, and no screen leads there.
Whether your team runs it for the customer, and on what terms, is a decision. It belongs to the product team and to whoever signs the contract, before the proposal goes out.
Not found is not proof
It is a search that came back empty, in the repositories your company connected. The feature is most likely absent. Do not turn it into a written “we can't” before the product team confirms, and never into a “we can” because the prospect insists.
Which questions can sales not ask?
Three boundaries, all deliberate.
The topics your company refuses. An administrator lists, profile by profile, what the agent will not discuss: security or internal pricing, for example. The refusal is stated plainly to Claude, which passes it on to you. Take the question to the person who owns the topic.
The code itself. The Everyone profile never shows code: no line, no file path, and the names of team members the filter recognises are removed. It is filtered and tested, and no filter is infallible; the detail is in who sees what. If a prospect's engineers want to see how a feature is built, that conversation belongs to your pre-sales engineer.
Decisions. A delivery date, a roadmap item, a discount, a custom development. None of them is a fact in the code: DeployIt reports what the code does, not what your company will decide. To tell a fact from a commitment, see which product questions you can answer without interrupting an engineer.
One practical limit: by default, the Everyone profile has 40 questions per person per month, a cap your administrator can change.
How does a sales team use it week after week?
Three habits are enough.
Before a meeting, ask the questions this kind of prospect always raises, and note the status beside each answer.
On a questionnaire, put each “does the product support…” line to Claude. Illustrative example, with invented figures: out of 20 functional lines, 14 come back Verified, 3 Backend only, 2 Not found, 1 Inconclusive. The pre-sales engineer reviews six lines, not twenty.
After a call, write the status next to the promise in your notes. Six months later, when the account opens a ticket about it, support reads the same code the same way: see how to answer support tickets from code.
Tell the team one more thing: every question is logged under the name of the person who asked it.
What DeployIt does here
DeployIt is an MCP server. Your company gets one link, https://mcp.deployit.ai/<company>/<code>; each person adds it to Claude (on the web, on the desktop or in Claude Code) and signs up with a name and an email, which is not verified; their questions are logged under that name. Everyone starts with the Everyone profile: questions about the product, answered from the code; a filter removes the code, the file paths and the names of team members it recognises from the answers, without proving their absence, and a leak test tells you what still gets through. An administrator gives the Developers profile (excerpts) or the Leadership profile (developer statistics) to whoever needs it. Repositories are connected from GitHub or GitLab; DeployIt makes no commit, branch or pull request, and only adds one webhook per repository.
The full description, profile by profile, is in DeployIt: ask your code and follow each developer's work from Claude.
Next step: write down the three questions your last prospect asked. Add the demo address below to your Claude connectors to see what an answer and its status look like, then connect one repository, add your company link to Claude in three steps and ask them about your own product.
Price. Free plan: 15 questions a week for the whole company. A 30-day trial, no card. Plans from €290 a month excluding tax for up to 25 tracked developers: see pricing.
Ask your code from Claude
30-day trial, no card. Or try the demo first: add https://mcp.deployit.ai/demo to your Claude connectors.
Frequently asked questions
How can a salesperson check whether the product supports a feature?
Ask the question in plain language from Claude, connected to the company repositories through DeployIt. The answer comes from the code and carries a status: Verified, Backend only, Not found or Inconclusive. Only a Verified answer can be repeated to a prospect as a fact.
What does “Backend only” mean for a sales promise?
It means the product can do it, but no screen leads there. A customer cannot do it alone from the interface, so it must never be promised as self-service. Whether your team can offer it another way is a decision to take with the product team before the proposal goes out.
Does “Not found” prove the product cannot do something?
It does not. Not found means the investigation searched without finding: the feature is most likely absent from the product, but that is not proof. Tell the prospect you do not believe it is supported, and have the product team confirm before it is written anywhere.
Can salespeople see the source code with DeployIt?
Not with the Everyone profile, which every sign-up starts with. The answers are prose: a filter removes the code, the file paths and the names of team members it recognises. No filter is infallible, so a leak test attacks the profile and tells administrators what gets out. Code excerpts are for the Developers profile, which an administrator gives person by person.
Which pre-sales technical questions can sales not ask?
The topics the company has put off-limits for the profile, security or internal pricing for example: an administrator lists them profile by profile, and the refusal is stated plainly. Questions that are decisions rather than facts, such as a date, a discount or a custom development, have no answer in the code at all.
Continue reading
How to answer support tickets from code, without a developer
For support leads, agents and customer success: one ticket followed from the question to the reply, and what to do with each of the four statuses an answer from the code can carry.
How to ask questions about your codebase in Claude before you ask an engineer
For support and product teams: most of the questions you send a developer have their answer in the code. How to ask Claude instead, and how to tell which ones still need a person.
How do you reduce developer interruptions from support?
For support leads, and the CTO whose developers they message: the questions that escalate fall into four cases. Documentation fixes one; for the one that comes back after every release, support asks Claude what the code does.