Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
What Is Fine-Tuning
Definition Fine-tuning is the process of taking a pre-trained AI model — one that has already learned general patterns from a large dataset — and training it further on a smaller, specialised dataset so it performs better at a specific task. Rather than building a model from scratch, which requires enormous computing power and data, fine-tuning adjusts the model’s existing...
What Is a Firewall
Definition A firewall is a security system that monitors incoming and outgoing network traffic and decides whether to allow or block specific connections based on a set of rules. It sits between your network (or server) and the outside world, acting as a gatekeeper. Firewalls can be hardware devices, software applications, or cloud-based services. They examine each connection attempt and...
What Is a Framework
Definition A framework is a pre-built foundation that provides the structure, conventions, and common functionality needed to build a software application. Rather than starting from a blank page and making every architectural decision from scratch, developers build on top of a framework that has already solved the fundamental problems — routing web requests, connecting to databases, handling security, managing user...
What Is a Funnel
Definition A funnel is a model that maps the stages a person moves through from first becoming aware of your business to eventually becoming a paying customer. It is called a funnel because the number of people narrows at each stage — many will discover you, fewer will show interest, fewer still will consider buying, and a smaller group will...
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 — and 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 actually 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 genuinely 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.