KorvaJoin the waitlist
Startups

How Support Workers Started Fixing Software the Same Day

Ramp let customer service staff change code directly, collapsing a months-long ticket queue into same-day repairs.

AI image
Y Combinator · How To Build The Future: Eric Glyman, Co-CEO of Ramp

At Ramp, the people fixing the software are often not engineers. In the second quarter, non-engineers created 7,000 proposed code changes, up from practically zero two years earlier.

Most of those changes came from the customer experience team, said Eric Glyman, co-CEO of Ramp, a corporate card and expense company. Internal AI tools let support staff propose software changes directly, instead of asking engineering for help.

To see why that matters, consider the old path for a bug. A customer reported a problem, and support sent a polite reply and hoped that would be enough.

If enough complaints arrived, someone wrote a user story and tried to persuade a product manager that it was worth doing. Then the request waited for prioritization, a designer, and an engineer, a process that could take about two months.

More often, Glyman said, the report landed in a bug database and was marked P3, meaning won't fix. In practice, the issue was set aside and never addressed.

The new path collapses those steps. A support worker talking to a frustrated customer can help make a fix that is done that same day, a shift Glyman compared to Toyota's Kaizen system in the 1980s, where factory workers could improve their own process on the line.

When a fix costs minutes instead of months, expectations rise. Colleagues stop accepting next Monday when today is possible.

Ramp felt the speedup in its release pace. The company, which used to ship just a couple of big updates annually, shipped a major release in each of the last five months, with faster growth and higher sales quotas to match.

Questions people ask

What is a pull request?

It is a proposed change to software code, submitted for review before it becomes part of the live product. An engineer usually checks that it works and does not break anything else, then approves it. At Ramp, AI tools help draft those proposals so non-engineers can start them.

What does P3 won't fix mean?

Software teams rank bugs by priority, with P1 as the most urgent and P3 as low priority. A P3 bug affects relatively few users or has a workaround, so it is often postponed indefinitely. Over time, those tickets accumulate into a backlog that rarely gets cleared.

What was Kaizen at Toyota?

Kaizen means continuous improvement, and Toyota used it to let factory workers suggest and make small process changes. The idea was that the person closest to the problem often sees the best fix. Glyman argues the same logic applies when support staff can fix the software they support.

More in Startups