LATEST / 2026
10 SEPT · VARTEQ sponsors four $2,500 cybersecurity scholarships through ISACA Foundation16 OCT · New engineering article examines fintech integration failures

Company / The continuity business

VARTEQ and the art of keeping software alive

Schools, genetic labs and payment platforms cannot pause for a rewrite. VARTEQ builds its business in the complicated space between what works today and what must work tomorrow.

Advertisement

Consider the school gradebook. It looks like a table: names down one side, numbers across the top. Yet behind it sit attendance records, class schedules, family permissions and reports a district must submit. Changing that table can mean changing a small institution’s nervous system. The interesting question is who understands all the connections well enough to touch it.

The useful bits
  • VARTEQ builds and repairs software for organizations with complicated workflows.
  • Its published work includes Follett, GeneDx, NORTH and Avatria.
  • Clients can buy a project, a managed team or additional engineers.

VARTEQ occupies this territory. Its service menu includes application development, testing, integrations, cloud modernization and AI. Plenty of engineering firms offer those things. The more revealing detail is how much of its work begins with software that already has users, dependencies and a history. A clean sheet of paper would be easier. These customers have a school day to finish.

A gradebook has a long memory

According to VARTEQ’s Follett case study, the relationship began with work to improve quality assurance, testing and continuous integration within a broader delivery team. Follett later retained VARTEQ as the sole contractor for that engagement. The firm describes continuous development and testing since 2014, spanning desktop and mobile software.

Its contributions cover school data features, integrations and education content tools. Aspen, Follett’s student information system, brings together work ranging from grades and attendance to health information and family access. Different people need different views of the same records. The product has to remember those distinctions every time someone adds a feature.

The implication for a buyer is straightforward: experience inside a system accumulates. An engineer who understands why a reporting rule exists can ask better questions about changing it. That makes continuity a practical purchasing criterion. Ask who knows the product, how knowledge survives handovers and what happens when the original team moves on.

VARTEQ team members working at desks in a shared office
A forest of monitors. Somewhere behind each screen, a business rule has an opinion. VARTEQ’s team at work. Photo: VARTEQ

The work between the breakthroughs

The same pattern appears in healthcare. VARTEQ says its GeneDx work began in 2018, supporting test ordering, billing, insurance, genetic counseling and results reporting. Engineers also contributed Python components to an AI module for inherited-disease data analysis. This is a contribution to a larger platform, with client-defined security and HIPAA requirements.

A genetic test needs an operational route from the medical practice to the laboratory and back. Someone must connect the scientific work to the people requesting it, paying for it and receiving the results. VARTEQ’s expertise includes those interfaces: backend services, application features and the exchange of sensitive information between different users.

Education offers a more visible example. VARTEQ built Prosvita in 2020 as classrooms closed. The platform combines lesson links, homework, attendance, gradebooks and mobile communication. Its case study reports more than 200,000 users. Public schools use it free; private institutions pay an annual subscription. That distinction belongs to Prosvita’s model, separate from buying VARTEQ’s engineering services.

Commerce adds another variation. For Avatria, VARTEQ built Cognito, an analytics system that gathers commerce data and trains machine learning models for product ranking and sales optimization. Here the engineering links customer behavior to merchandising decisions. It broadens the picture of the firm: industry knowledge matters, but the recurring job is connecting information to a usable business workflow.

Hours disappear in the plumbing

NORTH’s merchant platform provides a concrete before-and-after. VARTEQ describes fragmented deployment processes, aging runtimes and partner integrations that had to tolerate unavailable external systems. The team migrated more than ten repositories to GitHub Actions and upgraded more than fourteen microservices to Node.js 22 while continuing feature development.

Partner notifications became event driven, with delivery histories and failure monitoring. Each partner was processed independently, preventing one unavailable endpoint from delaying the others. VARTEQ reports notifications arriving in seconds rather than hours. The lesson is useful beyond payments: one slow recipient should have a contained consequence.

The staircase that needed a plan

One of VARTEQ’s more candid engineering articles concerns a Unity prototype inspired by staircase movement in God of War and Hogwarts Legacy. The experiment compared reactive AI prompting with a more structured approach. The first attempt generated code, then stumbled over malformed Unity metadata. Subsequent patches introduced conflicting behavior. After roughly fifteen iterations, the developer abandoned that approach.

The restart began with architecture analysis, a design and phased implementation. Review replaced the endless request to fix the latest symptom. The reported result was a functional, debuggable prototype with remaining rough edges. Readers can copy the sequence: understand the system, define the intended behavior, then inspect each phase. Without someone able to judge the architecture, the sequence loses its value.

Buy responsibility, then count engineers

VARTEQ offers three arrangements. With staff augmentation, the customer manages delivery. With a dedicated team, the customer sets priorities while VARTEQ runs the team. With an end-to-end project, VARTEQ takes responsibility for an agreed scope through release and support. Choosing between them starts with how much management capacity the buyer actually has.

There is a useful price reference in DNA325 founder Julia Koinak’s Clutch review: a $50,000-$199,999 ERP/CRM engagement. She describes six to ten assigned people and a working product in under six months after detailed requirements work. She reports staying within the original budget. That is one customer’s experience, with a defined scope.

“They have been providing timely and high-quality technical support for our internal products and websites.”

Julia Koinak, founder of DNA325 · Clutch, May 2023

The fit is clearest when an organization needs custom workflows and has people available to explain them. A standard product may serve a standard process more economically. Outsourcing also requires a client who can set priorities and accept work. More engineers cannot settle a business decision nobody owns.

The company’s stated working principles emphasize direct communication, clear ownership and learning through project work. Its careers page describes distributed teams serving international clients. For a customer, those promises become useful when translated into routines: a named person making decisions, a reviewable increment of software and a clear account of what needs attention next. That is also where a prospective buyer can compare suppliers. Ask to see the process working on a problem similar to yours, with the engineers who would do the job.

VARTEQ’s current ambitions include supporting the next group of engineers: in September 2026 it announced four $2,500 scholarships through the ISACA Foundation for students in Ukraine and Illinois. Its commercial proposition remains closer to the gradebook. Understand the connections. Make a change. Keep the day moving.