Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
Machine Learning
What It Actually Means Machine learning finds patterns in data and uses them to predict or classify. Rather than being told the rules, it is shown examples and works out the rules from them. This is the older, quieter branch of AI, and it has been running in ordinary businesses for years: fraud scoring, demand forecasting, spam filtering, recommendations, predicting...
Meta Tags
What They Actually Are Meta tags sit in a page’s code and describe it to machines rather than to readers. Three come up in conversation, and they matter very differently. The title tag is what appears as the blue headline in search results and in the browser tab. It is the single most important piece of text on a page...
Microservices
What It Actually Means Microservices split an application into separate small services, each responsible for one area, each deployed independently, communicating over a network. Orders, billing, notifications and users become four services rather than four parts of one application. What They Genuinely Solve Three problems, all of which appear at a particular size. Independent deployment. Teams release without coordinating with...
Middleware
What It Actually Means Middleware sits between an incoming request and the code that handles it, doing work that applies to many requests rather than to one. Every request passes through it on the way in. It might check whether the user is logged in, apply a rate limit, log the request, or reject something malformed, before the specific handler...
Model
What It Actually Means A model is the thing produced by training: a set of learned parameters that turns an input into an output. Not a program somebody wrote line by line, but a set of numbers derived from data, which is why nobody can read one and explain exactly why it produced a particular answer. In conversation the word...
Monolith
What It Actually Means A monolith is an application built and deployed as one unit. All the functionality lives in one codebase and runs as one thing. The word has acquired a negative tone it does not deserve. It is used to mean outdated, and it describes an architecture that is correct for the overwhelming majority of business systems, including...
MVC
What It Actually Means MVC splits an application into three parts. The model holds the data and the rules about it. The view is what the user sees. The controller takes a request, asks the model for what it needs, and gives the view something to display. It is the organising pattern behind most web frameworks, and its purpose is...
MVP (Minimum Viable Product)
Definition An MVP, or minimum viable product, is the smallest version of a product that a real user would choose to use instead of whatever they do today, built so you can learn whether the rest is worth building. Both halves matter. A small thing nobody can use teaches you nothing. A usable thing that answers no open question is...
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.