If the software can be rebuilt, what can't be copied?

That distinction matters. So does the direction this is moving.

If a small team can build a recognizable version of a product that once took a large organization to make, a familiar interface may become less of a moat. More companies will be able to try building for themselves, and customers will have more options. For a business that sells software or a service delivered through software, the question becomes: what would a customer lose if someone copied the visible part of what you do?

Often the answer is in the work people do together. A client remembers who understood their problem, who caught the exception before it became expensive, and who stayed involved after the initial setup. Your team may know why a customer needs a certain approval, which promises you made during onboarding, and when an automated answer needs a human conversation. Those details are harder to reproduce from a screenshot.

That does not mean relationships can excuse a weak product. Customers still need tools that work, secure handling of their information, and someone accountable when something breaks. It means the product and the people around it should reinforce each other. When routine work gets easier to automate, employees can spend more time on the parts of service that require judgment, trust, and context.

At Ruby, this is one reason we begin by learning how the work actually moves through a company. We look at the repeated questions, the handoffs, and the moments when someone brings knowledge of a particular customer into a decision. Some of that work can be documented and supported by AI. Some of it is exactly where an employee should stay close to the customer. The goal is to give people more time for that relationship, while making the routine parts more reliable.