# Oction Labs Sales Objection Responses Version 1.0 | For internal sales team use only --- ## How to use this document Read the concern. Acknowledge it. Respond in 2-3 sentences. Add a proof point where one fits. Then pivot to a concrete next step. Do not improvise claims. Stick to measured facts and the capabilities we have built. --- ## Security / Privacy Objections ### "How do we know our data is safe?" **Acknowledge:** You are right to ask. Every organization that takes AI seriously should start here. **Response:** Your documents live on infrastructure you control, inside your own network or a dedicated node. We do not operate a shared cloud service where your files sit next to another client's data. Encryption at rest and in transit is standard, and every access is logged to an audit trail you can review or hand to an assessor. **Proof point:** This is per-tenant isolation by design, not by policy. Your knowledge base is physically separate from every other deployment we run. **Pivot:** Let us walk through the architecture on a call and show you where each document sits at each stage. --- ### "What about client confidentiality / solicitor-client privilege?" **Acknowledge:** This is the barrier that stops most professional services firms from touching public AI tools. **Response:** With a sovereign deployment, nothing leaves your building. Your client matter, precedents, and correspondence are processed on your own hardware or dedicated infrastructure under your control. No third-party model provider sees the text, so the privilege and confidentiality analysis stays simple. **Proof point:** We have measured 0% fabrication on trap questions in our test set, which means the system cites real documents, not invented sources that could expose you. **Pivot:** We can run a live demo against your own precedent documents under an NDA. You will see exactly what touches the network and what does not. --- ### "Can you pass our security audit?" **Acknowledge:** If you cannot pass an audit, the system does not get turned on. That is a reasonable standard. **Response:** The stack is built to be auditable, not just secure. De-identification happens before storage, access is tied to named users and hardware keys, and every query and export is timestamped and logged. We have run this architecture through internal compliance review and can provide the control mapping your auditors will want. **Proof point:** Full audit trail is part of the base deployment, not an add-on. **Pivot:** Share your audit questionnaire or framework and we will return a populated control matrix within 48 hours. --- ### "What if there's a data breach?" **Acknowledge:** Breach response is a board-level topic, and you need a concrete plan, not a promise. **Response:** Because the system is single-tenant and air-gapped by design, a breach at another client is not your breach. Your environment is isolated. If an incident touches your own perimeter, you retain full ownership of the data and logs, so your incident-response team controls the timeline and the disclosure. **Proof point:** No shared tenant means no shared blast radius. **Pivot:** We can review your incident-response playbook and show how the deployment maps to your existing procedures. --- ## Cost / ROI Objections ### "This is expensive." **Acknowledge:** The sticker price is real. So is the cost of doing nothing. **Response:** Most mid-market firms we speak with are already bleeding six figures a year in non-billable search time, rework, and knowledge walking out the door with departing staff. The Standard deployment starts at $25,000 plus $10,000 per month, which turns into a fixed line item instead of a hidden capacity drain. **Proof point:** One engineering firm baseline we have modeled: 10 engineers spending 5 hours per week hunting for prior calculations, at a loaded rate of roughly $250 per hour, burns approximately $650,000 in annual capacity. **Pivot:** We can run the bleed calculator against your actual headcount and hourly cost in 15 minutes on the phone. --- ### "What's the ROI?" **Acknowledge:** You need a number you can defend to leadership or a board. **Response:** ROI starts with time returned to billable work. An associate who stops spending two hours a day searching precedents and starts billing those hours at $300 produces a measurable delta. The system also preserves institutional knowledge that otherwise retires or resigns, which is harder to quantify but easy to value after a key departure. **Proof point:** Our measured evaluation shows 74% correct retrieval-grounded answers, versus roughly 5-10% accuracy when the same questions are asked without grounded retrieval. That is the difference between finding the clause and starting over. **Pivot:** Let us build a conservative ROI model with your billable rates and search-time estimates. You can take it to your leadership unchanged. --- ### "Why not just use ChatGPT?" **Acknowledge:** ChatGPT is fast, cheap, and already on your staff's phones. The comparison is fair. **Response:** ChatGPT is a general-purpose tool that trains on public data and retains prompts. It cannot cite your own documents, it will hallucinate citations, and it is not compliant with privacy law or professional confidentiality rules. We are not competing with convenience. We are replacing the unsecured workaround your staff are already using with something that passes audit. **Proof point:** 0% fabrication on our trap-question test set. ChatGPT and similar public tools score materially higher on fabricated answers when tested against proprietary material. **Pivot:** Bring us a sample of three questions your team actually struggled with this month. We will show you the difference between a public guess and a grounded answer with the source paragraph attached. --- ### "Can we start smaller?" **Acknowledge:** A phased approach reduces risk and lets you prove value before expanding. **Response:** The Standard deployment is our smallest structured engagement: one department, one knowledge base, and your first reviewed workflow tools. We do not offer a trial or pilot in shared infrastructure because that would violate the sovereignty model. What we can do is scope the initial ingest tightly to one high-pain document set and prove value there before adding departments. **Proof point:** Six to eight weeks from kickoff to live system. You see results within the first quarter. **Pivot:** Let us identify the single highest-bleed document search problem in your organization and scope the first phase around that. --- ## Technical Objections ### "Will this integrate with our existing systems?" **Acknowledge:** No one wants a siloed system that duplicates work or breaks workflows. **Response:** The deployment sits alongside your existing file servers, document management systems, and identity providers. We ingest from standard formats and can build custom integrations at $250 per hour where an API or scheduled export exists. The AI does not replace your TMS, DMS, or EMR. It makes the knowledge inside them queryable. **Proof point:** We have built against unstructured file stores, SQL exports, and scheduled CSV dumps. If your system can export, we can ingest. **Pivot:** Tell us what systems you run today and we will map the integration points in writing before you sign. --- ### "What about our legacy documents?" **Acknowledge:** Most organizations we work with have decades of material in formats that predate any modern database. **Response:** The ingestion pipeline handles PDFs, scanned documents, Word files, spreadsheets, and plain text. For paper-era records that exist only in physical filing cabinets, we offer legacy data digitization at $5,000 per terabyte. Once digitized, they enter the same classified, de-identified pipeline as everything else. **Proof point:** A geotechnical client hypothesis we have modeled: decades of drill logs and closure docs in one cabinet at one site, made queryable for the next engineer who inherits the project. **Pivot:** Send us a sample of your messiest file formats. We will run them through the ingestion pipeline and show you what the system extracts. --- ### "How accurate is it really?" **Acknowledge:** Accuracy is the make-or-break metric. A wrong citation in a legal brief or an engineering calculation is worse than no answer at all. **Response:** On our measured test set, retrieval-grounded responses are 74% correct, compared to roughly 5-10% when the same questions are asked without grounding in your own documents. More importantly, when the system does not know the answer, it says so. It does not fabricate to sound helpful. **Proof point:** 0% fabrication on trap questions in our test set. The system prefers admitting a gap over inventing a citation. **Pivot:** We will run a live test on your own documents during the demo. You ask the questions and you judge the answers. --- ### "What if it hallucinates?" **Acknowledge:** Hallucination is the number-one reason regulated organizations hesitate on AI. The concern is justified. **Response:** Hallucination is primarily a problem with generative models that answer from public training data. Our system is retrieval-grounded: it searches your own documents and returns verbatim or closely derived passages with citations attached. It is not guessing from the internet. If the document does not contain the answer, the system states that explicitly. **Proof point:** 0% fabrication on our measured trap-question evaluation. Every answer points to a source document, page, or paragraph that you can verify. **Pivot:** During the demo, we will ask it a question your documents do not cover. You will see the "I do not know" response in real time. --- ## Process Objections ### "Our staff will never adopt this." **Acknowledge:** Technology that sits unused is a failed project, no matter how well built. **Response:** We have seen fastest adoption when the system answers a question staff already ask ten times a week. The interface is a plain search box. No new software to learn, no prompt engineering required. We also include staff onboarding as part of the deployment, and we tune the system based on early user feedback in the first 30 days. **Proof point:** The best measure of adoption is time-to-first-value. Most users get a useful, cited answer in their first session. **Pivot:** Let us identify the one question that triggers the most internal interruptions in your firm. We will show the team how the system answers it in seconds. --- ### "This will take too long to implement." **Acknowledge:** Six months to value is a death sentence for any internal technology project. **Response:** Our standard deployment runs six to eight weeks from signed agreement to live system, not months. There is no discovery phase to pay for. Kickoff includes document ingestion, knowledge-base build, and your first workflow tools. You see answers from your own material within the first few weeks. **Proof point:** The build phase is fixed-scope and time-boxed. We do not run open-ended projects. **Pivot:** We can share a week-by-week implementation timeline for the Standard deployment so you know exactly what happens when. --- ### "We've tried AI before and it failed." **Acknowledge:** A failed AI project leaves scars. Your skepticism is earned. **Response:** Most failed enterprise AI projects fail for three reasons: the tool was public-cloud and breached policy, the answers were not grounded and staff stopped trusting them, or the project never made it past a pilot because the business case was vague. We do not run pilots in shared infrastructure. We deploy sovereign, retrieval-grounded systems with a scoped use case and a fixed timeline. **Proof point:** 74% accuracy with retrieval grounding versus the ~5-10% you get from ungrounded tools. The difference is the difference between a tool staff trust and a tool they abandon. **Pivot:** Tell us what went wrong last time. We will be direct about whether our model addresses that failure or whether your situation is not a fit. --- ### "We need to run this through procurement / RFP." **Acknowledge:** Procurement is not a stall. It is a real process, especially in government and large firms. **Response:** We have worked with procurement and RFP cycles before. We can provide a full control matrix, security documentation, and pricing in the format your procurement team expects. For public-sector clients, the sovereign-deployment model aligns directly with data-residency and FOIPP requirements, which often strengthens the procurement case rather than complicating it. **Proof point:** No third-party model dependency, no US-cloud processing, full audit trail. These are procurement assets, not liabilities. **Pivot:** Send us your standard vendor questionnaire or RFP template. We will return a complete response within one week. --- ## Competitive Objections ### "Microsoft Copilot can do this." **Acknowledge:** Microsoft Copilot is a capable product and your organization may already pay for it. **Response:** Copilot operates inside the Microsoft cloud ecosystem. If your data-residency rules, client confidentiality obligations, or procurement policy allow that, it may be sufficient. If your data must stay on premises, if you need single-tenant isolation, or if you require citations to your own documents with 0% fabrication on audit, Copilot does not meet that bar. **Proof point:** Sovereign deployment means your documents never leave your perimeter. That is an architectural difference, not a feature gap. **Pivot:** We are not asking you to rip out Microsoft. We are asking you to compare where your most sensitive documents live in each model and decide which one your auditor would accept. --- ### "We're already looking at [competitor]." **Acknowledge:** You should look at alternatives. A single-source decision is poor practice. **Response:** We encourage the comparison. Ask every vendor three questions: where do my documents physically sit, what is the measured accuracy on my own material, and what happens to my data if I terminate. Most competitors in this space run multi-tenant cloud platforms with limited auditability. Our answers are concrete because the architecture is built to be inspected. **Proof point:** 74% measured accuracy, 0% fabrication, per-tenant isolation, full data export on request. **Pivot:** Run us in parallel. We will do a live demo on your own documents while you are still in evaluation with the other vendor. No commitment required. --- ### "We'll just build this ourselves." **Acknowledge:** A capable internal IT team can assemble open-source components into a working system. The question is whether that is the best use of their time. **Response:** Building a sovereign retrieval stack requires expertise in embedding models, vector storage, document pipelines, access control, and audit logging. We have already built it, tested it, and hardened it. Your team can spend six to twelve months building and debugging, or they can take ownership of a deployed system in six to eight weeks and focus on the integration and workflow work that only they know how to do. **Proof point:** We have run this architecture through internal compliance review and operational stress testing. You are buying the time and the risk we have already absorbed. **Pivot:** If your team wants to build, we respect that. Before they start, let us show them what a finished system looks like so their build spec is grounded in reality. --- ## Quick-reference proof points | Claim | Source | |-------|--------| | 74% correct retrieval-grounded vs ~5-10% without | Oction Labs measured evaluation | | 0% fabrication on trap questions | Oction Labs measured test set | | Sovereign deployment, per-tenant isolation | Architecture specification | | Full audit trail | Base deployment capability | | 6-8 weeks to live system | Standard deployment timeline | | Standard: $25,000 + $10,000/mo | Pricing schedule | | Enterprise: $200,000 + $20,000/mo | Pricing schedule | --- *eight agents. one organism.*