V2Soft and the art of keeping what works

At a regional insurer described in a Sanciti AI case study, changing billing meant testing the whole system. Policy administration, claims and billing shared a deployment unit. An infrastructure upgrade required coordinated downtime. The software could perform its duties; improving one part meant disturbing the others. That is a peculiar kind of success: a system becomes so central to the business that changing it becomes a business problem.

V2Soft, the Michigan company behind Sanciti AI, works in this territory. Its proposition starts with a question that sounds almost impolite in an industry devoted to the next thing: what should survive? Old applications contain accumulated decisions about how a company operates. Replacing their technology while preserving those decisions requires a good deal of detective work.

02An apartment, then a million users

Founder and CEO Varchasvi Shankar dates V2Soft’s incorporation to March 13, 1998. In a twenty-fifth-anniversary reflection, he recalled starting in a small apartment in Southfield, Michigan. The company grew into an international provider of application development, testing, consulting and technical staffing. These are practical businesses: clients need a working application, additional engineers, or someone accountable for keeping systems running.

One concrete example arrived through Blue Cross Blue Shield of Michigan. V2Soft began partnering on its member portal in 2012. A March 2017 announcement said the portal served more than one million active users and recognized V2Soft’s contribution to the mobile application with a Team Project Award. Here, “digital transformation” meant members managing healthcare online and on their phones.

That relationship also helps locate V2Soft in the market. Its customers include large organizations with obligations that outlive any particular technology fashion. Healthcare, automotive, manufacturing, financial services, government and energy recur across its materials. A glossy interface is useful. Reliable integration with the machinery behind it is where much of the work sits.

03Read the old code before writing the new

Sanciti AI turns that experience into a software platform. Its requirements agent, RGEN, reads existing code and other material to reconstruct requirements. CodeGen produces implementation artifacts. TestAI builds validation tests. Deployment and production-support capabilities carry the process beyond development. LEGMOD coordinates modernization work, including dependency analysis and planning changes in stages.

Consider the financial-services data-pipeline example published in May 2026. The customer’s transformation logic lived inside proprietary ETL tooling, with rising license costs and limited scalability. Documentation depended on people remembering how things worked. Manual tests sampled outputs rather than checking every path. The weak point was the organization’s ability to explain and verify its own data processing.

Sanciti’s account describes extracting transformation rules and data lineage, generating cloud-native pipelines, and comparing their outputs with the old system’s results. It reports more than 90 percent parity-validation coverage and modernization cost 50 percent below a manual-rewrite estimate. These are vendor-reported project results, with a specific comparison baseline. They should be read that way.

04The handoff is part of the product

Return to the insurer. RGEN mapped dependencies between policy, claims and billing. CodeGen generated separate cloud-ready services. TestAI targeted functional, regression and cross-module behavior. Sanciti reports that the three domains could then deploy independently, with more than 90 percent automated test coverage at first delivery. The practical gain was freedom to change billing without moving the entire institution.

A manufacturing case study makes a related point. Disconnected requirements, development and testing tools were losing context at each handoff. Adding engineers increased coordination work. Sanciti describes a shared pipeline connecting requirements to code and tests, with human review gates. Its reported 60 percent reduction in lifecycle effort belongs to that engagement, rather than a universal forecast.

This is V2Soft’s competitive pitch: engineering services alongside a platform that carries context through delivery. Buyers can also choose large systems integrators, specialist modernization firms, internal teams, and development tools such as GitHub Copilot. Those alternatives overlap with different parts of the job. The useful comparison is the workflow a buyer actually needs covered, including integration, evidence and continuing support.

05People remain in the business model

V2Soft still sells workforce solutions, managed applications, managed testing and offshore or nearshore delivery. Its business combines technical services and staffing with the Sanciti software offering. A customer can need temporary engineering capacity, an outsourced delivery team, or ongoing operational responsibility. That breadth makes the company relevant beyond teams shopping for an AI coding tool.

For an IT leader, the contract should specify who supplies people, owns delivery and supports the software after launch.

The cultural signals fit that service business. V2Soft lists integrity, honesty, loyalty, transparency, flexibility and excellence as core values. Its public materials describe a customer-first approach and a commitment to workplace diversity. Blue Cross recognized it again with a Supplier Partner Award in 2022. Relationships and repeat delivery provide a more concrete lens on that culture than the values list alone.

Procurement has its own vocabulary of reassurance. V2Soft announced completion of TISAX Assessment Level 3 in January 2026, relevant to information-security expectations in automotive supply chains. In May it reported an EcoVadis Gold medal, with its score rising from 75 to 85. These credentials address different concerns; neither substitutes for checking the proposed team, scope and delivery controls.

“It’s a passion of mine to solve real world problems with technology solutions.”

Varchasvi Shankar · Downtown Publications, 2020

06A smaller experiment beats a bigger promise

The most transferable lesson is procedural. Before a rewrite, identify the business rules that must remain true. Map dependencies. Choose one bounded service or data pipeline. Compare old and new outputs. Keep people responsible for approving behavior. V2Soft’s examples make this sequence visible, which is useful even to a reader who never buys its services.

For a buyer, cost should be evaluated against the same bounded scope. A saving measured against an estimated manual rewrite is different from cash returned against an actual prior budget. Ask a pilot to expose integration work, review effort and ongoing operating costs. Define acceptance criteria before measuring acceleration. Otherwise, an impressive percentage can answer a different question from the one procurement asked.

The fit is strongest where a valuable existing system needs careful change. For a small new application with little accumulated complexity, the same governance machinery may be unnecessary. And where nobody can decide which historical behavior is correct, generating more code will not settle the disagreement. V2Soft’s interesting bet is that understanding the software already running a business can be the first useful act of building its replacement.