Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
OAuth
What It Actually Means OAuth is how one system gets permission to act in another on your behalf, without ever being told your password. You have used it constantly. Connecting an app to your Google account, letting a tool post to a social account, authorising accounting software to read your bank feed. You are sent to the provider, you approve...
Off-Page SEO
What It Actually Means Off-page SEO is everything influencing your search performance that does not happen on your own website: links from other sites, mentions of your business, reviews, and the general question of whether you appear to be a real and credible operation. The core of it is backlinks, and it extends further than links alone. Why It Decides...
On-Page SEO
What It Actually Means On-page SEO covers everything on your own website that affects how it performs in search: the content, the page titles, the headings, the internal linking, the structure, the speed. The defining feature is control. This is the part nobody else has a say in, which makes it the fastest to improve and the first place to...
Organic Traffic
What It Actually Means Organic traffic is visitors arriving through unpaid search results: they searched, your page appeared, they clicked, and nobody paid for the placement. It is distinguished from paid traffic, direct traffic where somebody typed your address, referral traffic from links on other sites, and social traffic. Free To Click, Not Free To Earn The appeal is obvious...
ORM
What It Actually Means An object-relational mapper lets developers work with database records as ordinary objects in code, rather than writing database queries by hand. Instead of composing a query to fetch a customer, a developer asks for the customer and receives something they can work with directly. The ORM writes the query underneath. Why It Is Used It removes...
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.