Software development glossary for business owners
Plain-English definitions of the terms you will hear when planning a website, app, SaaS product or AI project, from API and MVP to RAG, CI/CD and multi-tenancy, with a note on why each one matters to your budget, timeline or risk.
A
- Accessibility (WCAG)Design & UX
Accessibility means building websites and apps that people with disabilities can use, including people who rely on screen readers, keyboard-only navigation or high-contrast displays. WCAG (Web Content Accessibility Guidelines) is the widely used international standard that defines how to do this, with conformance levels A, AA and AAA.
Why it matters: An accessible product reaches more customers, and in many countries accessibility is a legal expectation for public-facing services. Fixing accessibility during design is far cheaper than retrofitting it later.
- Admin panelWeb & apps
An admin panel is a private, password-protected area of a website or app where staff manage content, users, orders and settings without touching code. It is the back-office control room that sits behind the public-facing product.
Why it matters: A good admin panel lets your team run day-to-day operations themselves instead of paying a developer for every small change.
- AI agentAI & automation
An AI agent is software built around a large language model that can plan and carry out multi-step tasks, such as looking up information, calling other systems and deciding what to do next, rather than only answering a single question. Agents are given a set of tools and rules that limit what they are allowed to do.
Why it matters: Agents can take over repetitive, judgement-light work like triaging requests or preparing reports, but they need clear boundaries and human review for anything high-stakes.
- AnalyticsSEO & marketing
Analytics is the collection and reporting of data about how people find and use your website or app, such as visits, traffic sources, pages viewed and actions taken. Tools like Google Analytics or product analytics platforms turn these events into charts and reports.
Why it matters: Without analytics you are guessing about what works. With it you can see where customers drop off and decide where to invest next.
- APIData & backend
An API (application programming interface) is a defined way for one piece of software to request data or actions from another. For example, your website might use a payment provider's API to charge a card, or a shipping company's API to get delivery rates.
Why it matters: APIs are how your systems talk to each other and to outside services. A product with a well-designed API is easier to connect, extend and automate.
- App Store reviewWeb & apps
App Store review is the process Apple (and, in a similar form, Google for Google Play) uses to check every new app and update against its guidelines before it is published. Reviewers look at things like functionality, privacy disclosures, payments and content, and can reject a submission until issues are fixed.
Why it matters: Review time and possible rejections should be built into any mobile launch plan. Some business models, such as selling digital content, must follow store payment rules.
- AutomationAI & automation
Automation is using software to perform tasks that people would otherwise do by hand, such as copying data between systems, sending follow-up emails or generating invoices. It can range from simple rule-based workflows to processes that include AI for steps like reading documents.
Why it matters: Automating repetitive work reduces errors and frees staff for higher-value tasks. The best candidates are processes that are frequent, rule-based and well understood.
B
- BackendData & backend
The backend is the part of a software system that runs on servers rather than in the user's browser or phone. It handles business logic, stores and retrieves data from the database, enforces security rules and talks to other services.
Why it matters: The backend determines how reliable, secure and scalable your product is, even though users never see it directly.
- BackupInfrastructure
A backup is a copy of your data and files stored separately from the live system so it can be restored after accidental deletion, hardware failure, a bad update or a cyberattack. Good backup practice includes automatic schedules, off-site copies and regularly testing that restores actually work.
Why it matters: A backup that has never been tested may not work when you need it. Ask how often backups run, where they are kept and how long a restore takes.
- BugWeb & apps
A bug is a flaw in software that makes it behave differently from what was intended, such as a wrong calculation, a crash or a button that does nothing. Bugs are usually reported, prioritised by severity and fixed in later updates.
Why it matters: All software has bugs. What matters is having a clear process and agreement for how they are reported, prioritised and fixed, including after launch.
C
- CachingInfrastructure
Caching is storing a ready-made copy of data or a page so it can be served quickly the next time it is requested, instead of being recalculated or fetched from the database each time. Caches can live in the browser, on a CDN or on the server.
Why it matters: Caching makes sites faster and reduces hosting costs. Poorly configured caching can also show customers outdated information, so it needs care.
- Canonical URLSEO & marketing
A canonical URL is the preferred address of a page when the same or very similar content is reachable at several addresses, for example with and without tracking parameters. It is declared with a canonical tag in the page so search engines know which version to index and rank.
Why it matters: Without canonical URLs, search engines may split ranking signals across duplicate pages or show the wrong version in results.
- CDN (content delivery network)Infrastructure
A CDN is a network of servers spread around the world that stores copies of your website's files, such as images, scripts and pages. Visitors receive those files from the server nearest to them, which shortens load times and absorbs traffic spikes.
Why it matters: A CDN is one of the simplest ways to make a site faster for international visitors and more resilient under heavy load.
- CI/CDInfrastructure
CI/CD stands for continuous integration and continuous delivery (or deployment). It is an automated pipeline that tests every code change as it is submitted and then prepares or releases it to staging or production with minimal manual steps.
Why it matters: CI/CD makes releases smaller, more frequent and less risky, so fixes and features reach your customers faster with fewer surprises.
- Cloud hostingInfrastructure
Cloud hosting means running your website or application on computing resources rented from a provider such as AWS, Google Cloud, Microsoft Azure or Vercel, rather than on servers you own. Capacity can usually be increased or reduced on demand and is billed by usage or plan.
Why it matters: Cloud hosting avoids upfront hardware costs and makes scaling easier, but costs need monitoring because usage-based bills can grow with traffic.
- Code reviewBusiness & planning
Code review is the practice of having another developer read and check code changes before they are merged into the main product. Reviewers look for bugs, security issues, unclear logic and departures from agreed standards.
Why it matters: Code review catches problems early when they are cheap to fix and reduces dependence on a single developer's knowledge.
- Container (Docker)Infrastructure
A container is a self-contained package that bundles an application together with everything it needs to run, such as libraries and settings, so it behaves the same on any machine. Docker is the most widely used tool for building and running containers.
Why it matters: Containers reduce "it works on my machine" problems and make it easier to move an application between hosting providers.
- Conversion rateSEO & marketing
Conversion rate is the percentage of visitors who complete a desired action, such as making a purchase, booking a call or signing up. It is calculated by dividing the number of conversions by the number of visitors over the same period.
Why it matters: Improving conversion rate increases revenue from the traffic you already have, which is often cheaper than attracting more visitors.
- Core Web VitalsSEO & marketing
Core Web Vitals are a set of metrics defined by Google to measure real-world user experience on a web page: how quickly the main content loads (Largest Contentful Paint), how quickly the page responds to interactions (Interaction to Next Paint) and how stable the layout is while loading (Cumulative Layout Shift).
Why it matters: These metrics reflect how fast and smooth your site feels to customers and are among the signals Google uses in search ranking.
- CrawlabilitySEO & marketing
Crawlability is how easily search engine bots can discover and read the pages on your website. It depends on factors such as internal links, the sitemap, robots.txt rules, server errors and whether content is visible without heavy client-side scripts.
Why it matters: If search engines cannot crawl a page, it cannot rank, no matter how good the content is.
- CRMBusiness & planning
A CRM (customer relationship management) system stores information about customers and prospects, including contact details, conversations, deals and support history. Examples include HubSpot, Salesforce and Pipedrive, and some businesses build custom CRMs for specialised workflows.
Why it matters: A CRM gives your team one shared view of each customer. Connecting it to your website and other tools avoids manual data entry.
- Cross-platform appWeb & apps
A cross-platform app is a mobile app built from a single codebase that runs on both iOS and Android, using frameworks such as React Native or Flutter. Most of the code is shared, with platform-specific code added only where needed.
Why it matters: Cross-platform development usually lowers cost and time to market compared with building two separate native apps, while still delivering a native-feeling experience for most business apps.
D
- DashboardWeb & apps
A dashboard is a screen that summarises key information at a glance, usually with charts, numbers and tables drawn from one or more data sources. Dashboards can be internal tools for staff or features inside a product for customers.
Why it matters: A well-designed dashboard turns scattered data into decisions by showing the few numbers that matter most to the person looking at it.
- DatabaseData & backend
A database is an organised system for storing, retrieving and updating data, such as customers, orders, products or messages. Software applications read from and write to the database constantly, and it is usually the most important long-term asset in a system.
Why it matters: Your data often outlives the application around it. A well-designed database keeps information accurate, secure and easy to report on as the business grows.
- Database migrationData & backend
A database migration is a controlled, versioned change to the structure of a database, such as adding a table or column, run as a script so it can be applied consistently across environments. The term is also used for moving data from one database or system to another.
Why it matters: Managed migrations let a product evolve without losing or corrupting existing data. Moving data from an old system is often a significant part of a project's effort.
- DeploymentInfrastructure
Deployment is the process of releasing a new version of software to a server or app store so that users can access it. It can be manual or fully automated through a CI/CD pipeline, and good setups allow a quick rollback if something goes wrong.
Why it matters: Reliable, repeatable deployments mean updates can ship without downtime or late-night emergencies.
- Design systemDesign & UX
A design system is a shared library of reusable interface components, such as buttons, forms and cards, along with rules for colour, typography, spacing and usage. Designers and developers use it to build screens consistently.
Why it matters: A design system keeps a growing product visually consistent and speeds up building new features because common pieces do not need to be redesigned each time.
- DevOpsInfrastructure
DevOps is a set of practices that brings software development and IT operations together, using automation for testing, deployment, infrastructure setup and monitoring. The goal is to release changes quickly and reliably while keeping systems stable.
Why it matters: Good DevOps practice reduces downtime, shortens the time from idea to release and makes hosting costs more predictable.
- Discovery phaseBusiness & planning
The discovery phase is a short, focused period at the start of a software project for clarifying goals, users, requirements, risks and technical approach before full development begins. It typically produces a scope document, priorities, rough designs and a more reliable estimate.
Why it matters: Discovery reduces the risk of building the wrong thing and leads to more accurate quotes, which protects your budget.
- Domain name and DNSInfrastructure
A domain name is your website's human-readable address, such as example.com, which you register through a registrar. DNS (Domain Name System) is the internet's directory that translates that name into the server addresses where your website and email are actually hosted.
Why it matters: Your domain and DNS records should be registered in your own business account so you keep control of your web address and email.
E
- EmbeddingsAI & automation
Embeddings are lists of numbers that represent the meaning of a piece of text, image or other content, produced by an AI model. Content with similar meaning gets similar numbers, which lets software search by meaning rather than exact keywords.
Why it matters: Embeddings power semantic search and AI assistants that answer questions from your own documents.
- EncryptionSecurity
Encryption scrambles data so that only someone with the correct key can read it. Data can be encrypted in transit, while travelling over the internet, and at rest, while stored in databases or backups.
Why it matters: Encryption protects customer and business data if it is intercepted or a storage system is compromised, and is expected under most data protection rules.
- ERPBusiness & planning
An ERP (enterprise resource planning) system brings core business operations, such as finance, inventory, purchasing, manufacturing and HR, into one connected platform. Examples include SAP, Oracle NetSuite, Microsoft Dynamics and Odoo.
Why it matters: An ERP is often the system of record for a business, so websites, e-commerce stores and custom tools usually need to integrate with it.
F
- Fine-tuningAI & automation
Fine-tuning is further training an existing AI model on a set of your own examples so it adopts a particular style, format or specialised behaviour. It changes the model itself, unlike prompting or RAG, which only change the input the model receives.
Why it matters: Fine-tuning can improve consistency for narrow tasks, but it adds cost and maintenance. Many business use cases are solved with good prompts and RAG first.
- Fixed price vs time and materialsBusiness & planning
These are the two common ways to price software work. Fixed price agrees a set cost for a clearly defined scope, while time and materials bills for the actual hours spent at an agreed rate, allowing scope to change as the project evolves.
Why it matters: Fixed price gives budget certainty but requires well-defined requirements; time and materials gives flexibility but needs closer budget tracking. The right choice depends on how clear your scope is.
- FrameworkWeb & apps
A framework is a ready-made foundation of code, conventions and tools that developers build applications on top of, rather than starting from scratch. Examples include Next.js and React for web interfaces and React Native for mobile apps.
Why it matters: Choosing a popular, well-maintained framework makes it easier to hire developers later and reduces long-term maintenance risk.
- FrontendWeb & apps
The frontend is the part of a website or app that users see and interact with, including layouts, buttons, forms and animations. On the web it is built with HTML, CSS and JavaScript, often using a framework such as React.
Why it matters: The frontend shapes your customers' first impression and directly affects usability, speed and conversion.
- Full stackWeb & apps
Full stack refers to working across both the frontend (what users see) and the backend (servers, databases and business logic) of an application. A full-stack developer can build and connect all the layers of a product.
Why it matters: Working with a full-stack developer or team means fewer handoffs and a single point of responsibility for how the whole product fits together.
G
- GDPRSecurity
The GDPR (General Data Protection Regulation) is a European Union law that governs how organisations collect, store and use personal data about people in the EU, and the UK has a closely related version. It covers principles such as having a lawful basis for processing, data minimisation, security and individuals' rights to access or delete their data. This is a general explanation, not legal advice.
Why it matters: If you handle data about EU or UK residents, your software needs to support these obligations, for example consent records, data export and deletion. Seek legal advice for your specific situation.
- GraphQLData & backend
GraphQL is a way of building APIs where the client asks for exactly the data it needs in a single structured query, rather than calling multiple fixed endpoints. It was created at Facebook and is now an open standard.
Why it matters: GraphQL can make complex apps with many related data types faster and more flexible, though for simpler products a REST API is often sufficient.
H
- HallucinationAI & automation
A hallucination is when an AI language model produces information that sounds confident and plausible but is false or unsupported, such as an invented fact, quote or reference. It happens because these models generate likely-sounding text rather than looking facts up.
Why it matters: Any AI feature that gives customers or staff information needs safeguards such as grounding answers in your own data, citing sources and human review for important decisions.
- Headless CMSWeb & apps
A headless CMS (content management system) lets your team edit content such as pages, blog posts and product descriptions in one place, then delivers that content through an API to any website, app or other channel. Unlike traditional CMSs, it does not control how the content is displayed.
Why it matters: A headless CMS gives marketers easy editing while letting developers build a fast, custom frontend, and the same content can feed multiple channels.
- Headless commerceWeb & apps
Headless commerce separates the customer-facing storefront from the e-commerce engine that manages products, carts, orders and payments. The two communicate through APIs, so the storefront can be custom-built while platforms like Shopify handle commerce operations.
Why it matters: Headless commerce allows a faster, fully branded shopping experience, but it costs more to build and maintain than a standard theme-based store.
I
- Indexing (database)Data & backend
A database index is an extra data structure that lets the database find matching records quickly without scanning every row, much like the index at the back of a book. Indexes speed up searches and filters but take extra storage and slightly slow down writes.
Why it matters: Missing indexes are a common cause of apps that slow down as data grows, and adding the right ones can make slow pages fast again.
- IntegrationData & backend
An integration is a connection that lets two software systems share data or trigger actions automatically, such as sending new website orders into your accounting software. Integrations are usually built on the systems' APIs or webhooks.
Why it matters: Integrations remove manual re-typing between tools, which saves time and prevents errors in records.
- Intellectual property (IP) ownershipBusiness & planning
IP ownership in software development refers to who legally owns the source code, designs and other materials created during a project. It is normally set out in the contract, which should state whether ownership transfers to the client and on what terms, such as on final payment.
Why it matters: Owning your code and having access to the repository lets you change developers, raise investment or sell the business without obstacles.
K
- KPIBusiness & planning
A KPI (key performance indicator) is a measurable value that shows how well a business, team or product is achieving an important goal, such as monthly revenue, customer churn or average order value. KPIs are chosen deliberately and tracked over time.
Why it matters: Defining KPIs before a software project starts gives you a clear way to judge whether the investment is paying off.
L
- LatencyInfrastructure
Latency is the delay between a request being made and the response starting to arrive, usually measured in milliseconds. It is affected by physical distance to the server, network conditions and how long the server takes to process the request.
Why it matters: High latency makes apps feel sluggish. Hosting close to your users and using a CDN are common ways to reduce it.
- LLM (large language model)AI & automation
A large language model is an AI system trained on very large amounts of text to understand and generate human language. Examples include OpenAI's GPT models, Anthropic's Claude and Google's Gemini, which can draft text, summarise, answer questions, classify content and write code.
Why it matters: LLMs can add capabilities like smart search, document processing and chat assistants to existing products, usually through an API rather than by training your own model.
- Load balancingInfrastructure
Load balancing distributes incoming traffic across several servers so no single server is overwhelmed. If one server fails, the load balancer sends traffic to the healthy ones.
Why it matters: Load balancing keeps your application available during traffic spikes and hardware failures.
- Low-code and no-codeBusiness & planning
Low-code and no-code platforms, such as Webflow, Bubble, Airtable or Zapier, let people build websites, apps or workflows using visual editors with little or no programming. Low-code tools allow some custom code; no-code tools aim to need none.
Why it matters: These tools can be a fast, inexpensive way to validate an idea, but they can become limiting or costly as requirements, users or data grow.
M
- Maintenance and supportBusiness & planning
Maintenance and support is the ongoing work after launch to keep software secure, working and up to date, including fixing bugs, applying security patches, updating dependencies and monitoring uptime. It is often provided under a monthly retainer or support agreement.
Why it matters: Software that is not maintained gradually becomes insecure and breaks as browsers, phones and third-party services change, so ongoing costs should be in your budget.
- MicroservicesData & backend
Microservices is an architecture where an application is split into many small, independently deployed services, each responsible for one area such as payments or notifications. The alternative is a monolith, where the whole application is built and deployed as one unit.
Why it matters: Microservices can help large teams scale, but they add operational complexity. Most new products and small teams are better served by a well-structured monolith.
- Multi-tenancyData & backend
Multi-tenancy is a software design where a single application serves many separate customer organisations, called tenants, while keeping each tenant's data and settings isolated from the others. It is the standard approach for most SaaS products.
Why it matters: Getting tenant isolation right is essential for security and is much harder to add later, so it should be planned from the start of a SaaS build.
- MVP (minimum viable product)Business & planning
An MVP is the simplest version of a product that delivers real value to early users and lets you test your core assumptions with the market. It includes only the essential features, with further features added based on feedback.
Why it matters: An MVP reduces the time and money spent before you learn whether customers will actually use and pay for your product.
N
- Native appWeb & apps
A native app is a mobile app built specifically for one platform using that platform's own languages and tools, such as Swift for iOS or Kotlin for Android. Native apps have direct access to all device features and platform-specific interface conventions.
Why it matters: Native development can suit apps with demanding performance or hardware needs, but building for both platforms typically means two codebases and higher cost.
- NoSQL databaseData & backend
A NoSQL database stores data in formats other than traditional tables with rows and columns, such as flexible documents, key-value pairs or graphs. Examples include MongoDB, Firebase Firestore and Redis.
Why it matters: NoSQL databases can be fast to start with and suit certain real-time or flexible data needs, but complex reporting and relationships are often easier in a relational database.
O
- OAuthSecurity
OAuth is an open standard that lets a user grant one application limited access to their account on another service without sharing their password. It is what happens behind the scenes when you click "Sign in with Google" or connect an app to your calendar.
Why it matters: OAuth enables convenient social sign-in and secure connections to third-party services while keeping passwords out of your systems.
- Open sourceBusiness & planning
Open source software has its source code publicly available under a licence that allows anyone to use, study, modify and share it. Much of the modern web, including React, Node.js and PostgreSQL, is open source.
Why it matters: Open source reduces licensing costs and vendor dependence, but each licence has terms, so it is worth confirming that the components used are compatible with your commercial plans.
- ORMData & backend
An ORM (object-relational mapper) is a tool that lets developers work with database records as objects in their programming language instead of writing raw database queries by hand. Examples include Prisma and Drizzle for TypeScript.
Why it matters: ORMs speed up development and reduce some classes of errors, though performance-critical queries may still need hand-tuning.
P
- Payment gatewayWeb & apps
A payment gateway is a service that securely processes online card and wallet payments between your website or app, the customer's bank and your bank. Examples include Stripe, PayPal and Adyen, which also handle fraud checks and much of the card security compliance burden.
Why it matters: Choosing the right gateway affects transaction fees, supported countries and currencies, payout speed and how much security compliance work falls on you.
- Penetration testingSecurity
Penetration testing is an authorised, simulated attack on your application or infrastructure by security specialists to find vulnerabilities before real attackers do. Testers produce a report describing the weaknesses found and how to fix them.
Why it matters: A penetration test gives independent evidence of your security posture and is often requested by enterprise customers and insurers.
- Product roadmapBusiness & planning
A product roadmap is a plan that shows what features and improvements a product will receive and in roughly what order or timeframe. It connects business goals to development work and is updated as priorities change.
Why it matters: A roadmap helps you and your development team agree on priorities, which keeps budgets focused on the features that matter most.
- PromptAI & automation
A prompt is the instruction and context given to an AI language model to produce a response, such as a question, a task description, examples and rules to follow. Designing prompts carefully, often called prompt engineering, has a large effect on output quality.
Why it matters: Well-designed and tested prompts make AI features more accurate and consistent without the cost of training a custom model.
- PrototypeDesign & UX
A prototype is an early, interactive model of a product that shows how it will look and behave, ranging from clickable design mock-ups to rough working code. It is used to test ideas with users and stakeholders before full development.
Why it matters: Testing a prototype reveals usability problems and misunderstandings when they are still cheap to change.
- PWA (progressive web app)Web & apps
A progressive web app is a website built to behave like an installed app: it can be added to a phone's home screen, work offline or on poor connections, and in many cases send push notifications. It runs in the browser, so it does not require app store distribution.
Why it matters: A PWA can give customers an app-like experience at lower cost than separate native apps, though some device features and store visibility are limited.
Q
- QA (quality assurance)Web & apps
Quality assurance is the process of checking that software works correctly and meets requirements before it reaches users. It includes manual testing by people and automated tests that run on every change, covering features, devices, browsers and edge cases.
Why it matters: Proper QA prevents embarrassing and costly bugs from reaching customers, so ask how testing is handled and what is included in the quote.
R
- RAG (retrieval-augmented generation)AI & automation
RAG is a technique where an AI system first searches your own documents or database for relevant information, then gives that information to the language model so it can answer using your actual content. This grounds answers in your data without retraining the model.
Why it matters: RAG is the common way to build AI assistants that answer accurately about your products, policies or knowledge base, and it reduces hallucinations.
- Rate limitingSecurity
Rate limiting caps how many requests a user, device or system can make to an application or API within a set time window. Requests beyond the limit are slowed down or rejected.
Why it matters: Rate limiting protects your system from abuse, brute-force login attempts and runaway costs, especially for paid services like AI APIs.
- RefactoringBusiness & planning
Refactoring is restructuring existing code to make it cleaner, simpler or easier to maintain without changing what it does for users. It is a standard way of paying down technical debt.
Why it matters: Regular refactoring keeps future development fast and affordable, even though it produces no visible new features.
- Relational databaseData & backend
A relational database stores data in tables of rows and columns and links related records, such as customers and their orders, through shared identifiers. Data is queried using SQL, and popular examples include PostgreSQL and MySQL.
Why it matters: Relational databases are a reliable default for most business applications because they keep data consistent and make reporting straightforward.
- Responsive designDesign & UX
Responsive design is an approach where a website's layout automatically adapts to the size of the screen it is viewed on, from phones to tablets to large desktop monitors. The same site rearranges and resizes content rather than requiring separate versions.
Why it matters: A large share of web traffic comes from mobile devices, and Google primarily uses the mobile version of a site for indexing, so responsive design is essential.
- REST APIData & backend
A REST API is the most common style of web API, where each type of data is available at its own web address and standard HTTP methods are used to read (GET), create (POST), update (PUT or PATCH) and delete (DELETE) it. Responses are usually in JSON format.
Why it matters: REST is widely understood, so a REST API makes it easy for other developers and services to integrate with your product.
- Role-based access control (RBAC)Security
Role-based access control assigns permissions to roles, such as admin, manager or viewer, and then assigns users to those roles, instead of setting permissions for each person individually. It is a common way to implement authorization.
Why it matters: RBAC makes it easy to give staff and customers exactly the access they need and to change it quickly when people join, move or leave.
S
- SaaS (software as a service)Business & planning
SaaS is software delivered over the internet on a subscription basis, where customers use it in a browser or app rather than installing and maintaining it themselves. Examples include Slack, Shopify and Xero.
Why it matters: SaaS creates recurring revenue for the provider, but building one involves accounts, billing, multi-tenancy and ongoing hosting from day one.
- ScalabilityInfrastructure
Scalability is a system's ability to handle growth, such as more users, data or transactions, without major slowdowns or a rebuild. Systems can scale vertically by adding power to a server or horizontally by adding more servers.
Why it matters: Planning for reasonable growth avoids expensive rewrites, but over-engineering for scale you may never need wastes early budget.
- Scope creepBusiness & planning
Scope creep is the gradual expansion of a project's requirements beyond what was originally agreed, often through many small additions requested along the way. Without a change process, it pushes back deadlines and increases cost.
Why it matters: A clear scope document and an agreed process for handling change requests keep your project on time and on budget.
- Server-side rendering (SSR)Web & apps
Server-side rendering means a web page's HTML is generated on the server for each request and sent to the browser ready to display, rather than being assembled by JavaScript in the browser. Frameworks such as Next.js support it.
Why it matters: SSR helps pages show content quickly and makes them easier for search engines to read, which benefits SEO for dynamic content.
- ServerlessInfrastructure
Serverless is a hosting model where you run code without managing servers yourself; the cloud provider runs it on demand and scales it automatically. Servers still exist, but provisioning and maintenance are handled by the provider, and you typically pay per use.
Why it matters: Serverless can lower costs for variable or low traffic and reduce operations work, though it has limits for long-running or very high-volume workloads.
- Single-page application (SPA)Web & apps
A single-page application is a web app that loads once and then updates content in the browser as the user navigates, without full page reloads. Gmail and many dashboards work this way, typically built with frameworks like React.
Why it matters: SPAs feel fast and app-like for logged-in tools, but public pages built purely as an SPA can be harder for search engines to index.
- SitemapSEO & marketing
A sitemap is a file, usually XML, that lists the important pages on a website along with details such as when they were last updated. It is submitted to search engines to help them discover and crawl your content.
Why it matters: A sitemap helps new and updated pages get found by search engines faster, especially on larger sites.
- SSL/TLSSecurity
TLS (Transport Layer Security), and its older predecessor SSL, is the technology that encrypts data travelling between a browser and a website. A site using it shows HTTPS and a padlock in the address bar, and certificates are often available free from providers like Let's Encrypt.
Why it matters: HTTPS protects customer data such as logins and payment details, and browsers warn visitors about sites that do not use it.
- Staging environmentInfrastructure
A staging environment is a private copy of your website or app that mirrors the live (production) setup, used to test new features and updates before they are released to real users.
Why it matters: Staging lets you review and approve changes safely, without risking your live site or customer data.
- Statement of work (SOW)Business & planning
A statement of work is a document that defines a project's deliverables, scope, timeline, milestones, pricing and acceptance criteria. It is usually attached to the main contract between client and developer.
Why it matters: A clear SOW sets shared expectations and gives both sides a reference point if questions about scope or payment arise.
- Static site generation (SSG)Web & apps
Static site generation builds a website's pages into ready-made HTML files ahead of time, when the site is published, rather than on each visit. Those files can then be served very quickly from a CDN.
Why it matters: Static pages are fast, secure and cheap to host, making SSG a strong choice for marketing sites and blogs whose content changes infrequently.
- Structured dataSEO & marketing
Structured data is code added to a web page, usually in the Schema.org JSON-LD format, that describes its content in a machine-readable way, such as a product's price, an article's author or a business's address and opening hours.
Why it matters: Structured data helps search engines and AI answer engines understand your pages and can make them eligible for rich results such as star ratings or FAQs.
- Subscription billingWeb & apps
Subscription billing is the system that charges customers automatically on a recurring schedule, such as monthly or annually. It handles plans, trials, upgrades and downgrades, proration, failed payment retries and invoices, often using a service like Stripe Billing.
Why it matters: Billing logic has many edge cases, and getting it wrong directly affects revenue and customer trust, so it is worth using proven tools.
T
- Tech stackBusiness & planning
A tech stack is the combination of programming languages, frameworks, databases and services used to build and run a software product, for example Next.js, Node.js and PostgreSQL hosted on a cloud platform.
Why it matters: Your stack affects development speed, hosting costs and how easy it will be to hire developers in the future, so mainstream, well-supported choices are usually safer.
- Technical debtBusiness & planning
Technical debt is the future cost created when software is built with shortcuts or quick fixes instead of a cleaner approach. Like financial debt, it can be a reasonable trade-off for speed, but it accumulates interest in the form of slower development and more bugs.
Why it matters: Some technical debt is normal, but unmanaged debt makes every future change slower and more expensive.
- Technical documentationBusiness & planning
Technical documentation is written material that explains how a software system is built, configured, deployed and used, including setup instructions, architecture notes and API references.
Why it matters: Good documentation means another developer can take over your project without starting from scratch, protecting your investment.
- Two-factor authentication (2FA)Security
Two-factor authentication requires users to prove their identity with two different types of evidence, typically a password plus a one-time code from an authenticator app, text message or hardware key.
Why it matters: 2FA makes accounts much harder to take over even if a password is stolen, and it is especially important for admin accounts.
U
- UI (user interface)Design & UX
The user interface is everything a user sees and interacts with on a screen, including layout, colours, typography, buttons, icons and forms. UI design focuses on making these elements clear, consistent and visually appealing.
Why it matters: A clear, professional interface builds trust and makes your product easier to learn and use.
- Unit testWeb & apps
A unit test is a small automated test that checks one specific piece of code, such as a pricing calculation, produces the expected result. Unit tests run in seconds and are typically executed automatically on every code change.
Why it matters: Unit tests catch regressions early, making it safer and cheaper to change the software later.
- Uptime and SLAInfrastructure
Uptime is the percentage of time a system is available and working. An SLA (service level agreement) is a contractual commitment about service levels, such as guaranteed uptime, support response times and what compensation applies if targets are missed.
Why it matters: An SLA makes expectations explicit. Check what it actually covers, how uptime is measured and what remedies you receive.
- UX (user experience)Design & UX
User experience is how easy, efficient and satisfying it is for someone to use a product to achieve their goal. UX design involves researching users, mapping their journeys, structuring information and testing designs with real people.
Why it matters: Good UX reduces support requests and abandoned sign-ups or checkouts, which directly affects revenue.
V
- Vendor lock-inBusiness & planning
Vendor lock-in is when a business becomes so dependent on a particular provider's platform, tools or proprietary formats that switching away would be difficult or expensive. It can apply to hosting, software platforms or a development agency.
Why it matters: Owning your code, data and accounts, and favouring open standards where practical, keeps your options open if prices or service quality change.
- Version control (Git)Infrastructure
Version control is a system that records every change made to a codebase, who made it and why, so changes can be reviewed, combined and reverted. Git is the most widely used version control system, often hosted on services like GitHub or GitLab.
Why it matters: Version control protects your code from loss, enables team collaboration, and its repository should be owned by or accessible to your business.
W
- WebhookData & backend
A webhook is an automatic message one system sends to another when a specific event happens, such as a payment succeeding or a form being submitted. Instead of repeatedly checking for updates, the receiving system is notified in real time.
Why it matters: Webhooks are what make integrations feel instant, for example updating an order status the moment a payment clears.
- WireframeDesign & UX
A wireframe is a simple, usually black-and-white layout sketch of a screen that shows where content, navigation and buttons will go, without final colours, images or styling. It focuses on structure and flow rather than visual design.
Why it matters: Wireframes let you agree on structure and functionality early, before time is spent on detailed design or code.
Still unsure what your project needs?
Describe what you want to achieve in your own words. I will translate it into a plan, without the jargon.
Request a quote