# Understanding PAI Most software tells you how to do things. This document tells you how PAI *thinks* — the operating logic underneath the features. Once this clicks, everything else in PAI makes immediate sense. ## The Problem PAI Is Solving Creative project work runs on agreements. What you sold the client, what you committed to vendors, what each day is budgeted to cost, who gets paid at what rate, for how many hours. Whether you're producing a TV commercial, a print campaign, a radio spot, or a digital content series — the financial structure underneath is the same. In practice, these agreements tend to live in scattered places — email threads, spreadsheets, phone calls, PDF attachments. By the time a project wraps, it can be genuinely hard to know whether you made money, and nearly impossible to know precisely *why* you did or didn't. PAI exists to change that. Not by simplifying the agreements — they're complex because creative work is complex — but by keeping all of them in one place and connecting them to each other. ## The Central Idea: Protect Your Margin PAI is built around a single principle: **protect your margin by being explicit about what you agreed to on both sides.** On the client side, that means being specific when you build an estimate. Not "editor, a few days" but "one editor, four days, at $800/day external, $750/day internal." PAI asks for that level of detail because it's the foundation of everything that follows. The estimate is your record of what you sold. On the vendor side, that means being specific about the terms of the engagement. Not just the rate, but the baseline — how many hours define a standard day, what triggers overtime. PAI calls this "min hours," and it's not a bureaucratic detail. It's the definition of your agreement with the vendor, entered once, so PAI can track whether that agreement is being honored as the project runs. When both sides are captured explicitly, PAI can do something that's otherwise very hard: connect them. You sold it for X. You've committed Y to vendors. You've spent Z so far. You're over or under by the difference. PAI will always show you that, in real time, without you having to calculate it. ## Two Cost Tracks: What You Pay Out and What You Put In A real project costs you in two ways. There's the money you pay out — vendors, freelancers, rental houses, anything that leaves the building. And there's the cost of the people you already employ — the staff hours your team spends delivering the work. Both are real costs. Only one of them shows up on an invoice. PAI tracks both, as two parallel cost tracks on every project: - **Out-of-Pocket** — external spend paid to vendors and freelancers. Everyone on the project sees it. - **In-House** — the cost of your own staff's labor, drawn from each person's rate card. Because that cost exposes your true cost of delivery and the margin you make on internal work, the internal dollars are visible only to those you grant access; everyone else still sees the hours and the external side. Every line item declares which track it belongs to through its **Resource Type**. That single designation is what lets PAI keep the two costs straight — and then combine them. A margin that counts only out-of-pocket spend tells you how the vendor side performed. A margin that also counts in-house labor tells you what the project actually cost to deliver, and what you actually made. PAI shows you both, so the number you act on is the true one. This is the same discipline as everything else in PAI: be explicit about a cost, and PAI will track it and tell you where it stands. In-house labor was always a cost. Now it's a tracked one. ## What PAI Tells You — and What It Doesn't PAI's job is to tell you the truth about your project's financial position. It does this reliably, but only if you feed it accurate information. What PAI will not do is tell you what to decide. If a project runs over and pushes you past budget, PAI will surface that overage immediately and show you exactly how much it is. Whether you absorb it, charge the client, or split the difference — that's your call. PAI informs the decision. It doesn't make it. This is an important distinction. PAI is not managing your client relationship or your vendor relationship. It's giving you the information you need to manage those relationships yourself, from a position of clarity rather than guesswork. ## Meticulous Without the Overhead The level of operational detail PAI asks for can feel unusual at first. Most production tools don't require this kind of specificity, and most teams don't maintain it — not because it isn't valuable, but because the manual effort to maintain it historically outweighed the benefit. PAI is designed to close that gap. The structure is there to serve you, not the other way around. Once the estimate is built, PAI generates the budget. Once vendors are assigned, PAI tracks the spend. Once expenses are posted, PAI notifies vendors and manages the invoice flow. The meticulous structure runs in the background; what you see is a clear picture of where you stand. Users who understand this tend to get productive in PAI quickly. The app isn't asking for detail for its own sake — it's building the connective tissue that makes the whole picture visible. ## Where to Go from Here If you're setting up PAI for the first time, start with [First Login and Setup](./First-Login-and-Setup.md), then [Organization Setup](../01-Organization-Setup/Organization-Settings.md) to configure your workspace before creating any projects. If you're ready to bid a project, go to [Creating a Project](../02-Bidding-a-Project/Creating-a-Project.md). If you want to understand how PAI shows you your financial position in real time, see [Live Margins](../06-Financial-Visibility/Live-Margins.md) — that's the clearest expression of this philosophy in the product.