Question 1

What does Ovvos Pipeline not do?

Accepted Answer

No kanban board. Dragging a card changes a status without a reason. In Pipeline every status change, comment and reminder lands in an audit trail with who, when, and old and new values — and the leads table carries 21 columns, ten filter groups and in-place editing, which a wall of cards cannot. No AI scoring or forecasting. A forecast built on a number somebody typed is a guess dressed as data. Pipeline’s profit figures come from a wizard that makes a person enter the actual cost and freight before a deal can close, so every report downstream is built on figures someone stood behind. No public API or third-party integrations. Every connector is a second copy of your data to keep in sync. Pipeline connects to Live Chat and Outreach inside the platform, where the record is the same record — and nothing outside Ovvos can quietly read or rewrite your customers. No discounts, quote approvals or e-signature. A quote is priced from your catalogue at the price you set; margin is captured once, at close, on the real numbers. Adding a discount field invites the salesperson to give it away on the quote and lose the trail. Approvals and signatures belong to your contract process, not to a PDF generator. Desktop-first, no mobile app. Pipeline is where a salesperson works a deal — 21 columns, side-by-side quotations, drill-down reports. That is a screen job. A phone app would be a second, thinner product to maintain and a second place for the data to be wrong.

Question 2

What does Ovvos Live Chat not do?

Accepted Answer

You bring your own AI key. Ovvos does not resell AI capacity or mark it up. You choose OpenAI or Anthropic, the model, and the spend — and the dashboard shows you what it cost, labelled as an estimate. Without a key, it is still a complete human chat product. No agent-versus-supervisor roles. Support teams at this size share one queue. A role hierarchy inside the chat tool would mean tickets nobody is allowed to open. Access to Live Chat is one switch per person; the company-wide roles already decide who administers the platform. Agents send text, not files. Files leaving through a chat window are the classic way a price list or a contract ends up with the wrong customer. Visitors can upload; agents reply in words and send documents through the channel your company already controls. Overridable English, not machine translation. Every word the visitor sees can be rewritten to your voice and your market. Auto-translating a support conversation mid-sale is how a warranty term gets mistranslated; a human agent, or your own wording, does not. Messages arrive within a couple of seconds, not milliseconds. The widget is designed to keep working through any proxy, firewall or corporate network your visitors are behind. Reliability on every site beats a real-time badge that fails on the ones that matter.

Question 3

What does Ovvos Outreach not do?

Accepted Answer

No drip sequences or automations. Automated sequences are how a company emails a customer three times after they replied, or after they unsubscribed. Every Outreach campaign is a deliberate send — approved by a manager, simulated first, scheduled for a time you chose — and your sending reputation is protected by it. No "send now" button. Every send is scheduled, even if for a minute from now. That one step is where a wrong list, a broken merge tag or an unverified domain gets caught by the simulation and the approval — rather than by 7,000 recipients. A simple subject/content split, not "statistical A/B". At the list sizes most companies actually send to, a significance test is theatre. Outreach gives you the split and the honest numbers; you make the call rather than a p-value making it for you. Reply tracking counts the reply link, not your inbox. Reading your inbox would mean giving a marketing tool access to your mail. Outreach tracks the reply link it sent and leaves the mailbox to the people who own it. No AI writing your emails. Your customers can tell. Outreach is the sending infrastructure and the reporting that says whether it worked; the words stay yours.

Question 4

What does Ovvos Freight not do?

Accepted Answer

Orders and money, not SKU line items. A purchase order in Freight carries a total, a vendor, dates and payments — what a trader actually negotiates. Line-item stock belongs in Stockroom; putting it here would turn a clean order record into a second inventory system that disagrees with the first. No carrier integration or live tracking. Carrier feeds are wrong often enough that someone checks anyway. Freight is the system of record: a human enters the status, the ETA and the bill-of-lading number, and the activity log shows who entered it and when — which is what you need when a shipment is disputed. No reports or export yet. Freight was built for the daily question — where is this order and have we been paid — answered on one page. Reporting is next; we would rather ship it properly than bolt on a CSV button that becomes the spreadsheet you left. Not connected to Pipeline or Stockroom. A won lead becoming a sales order automatically sounds efficient until a quote is won twice or revised after the order shipped. Freight starts from a deliberate act: someone creates the order and states what the customer pays and what the goods cost — separate figures, never derived from each other. One currency per copy; no taxes or landed cost. Mixing currencies inside one order record is how margin becomes fiction. Each copy of Freight runs in one currency, and margin is a plain fact: order amount minus what you paid. Tax and duty belong in the books, not in the logistics log.

Question 5

What does Ovvos Board not do?

Accepted Answer

No kanban board, despite the name. A card dragged to "Done" is done because someone said so. In Board, the assignee hands work up, the manager reviews it, and only the person who asked can close it — and every hand-off is timed in your working hours. Columns would let anyone skip the route. No priority flag. When everything can be marked urgent, everything is. Board routes work to a department’s manager, who decides what their team does first — a person with context, not a red label anyone can set. No @mentions, checklists or time estimates. Mentions pull work back into personal inboxes, which is the problem Board removes. Checklists hide sub-work that should be its own task with its own owner and review. Estimates are guesses; Board measures the actual time instead. Six fixed statuses. A configurable workflow is a workflow nobody agrees on. Board’s six stages are the ones every company understands without training — created, assigned, in progress, review, rework, complete — so a report from one department means the same thing in another. No links into other tools’ records. A task that points at an invoice or a shipment quietly becomes the place people track that invoice. Board keeps the work log separate from the record it is about, so each stays authoritative.

Question 6

What does Ovvos Roster not do?

Accepted Answer

It does not block a request that overlaps or exceeds the balance. A system that refuses a request makes the decision instead of the manager. Roster records it, shows HR exactly how many days could not be deducted, and leaves the call with the people who know whether the exception is fair. No accrual, carry-over or pro-rata. Every company’s carry-over policy is different and most of them have exceptions. Balances are set by HR per year, on the record, with a note — which is what an auditor can read, and what an accrual formula somebody configured in 2024 cannot explain. No attendance, timesheets or payroll. Roster is the leave and working-pattern system, and it is careful about that arithmetic across countries and working weeks. Clocking people in and out, or running payroll, is a different product with different regulators — bolting it on would make both worse. Half days are recorded by HR, not requested. Half-day rules vary by country and contract. Keeping them as an HR adjustment with a note means every one is explained, rather than a self-service option that silently rounds a balance. Requests cannot be edited or withdrawn. Once submitted, a request is a record two people may already have acted on. Corrections are made by HR, on the record, so the approval chain always shows what was actually agreed.

Question 7

What does Ovvos Stockroom not do?

Accepted Answer

No costs, prices or valuation. Stockroom counts units — on hand, reserved, available, incoming — and those numbers are only trustworthy if nobody is tempted to adjust them to make a valuation look right. Money belongs in the books; quantities belong here, and they never argue. No barcode scanning. Scanning is only faster than typing when every unit is labelled and every person has a scanner. Serial numbers in Stockroom are pasted one per line or ticked from a list, which works on the first day in every warehouse with no hardware. No purchase orders or supplier records. A stock tool that also raises purchase orders becomes a procurement system with a stock count attached. Stockroom records the PO reference and the ETA on incoming stock — the two things the warehouse needs — and leaves buying to the people and tools that do it. No forecasting or auto-reorder. A threshold a human sets is a threshold a human understands. Automatic reordering from a demand model is how a company ends up with 400 units of last year’s model. No stock-take workflow. Corrections are made one product and one location at a time, each with a reason and each in the log. A bulk "count sheet" hides which line was wrong and why.

Question 8

What does Ovvos Depot not do?

Accepted Answer

No prices, customers or orders. Depot answers one question — what do we own and where is it — and answers it honestly because nothing in it is for sale. The moment a parts register carries a price, it starts being managed for value rather than for truth. Sellable stock is Stockroom’s job. No one-click transfers between locations. A transfer is two movements: out of one shelf against a reference, into another against the same reference. Depot makes you record both, so the history on each shelf explains itself and a part cannot vanish "in transit". No email alerts. Low-stock emails are ignored by the second week. Depot puts the low-stock report one click away, lowest first, so the person about to order checks it — at the moment it matters. Parts are entered, not imported, today. A spare-parts register is only as good as its part numbers, and imports are how a decade of typos arrive at once. Adding parts as you shelve them — with a photograph — gives you a register you can trust from day one.

Question 9

What does Ovvos Handbook not do?

Accepted Answer

No approval workflow. An approval queue is where help-centre articles go to die. Handbook trusts the people you gave access to, keeps every version with author and change note, and lets you unpublish in one click. "Needs review" exists as a label your team can use as a convention. Version history is readable, not one-click restore. A restore button rewinds an article and silently discards the edits after it. Reading an old version and copying back the part you want is a deliberate act that keeps the record honest. The public help centre is public. A help centre that customers must log into is one they will not read, and one search engines cannot index. Handbook publishes what you mark published; anything else returns "not found" — including its attachments. Plain search, no fuzzy matching. Search that "helpfully" returns near-matches hides the searches that found nothing — and those are the articles you have not written yet. Handbook logs them and puts them on your dashboard as content gaps. Machine translation on your own account. Sixteen languages through your Google, DeepL, Microsoft or OpenAI key, cached per article, with your product names protected. Human translation workflows belong to a translation agency; Handbook makes the machine version good, cheap and yours.

Question 10

What does Ovvos Lexicon not do?

Accepted Answer

Not connected to your accounting system. The right code is a decision your finance lead made; posting it belongs to your ledger. Lexicon tells the person the code and they enter it wherever they work — so it fits any accounting system, and never writes to one by accident. No approval on the coding standard. The standard is owned by one finance lead with a manager role, configured once and generated in full. Adding an approval step to that would slow the one person whose job it is to decide. No export of the catalogue. An exported list is a spreadsheet the moment it leaves — three months later it is the outdated copy the tool was built to replace. Lexicon is the live reference; people search and copy the current code. Single-language. An expense code is the same string in every language; it is the description that helps, and that is assembled from your own reference lists in the words you chose.

Question 11

What does Ovvos Claim not do?

Accepted Answer

Locks expire on your decision, not on a timer. A lock that lapses automatically at midnight hands a live deal to a competitor because a partner was in a tender meeting. Claim shows the countdown to the partner, counts expiring locks on your dashboard, and lets your team close one out deliberately. Floor prices are shown, not enforced. The person approving a special price sees the floor for that tier next to the number they are typing. A hard block would be overridden by email the first time a strategic deal needed it — and then the trail is gone. Claim keeps the decision, and the snapshot, on the record. No automatic conflict detection. Two partners registering the same school is a commercial judgement, not a database rule — and the "same" customer is spelled three ways. Claim lets both deals in with timestamps and line items, and your team locks the one that is genuine. No partner leaderboards or scorecards. Rankings shown to partners encourage registering everything in sight to climb the table — exactly the hoarding deal registration exists to stop. No partner passwords, ever. A registration ID and an emailed single-use code. Nothing to issue, reset or leak, and nothing that gives a partner a login to your business systems.

Question 12

What does Ovvos Vault not do?

Accepted Answer

Encrypted at rest — not zero-knowledge. Zero-knowledge means a forgotten master password loses the company’s registrar login forever. Vault encrypts every password before it is stored, so a copy of the database is not a copy of your passwords — and your company, not a departed employee, still holds the keys. A code to your email, not an authenticator app. Every shared login in a business is already tied to a company mailbox that IT controls and can revoke the day someone leaves. Tying the reveal to that mailbox — or to a director — uses the control you already have, with nothing new to enrol or lose. All-or-nothing per person, plus one flag. Per-entry sharing matrices are where credentials get shared with the wrong person by a tired administrator. Vault keeps it simple: the people you grant see the list, and the entries that matter carry management approval, which puts a director between anyone and that secret. No browser extension, autofill or phone app. Autofill is the attack surface of consumer password managers. Vault is a web page you copy from, inside your company’s login, for the logins that belong to the business rather than to a person. No import or export. A bulk export is a plaintext file of every company credential. Entries go in and come out one at a time, on purpose.

Question 13

What does Ovvos Spec not do?

Accepted Answer

Products are entered against your structure, not imported. A spec sheet is only as good as the fields it compares on. Defining the sections yourself and entering each product against them — then duplicating to the next model — is what makes every sheet read like your category rather than a vendor’s CSV. Not linked to your CRM catalogue. A sales catalogue holds part numbers and prices; a comparison sheet needs 177 specification fields a CRM does not have. Keeping Spec’s catalogue its own means a price change never quietly alters a published datasheet. A PDF you send, not a public link. A comparison sheet is a sales document, sent to a specific buyer at a specific moment. A public link is a page a competitor can read and a search engine can index. One current sheet per product set. Regenerating replaces the previous file, so the repository always holds the current comparison and nobody sends last quarter’s by mistake. Optional AI notes, on your own key. One plain-English line per row, only when you ask, only on rows where the products actually differ — and never sent for rows where they agree. You pay your provider directly and choose the model.

Question 14

What does Ovvos Broadcast not do?

Accepted Answer

Publishing is immediate — no scheduling. A scheduled announcement goes out with the facts as they were when it was written. Broadcast publishes when a person presses the button, so what lands is what is true at that moment. Nothing can be edited after publishing. A read receipt is only worth something if the words the person read are the words on the record. If the message changes, everyone gets a new one — and a new receipt. Targeting decides who is emailed, not who may read. Broadcast is for company announcements, not confidential distribution. Every published notice is on the board for anyone with the tool, so a policy is never something one department heard and another did not. "Read" means opened, not signed. An "I agree" button is clicked without reading. Broadcast tells you honestly who has opened the announcement and who has not — and leaves formal attestation to the process that needs it. Plain-text body. Formatted announcements become newsletters, and newsletters are skimmed. A short plain notice with the document attached is read.

Question 15

What does Ovvos Ledger not do?

Accepted Answer

Not yet available. Ledger is built and passes 114 integrity checks nightly on our testing system, but it has no customers yet. We will not sell books to anyone until they have carried real load. One currency, locked at first posting. Switching or mixing currencies without converting every historic figure silently restates a company’s entire history. Ledger makes that impossible rather than merely discouraged. If you invoice in several currencies, it is not the right tool. No bank feeds — statements are uploaded. A live bank connection is a third party inside your books. Uploading the statement file your bank issued, with the sign of every line shown before anything is written, keeps the evidence in your hands. Rules suggest, checks report, nothing repairs itself. A failing check is the evidence of the bug that caused it. Software that auto-categorises, auto-reconciles or auto-corrects destroys that evidence. Every posting in Ledger is a human decision, on the record. Not connected to the other Ovvos tools. Coupling the ledger’s correctness to an operational tool’s uptime is a trade nobody should make. Invoices are raised in Ledger or imported by file, deliberately.

What each tool replaces. What it doesn't do.

Pipeline

Live Chat

Outreach

Freight

Board

Roster

Stockroom

Depot

Handbook

Lexicon

Claim

Vault

Spec

Broadcast

Ledger · coming next

Still interested?
Good — so are we.

Tell us who you are.

Thank you — we have it.

Revenue

Operations

Work & people

Knowledge

Coming next