Builder's brief: the upgrade problem never retired 2016: Nextworld begins 2026: the CTO takes on agentic development Builder's brief: the upgrade problem never retired 2016: Nextworld begins 2026: the CTO takes on agentic development

People / Enterprise software

Vito Solimene Built a Career Around What Happens Next

He spent decades inside the machinery of enterprise software. Then he helped start Nextworld to change the one habit the industry never quite shook: making every useful customization a future liability.

Enterprise software has a long memory and a mischievous sense of timing. The customization that saves a department on Tuesday can return three years later wearing an upgrade invoice. Vito Solimene has spent more than three decades working inside that contradiction. He helped build the tools that let companies shape software around their work. Then he watched the industry discover, repeatedly and at considerable expense, that shaped software can harden around a company like plaster.

His career runs through the institutions that defined modern business software: J.D. Edwards, PeopleSoft, Oracle, and now Nextworld, the Colorado company he co-founded in 2016. The names changed. The underlying argument did not. Businesses need software particular enough to reflect how they actually operate, yet durable enough to accept the next release without an archaeological excavation.

Solimene's answer is architecture, a word with all the glamour of municipal drainage and much the same importance. At Nextworld he leads platform architecture, front-end development, and AI. The combination is revealing. What users see, what developers build, and what intelligent systems automate are not separate curiosities. They are rooms in the same house, and somebody eventually has to inspect the wiring.

3Software patents held
2016Nextworld founded
3+Decades in enterprise software

The education of a toolmaker

Solimene studied computer science at Rutgers College from 1986 to 1990. His professional education continued at J.D. Edwards, where he became instrumental in the design and architecture of the application development toolset. This was software for making software, the backstage machinery used to turn business rules into working applications. It placed him close to a basic truth of enterprise computing: flexibility is not an optional flourish. Every warehouse, payroll office, distributor, and manufacturer has an exception that somebody considers absolutely essential.

A patent application he filed with Robert Provencal in 1996 offers an early glimpse of his instincts. The invention concerned configurable controls in a graphical user interface: a persistent shortcut, context-sensitive menus, and tools that let users determine how commands appeared. The vocabulary belongs to desktop computing of the 1990s. The idea behind it feels current: expose power without demanding that the user memorize the machine.

He rose to vice president of engineering and head of application development at J.D. Edwards. Then corporate history began moving around him. PeopleSoft acquired J.D. Edwards in 2003. Oracle acquired PeopleSoft soon after. Solimene continued leading application development through both transitions and ultimately held leadership roles at Oracle, where his later responsibilities included the Core HR application development team.

Designs and architects application development tools at J.D. Edwards.

A configurable graphical-interface patent is granted.

Leads through the PeopleSoft and Oracle acquisitions.

Co-founds Nextworld with a group of enterprise software veterans.

Writes publicly about production AI, platforms, and agentic development.

There is a temptation to tell acquisition stories as tales of clean succession: one logo disappears, another arrives, everyone receives a new lanyard. Engineers experience them differently. Products have customers, integrations, undocumented habits, and release promises. Solimene's route through two acquisitions gave him a long view of what persists when ownership changes. Code survives. Customer expectations survive. Technical debt, that faithful old employee, reports for work under the new management.

Vito Solimene seated at right in conversation with a colleague in a Nextworld company photograph
The builder in conversation: Solimene, at right, in Nextworld company photography. Enterprise architecture is a team sport, although the whiteboard occasionally demands extra time.

A new company for an old grievance

Nextworld began in Colorado in 2016 with Ed McVaney, the co-founder of J.D. Edwards, and a group of veterans that included Solimene, Kylee McVaney, Axel Allgeier, and Konrad Rogers. Their grievance was specific. Enterprise vendors had made customization necessary and upgrades punishing. Companies either bent their processes around rigid software or modified the software until the next major release became an ordeal.

The new company put a platform beneath its applications and treated customization as something that should remain separate from the core. Metadata, APIs, no-code tooling, workflow automation, and a shared data model are not cocktail-party material. Together, however, they aim at a very human outcome: the people who understand an operation can improve it without condemning their successors to years of repair.

“We designed the Nextworld EAP so that our customers could focus digital modernization efforts on the most meaningful and high-impact business initiatives.”Vito Solimene

Solimene has written that a platform is more than a framework. A framework provides components and conventions; a platform takes responsibility for more of the finished system's life, including security, data, deployment, monitoring, and upgrades. The distinction sounds technical because it is technical. It is also commercial. Every responsibility the platform truly owns is one less obligation quietly handed to the customer.

In February 2025, Nextworld announced a $65 million Series F round led by the McVaney Investment Partnership. The funding was earmarked for product development and global expansion. Money is not proof of architecture, of course. It is permission to test the architecture at a larger scale, where elegant diagrams encounter busy warehouses, unfamiliar processes, and the cherished spreadsheet maintained by a person named Linda who is on holiday.

AI, after the applause

Artificial intelligence has brought the customization question back with fresh urgency. If software can be produced from a prompt, then more software will be produced. The speed is seductive. The bill for unmanaged speed arrives later, when generated code must be secured, tested, integrated, monitored, explained, and changed.

Solimene's recent writing distinguishes agentic development from “vibe coding,” the casual practice of prompting until an application appears to work. His concern is not aesthetic. Enterprise applications touch permissions, financial records, inventory, employees, and customers. A plausible screen is not the same thing as a dependable system. He argues for specifications and guardrails, with agents operating inside a platform that already understands data models, logic, security, testing, and deployment.

“We're not chasing hype. We're solving the hard problems: modernization without disruption, AI that actually does something useful, and architecture that doesn't punish you for customizing it.”Vito Solimene, 2026

That quote contains the mature engineer's allergy to a demo that refuses to discuss Tuesday morning. When Nextworld released expanded AI features in 2025, Solimene described the goal as putting intelligence in the hands of the people doing the work. The useful phrase is “doing the work.” It moves AI away from theatre and into a process with a deadline, an exception queue, and somebody accountable for the result.

In March 2026, he opened Nextworld's technical blog with an invitation to argue through hard problems. The proposed subjects included architecture tradeoffs, legacy integrations, AI, production refactors, and assumptions that proved wrong. It was an unusually honest editorial menu. Software companies happily publish victories. Postmortems about a belief that failed tend to remain in the family.

The founder who would rather build

Nextworld's biography of Solimene says he prefers building to talking about building. His public record supports the description: there is more architecture than autobiography. The available personal notes are concise. He is a family man with a wife and two sons. He plays golf and tennis and has pursued CrossFit and weightlifting. These are activities with scorecards, repetitions, and visible form. One suspects that vague progress holds limited charm.

He also emphasizes teams. The point matters because platforms are institutional products. No single architect can anticipate every business process, security boundary, integration failure, or strange Tuesday. Solimene's career has been spent building abstractions, but his language keeps returning to the people who build and use them. A platform succeeds when other people can do consequential work without requiring its original designers to hover nearby.

That belief also explains the company he keeps. Nextworld reunited figures whose histories overlap at J.D. Edwards: Ed and Kylee McVaney, product leader Axel Allgeier, and operations chief Konrad Rogers. In a recorded founder conversation, Solimene, Kylee McVaney, and Rogers revisited the culture around J.D. Edwards and Ed McVaney's influence. It was less a nostalgia tour than a reminder that enterprise products inherit habits from the organizations that make them. Architecture can separate custom work from a core release. Culture determines whether a team bothers to protect that separation when schedules tighten.

Outside work, the available sketch is pleasingly kinetic. Golf and tennis reward placement and patience; CrossFit and weightlifting are more candid about the number on the bar. Solimene's professional concerns share that preference for visible tests. Can a customization survive an upgrade? Can an agent work within permissions? Can a platform carry an application from first prompt to production? The answers are measurable, which is convenient, because enterprise software has enjoyed quite enough adjectives.

The neatest summary of his career may be hidden in the distance between that 1990s interface patent and today's AI agents. The technology changed from menus to models. The design problem barely moved. How do you give a person more power without requiring them to carry all the complexity? How do you make a shortcut configurable without making the entire system fragile? How do you let the next builder begin from solid ground?

Enterprise software will never be finished. Businesses change, regulations change, markets change, and somebody will always discover a process that the original specification omitted. Solimene is not trying to end that restlessness. His work is a wager that change can stop behaving like punishment. After three decades inside the machinery, he is still building for what happens next.