Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
Embeddings
What It Actually Means An embedding turns a piece of text into a list of numbers that represents its meaning. Passages about similar things produce similar numbers, even when they share no vocabulary at all. That last point is the whole value. Traditional search matches words: ask about “staff leaving” and a document about “employee attrition” is invisible, because no...
Encryption
What It Actually Means Encryption scrambles data so it is unreadable without the key. That is the whole idea, and it comes in two situations that get conflated constantly. In transit protects data moving between places: your browser and the website, the application and its database, one service and another. This is what the padlock in the address bar indicates,...
End-to-End Testing
What It Actually Means An end-to-end test drives the whole system the way a person would: open the site, log in, add an item, check out, confirm the order appears. Automated, through a real browser, against a running application. It is the only kind of test that verifies the thing your customer actually does, all the way through, which is...
Endpoint
What It Actually Means An endpoint is a single address in an API that performs one specific operation: fetch a customer, create an order, update a status. An API is the whole set. An endpoint is one thing in it. When a developer says the endpoint is returning an error, they mean one specific operation rather than the whole integration....
Environment Variable
What It Actually Means An environment variable is a setting supplied to an application from outside it, rather than written into the code. The same application then behaves differently depending on where it is running. On a developer’s machine it connects to a local database; in production it connects to the real one; and the code is identical in both....
ERP
What It Actually Means Enterprise resource planning is one system running the core operational functions of a business: finance, purchasing, stock, orders, sometimes manufacturing and payroll. The idea is a single source of truth. A sale updates stock, triggers purchasing, posts to the ledger and appears in reporting, without anyone re-entering it anywhere. Why It Is A Bigger Decision Than...
About the Glossary
Why Plain Language Matters More Than Technical Fluency
Every software project involves terminology that business owners are expected to understand but rarely have reason to learn. Developers use terms like API, CI/CD, middleware, and bearer token as if everyone shares the same vocabulary. When a client nods along without fully understanding, decisions get made on incomplete information. That gap between technical language and business understanding is where the most expensive mistakes happen: approving architectures you cannot evaluate, signing off on testing strategies you cannot verify, and accepting timelines based on concepts you have not had properly explained.
This glossary exists to close that gap. Each entry provides a plain-English definition, an explanation of why the term matters to your business, and a concrete example of the concept in action. These are not textbook definitions written for computer science students. They are practical explanations for the person who needs to make decisions about software without becoming a developer in the process.
We built this glossary from the questions our clients ask in discovery calls, during project reviews, and in Slack threads where someone finally admits they are not sure what a term means. The entries reflect what business owners need to understand, not what a technical writer thinks is important. Across hundreds of client engagements, we have found that the single biggest predictor of a smooth project is a client who understands enough vocabulary to ask the right questions. Not to write the code. Just to evaluate the answers they are given.
The definitions here deliberately link to deeper content elsewhere on the site. If a glossary entry sparks a question about how we implement something, the Knowledge Center, Services, and Systems sections have the full picture. The glossary is the starting point, not the destination.
Need a Term Explained?
If you have come across a term we have not covered yet, let us know and we will add it.