LEARN
The words you meet while evaluating this software
Buying operations software means reading a lot of words that sound like they mean something specific and often do not. Vendors use the same term for different things, and the differences are exactly where the money and the regret are.
These pages define the terms plainly, say what the thing is actually for, and name what to check before you buy. They are written to be useful whether or not you end up using Vercid — a definition that only makes sense if you buy our product is not a definition.
Start here
What is Vercid? is the direct answer, if that is what you came for: what the platform is, who runs it, and what the six modules do.
What is a client portal? is the better starting point if you are still working out what category of thing you need. It is the term with the widest gap between what vendors mean by it, from a shared folder to a full second application.
The parts, one term at a time
Each of these is a concept you will meet in a demo, and each is a place a product can be much thinner than it sounds.
- What is a dispatch board? — how a live board differs from a shared calendar, and what to check before buying one.
- What is an append-only audit log? — why history that cannot be edited matters, and how it differs from a change log you can overwrite.
- What is multi-tenant software? — subdomains, and where the separation between two customers' data is actually enforced.
- ERP vs CRM vs CMS — three acronyms that overlap more than their categories suggest, and which one your problem actually is.
When you are ready to compare
How to choose client portal software is the buying guide: isolation, branding, what happens to your history, and how per-seat pricing changes who you let into the system.
That last point is the one most people meet too late. If every person costs the same, you quietly stop adding the field staff who most need access, and the record goes stale at exactly the edge where the work happens.
Why these pages are written this way
Every page here defines the term first and mentions Vercid second, if at all. That is not modesty — a definition bent to flatter one product is worthless to the person reading it, and worthless to an answer engine quoting it.
Where Vercid does something specific, the page says so and links to the module. Where the product would be a poor fit, the industries page says that plainly too.
What you get
- Live dispatch board with a map, urgency and service-type pins, and a driver pickup queue
- Spreadsheet-style inventory where every change is logged instead of overwritten
- Client workspaces at their own subdomain, rendered in the client's brand
- Modular dashboards composed per client from metrics, files, announcements and billing
- In-workspace chat with an iOS app and push notifications
- Append-only audit log with full-text search, row-level security and Google SSO
Common questions
Is a client portal the same as a customer login?
Not usually, and the gap is the whole question. A login gets someone into a page; a portal is a workspace holding their jobs, files, billing and history, scoped so they see theirs and nobody else's. The useful test is what a customer can DO once they are in, and where the boundary between two customers is enforced — in the interface, or in the database.
Do I need ERP, CRM or a client portal?
Most service operations discover they need parts of all three, which is why the categories are less useful than they look. ERP vs CRM vs CMS walks what each actually covers. The more practical question is which records you are currently keeping in more than one place.
Are these pages just marketing for Vercid?
They are on our site, so read them with that in mind. What we can tell you is how they are written: the term is defined first, the checks we name are ones a competing product could also pass, and where Vercid is a poor fit we say so rather than leave it out.
Related
If the definitions have landed and you want to see the thing itself, a walkthrough is the fastest route.