SaaS

The Business Behind the Software

Comments

  1. Eli Brandt on The Meter Is the Strategy: Choosing the Right Unit of Value for Your AI Product

    In reply to Dane Whitlock

    Dane, you’re right to put runway ahead of pricing elegance. A platform fee only protects a bootstrapped founder if it covers the cost of serving that customer at today’s volume, not at the scale in a spreadsheet. And if outcomes take 60 days to verify, billing the base fee upfront matters as much as choosing the right meter.

    I’d also keep the first version of outcome tracking simple. Record what the agent did, what it cost, and whether the customer accepted the result. You can refine attribution later. You can’t recreate the missing history.

  2. Dane Whitlock on The Casino Vibe: Why Rationed Limits Are the Tell of a Broken Pricing Model

    For a small, customer-funded product, the dangerous limit is the one you discover after the invoice arrives. I’d push back slightly on pricing per completed workflow as a complete fix. An agent can retry the same workflow ten times, and you still pay for every attempt.

    Before promising a feature, I’d run a paid pilot and record the model cost of each job, including failures and retries. If a customer pays $500 a month and one busy week can produce a $300 inference bill, that is not predictable revenue. It is an open liability. Set a maximum cost per job and decide what happens when the agent reaches it: stop, hand the work to a human, or ask the customer to approve another attempt.

    Customers should know those boundaries before they buy. A fixed, honest limit is less magical than “unlimited.” It also lets a tiny team keep the promise it made without gambling its cash flow on the next API bill.

  3. Priya Raman on Revenue Isn’t Cash: A Bootstrapper’s Guide to Getting Paid on Time

    In open-core businesses, the cash gap can start before the contract does. An enterprise buyer may ask for security reviews, deployment help, and a roadmap commitment while procurement is still months from paying. “The software is already free” does not make that work free to deliver.

    I’d put a boundary at the start of that work, not at the end of a late-invoice sequence. Keep the community edition available. Tie dedicated onboarding and support to an approved purchase order or an upfront payment. That protects cash without making the open-source community carry the cost of an enterprise sale.

  4. Maraya on Your AI Customer Can Build It Now. Price the Work They Don’t Want to Own

    In reply to Mara Delgado

    Mara, I’d make that return rate a contract term, not just a report. Agree on which exceptions require the buyer’s judgment, then set a ceiling on how much routine work can come back. Above that ceiling, the vendor handles it or credits the buyer.

    Otherwise the vendor gets paid for the easy invoices while the buyer still needs a team for the hard ones. That is exactly the responsibility the buyer thought they were purchasing.

  5. Mara Delgado on Revenue Isn’t Cash: A Bootstrapper’s Guide to Getting Paid on Time

    An annual contract with net-60 terms is not really a prepayment. If you offer an annual discount for it, you may be giving up margin while still financing the customer’s purchase.

    I’d make the discount conditional on payment timing: one price for annual payment at signing, another for annual billing on extended terms. That turns a hidden cash-flow cost into a clear choice for the buyer.

  6. Eli Brandt on Your Usage Meter Is Not a Pricing Strategy

    In reply to Priya Raman

    Priya, “exploration being fined” is exactly the feeling to avoid. I’d make one distinction: the habit loop need not be free, but it must be predictable. Give teams a generous, capped space to learn. Then charge for production work they can recognize as valuable, while keeping the model’s token bill out of their way.

  7. Dane Whitlock on The Renewal Is Where Your New Pricing Model Gets Tested

    For a bootstrapped company, a renewal surprise can be a cash-flow problem before it becomes a churn metric. Losing one $24,000 annual customer may mean losing the cash earmarked for a contractor or several months of hosting. I’d forecast that account’s next bill before proposing new terms, then ask a harder question: can we afford the bridge we’re offering?

    I’d keep a simple renewal ledger: current contract, last 12 months of usage, projected bill, transition promise, and the date that promise ends. Put the expected cash receipts beside the costs of serving the account. If a cap protects the customer but leaves us underwater during a peak month, we need to know that before we sign it.

    The point isn’t to squeeze the first renewal for maximum uplift. It’s to reach the second renewal with the customer’s trust and the company’s cash intact.

  8. Maraya on Revenue Isn’t Cash: A Bootstrapper’s Guide to Getting Paid on Time

    In reply to Eli Brandt

    Eli, that’s the sharper clock. I’d pair it with a dollar figure: the most delivery cost we incur before payment lands. A 30-day gap is manageable at $200 and dangerous at $20,000.

    For agentic products, that makes prepaid credits more than a billing preference. They set a clear limit on how much work the company finances, while letting customers choose when to add more.

  9. Priya Raman on Your AI Customer Can Build It Now. Price the Work They Don’t Want to Own

    In open-core, customers have always had a build option. Some even run our code themselves. The ones who pay are buying a team that will maintain it, answer when it breaks, and make upgrades less risky. AI makes that choice more common, not fundamentally different.

    I’d be careful with outcome pricing when the vendor cannot control the whole outcome. If the customer owns approvals or a brittle accounting integration, “invoice completed” can become a dispute about whose system failed. Price the responsibility you can actually take. Then make the handoff visible enough that both sides can tell when you delivered it.

  10. Mara Delgado on Your AI Customer Can Build It Now. Price the Work They Don’t Want to Own

    Per-accepted-invoice pricing sounds clean until the vendor gets to decide which invoices are “exceptions.” The buyer could end up paying for the easy work while keeping the costly tail.

    I’d put a bounded amount of exception handling in the base price, then report the share of invoices sent back to the customer. That return rate is part of the bargain. If it climbs, the buyer hasn’t really transferred responsibility.

  11. Eli Brandt on Revenue Isn’t Cash: A Bootstrapper’s Guide to Getting Paid on Time

    In reply to Maraya

    Maraya, I’d add one clock: days from first delivery cost to bank deposit. Signature-to-cash tells you how long collection takes. Cost-to-cash tells you how long you’re financing the work.

    That matters for agentic products, where inference costs can start as soon as the product begins acting. A long payment term paired with heavy early usage may need an upfront credit or a usage limit, not just a higher annual price.

  12. Dane Whitlock on Your Cloud Is Not the Product

    In reply to Maraya

    Maraya, the CFO test is useful, but for a tiny team I’d run it before building the next cloud feature. Ask three paying customers: “What work stopped landing on your team because we run this?” If the answer is “our engineer no longer spends six hours a month on upgrades and recovery drills,” you have a claim worth testing in the sales conversation. If they can only say “we don’t manage servers,” don’t hire a sales team or build an enterprise feature checklist yet. Find the responsibility customers will actually pay you to take on, then fund that work from their payments.

  13. Maraya on Revenue Isn’t Cash: A Bootstrapper’s Guide to Getting Paid on Time

    Payment timing is part of the price. A $30,000 deal paid in 60 days asks a bootstrapped company to finance the customer. That cost belongs in the decision, even when the contract value looks great.

    I’d track days from signature to bank deposit by customer type. If enterprise deals consistently take longer, that pattern should shape the offer: an onboarding payment, a later start date, or a price that reflects the wait. Better to design for the cash cycle than be surprised by it every quarter.

  14. Priya Raman on When a Customer Pays for an Open-Source Feature

    One question I’d ask before signing: is the customer comfortable funding a feature their competitors can use? I’ve seen that surprise surface only after the work is done.

    If the answer is no, a private integration may be the honest deal. If the answer is yes, sell speed and support. Don’t quietly sell ownership of a shared feature.

  15. Mara Delgado on When a Customer Pays for an Open-Source Feature

    In reply to Dane Whitlock

    Dane, your “would we maintain it if they leave?” test is the right gate for upstream work. I’d make the maintenance allowance a separate, renewable line item. Otherwise the customer sees one feature price while the team quietly takes on a subscription-sized obligation. If the customer won’t pay for ongoing support, that’s useful evidence that a supported adapter is the better package.

  16. Eli Brandt on Hire Slow, Stay Small: A Bootstrapper’s Playbook for Making Your First (and Maybe Only) Hire

    In reply to Dane Whitlock

    Dane, fixed-price buys cost certainty, but it can also reward a rushed audit. I’d define the acceptance criteria as tightly as the fee: which docs improve, how you’ll check accuracy, and how much founder review the work needs.

    I’d make the same distinction on the 60-day test. You should be able to measure output by then. Churn or revenue may take longer to move. The early signal is whether this person reliably takes work off your plate without creating a new review job.

  17. Maraya on The Meter Is the Strategy: Choosing the Right Unit of Value for Your AI Product

    In reply to Eli Brandt

    Eli, the platform fee should cover the cost of keeping the account live, not become the main source of margin. For the cash-flow gap, I’d pair that modest fee with prepaid outcome credits, used only when both sides agree an outcome was delivered. The renewal conversation then stays where it belongs: not “Did you use the software?” but “What did it accomplish?”

  18. Dane Whitlock on Customer-Funded Development: How to Build Your Roadmap Without Burning Runway

    In reply to Eli Brandt

    Eli, you’re right. My “build cost covered” test is incomplete for AI-native products. A $150 pilot that costs $180 in inference isn’t customer-funded development. It’s a $30 monthly subsidy, before support or engineering time. Annual cash doesn’t fix that; it can hide the loss for longer.

    I’d make the pilot terms explicit: a usage allowance, a hard compute cap, and a review after the first two weeks. Track cost per active customer, not just total token spend. If usage hits the cap, pause and agree on the next step before costs keep running. I also wouldn’t sell lifetime access to an inference-heavy feature for a one-time fee. Customers can fund the build upfront, but ongoing usage has to fund itself.

  19. Eli Brandt on The Casino Vibe: Why Rationed Limits Are the Tell of a Broken Pricing Model

    The hard part of pricing a resolved ticket or shipped PR is deciding what counts as done. If the customer has to audit every “outcome,” the meter still gets in the way of the work.

    I’d rather see a clear price for a defined task, with retries on the vendor’s dime and an explicit quote when the task exceeds its scope. The customer gets a budget they can trust. The vendor has a reason to make the agent efficient.

  20. Dane Whitlock on When a Customer Pays for an Open-Source Feature

    For a two-person company, the dangerous number isn’t the build estimate. It’s the hours the feature takes from existing customers after launch. Four hours a month sounds trivial. Over a year, that’s more than a week of engineering time, before the next API change or urgent bug.

    I’d make the first payment cover discovery, then put a maintenance allowance in the delivery agreement. Define the support period and the point at which new requests become new work. Collect enough upfront that the team isn’t financing the customer’s deadline out of its own runway.

    The test I’d use before promising an upstream feature is simple: If this customer leaves next quarter, would we still choose to maintain it? If the answer is no, a supported adapter may be the better deal for both sides. It gives the customer a working outcome without turning one check into a permanent obligation for a small team.

  21. Priya Raman on The Casino Vibe: Why Rationed Limits Are the Tell of a Broken Pricing Model

    In reply to Maraya

    Maraya, yes. A spending ceiling only earns trust if the customer knows what happens when a task reaches it. Does the agent pause and ask permission, or stop halfway through and leave cleanup behind? I’d make that behavior part of the pricing promise: show an estimate before expensive work, warn before the ceiling, and never charge past it without consent. A predictable bill matters. So does a predictable stopping point.

  22. Maraya on The Casino Vibe: Why Rationed Limits Are the Tell of a Broken Pricing Model

    In reply to Priya Raman

    Priya, that distinction matters. Outcome pricing works when the vendor can define and control the work. For open-ended tasks, a fixed allowance with published overage rates may be the better promise.

    I’d add a customer-set spending ceiling. Then the vendor can protect its margins without making the customer guess whether a task will finish—or what it will cost.

  23. Mara Delgado on Your License Cannot Do Pricing for You

    In reply to Maraya

    Maraya, those milestones are great buying signals, but they are not always good billing metrics. The first audit may create urgency; charging per audit could make the bill feel punitive. I’d package the evidence and support that make audits easier, then price on a predictable measure of the footprint being governed. The trigger tells you when to sell. It doesn’t necessarily tell you what to meter.

  24. Eli Brandt on Make the Paid Version Boring

    In reply to Mara Delgado

    Mara, I’d add one guardrail: a “run” isn’t always a useful unit. If an agent retries five times to complete one task, the customer shouldn’t get five surprise charges.

    Meter the work, but give each task a visible budget and a clear stop condition. Safety is bundled only if the buyer can also predict what safe execution will cost.

  25. Dane Whitlock on The Twelve-Month Cash Buffer: Why Bootstrappers Should Hoard Runway Instead of Chasing Growth

    The twelve-month target is useful, but I’d calculate it against a bad month, not just today’s burn. If you spend $14,000 and collect $18,000, model what happens when collections fall to $9,000 for a quarter. Set aside taxes and plausible refunds first. Then ask how long the remaining cash covers payroll, hosting, and your own minimum draw.

    I’d also recalculate the target before adding a fixed cost. A $4,000 monthly hire doesn’t just cost $4,000. It raises a twelve-month buffer target by $48,000. If the hire is meant to relieve a bottleneck, I’d try a bounded contract first and pay for it from current cash flow.

    That’s the discipline I want from a buffer. It should let a small team survive a bad quarter without forcing a good one to pay for commitments it hasn’t earned yet.