Ovvos was built inside a working company to replace the CRM, the mailing tool, the task board, the stock sheet and the rest — with one system, one login, and one thing for each person to learn. Fourteen tools available today, running our own business since 2023.
What we kept running into
01
We hired people for their judgement about customers, stock and shipping — then asked them to become experts in five pieces of software. They didn't want to. We stopped blaming them.
02
The CRM did not know about the shipment. The stock sheet did not know about the quote. Moving data from one tool to the next was a nightmare, and a person became the integration layer.
03
Quietly, one team at a time, the tools went unused and the spreadsheets came back. Nobody announced it. The renewals still arrived.
04
Licences for software nobody used. That was the moment: one system, built by someone who knew exactly what the owner, the directors, the managers and the admin each needed to see.
Why Ovvos exists
Ovvos was not designed as a product. It was built inside a working company, by the person running it, to replace the software that company had already paid for and quietly abandoned.
All tried, all paid for, all eventually left. They are good products. That was never the problem.
Over years of building businesses from scratch — and running a US company's international operations — we ran the back office on the best-known tools in the market. Each one was good at its job. And each job was one job. The CRM did not know about the shipment. The stock sheet did not know about the quote. The third problem always meant a third tool, a third login, and a third learning curve.
The pattern was the same every time. Connecting the tools was a mess. Moving data between them was a nightmare. And the people we hired for their judgement about customers, stock or shipping were being asked to become experts in five pieces of software instead. Slowly, they stopped opening them. The company kept paying.
The moment was an ordinary one: a licence renewal for tools the teams had already abandoned. Expecting one person to master five systems to do their job was too much to ask — their focus belongs on what they are good at, and the system should carry the rest. We knew exactly what a business needs, what managers expect from a report, what an administrator needs, what a director needs, and what the owner needs to see. So, as someone technical by heart who had been building applications for years, the managing director started building it. Alone.
Ovvos went live in our own business in mid-2023 and we have not used another tool since. The teams are aligned around one system with one login. Nobody learns five products — they learn one. Every department's notifications arrive in one place. Everything happening in the company is within reach, all the way to the bottom. And when the owner needs to speak to everyone, there is a tool for that, and it shows who got the message and who has not opened it yet.
Now we are opening it to other companies. Everything in it comes from running one — which is why these principles are not a manifesto but a list of things that went wrong before.
How we built it instead
We did not build one giant app. Ovvos ships Pipeline; our sales team runs a copy called Sales and our buyers run one called Procurement. Both are real, neither sees the other's deals, and both open from the same login the warehouse and HR use. Two departments, two CRMs, one company.
01 · Sign up
One company, one admin, thirty seconds.
02 · Generate your tools
Pick a tool from the catalogue, name it what your team calls it, choose its icon and colour. It is ready to work in a few seconds, with sensible defaults in place and you as its admin.
03 · Invite your people
Access is granted per person per tool, with a role on that tool separate from their company-wide role. Credentials can be emailed automatically.
04 · Follow the checklist
Every tool ships a setup checklist docked in its sidebar. Several steps tick themselves when your configuration is genuinely done. There is no implementation phase.
Switching between tools never means a new login or a new interface: one dark icon rail, one per-tool sidebar, one command palette, one notification model.
The catalogue
Keep scrolling — the cards stack as they pass. All fourteen are available today and in every account; a fifteenth, Ledger, is in testing.
Depth, not widgets
Outreach gives each copy its own verified sending domain and its own reputation at the email provider, checks your DNS records live until they turn green, renders the preview with the same code that sends, and halts a campaign by itself at a 3.5% bounce rate.
Outreach →Claim lets resellers sign in with a registration ID and an emailed code, locks each deal to the partner who found it with an owner and an expiry, and stores every approved price with a snapshot of your standard and end-user prices at that instant.
Claim →Live Chat puts visitors on a live globe, writes its opening line from the page they are actually on, hands over to a person when it should — then converts the conversation into a CRM company, contact and lead with AI-suggested classification.
Live Chat →One design language
This is the rule that came out of watching good people abandon good software. The same frame, the same lists, the same alerts. Uppercase headers, row hover, click anywhere on a row to open it, an actions column, control over which columns show, and an empty state that offers a way forward.
Light mode and dark mode, on every screen of every tool — plus a comfortable and a compact density. Each person chooses; nobody is stuck with a theme that hurts their eyes at 8pm. A standing rule, not an aspiration.
Every user picks their own theme — light or dark — and their own density, comfortable or compact. The choice follows them across all fourteen tools.
Isolation by construction
Every screen, every report and every export in every tool is limited to your company — and seven independent checks enforce it, so one failing does not open a door. An architecture audit in August 2026 found no leak.
Vault goes further: passwords are encrypted, revealing one needs a code emailed to you, and its files are never served from a public address.
AI, in four specific places
OpenAI or Anthropic, chosen per website, on your own key — Ovvos does not resell AI capacity. Cost is shown rather than hidden: replies sent, words processed and estimated monthly spend, stated as an estimate from published list prices. Every other tool works without any AI at all.
Per-website persona and instructions; answers in context, captures customer details, and decides for itself when a human is needed.
Written from the page the visitor is on and the trigger that fired — time on page, scroll depth, exit intent.
Title, description, company type, product type, brand and customer type proposed from the conversation when converting a chat.
Analytical reports over your chat data for any range, and an optional plain-English line per row on Spec comparison sheets.
We are listening
We are not the company that hands you a tool and tells you how to work. Several tools in the catalogue exist because an organisation using Ovvos told us what was missing — and when we build something from that feedback, we make it available to everyone, so each customer benefits from what the others have been asking for.
That is why every single user of Ovvos has a feedback button, on every screen. Not a form on a website. A button, inside the tool, next to the thing they want changed.
Feedback → catalogue
When a request from one organisation is something every business needs, we build it into the platform and release it to all customers at no extra cost. Your feedback shapes the product other companies use — and theirs shapes yours.
Custom tools
Some needs are yours alone. We design and build custom tools for a single organisation — on the same platform, the same login and the same design as the other fourteen — visible to nobody else. We do not limit ourselves to the tools we have already built.
Pricing
We have paid per-seat prices ourselves and watched the bill climb every time the team grew. So Ovvos charges one price per organisation — every tool, every copy, every person you hire. We want our customers to see growth in revenue, not in subscriptions.
One organisation. One price.
Add a department, hire ten people, open a fifteenth tool — the price does not move. Ask us for the current rate.
Talk to us
By invitation and application
Not open to everyone
We take on selected entrepreneurs and organisations. Two kinds, in particular:
Those just starting out
Struggling with a subscription for every problem, and a per-user fee for every person — many of whom will never use most of what that seat pays for.
Those paying hundreds of thousands
Established organisations whose annual subscription bill has grown with their headcount, for tools their teams barely open.
The beauty of Ovvos: we do not charge per user. We charge per organisation. We want our customers to see growth in revenue — not in expenses, just because the team grew alongside the subscription bill.
What a demo looks like
Onboarding is part of the product — setup checklists, spotlight tours and walkthroughs in the ⌘K palette — so there is no separate implementation project to buy.
Straight answers
Yes — that is the normal case, and it is how Pipeline is used in production today. Each copy has its own data, settings and user list; access to one grants nothing on the other.
In Freight, yes, per entity: enable, disable, rename or retype a field and edit its dropdown options. Across the other tools, the lookup lists that drive the dropdowns are yours to configure and reorder.
Yes, where it matters most. Pipeline imports companies with their contacts, products and leads through a four-step wizard with column mapping, in-place fixes for broken rows and duplicate resolution. Outreach imports contact files with a side-by-side conflict review, and Stockroom imports bulk quantities. Other tools are entered directly.
A company-wide role plus a separate role on each copy of a tool. In Pipeline and Board, managers see their own departments’ work while directors and administrators see everything. Access to your company’s data is enforced on every request, not by hiding buttons.
No. Outreach registers your sending domain with the email provider for you and shows the DNS records to publish — the only step outside Ovvos. Your reputation at the provider is measured on your own sending alone.
No. Ovvos is priced per organisation, not per user. Hire, add departments, open more tools — the price stays where it was. We would rather your costs grow with your revenue than with your headcount.
Yes. We design custom tools for a single organisation on the same platform, visible only to them. And when a request is something every business needs, we build it into the catalogue for everyone.
Every screen, in both themes, at two densities. It is checked as part of the work rather than bolted on later.
Half an hour on a demo account, your own tools created live, your customer list imported while you watch — and a straight answer to anything we don't do.
Book a demo · by application
Half an hour on a demo account. We confirm the time by email.
We will confirm by email shortly.