An uncomfortable exercise
I handed an outside reviewer my public website and three screenshots. No introduction, no context about my reasoning, no relationship. Then I asked what was actually wrong with it.
The value of a stranger is that they owe you nothing. Everyone who knows you and knows how hard you worked softens what they say, usually without deciding to. A reviewer with no relationship has no reason to be kind and no history to be kind about.
Three findings came back. All three were correct, and two of them stung.
"This is clonable"
The first finding: nothing in the technology is exotic. The pieces that make live production work (moving video between devices, compressing it, sending it over networks) are well-understood, widely available components. A competent team could assemble something similar.
My first instinct was to argue. There is a great deal of specific work behind the parts that function reliably, and none of it was visible to someone looking at a website.
Then I noticed that my instinct was the finding. I wanted to defend the effort, and the reviewer had assessed the product. Those are different things, and only one of them is visible to anyone who has not built it. If the difficulty is invisible from outside, then from outside it does not exist... and "outside" is where every prospective user stands.
So the finding held. The individual components are commodity. That is simply true, and a product whose defensibility depends on nobody else being able to obtain the same components is not defensible.
"Price is a wedge, not a moat"
The second finding was sharper.
Being cheaper than the established alternatives gets attention. It gets a first look, a trial, a conversation. That is a wedge... it opens a door.
It is not a moat. Anyone can lower a price. A larger competitor can lower a price further and absorb the loss for longer than one person can survive. If the reason to choose this is that it costs less, then the reason to leave is that someone else costs less still, and that is a position with no floor.
This one stung because price had been doing more work in my thinking than I had admitted. It is easy to lean on, because it is measurable and immediate and it does produce interest. But interest is not retention, and a wedge held long enough starts being mistaken for a strategy.
"Reliability, if real, is the only actual moat"
The third finding was the useful one, and it was conditional in a way I have thought about ever since.
The reviewer's conclusion: if the software genuinely works (reliably, on ordinary hardware, on the day it matters, run by someone who is not an expert) that is defensible. Not because it is technically hard to copy, but because it takes years of contact with reality to accumulate.
Reliability in live production is not a feature. It is the sum of a very large number of specific encounters with the ways things fail: the network that degrades halfway through, the phone that changes its mind about orientation, the display that renumbers itself, the recording that gets interrupted, the volunteer who has fifteen minutes. Each one is small. None of them can be reasoned about in advance. They have to be met.
A competitor can copy the feature list in months. They cannot copy the accumulated encounters, because those only arrive at the speed of real events happening in real rooms.
Note the condition, though: if real. The reviewer was explicit that this was contingent, not observed. They could not verify reliability from a website, and neither can anyone else. It is a claim that only pays off if it is true, and only becomes visible over a long time.
That is an uncomfortable moat to hold, because it cannot be demonstrated in a demo. It can only be earned slowly and lost quickly.
"Lock-in does not exist yet"
There was a fourth observation, made almost in passing, that I have come to think about the most.
Nothing holds a user. No accumulated data they would lose, no workflow they could not rebuild elsewhere, no switching cost. A user who wants to leave simply leaves.
The tempting response is to build lock-in... make the data harder to extract, the workflows more proprietary, the exit more expensive.
I decided against it, and it is worth saying why rather than just claiming virtue. The people using this are volunteers running services and events. Making their exit expensive would mean holding their work hostage against their judgement about whether this is still the best option. That is a strategy that works, and it works by making people stay who would rather leave.
The alternative is harder and I think it is the only one consistent with who I am asking to trust me: be worth staying for. No hostages, no artificial friction. If someone finds something better for their venue, they should go, and I should find out why.
That decision may cost me. It also means every user here is one who currently wants to be here, which is a more honest number than a retention figure inflated by exit costs.
What I changed
Less than you might expect, and more than it sounds.
I stopped treating price as a position. It is still there, still true, and it is no longer the argument.
I started treating reliability as the actual product rather than as a quality of the product. That reorders priorities: the boring work of handling failure modes is not maintenance getting in the way of features... it is the thing itself.
And I started publishing the failures, which is partly why articles like this exist. If reliability-if-real is the moat, then the evidence has to be visible, and the only honest evidence is a record of what broke and what I did about it.
Why do this
The exercise cost an afternoon and told me more than months of my own thinking, for one reason: the reviewer had no stake in my feelings.
If you build something, I would recommend it. Not a friend, not a user who likes you, not an advisor who wants to be invited back. Someone with no relationship, given only what a stranger would see, asked what is wrong.
You will want to argue with the answer. That reaction is worth examining more carefully than the answer itself, because it usually marks the place where you have been defending the effort instead of assessing the result.