Thinking from David and the team on building systems that last.
David Cordover · Seats and usage are just two ways to count what customers pay for. With AI doing more of the work, decide what you're selling first, then choose the unit.
Read the article: Per-seat vs. usage-based is the wrong question.David Cordover · “Per seat, billed annually” says how a price is counted and collected, not what the customer buys. A pricing framework: the seven things customers pay for.
Read the article: Seven things a customer can pay for.David Cordover · Inspections, the defect queue, reseal planning and claim defence packs, all driven by the council's own Road Management Plan. Click through the working mockup yourself.
Read the article: We built a council road management platform.David Cordover · Hundreds of emails a day and an empty inbox by the end of it. The method is simple: touch each email once, check at set times, and let Gmail do the sorting.
Read the article: Dealing with emails.David Cordover · Pet registration lived in the core system and permits lived in a spreadsheet. We fixed it with a working, click-through mockup built in about an hour.
Read the article: We built a council pet registration system in one hour.David Cordover · A 0.1% chance at $1B, or a 90% chance at $1M? Maybe the right question isn't how big you could build, but how much you actually need.
Read the article: Do you want a billion, or a million?Businesses doing $5–50M in revenue, and especially those around $15M.
You already have a working model, and you're running it, not testing it. Owners who've been through a custom software build before and know the real cost isn't the build.