vinny Raises $2.1M Seed for RV Workflow Software

A manufacturer needs a dealer's permission to see some of the quality information vinny wants to organize. That small condition puts a large commercial assignment inside the Austin software company's expansion: persuade businesses handling the same RV to make their records useful to one another.

vinny announced a $2.1M Seed round led by York IE on November 10, 2026, bringing its total funding to $3M. The company builds inspection and documentation software for RV dealers, manufacturers and transport carriers. Its vehicle identification number, or VIN, supplies the stable reference as a unit passes through different organizations.

The capital will support wider deployments, partnerships, integrations, automation and reporting. For operators, the proposition is practical: preserve what someone discovered about an RV before that information has to be reconstructed by the person receiving it. For vertical software investors, vinny offers a close view of the work required to make a shared industry record possible.

A funding round built around repeated inspection work

York IE led the oversubscribed financing, with unnamed strategic and angel investors participating. York IE VP of Investments Matt Shapiro will join vinny's board alongside co-founders Trip Edwards and Rob Cochran. The announcement places expansion across dealer groups, manufacturer programs and carrier partnerships beside the product-development work, giving the money a distribution assignment as well as an engineering assignment.

vinny reports more than 10,000 inspections across over 5,300 RVs, with the number of documented units growing approximately 13-fold in 2026. Those are company-reported activity figures. They show repeated use of the inspection workflow; revenue, retention, contract values and the economics of each deployment were not disclosed in the announcement.

There is a useful distinction between an inspection and the vehicle it describes. The same RV can be examined at several points, by people answering different questions. Keeping those observations associated with the VIN gives a later team a starting point, while leaving room for its own inspection and judgment. That is the operating idea behind the expansion, and it gives dealer adoption a significance beyond adding another software login.

The product begins before the repair order

vinny's product documentation describes guided inspections that capture findings, photographs, video, notes, timestamps and signatures against a vehicle record. Workflows cover delivery acceptance, pre-delivery inspection, service, trade-ins and customer walkthroughs. Staff can work from phones or tablets while documenting the unit, rather than waiting to assemble the record afterward.

The distinction matters when software is being sold to somebody with an existing process. A technician has a finding to capture. A service writer needs usable documentation. Another organization may require a particular form. The information becomes more valuable when it survives those changes in responsibility without demanding that each person reconstruct what the previous person meant.

The company's FAQ makes the current integration boundary explicit: vinny generates structured repair-order export files, while native dealer management system integrations and automatically mapped manufacturer repair codes remain in development. It also states that manufacturers retain warranty coverage and approval decisions. Better documentation can support that decision without transferring authority to the software vendor.

For a buyer, those details belong in the implementation conversation. An export process still has to fit the way a service department works, and a clear inspection record still has to reach the right destination. The funding provides resources to improve those connections while dealers continue operating the systems they already have.

People carrying the dealership context into software

The current leadership page identifies Trip Edwards as co-founder and CEO, Rob Cochran as co-founder and CRO, John Washbourne as CTO, and Bobbie King as Head of Product. Edwards previously co-founded Attunely and worked at Pioneer Square Labs. Cochran's background includes RV parts and service businesses, while Washbourne brings software engineering and systems architecture experience.

The company's earlier launch announcement also named Keith Chilek in the founding team. That is part of vinny's origin, rather than evidence of a current operating title. Its official About page identifies New Stack Ventures and Market Square Ventures as backers, separately from the latest round's disclosed lead and unnamed participants.

The team's mix makes the product question more interesting than whether a paper form can be put on a screen. Field staff need to capture a finding while they are examining the vehicle. Office staff need enough structure to move the work onward. Product and engineering decisions have to respect both situations, including the time and attention available to the people doing them.

That creates a demanding sales conversation. The software has to make sense to the department using it today and to the businesses that may benefit from its information later. Dealership knowledge can help explain the problem, but each deployment still has to earn its place in the working day.

Dealer consent shapes the wider quality opportunity

vinny's manufacturer offering describes access to structured field information with participating dealer authorization and data controls. The company positions category and component trends as material for training, service bulletins and supplier follow-up. Factory-side applications remain an area of early conversations, rather than a basis for claiming broad production deployment.

The permission requirement has commercial weight. A dealer collecting the evidence and a manufacturer reviewing it may have different immediate priorities. Building a useful connection requires an agreement about who sees the record and why sharing it helps. The stable VIN can connect the information technically; cooperation determines how far that connection travels.

The financing also supports AI-related work, including natural-language reporting, repair-code mapping and computer vision research. Those plans should be read alongside the current product boundary. Structured inspection data gives the company material to work with, while the usefulness of any additional capability will depend on the quality of what staff capture and how it fits the next task.

For vinny, expansion now means more places where that agreement has to hold: a technician documenting a finding, a service writer preparing the next step, and a manufacturer receiving information the dealer has agreed to share. The RV keeps moving through the chain. The company is spending its new capital on making the record travel with it.