My business partner and I started our company seventeen years ago with $50 and an idea. We had no outside funding and no runway. We had a product we built ourselves, a hosting environment we set up ourselves, and a commitment to not spend money we didn’t have.
That constraint gave me the best discipline I’ve ever developed. When you can’t raise a round to cover bad decisions, you learn fast what actually counts.
Today that company processes hundreds of millions of dollars in transactions for thousands of customers. The habits that made it work (questioning every expense, measuring outcomes, and building lean operations that perform at scale) kept paying off when I joined public boards. If anything, they count for more now.
The discipline of spending someone else’s money carefully starts with treating it exactly like your own.
1. “We Have Always Done It That Way” Is Not a Budget Strategy
When I was appointed to the Griffin-Spalding Business Tourism Association, the local DMO responsible for spending hotel-motel tax revenue under Georgia state law, one of the first things I did was go through the existing technology and vendor contracts line by line.
What I found won’t surprise anyone who has audited an organization that hasn’t been seriously managed in years. Contracts hadn’t been renegotiated. Nobody had compared the services against current alternatives. Vendors were collecting monthly fees for work that either wasn’t needed anymore or could be done better for a fraction of the cost.
I identified over $40,000 in annual savings by cutting unnecessary contracts and migrating to a modern, managed hosting environment. Some of those contracts had been in place for years because the previous vendors were connected to a prior board member. The board had inherited them and never questioned them.
It’s a common pattern in public organizations. When the money comes from public tax revenue, it’s also unacceptable.
2. Public Boards Should Audit Technology Spending Like a Startup Would
A self-funded startup holds every vendor relationship up to one question: does this produce enough value to justify the cost? If the answer is no, the contract ends.
Public boards rarely work that way, because nobody personally loses money when the board wastes it. That’s exactly why the review has to be built into how the board operates. You can’t count on any one person’s habits.
A good technology audit for any public board should ask:
- What does each vendor or contract actually deliver each month?
- When was the contract last competitively reviewed?
- Is the pricing consistent with current market rates for comparable services?
- Are any services duplicated across multiple vendors?
- Is the board paying for capacity or capabilities it does not use?
Georgia’s procurement guidance for public entities supports competitive evaluation of vendor relationships [1]. The board doesn’t need to be hostile to existing vendors. It does need to be honest about whether each contract still earns its cost.
3. Lean IT Operations Don’t Mean Cutting Corners
Cheap and lean are different things. Cheap means buying the lowest-priced option no matter the quality or risk. Lean means getting rid of waste while keeping performance the same or making it better.
For public board IT, lean usually looks like this:
- Managed hosting over custom server administration. A modern managed hosting environment costs less, performs better, and takes less staff time than aging infrastructure kept up under a legacy contract.
- Software-as-a-service for standard functions. Email, document storage, meeting management, and public records tools all have modern cloud options that cost less and are easier to maintain than legacy installations.
- Performance-first website design. A government or DMO website that loads in under two seconds on a mobile device costs almost nothing extra to build, and it makes a big difference for public access. Slow websites lose visitors and waste part of every marketing dollar spent sending traffic to them.
- Annual contract reviews as standard board practice. Every year, as a line item on the board calendar. Don’t wait three years for someone to finally complain.
4. Speed and Cost Are Not in Conflict
One of the myths that hangs on in public sector IT is that better performance takes more spending. In my experience, it’s usually the other way around.
The GSBTA hosting migration that produced $40,000 in annual savings also improved site performance, added proper SSL certificate management, improved uptime, and cut the staff time needed to manage the environment. We spent less and got more.
Most small public boards can get that same result if they’re willing to do the audit work. The barrier is rarely technical. It’s usually political. Existing vendors have relationships, inertia is comfortable, and nobody wants to be the one who tells a longtime contractor their contract is ending.
Protecting a vendor relationship at the expense of public money is a failure of fiduciary duty.
5. What Startup Discipline Looks Like in a Board Room
Running a self-funded company for seventeen years means I’ve made every budget mistake personally. When a vendor wasn’t delivering, I felt it. When a hosting decision was wrong, I fixed it myself at 2 a.m. That ties the quality of your decisions very directly to how things turn out.
Public boards don’t have that direct feedback loop. A bad vendor contract just drains money in the background. Nobody gets a call at 2 a.m. So the discipline has to be on purpose.
At a board table, startup discipline looks like:
- asking for itemized invoices and reviewing them,
- making vendors justify a renewal instead of assuming it,
- comparing costs against publicly available market rates,
- and treating “that is how we have always done it” as a reason to look harder.
The public organizations that manage technology well almost always have at least one board member or staff leader who has had personal skin in the game running an efficient operation. If you have that experience, bring it to the table and use it.
6. The Bigger Point About Board Governance
Technology spending is one example. The same discipline works in any operational area a public board oversees.
I’m not saying government should run like a startup. Public accountability, procurement law, and open-records requirements all put limits on boards that private companies don’t face [1]. Those limits are legitimate and they exist for good reasons.
What I’m asking for is the same seriousness about outcomes, costs, and results that a founder who built something from nothing brings to every line of the P&L. You don’t need a startup background for that. You just have to decide that the public money in your care deserves the same scrutiny you’d give your own.
Frequently Asked Questions
Self-funded startups get in the habit of justifying every expense, measuring outcomes, and cutting anything that doesn't produce results. A public board can use those same habits when it reviews technology contracts and operational spending.
Yes. Many boards inherit outdated contracts with vendors who charge high monthly fees for low-value work. A structured review often turns up chances to consolidate and renegotiate, which cuts costs without giving up capability.
Keeping legacy contracts going because that's how it's always been done, without checking whether the work is still needed or whether there are better options at a lower cost.
References
- Georgia Municipal Association. (2023). Digital Infrastructure Procurement Guidelines for Local Officials. Georgia Municipal Association. https://www.gmanet.com/




