Skip to main content
Reference

Glossary

Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.

All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

What Is a Webhook

Definition A webhook is an automatic message sent from one system to another when a specific event happens. Unlike a regular API call where your system asks for information, a webhook is the reverse — the other system tells yours that something has occurred. It is a push notification between servers, triggered instantly by events like a payment completing, a...

What Is WooCommerce

Definition WooCommerce is a free, open-source e-commerce plugin for WordPress. It adds online shop functionality to a WordPress website, allowing you to list products, manage inventory, accept payments, calculate shipping, handle tax, and process orders — all from the same WordPress admin dashboard you already use to manage your content. WooCommerce supports physical products, digital downloads, subscriptions, and bookings. Its...

What Is WordPress

Definition WordPress is a free, open-source content management system (CMS) that allows you to build and manage websites without writing code from scratch. It started as a blogging platform in 2003 and has since grown into a full website-building framework used by businesses, publishers, and organisations of all sizes. WordPress provides an admin dashboard where you can create pages, publish...

What Is a Workflow

Definition A workflow is a defined sequence of steps, decisions, and handoffs that moves a task or process from start to completion. Workflows can be manual (a checklist that a team follows), semi-automated (some steps handled by software, others by people), or fully automated (the entire sequence runs without human involvement). In software and business operations, workflows formalise how work...

What Is Workflow Automation

Definition Workflow automation is the use of software to perform a sequence of business tasks automatically, following predefined rules and triggers, with little or no human intervention for routine cases. It replaces manual, repetitive processes — passing documents between departments, sending follow-up emails, updating records across systems, generating reports — with automated sequences that execute consistently every time. Workflows can...

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.