The category keeps changing. The bar doesn't.
Since 2004, Vinove has applied one test to every technology decision. The language changes. The categories shift. The question doesn't.
The three questions
Does it work where it counts?
Not in the demo environment. In production, six months later, under real load.
Does it hold up after the launch noise fades?
The 90-day test is easy. The 18-month test is where most technology fails.
Is someone still depending on it a year later?
Dependency is the only metric that matters. It cannot be faked.
Custom software when software-as-a-service was still a bet. The discipline of building what customers actually used, not what looked impressive in a proposal. The standard was the same then: does anyone actually use it?
The companies that built software people depended on in this era are still operating. Vinove's companies from this period - built on the same standard - are still running. That is not a coincidence.
Digital growth, workforce tools, billing infrastructure. Each company built around a specific problem, not a broad category claim. The standard held through all of it.
Workstatus and Invoicera were built in this era. Both are still operational. Both have customers who have depended on them for years. When someone asks for proof that the standard works, those two companies are the answer.
AI and what comes next. The language changes every few years. The question hasn't changed once: does it work where it counts?
AI compresses the timeline between shipping impressive things and discovering they don't work. The standard becomes more important, not less. Vinove applies the same three questions: does it work? does it hold up? is someone still depending on it? The technology changes the speed of the cycle. It does not change the cycle.
Four things the standard produces.
-
Ships to real customers, not demos.
A demo only proves that a thing is possible under controlled conditions. Production proves that people trust it with actual work. Most software failure is not a technical failure. It is the gap between what worked in the rehearsal and what anyone will actually use.
-
Survives the launch quarter.
The press cycle measures announcements. The 18-month cycle measures whether the announcement mattered. Software that was celebrated at launch and abandoned by the following year is not a success with a short tail. It is a failure that took time to confirm. The standard requires the 18-month question to be asked before the first line is written.
-
Gets adopted, not just deployed.
Installed software that nobody uses is not a product. It is an obligation. The distinction matters because deployed software generates support costs, compliance requirements, and eventual migration work without generating the value it was supposed to create. Adoption, people building habits around something, is the only signal worth measuring.
-
Earns dependency.
The highest bar: someone's operations depend on it. A billing system that a business cannot run without. A workforce tool that a team has built their day around. Not preferred. Not recommended. Depended upon. The distance between those states is the distance between optional software and infrastructure. Everything Vinove builds is aimed at the second state.
Twenty-one years of applying the same test.
Across five companies, four technology cycles, and thousands of projects. The standard that determines whether any of it was worth building has not changed once.
Build technology that works where it counts, holds up after the launch noise fades, and earns dependency.
This is the operating standard. Not a mission statement. Not an aspiration.
The test applied to every decision since the first company was founded.