Glossary

Startup software terms, in plain English.

The acronyms and jargon founders hit when they start building software, defined without the hand-waving and linked to how we put each one into practice.

  • Agile

    A way of building software in short, iterative cycles with frequent feedback, instead of one long plan.

  • API (Application Programming Interface)

    A defined way for two pieces of software to talk to each other and exchange data.

  • Backend

    The server-side part of an app: the logic, databases, and APIs users never see directly.

  • CI/CD (Continuous Integration and Delivery)

    Automated pipelines that test and release code safely and often, instead of in risky big-bang launches.

  • Cloud Hosting

    Running your app on rented, on-demand infrastructure instead of your own physical servers.

  • Database

    The organized store where your product keeps its data: users, orders, content, and everything else.

  • Frontend

    The part of an app users see and interact with: the screens, buttons, and visuals in the browser or app.

  • Full-Stack

    Spanning both frontend and backend: an engineer or team comfortable across the whole product.

  • MVP (Minimum Viable Product)

    The smallest version of your product that delivers real value and lets you learn from actual users.

  • Product-Market Fit

    The point where your product satisfies a strong market demand, meaning people genuinely want what you built.

  • Prototype

    A quick, often throwaway model used to test an idea or design before committing to a real build.

  • SaaS (Software as a Service)

    Software delivered over the internet on a subscription, instead of installed and owned outright.

  • Scalability

    A system's ability to handle growth in users, data, or traffic without falling over or slowing down.

  • Tech Stack

    The set of languages, frameworks, and tools used to build and run your product.

  • Technical Debt

    The future cost of shortcuts taken today: code written fast that will need cleaning up later.

  • UI / UX

    UI is how a product looks; UX is how it feels to use. Together they shape the whole experience.

  • Version Control

    A system that tracks every change to your code, so teams can collaborate and roll back safely.

  • Wireframe

    A simple, low-detail sketch of a screen's layout, used to plan structure before visual design.

Let's build something together.

Tell us what you're working on. We reply within 24 hours with an honest read on scope, timeline, and cost.