The Two-Year Job: Why Vetting Products and Owning the Process Is How I Protect the Customer

I have wanted to write this one for a while. It is not a flattering story. That is why it belongs here. If the only stories I tell are the ones where the system worked and the client cried at the reveal, I am selling marketing, not telling you what this work actually looks like.

This is a project that did not work. I lost the customer. The lesson is on me. I am keeping the people anonymous. The names do not matter. The pattern does.

How the introduction came in

An electrician I had worked with for years called me about a new homeowner who wanted a real automation system. He was not just a referral. He was a friend. He had watched me run wire, finish racks, and follow up after the punch list. He was sending this client to me because he trusted me to do the right thing by them. That is the best phone call in this business. It is also the one with the most weight on it.

I went for the walkthrough. The home was beautiful. The budget was real. The scope was the kind of work I love. The homeowner had strong opinions about technology, which is normal in this market. They had already made some platform decisions, including the voice control they wanted.

I wrote the proposal. We signed paperwork. We started.

The mistake I made on day one

The client told me which voice platform they wanted. I said yes. I had not lived with it. I had not vetted it. I trusted the manufacturer's word about how it would behave because their marketing was strong and the demos were strong. That was the recipe for disaster.

The customer hires an integrator because they are not an integrator. They are paying for years of judgment about which products survive contact with a real home, which products age well, which products fall apart at month eight. If I take that judgment off the table because the client has a strong preference, I am not giving them what they bought. I am giving them an order-taker with a logo on the truck.

I did not do that job. I spent two years trying to deliver against decisions I would never have made if I had been doing it.

What two years of friction actually looked like

Here is the part that bothered me the most. The scope was clear. We documented as we went. We sent summary emails. We tracked tickets and decisions and equipment behavior. When the vendor pushed back, we had logs, screenshots, configurations, and timelines to prove the issue was not on our side. We did the operational work right.

It did not save us.

We were doing the right things on documentation and we were still going further into a hole every month. That is what made the pain hurt the way it did. We did not fail because we did not write things down. We did write it down. The failure was upstream of the documentation. We were defending a product that was not ready, from a manufacturer who was not standing with us. No amount of careful tracking rescues a job from that. It only lets you see the hole getting deeper in higher resolution.

The day my heart dropped

I am not going to name the voice platform. The point of this story is not which brand it was. The point is what I learned.

I had believed in the hype. The marketing was strong. The demos were strong. The story the manufacturer told was the kind of story integrators want to believe about a category that has, for a long time, promised more than it delivered.

In the home, the experience did not match the story. The platform misunderstood people when they spoke to it directly. It would do things on its own, in rooms nobody was in, that nobody had asked it to do. Music turning on with no one near it. The customer had a technology background. They were careful. They were observant. They flagged the problems clearly.

I escalated to the manufacturer. What came back, more than once, was a suggestion that the customer was talking to it wrong. That the user was the problem. That should have been a louder alarm bell than it was. I was so taken aback by that response that I lost time on how to even push back against it.

And then, in the middle of going back and forth, trying to make the product behave the way it had been sold to behave, I found something else. The customer had raised a concern. I went to confirm it myself, hands on, the way I should have done before any of this product ever entered the home.

What I found was that I could retrieve audio I should never have been able to retrieve. Not as an administrator. Not as a technician. Not as anyone. The platform was supposed to be a voice command surface, not a recording surface. The fact that any audio of any kind could be played back, by me or by anyone, was a complete privacy failure. There is no configuration tweak that makes that acceptable. There is no manufacturer reply that lands the right way. Audio that could be played back later should not have existed in the first place.

My heart dropped.

Not because of any one thing on any one recording. Because of what I understood in that moment. I had vouched for this product. I had stood in a customer's home, the home of a homeowner my friend had introduced me to, and said yes when they asked if this was a real platform. What I had brought into their home was something I would never have approved if I had known what I was looking at.

I had brought the enemy in. That is not a phrase I use lightly and I have not used it about a product since.

This is not what we do. This is not who we are. These are not the brands we align ourselves with. Integrity always must come first, even when it hurts. People need to believe we will do the right thing even when no one is paying attention. That is one of the core pillars we stand on.

How it ended, and what we did next

We fired the manufacturer. We handed the voice scope to another integrator. We were not interested in watching the product grow up, and we were not interested in doing R&D for them inside our customer's home. We had already spent two years being their unpaid feedback loop. The customer had already paid for that with their own time. We were done being a guinea pig for that brand. We own our jobsites.

We are still friendly with the customer. They were not a bad customer. They were careful and observant. They were also stuck in a hard situation with an integrator who had not done the homework. When they call us, we still pick up. We still support what is in the home, free of charge in many cases, the way you support someone you owe something to. A standing pledge against the work I did not do well enough at the start. I am not asking the reader to give me credit for that. It is just what right looks like.

The friendship with the electrician survived, because of who he is. He was understanding throughout. He saw the hours we were putting in. He saw the care. He saw the manufacturer not behaving the way a manufacturer should. He never made me feel that the failure was a betrayal of his trust. That is a grace I did not earn. It is on me to make sure I never put a friend in that position again.

What I changed

This is the part that matters, because the only thing worse than a bad project is a bad project you did not learn from.

I eat my own dog food. I run Crestron in every square inch of my own house. Every room. Every scene. Every edge case. That is how I know exactly what it does, exactly how it behaves, exactly what to stay away from, and exactly what to recommend. Every product has edges. Knowing where they are is not something you read in a spec sheet. It is something you live with. I had not lived with the platform on this job. I trusted the manufacturer's word over my own experience, because I had no experience to trust. That was the recipe for disaster. The lesson is permanent. If I have not lived with it, I do not put it in a customer's home.

I vet every product, every time. Not just whether it works on the bench. Whether it survives a power cycle at three in the morning. Whether it ages well. Whether the company behind it stands with me when something goes wrong. Whether the privacy posture is something I can defend out loud to a homeowner. Whether the vendor's first move when I escalate is to take it seriously or to suggest the customer is wrong. Those questions are not optional anymore. If a client wants a platform I have not vetted on those terms, I tell them. I do the work. Then I tell them what I learned. If the answer is no, the answer is no, regardless of how strong the marketing is or how much the client loves the demo.

I own the process, or I do not take the job. How we communicate. How decisions get made. How disagreements get resolved. How scope changes get priced and approved. Who signs off on what before the next phase starts. None of that is up for negotiation. That is the integrator's discipline. A client who does not want me to bring my process is not asking for an integrator. They are asking for a vendor.

Documentation is necessary. It is not a rescue plan. We documented this job carefully. It is how we eventually proved our work to the people who needed to see it. It did not save the project. Good documentation cannot turn a wrong-fit project into a right-fit project. It can only show you the shape of the hole you are standing in. The work of preventing the hole is upstream. Vetting and ownership at the start. The documentation comes after the right decisions, not instead of them.

A referral from a friend in the trade is sacred. It is a loan against their name and their relationships, not just their reputation as a contractor. I owe them a fast, honest read on the fit. I owe them a heads-up if it starts going sideways. I protect the people who put their name on me by telling them early when something is off, not by hiding it and hoping I can fix it before they find out.

I am willing to walk away. There is real money in this business. There is also real cost in saying yes to the wrong project. The two-year job cost me more than it paid, when you count the friendship, the team time, and the hit to my own confidence. I would rather lose a deal at the proposal stage than lose a customer and a friend at the punch list.

What protecting the customer actually means

A lot of people in this trade hear "the customer is always right" and turn it into a permission slip to stop thinking. The customer is not always right about the product list. The customer hired me because I am supposed to know things they do not know yet. The day I stop bringing that to the table is the day I stop being worth what they are paying.

Protecting the customer means telling them no when no is the right answer. It means doing the homework before the platform gets specified, not after the customer is the one finding the problems. It means looking past the marketing on a hot product and asking whether the company behind it will pick up the phone when I need them to. It means walking away from a job where I can tell, on the first visit, that I will not be allowed to do the job they actually need me to do.

I did not protect that customer. I gave them what they asked for, and what they asked for did not serve them. That is not a difficult-client story. That is an integrator who forgot that being agreeable is not the same thing as being responsible.

For the homeowner reading this

If you are about to start a project of this size, ask the integrator how they vet products. Ask which products they have stopped using, and why. Ask how they handle a request from you for a platform they would not have specified themselves. If the answer is "we install whatever you want," you are hiring a vendor, not an integrator. They are not the same job.

And if any of the technology in your house has a microphone, ask where it is, when it is on, and what gets stored. The honest answer is fine. The dodge is the problem.

For the trade partner reading this

If you have ever sent a client somewhere and watched it not work, you know the feeling. I owe you the same diligence on my side that you give on yours. If I am not the right fit for the homeowner you are about to introduce me to, I would rather tell you that on the phone before the walkthrough than learn it together at month eighteen.

What I tell my own team

We talk about this job internally. Not as a horror story. As a checklist. When a new project manager joins us, I walk them through what I should have done at the beginning and did not. Then we look at our current jobs and ask, where on this list are we today. Has every product been vetted, including the ones the client asked for. Have we lived with it. Will the manufacturer pick up the phone when something goes wrong. That checklist has saved us at least two projects I know about, and probably others I do not.

I did not love writing this. It is the kind of story you tell at the end of a long day to someone you trust, not in a blog post under your own logo. I am writing it anyway, because the version of this work that is honest about what does not work is more useful than the version that pretends every project ends at the reveal photograph. We have done excellent work for many years. Some of the best things I know how to do, I know how to do because of this project. I will tell you the truth even when it is uncomfortable, especially then.

People buy Restrepo sites. Not the manufacturers that are inside of them. That is the standard now, and there is no going back from it.