Advance Medical

WHEN SOFTWARE BUILT FOR TODAY HAS TO SUPPORT TOMORROW

August 2026 - Manufacturing / Insight


Building software has never been easier. Owning it is a different matter. We look at what happens when changing equipment, technology and expertise reshape the long-term software decision. See how this fits into your Lab Setup →


AI-assisted coding is changing software development. Tools that generate code from natural-language instructions are lowering the barrier to creating applications and internal tools. According to the 2025 Stack Overflow Developer Survey, 84% of respondents were using or planning to use AI tools in their development process. Yet adoption does not automatically translate into confidence: 46% said they distrust the accuracy of AI-generated output. For manufacturers, easier access to software development raises an interesting question. Why invest in a specialized platform when creating software internally is becoming faster and more accessible?

In the earlier years of the industry, many laboratories developed their own software because suitable alternatives simply did not exist. Some of those systems have since evolved over decades and remain closely aligned with the laboratories that created them. What is changing is the effort required to start building. What has not changed is what happens after the software has been built. It must communicate with equipment, manage critical data, adapt to changing requirements and remain maintainable as people and technologies change. The real comparison is therefore not simply development cost versus software licence. It is the long-term value and responsibility of software ownership.

FocalPoints Designer

Specialty lens design can quickly become a complex software undertaking.

DEVELOPMENT IS ONLY THE STARTING POINT

Internal development can offer significant advantages. It gives manufacturers control over their software and allows functionality to be built around specific processes, products and internal expertise. For some laboratories, that close fit is precisely what makes proprietary software so valuable.

But the initial application represents only part of the investment. Testing, infrastructure, documentation, security, integrations, training, maintenance and future compatibility become ongoing responsibilities. As a system evolves, technical debt can also increase the resources required to introduce new functionality or maintain existing code. Internal development creates an asset, but it also creates something that needs to be maintained and managed. In manufacturing, that responsibility becomes particularly important because software rarely operates in isolation.

84%
Planning to use AI development tools
72%
Vibe coding not used professionally
66%
Frustrated by AI answers
46%
Distrust AI-generated output

AI development is growing faster than confidence (2025 Developer Survey)

THE COST OF MAINTAINING CONNECTIONS

A specialty contact lens laboratory may need to connect ordering systems, lathes, inspection instruments, topographers, aberrometers, lasers, autoloaders, packaging processes and external business systems. Each integration needs to work reliably, but it also needs to keep working. Machines change. Operating systems evolve. Equipment manufacturers release updates. New instruments enter the production environment. Processes develop over time. An internally developed platform therefore requires more than the ability to create each connection. The laboratory also takes responsibility for maintaining the ecosystem around them. And this is where the question can begin to change.

WHEN THE ENVIRONMENT CHANGES

Proprietary software is not inherently inefficient or outdated. A well-developed internal system can fit a laboratory like a glove, reflecting its designs, equipment, terminology and manufacturing processes in ways that would be difficult for another platform to reproduce exactly. It may continue doing that successfully for decades. Its real test comes when the environment around it changes.

A laboratory may want to introduce equipment from another manufacturer. New measurement or optical technologies may need to exchange information with the design and manufacturing environment. Or the people who created and maintained the software may no longer be available. None of these situations means the original system has failed, simply the laboratory's requirements have changed. At that point, the ownership question becomes different. It becomes: “Do we want to continue owning the development required for where we want to go next?”

Turnkey Solution

As environments evolve, software must evolve with the equipment.

RESILIENCE ALSO DEPENDS ON PEOPLE

Long-term software resilience is not only technical. Internally developed software often contains knowledge accumulated over many years. The people who created it may understand not only the code, but why particular decisions were made, how exceptions are handled and how the software has evolved alongside the laboratory. When that knowledge is concentrated among one person or a small team, documentation, knowledge transfer, training and succession become part of software ownership. A production system needs to remain understandable even when the people who originally created it are no longer responsible for it.

THE OTHER SIDE OF THE DECISION

An established specialized platform is not automatically the better answer. Moving away from proprietary software has a real cost. Years of development may have created an environment that reflects the laboratory's way of working extremely closely. Processes may need to change. Knowledge needs to be transferred. People need training. Existing designs and manufacturing workflows need to be evaluated in a new environment. The laboratory also becomes dependent, to some extent, on the architecture and direction of the chosen platform.

On the other side of the trade-off are capabilities that no longer need to be developed and maintained entirely with internal resources. A specialized platform can also bring the collective experience gained from working with multiple laboratories, incorporating knowledge from different workflows, equipment configurations and operational requirements. An internal platform, by comparison, is naturally shaped by the experience and priorities of a single organization. Both approaches create responsibilities and dependencies. They are simply different ones. The relevant question is which model best supports where the laboratory wants to go.

FocalPoints Logo

WHERE FOCALPOINTS FITS

For laboratories considering FocalPoints®, there is an important architectural consideration. FocalPoints is centered around lens design, with design and manufacturing closely interconnected. The core design-to-manufacturing environment therefore needs to be evaluated as a whole. Moving to FocalPoints is not simply a matter of replacing individual pieces of a proprietary manufacturing system.

A hybrid environment can exist around that core, for example through connections with external ordering and business systems. But moving the core design and manufacturing process to FocalPoints is a more fundamental decision. FocalPoints provides an environment developed specifically for specialty contact lens design and manufacturing, with integrations across multiple equipment manufacturers and technologies.

The value is not simply that an integration exists. It is that the responsibility for developing and maintaining a broader platform is shared with a technology partner whose software evolves across multiple laboratories, equipment manufacturers and technologies. Whether that trade-off makes sense depends on the laboratory.

Although I had over 20 years invested in my own ERP system, I moved my lab to FP and never looked back. That decision freed me to focus on new design development and growing my business. It was one of the best decisions I ever made.

Charley Creighton, Former Owner, Alden Optical

LOOK BEYOND THE SOFTWARE OF TODAY

AI will continue to make aspects of software development faster and more accessible. But easier development does not remove the responsibilities that come with ownership. The comparison therefore needs to extend beyond development costs and software licence fees. Equipment strategy, integrations, future technologies, internal expertise, external licensing needs, knowledge continuity, maintenance and the resources required for continued development all form part of the decision. For some laboratories, retaining proprietary software will remain the right answer. For others, changes in equipment, technology or internal resources may shift the balance toward an established industry platform. The important point is that the software itself does not necessarily have to become worse for the decision to change. Sometimes, the laboratory simply needs it to support a different tomorrow.

UNDERSTANDING THE TRADE-OFF

At Advance Medical, we have worked with specialty contact lens laboratories for more than 30 years. We understand that moving away from proprietary software is rarely just a technical decision. Our role is to understand what works today, where the laboratory wants to go next, and whether FocalPoints represents the right answer for those requirements. It will not be the right answer in every situation.

We know how difficult it is to move away from software that has effectively been built like a glove around the business. There is a real trade-off, and our job is to understand it with the customer before recommending a solution, not after the decision has been made.

Filippo Selden, CEO Advance Medical

Ask Information

SEE HOW THIS COULD WORK IN YOUR LAB

Want to see how this applies to your lab? Share a few details about your workflow and goals, and we’ll guide you to the right FocalPoints configuration.

Talk to our Team


Copyright © Advance Medical, 2026 | Privacy & Terms