Business ProfileforSecoy Custom Structures

On 4/9/2023, my wife, *************************, and I agreed to a contract with **** ************************************************ **** agreed to build an addition to our home and provided a quote of $87,000. **** reported the project would be fast and easy, and completed in 3-4 weeks. He requested a deposit of $52,525, which we paid to him in full. Immediately, **** and his team had bad attendance and were not providing quality work as evidenced by extensive water damage to our home. I spoke to **** on the phone on 8/14/2023 to resolve several concerns. **** agreed he was not able to finish the work and also agreed to us switching contractors so someone else could finish the job. He spoke about having too many other projects and not enough help. On several occasions we requested details from **** about the work done to justify the costs. On 8/15/2023, we requested a prompt refund of the unused portion of what we paid. **** refused. Instead, on 9/18/2023, he sent an electronic invoice requesting $9,595.42 in addition to the $52,525 deposit. The invoice lacked any details of the work done to justify the costs, despite repeated requests to understand why he felt he was owed this money, he refused. We responded to ****'s invoice with a letter in accordance with the prompt pay act in ******* that we would not be paying the invoice, we had to file a claim with our home owner's insurance for the water damage caused by ****'s negligence, and we learned much of the work he did was not in compliance with building codes and we would have to pay another contractor to remediate those issues. **** wrote back with a threatening message that if we do not pay him he would come to our home, remove our windows, remove our doors, file criminal and civil suits against us, and put a lien on our property. We believe **** was reasonably owed $37,994.66 for the work he did and his incorrect work has cost $18,500 to repair. Therefore, we believe ************* us $33,030.34 and we want to have this problem resolved.