Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
What Is a Landing Page
Definition A landing page is a standalone web page built with one specific goal in mind — getting the visitor to take a single action. That action might be filling in a form, booking a call, signing up for a trial, or making a purchase. Unlike a typical website page that offers navigation and multiple options, a landing page strips...
What Is Laravel
Definition Laravel is an open-source PHP framework designed for building web applications. A framework provides pre-built tools and conventions so developers do not have to solve common problems from scratch — things like user authentication, database management, email sending, job queuing, and routing. Laravel organises code using the MVC (Model-View-Controller) pattern, which separates the data layer, business logic, and user...
What Is a Large Language Model
Definition A large language model (LLM) is an AI system that has been trained on enormous quantities of text data — books, articles, websites, code — to learn the patterns and structure of human language. Once trained, it can generate coherent text, answer questions, summarise documents, translate between languages, and perform many other language tasks. The “large” refers to the...
What Is Latency
Definition Latency is the time delay between a request being sent and the response arriving. When a visitor clicks a link on your website, latency is the gap between that click and the moment the server begins delivering the page. It is measured in milliseconds and affected by physical distance, network congestion, server processing time, and how many steps the...
What Is Lead Generation
Definition Lead generation is the process of attracting people who might be interested in your product or service and capturing their contact details so you can follow up with them. A “lead” is anyone who has shown some level of interest — they might have filled in a form, downloaded a guide, signed up for a webinar, or requested a...
What Is a Lead Magnet
Definition A lead magnet is a free resource or incentive you offer to potential customers in exchange for their contact details, usually an email address. Common examples include downloadable guides, checklists, templates, free trials, discount codes, and webinars. The key principle is that you are giving something genuinely useful, and in return, the visitor gives you permission to follow up....
What Is a Legacy System
Definition A legacy system is any software application or technology infrastructure that is still in active use but is built on outdated technology, architecture, or practices. The term does not necessarily mean the system is broken — many legacy systems work reliably and handle critical business operations. What makes them “legacy” is that they are difficult to maintain, expensive to...
What Is a Library
Definition A library is a collection of pre-written code that performs a specific task or set of related tasks. Developers add libraries to their projects to avoid building common functionality from scratch — things like date formatting, image processing, PDF generation, or chart rendering. Unlike a framework, which dictates how your entire application is structured, a library is a tool...
What Is a Load Balancer
Definition A load balancer is a system that distributes incoming network traffic across multiple servers so that no single server bears too much demand. It sits between your visitors and your servers, directing each request to whichever server is best positioned to handle it — typically the one with the lightest current load. If one server fails, the load balancer...
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.