> ## Content Index
> Fetch the complete content index at: https://www.kaitlinquinn.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# White Glove Service or Paywalled Progress?
- URL: https://www.kaitlinquinn.com/blog/white-glove-service-or-paywalled-progress/
- Published: 2026-11-03T02:08:23.000Z
- Updated: 2026-11-03T02:08:23.000Z
- Description: TL;DR: We’re told profit drives innovation. But what happens when the next advance would make us less profitable to serve? White glove service promises to carry us forward. I’m questioning whether we’re paying to move, or paying to remain dependent.
- Author: Kaitlin Quinn

I needed to send a contract.

That was the task. Somewhere between opening the document and getting it back signed, I found myself comparing software subscriptions, looking for free alternatives, and learning which ordinary functions had been separated into which paid plans. I had work to do. Now I had preliminary work to do so I could do the work.

Inside a corporation, someone has already selected the applications and purchased the licenses. You might have to argue for another tool. Mostly, you work within what is there. As an entrepreneur, the purchasing questions become mine. So does the time spent answering them.

Adobe’s free Reader can view, fill, and sign PDFs. Editing the existing contents requires its paid software. Finding out which visible features I can actually use becomes part of completing the task. Then I start comparing alternatives. Before I have exchanged a document with another person, I am evaluating a small portion of the software economy.

That search brought me toward projects such as ArtCraft, which is developing free, open-source tools for familiar creative and document workflows. Many are still early builds. What interested me was the choice to make those capabilities available under a different arrangement. The function I needed and the business model I had encountered were separable.

I kept thinking about how much time people spend discovering that distinction for themselves. Then I thought about every other company waiting for a little piece of the same day.

I used to work at Disneyland. I remember managers and executives walking around in white Mickey Mouse gloves, interacting with guests. There was a literal version of the promise: white glove service. The details would be handled. Someone was paying attention. You could trust the experience.

I hear that promise in technology, too. We will guide you through this. We will take care of the complexity. We will get you to the next step. After years working inside the machinery, I have become interested in that next step. Who decided where it ends? How many more people will I have to pay before I reach the thing I originally needed?

The gloves are a reassuring place to look. They can also keep our attention on how pleasantly we are being escorted through a process whose construction deserves a much less pleasant conversation.

I have worked in product management. The question of how to profit from something can arrive well before the product does. We discuss what belongs in the base offering, what could become an upgrade, and which part of the customer’s work might support another service. By the time someone encounters the helpful little invitation on their screen, the commercial decision may be old news.

I have watched novel ideas get passed over when the opportunity to productize them was less apparent. I have also watched the process around a problem become something else to sell. There is an extraordinary amount of creativity available for finding another transaction between a person and the outcome they need.

What could we do with that creativity if getting them through it were enough?

People deserve to be paid for skilled work. I want to pay people well myself. The question that bothers me is what we are paying the business to preserve. A company can earn money by removing a difficulty. It can also earn money by becoming very good at accompanying us through it, indefinitely. From outside, both can look like help.

We have built a way of doing business in which making something easier can become another reason to charge more. The benefit of innovation arrives at the company as a new revenue opportunity before it arrives at the person as relief.

We have learned to recognize this strange kind of advancement elsewhere. I spent years receiving raises around 3%. A raise is presented as progress. If the cost of maintaining your life rises by the same amount, the larger number has bought you the ability to remain where you were. You are supposed to experience the increase as recognition while continuing to figure out why you have so little room.

That is the feeling I am trying to put my finger on. Something has improved in the account we are given. Our actual ability to live or work has barely moved. Meanwhile, someone can point to the improvement as evidence that the arrangement is serving us.

Scale that across the companies a person depends on. Each has its own explanation for the price, the restriction, the extra step. The person has to live with all of them together. They become the unpaid administrator of everyone else’s carefully managed offering.

We describe these as consumer choices, as though everyone has enough money and time to shop their way out of the difficulty. Someone already struggling to afford their life has to absorb the charge or find the workaround. Either way, the cost reaches them. A company can make that cost small enough to defend in isolation while a person spends their day trying to survive the total.

Having worked inside these companies, I know how much of the machinery is people applying knowledge and coordinating work. Building an alternative can require a skilled team and considerable resources. It still changes your perspective to understand how something works, especially when the presentation around it has made the capability feel much further out of reach.

Once you have seen that from the inside, it becomes harder to accept every obstacle as a technical necessity. Some of what we experience as complexity is a decision about what we are allowed to access, understand, or do for ourselves. This becomes difficult for me to sit with in public safety.

I am building the Groundtruth 911 Validation Workbench to help practitioners examine the geographic data behind Next Generation 911, or NG9-1-1\. Roads, address points, and service boundaries are part of the infrastructure that helps a call reach the right place and helps responders find the person who needs them.

The person maintaining that data needs to see what is wrong, understand why it matters, and have a useful way to work through it. I believe tools that support that understanding should have been ordinary in our field years ago. I am building with a deliberately lightweight technical approach because I want the machinery to take up less of the practitioner’s day.

The National 911 Program describes NG9-1-1 technology as available and explains that implementation requires coordination across public safety and government. Its work on geographic information systems, or GIS, identifies staffing, data development and maintenance, and funding as major challenges. [www.911.gov](https://www.911.gov/issues/ng911/?utm%5Fsource=chatgpt.com) Those are substantial obligations. They are also reasons to make the available expertise easier to use and carry forward.

The practitioners I know are already working hard. Many are trying to maintain essential infrastructure with too little time and too few resources. When every piece of assistance comes through another separately priced relationship, the person responsible for the whole job is still responsible for making all those pieces add up.

I want them to get through the foundational work and have a maintenance plan they can actually carry out. I want to know what our field could accomplish once that becomes a dependable starting point.

Sometimes the scale of what I can currently offer feels like a bake sale. I have limited means, and I have managed to get one chocolate chip cookie onto the table. Everyone around me needs a cookie. I want to get it to them because I already have a brownie recipe in my head, and I am excited about the brownies.

I am also talking with people who know things I do not, sharing ideas about how to make the cookies better. After the brownies, there might be macarons. There might be a whole shop. The possibilities are why I want to keep working.

I could spend years finding ways to get more money out of the cookie. I keep wondering what happens to everything else while we do that. How much energy goes into defending the current offering and preserving the customer’s need to return? How much more could the customer accomplish if we helped them finish this part?

I want Groundtruth 911 to become a sustainable company. I want the work to support me and the people who contribute to it. There are already more useful things I want to build than I have the means to build. Helping someone move forward gives that work somewhere to go. Keeping them at the first step would make my own imagination smaller.

This is the part of innovation I wish we talked about more: what becomes possible for other people after they receive it. They have ideas, too. They have knowledge of their own communities and problems I have never encountered. Their capacity to build should be part of what our work produces.

I heard that capacity in the work people shared at the Oregon Public Health Association conference. I heard about funding, too. At a women-owned business listening session for the governor, I heard women describe the roadblocks they faced in getting their work supported. Those rooms made the distance between having something useful to contribute and having the resources to deliver it feel particularly wasteful.

We have people who want to do the work and people who need the work. Somewhere between them sits the requirement to make the work financially attractive on terms that may change what gets delivered.

What happens to progress when every solution has to become a business opportunity?

For me, that question eventually reaches the person calling 911\. They have no reason to know which part of the system belongs to which company. They cannot work around the missing integration or negotiate a better package. They need help, and every decision made before that moment is now part of whether they can reach it.

That is why public safety belongs in my public health studies. We cannot talk seriously about a healthy population while treating the ability to reach safety as someone else’s separate subject. The funding arrangement, the technical decision, and the person waiting for help belong in the same conversation.

I wrote [“For-Profit, Nonprofit, Anti-Profit”](https://www.kaitlinquinn.com/blog/for-profit-nonprofit-anti-profit/?utm%5Fsource=chatgpt.com) because I am trying to work out what a business owes the people whose lives its decisions reach. Building one has made that question more immediate. I have to choose what I charge for and what I make easier. I have to decide how much of the knowledge stays with me.

I want to be able to tell someone we have helped them get past a problem. I want that to mean they have somewhere else to go, with more capacity than they had before. They should get to be excited about what comes next, too.

White glove service asks us to trust the person guiding us. I think we should be able to examine where they are taking us, including whether they have a financial interest in keeping the journey going.

We are being asked to pay for progress. At some point, we should be able to arrive.