Glossary

The specific conditions that define "done." Work is complete when it meets these — not when the client simply likes the direction. Vague acceptance criteria is how revision cycles never end.

Money owed to you by clients for services already delivered. High accounts receivable means you've done the work but haven't been paid — a cash flow risk, not a revenue win.

A written addition to an existing contract that modifies or extends it. Adding new deliverables mid-project should go in a signed addendum, not a Slack message.

A project approach that breaks work into short cycles (sprints) with frequent reviews and adjustments. Contrasted with waterfall, which plans everything upfront and delivers once at the end.

When all stakeholders share the same understanding of goals, priorities, and approach. The goal of most early-phase meetings. Misalignment discovered late is expensive.

A defined way for software systems to talk to each other. When you ask a client's CRM to send data to your invoicing tool, that connection goes through an API.

A way to resolve disputes outside of court. Both parties agree in advance to let a neutral third party decide. Usually faster and cheaper than litigation.

The predictable yearly revenue from subscriptions or retainers. Preferred over total revenue for measuring business stability because it excludes one-time income.

The creative vision for a project — the visual style, tone, and decisions about how everything looks and feels. Art direction sets the standard; execution follows from it.

Verifying identity — proving you are who you say you are. Passwords, tokens, magic links, biometrics. Gets you through the door.

Controlling what an authenticated user is allowed to do or access. Authentication = who you are. Authorization = what you can do. Both matter; confusing them is a security bug.

The server-side layer of a software product: databases, business logic, APIs. Not visible to end users. When something breaks invisibly, it's usually the backend.

The full list of features, bugs, and tasks to be built — ranked by priority. Items get pulled from the backlog into the current sprint. An unmanaged backlog becomes a graveyard.

The visual and verbal elements that make a company recognizable: logo, color palette, typography, voice. A brand identity is a system, not just a logo.

When one party fails to meet their obligations under the contract. Missing a deadline is breach. Not paying is breach. Naming breach consequences turns a vague violation into an actionable event.

An error in code that causes unexpected or incorrect behavior. Bugs range from cosmetic (wrong color) to critical (data loss). Severity determines priority, not visibility.

How fast a business spends money — usually per month. If your burn rate exceeds revenue, you're losing money. Runway = how many months until you run out.

How much it costs to acquire one new client — time spent on proposals, outreach, and onboarding. Compare CAC to LTV to know if a client type is worth pursuing.

The movement of money in and out of a business. Profitable businesses can still fail from cash flow problems — if you're always owed more than you've collected, you can't pay your own bills.

The structured process of helping people adapt to organizational changes. Most technology projects fail not because the software is wrong but because the people part wasn't managed.

The rate at which clients or subscribers stop paying. High churn means you're replacing your client base repeatedly instead of building on it — expensive in time and acquisition cost.

Automated pipelines that test code when it's submitted and deploy it when tests pass. CI/CD means code goes from developer to production without a manual release process.

Software for creating and managing digital content without writing code. WordPress, Webflow, Contentful. Clients edit their own content; developers configure the system.

The color model used for print. Colors mix as physical pigments — different from RGB. What looks right on screen often needs adjustment for print production.

A mutual agreement to keep certain information private. Covers client plans, proprietary processes, and unreleased work. Often formalized as an NDA.

The document that defines a creative project before work begins: goals, audience, constraints, deliverables, and what success looks like. A bad brief is the root of most bad work.

A specific, named output you've committed to produce. Not "design work" — the five pages in the SOW, in Webflow, as a live site. If it isn't named, it isn't a deliverable.

The process of releasing code to a live environment. Deploying to production means real users see the change. Deploying to staging means only the team does.

Upfront payment before work begins. Standard is 50% for project work. Commits the client before you've spent an hour — and means you have something in hand before delivering anything.

The initial phase of an engagement focused on understanding the client's situation before recommending solutions. Skipping discovery leads to solving the wrong problem well.

72 DPI for screen. 300 DPI for print. Resolution determines whether an image looks sharp or blurry at its output size. Low-res images can't be fixed by scaling.

A consulting project or contract — the full scope of work from kickoff to delivery. Each engagement typically has its own SOW, timeline, and deliverables.

Expenses that don't change with output: software subscriptions, equipment, insurance, rent. You pay them whether you have one client or ten.

A contract clause that suspends obligations when extraordinary events outside anyone's control make performance impossible. Natural disasters, pandemics, government shutdowns.

The visible, user-facing layer of a software product — what you see and interact with in a browser or app. HTML, CSS, JavaScript. The interface a designer's work lives in.

Comparing the current state to the desired state to identify what needs to change. The gap is what you're being hired to close.

The moment a new system, product, or process is launched for real use. Go-live is both a milestone and a risk event — problems that weren't visible in testing become visible immediately.

A structure of horizontal and vertical lines used to organize elements on a page or screen. Grids create alignment, rhythm, and visual consistency across a layout.

Revenue minus the direct cost of delivering that revenue. A high gross margin means you keep most of what you earn before overhead. Low gross margin means most of the money passes through.

A clause where one party agrees to cover costs if a third party makes a claim against the other. Protects you from being pulled into disputes that aren't your fault.

Ownership rights to creative work. The key question: who can use, sell, or modify the deliverables? Standard freelance practice: IP transfers to the client on final payment.

Which legal system applies to your contract — which state or country's laws govern, and where disputes are heard. Set this to where you are, not where the client is.

The spacing between individual letter pairs. Affects readability and the visual texture of a word. "AV" and "WA" typically need tighter kerning than other pairs.

A payment owed if a client cancels after work has begun. Typically 25–50% of the remaining balance. It compensates you for time blocked and work already done — not a penalty.

A measurable value that tracks progress toward a specific goal. A KPI without a target is just a number. A target without a KPI is just a wish.

A financial penalty on overdue invoices. Standard is 1.5% per month. Its main function isn't the fee itself — it makes "on time" worth something to the client.

The delay between a request and a response. Measured in milliseconds. High latency makes software feel slow even when the underlying system is working correctly.

The vertical spacing between lines of text. Named after the lead strips used in old typesetting. Too tight and text is claustrophobic; too loose and it loses cohesion.

Legal responsibility if something goes wrong. A contract's liability clause limits how much you can be held accountable for. Without one, exposure is uncapped.

The total revenue expected from a single client over the entire relationship. LTV tells you how much a client relationship is actually worth — not just the first project.

A specific, dated checkpoint in a project — often tied to a payment or a deliverable review. Milestones break a long project into accountable stages.

A realistic preview of a finished design shown in context — a logo on a business card, a website on a laptop screen. Used for client presentation before final production.

A visual collage of references, colors, textures, and images that establish the direction for a project. Gets everyone aligned on tone before any design work begins.

Predictable monthly income from ongoing contracts or subscriptions. One retainer at $3,000/month is more valuable than a $6,000 one-off because you can plan around it.

A standing contract covering the rules of your working relationship — liability, IP ownership, and how disputes get resolved. Signed once, applies to every project with that client.

The simplest version of a product that delivers core value and can be tested with real users. Not the final product — the first testable version. Ship it, learn from it, iterate.

A confidentiality agreement that prevents you or the client from sharing proprietary information — business plans, unreleased work, your processes — with outside parties.

The empty space around or between design elements. Often as important as the elements themselves. Good use of negative space creates clarity, focus, and breathing room.

Payment window terms. "Net 30" means payment is due within 30 calendar days of the invoice date. Shorter windows (Net 15, Net 7) reduce your exposure with new or unknown clients.

Revenue minus all costs — the actual percentage you keep after everything is paid. Gross margin looks good; net margin tells the truth.

A clause restricting you from working with competitors of your client for a defined period. Broad non-competes in freelance contracts are often unenforceable — read them carefully.

A goal-setting framework: one qualitative objective (what you want to achieve) paired with 2–3 measurable key results (how you'll know you got there). OKRs should be ambitious and transparent.

The ongoing costs of running a business not tied to any specific project: software, insurance, professional fees, your own unbillable time. Factor overhead into your rates, not after.

A financial statement summarizing revenues, costs, and expenses over a period. Shows whether the business is making or losing money — and where the money went.

Breaking a project into sequential stages, each with its own deliverables and sign-off. Reduces risk by making large projects reviewable in parts before committing to the next phase.

A formal document from a client authorizing a purchase and committing to pay. Large companies often require a PO before they'll process an invoice. Get the PO number before you start.

Testing to verify that software works as intended before release. QA catches bugs the developer didn't see. Skipping QA saves time once; it costs more time later.

An image made of pixels — JPEG, PNG, GIF. Loses quality when scaled up. Raster files are best for photos and complex images, not logos or icons you need at multiple sizes.

A storage location for code, managed with version control (usually Git). Every change is tracked. You can see who changed what, when, and why — and revert if needed.

An ongoing arrangement where a client pays a fixed monthly amount for defined services or availability. The deliverable is access to you, not a specific output.

A document asking vendors to describe how they would approach a project and at what cost. Responding to an RFP is a significant time investment — qualify the opportunity before committing.

The color model used for screens. All three channels at full intensity produce white (additive color). What you design in RGB may not reproduce accurately in CMYK print.

A clause giving a client the opportunity to hire you for follow-on work before you take it elsewhere. You're not obligated to accept their offer — only to offer them the chance first.

What you get back relative to what you put in: (Revenue − Cost) / Cost. Useful for evaluating whether a tool, campaign, or engagement is worth continuing.

Software delivered via the cloud on a subscription basis — Slack, Notion, Figma. You don't install it; you pay to access it. Recurring cost, no maintenance, accessed anywhere.

The structure defining how data is organized in a database: tables, columns, types, and relationships. Changing a schema after data exists is expensive — design it carefully upfront.

The gradual expansion of a project beyond what was agreed. Almost always starts before the work does, in the gap between what both parties assumed was included.

A written commitment about your availability and response times. It answers "what can I expect from you?" before a client has to ask.

Someone with specialized knowledge in a specific domain. In a consulting engagement, the SME on the client side is often the person who actually knows how things work — not the executive sponsor.

A per-project document that defines what you're building, when it's due, and what it costs. It's what you point to when a client asks for more than you agreed.

A fixed-length work cycle — usually 1–2 weeks — in an agile team. At the end of each sprint, working software is reviewed and the next sprint is planned.

A near-identical copy of the production environment used for testing before release. What you test in staging should behave like production. If it doesn't, the staging environment is wrong.

Anyone with an interest in the outcome of a project: decision makers, end users, department heads, executives, clients. Identifying all stakeholders early prevents surprises late.

A document defining the visual and verbal rules for a brand: how to use the logo, which fonts, which colors, what language is and isn't on-brand. A style guide makes a brand consistent at scale.

The accumulated cost of shortcuts and quick fixes that will need to be properly addressed later. Like financial debt: sometimes worth taking on, always has interest, and eventually must be paid.

The art of arranging text — choosing typefaces, sizes, weights, and spacing to make content readable, structured, and expressive. Typography carries a brand's personality.

The client or end user validates that the software meets requirements before sign-off. UAT is the moment when "built as specified" meets "works as expected" — they're not always the same.

99.9% uptime sounds good until you calculate it: about 8.7 hours of downtime per year. 99.99% is 52 minutes. What your SLA promises matters when a client's revenue depends on your tool being up.

Expenses that scale with output: subcontractors, materials, per-project software, printing. Unlike fixed costs, they rise and fall with the amount of work you take on.

An image defined by mathematical curves rather than pixels — SVG, AI, EPS. Scales to any size without quality loss. Logos and icons should always be delivered as vectors.

A system — usually Git — that tracks every change to code over time. Enables collaboration without overwriting each other's work, and lets you revert to any previous state.

An automated message sent from one system to another when a specific event occurs. A payment is confirmed → Stripe sends a webhook to your app → your app updates the invoice status.

A basic structural sketch of a page or interface showing layout and hierarchy, without color or final design. Wireframes lock in structure before visual design begins — cheap to revise, expensive to change later.

A legal arrangement where the client owns everything you create because it was commissioned work. Standard for most freelance relationships once paid — which is why IP clauses matter.

A structured working session with stakeholders used to gather information, align on direction, or solve problems. A well-run workshop produces decisions. A poorly run one produces action items that go nowhere.