# Runway on the home board. A month closed before the investor update URL: https://www.orla.finance/en/for/saas Markdown twin of that page. Append `.md` to any Orla page URL to get one. Tidewater Metrics sells an analytics product on Stripe and runs a team of nine on payroll and contractors. #### Burn and runway, from the rows The investor asks for burn and runway on the first of the month. Is the answer a spreadsheet from last quarter, or this morning's rows? - Burn and runway come off the last three full months of the book, not a typed-in figure. - The P&L as a tree splits every category by team, six months side by side, and every figure in it opens into the rows it was made of, one row at a time. - Ask for the investor update and it is put together from the rows: in, out and net against last month, runway, burn, MRR, DSO, and the three main movements with their arithmetic. It never invents a cause the rows do not carry. Where routines are switched on, the same question goes out by mail on the first of the month. - Three figures instead of a list: free on the accounts you can send from, committed to this week's payments, and what is left, per currency. Wallets and exchanges stand beside the figure, not inside it, because a position is not money to send. - How dependent the company is on one client, from what actually arrived over twelve months: the largest client's share, how many clients make eighty percent, and what a month loses if the largest leaves. - A report is described in words and saved as a question, and it runs again each time it is opened. - Published by link as a frozen snapshot that expires; the team's thread stays inside. #### Stripe daily as rows, any other system by push Revenue is in the Stripe dashboard, the payouts are in the bank, and the billing system you built yourself has no connector at all. What did we actually earn this month? - Stripe connects with a key you make there; sales come in daily, with the fees kept separate from them. - A payout is a transfer between your own accounts, never income; nothing counts twice. - For a system with no connector the direction is reversed: Orla holds no key of yours and calls nobody. Your own automation, a script or a scheduled job posts the rows, and Orla files them into that source's own accounts. - The push key files rows into its own source and can touch nothing else in the book. It lives 30, 90 or 180 days or a year, never forever; a row sent twice is filed once, a call is one batch that is undone whole, and a source silent for three days is marked quiet. - Pushed rows count as imported, never as money arriving on a rail, so an automation that ships on payment does not fire on them. They come out of the plan's synced rows for the month, the allowance bank and exchange sync use. - The annual plan's invoice is paid by card via your own Stripe, by transfer or in USDC. - Connection health on one page; a daily rule names a connection that quietly broke. #### Annual plans invoiced and chased Two enterprise customers pay annually by invoice, one is late, and procurement wants a credit note for dropped seats. Who chases whom? - Four figures as filters: owed, overdue, received this month, paid without an invoice; each one opens its own list. - Who owes, one row per client and not per invoice: how much, how late the oldest is, how many reminders went and when, whether they answered, the day they promised, and one next step with its reason. Three reminders and silence means it is time to phone. - Recurring invoices, reminders, and an invoice that marks itself paid when money lands; your backend hears invoice.paid as a signed event, whichever way it was paid. - The invoice mail names you in the subject, and the client's Reply goes to the billing email printed on the document. The From line stays Orla on purpose, so a mail about money cannot pretend to come from someone else. - A credit note corrects a sent invoice as a second document, never an edit. - A client gets a chat of their own: the invoice arrives with its buttons, and every reply lands in your channel under their name, with any file they drop. #### One payment page that answers a person and a machine A client pays for onboarding by link before the contract is signed, and other people's agents call your API all night. Can your server name a price per call, and does the money land in the book already attributed? - A request by link: the amount, what it is for, and the rails the payer may use to settle it with you. Paid by card via your Stripe, by transfer or in stablecoins, matched to the request and booked as income the day it lands. - Your server names the price for a machine: a key with the payments scope mints a payment request and gets a URL back. A person opening it sees the ways to pay; an agent is answered with a price (x402) and pays it in USDC on Base, Ethereum or Polygon, with no account and no key on its side. - The floor is one dollar, the payee receives the full amount, and paid is set only after the chain confirms. The first paid call gives the endpoint a card of its own, and a metered endpoint books one income row a day, so a busy endpoint reads as one line and not as thousands. - Client credits carry the calls that cost less than a dollar: the client pays ahead, your server charges one call against that client, and the answer is either paid or a refusal with a top-up request ready. There is never an overdraft, the balance is service you still owe and not money Orla holds, and the client reads it on a page of their own without an account. - Seller keys live in the cabinet: a name, the scopes, an optional webhook address, the key and the webhook secret shown once. A key acts as the person who issued it, in one book, so removing that person or making them a viewer stops their keys on the next call; a leaked payments key cannot issue, void or chase an invoice. - A machine that paid becomes a contact: the day's payments list each payer's address, one press makes a stranger a contact, and a learned address never lands on a card you already keep. - The seller side is new: the key door is on for listed books, the payment routes have a switch of their own, and what the paid plans sell is the machine payments themselves. The developers page has every route and limit. - A permanent payment address for the space; on your @handle page a visitor names an amount and gets a link of their own, on the rails you allowed. #### Contracts, order forms and policies on one shelf The MSA is in one inbox, the order form in another, the insurance policy in a folder nobody opens. Where is the paper, and what is each file attached to? - Filed by a schema you set in words, with versions and access. - A document becomes a bill to pay or the receipt on a payment; upload in bulk. - A Google Drive folder is a door into the book. - A whole sort run is previewed as a plan and undone as a whole; a document can be sealed in the browser so the server itself cannot read it. #### Contractors paid in one batch Three contractors on three continents, paid twice a month. One run, a threshold, and the CEO never pays anyone alone. - A queue for signature with an approval threshold and the number of signatures it takes; the preparer's own signature does not count. - The rule checks the batch total, so it cannot be dodged by slicing. - Fiat payouts leave from your own bank, and Orla cannot send them alone. From Mercury each payment is a request in Mercury's approval queue, and the token has no Send Money right; in Airwallex it is a line of a draft batch per currency that a person submits there; in Revolut Business a draft a person approves inside the bank. Mercury and Airwallex reach spaces as they roll out. - A PayPal payout is different and says so: once approved it waits on the Payments page, and a person pressing Pay via PayPal is what sends it. - Batch payouts, on the plans that carry them: up to 200 per batch, CSV preview, duplicate warning, autosave, and a template for the next one. #### Team cards funded from the USDC treasury Growth runs ads on one card, infrastructure runs Datadog and Vercel on another. Can each carry its own ceiling, topped up from the USDC treasury? - Virtual Visa or Mastercard cards from a prepaid balance, topped up in stablecoins. - A card per person with a ceiling, freeze and block; the issuer's history is checked against what you allocated, so a stray charge shows up the same day. - Refunds are answered in the books on their own. #### Software and marketing against a monthly budget Every hire adds three seats somewhere, the ads budget is gone by the twentieth. What may the month spend, and who hears first? - Monthly limits per category, what is left of each, what slipped past. - A budget watch tells the team before the limit, not after. - Unspent budget rolls into next month; the spend breaks down per team member. #### Every subscription on one calendar AWS on the third, Datadog on the fifth, payroll on the first. What leaves this month, and where is the low point, and on which day? - Everything dated on one page: what is overdue, what falls this week, what is coming in, and where the balance lands at month end. - Contracts add what they promise; a row that looks recurring gets a hint. - The forecast names the low point and its day; unpriced rows are listed, not guessed. - Ask what got more expensive: the last charge against the typical one before it, in the supplier's currency, so a month with an extra seat does not read as a price rise. A press writes the new price into the plan; nothing is cancelled with the supplier, which only the supplier can do. - A rule tells a person before a balance goes below the line or a budget is nearly spent. #### The month to the accountant Board meeting on the tenth, the accountant wants the month by the fifth, and the last export still had rows without an account code. - A closing checklist with a door into each list: rows without a category, rows without an account code, rows without paper, payments without a quorum, and every invoice still unpaid at the close. - A zip archive, a journal CSV, and each account's feed for QuickBooks Online and Xero. - Rows without paper are asked of whoever paid: the teammate answers with the file, No receipt or Not mine, or presses Attach a receipt in Slack or Telegram, and the row closes itself when a file arrives by any door. - Review, Close, Reopen with a reason; what changed after the export is visible. - A closed month is read-only at every door; the archive says who sorted what. #### Five people, five different views - Founder: Reads burn and runway on the home board, issues the seller keys, and signs what crosses the threshold. - Finance lead: Prepares the contractor batch, reads who owes and what the next step is, and closes the month. - Account manager: Sends the order form and the invoice, and hears in the channel when the client asks for time. - Team member: Files a receipt from the channel and sees only the cards and claims that are theirs. - Accountant: Gets the month in files, Stripe's rows included, and a seat that reads the closed period. #### Ask how much hangs on one customer The composer counts what arrived over twelve months, not what was invoiced, and says what a month loses if the largest customer leaves. - How much hangs on one client: The largest client's share over twelve months, how many clients make up 80%, and what a month loses if the largest leaves. - Why a figure moved: Income, spending, burn or runway against the month before, broken down by category with the arithmetic the reports use, and never a cause the rows do not carry. - The investor update: KPI, cash flow, top clients, MRR and runway for the month, with the three moves that mattered explained. #### Revenue in, signed events out Revenue comes in from Stripe and machines that pay per call; contractors are paid from your bank; signed events go out. #### Signed webhooks, signed payouts - Events, not your books: Amount, currency, direction, account, ids and time, signed with HMAC-SHA256. No names, memos or addresses: a leaked address costs a number and a timestamp. - Signing rules: A threshold, the number of signatures, address book only, a monthly allowance per person. - Oversight: An oversight report frozen the day after the month ends, with every exception to the rules. - Agents: Your own agent spends only from its own wallet, inside a fence and a daily ceiling, and proposes the rest for a person to sign. A receipt per dollar. #### Questions ##### Where does runway come from? From the book: burn is the average of the last three full months of outgoings, runway is the liquid balance divided by it. Neither is typed in, and both open into the rows behind them. ##### Do we have to leave QuickBooks or Xero? No. Orla is the layer before it. The accountant keeps their software and receives the month from Orla as statements for every account, a journal and one archive. ##### Can our API charge other people's agents per call? Yes. Your server asks Orla for a payment request and gets a URL; an agent calling it is answered with a price and pays in USDC, with no account on its side. Calls under a dollar are charged against credits the client paid ahead, never into overdraft. The seller side is on for listed books while it is new, and machine payments are sold by the paid plans. ##### How does our backend hear that money moved? Through event subscriptions: money in, money out, invoice paid, payout executed, payment awaiting approval and payment blocked go to your https address, signed, at least once, with retries over a day and a delivery log you can replay. They come with the higher paid plans; the webhooks page lists the events and the plans. ##### Can an agent close the month or pay anyone? An agent may put a payment from the space's accounts in the queue and a person signs it; what it pays alone comes from its own wallet, inside your limits. Closing a month is a person's press with a reason, and a closed month is read-only at every door.