A response from Kevin Hooks · Draft for review

The website dispute:
my side of the story.

A website has publicly claimed its author built a site for Hooks Fence Company, let it run for months, and received no payment. I did not pay for the project. I dispute its description of the work as completed and acceptable. A version was put online for me to review from about 60 miles away; I did not use or promote it as advertising for my company because I found it unsatisfactory.

What was published

The allegation I am answering

“They ghosted the invoice.”

The headline appeared on hooksfencing.com when checked September 28, 2026. The page also says the author worked for months and received no payment. I acknowledge that I did not pay; I dispute the suggestion that I accepted a finished site and simply disappeared. In my account, the live version was a way for me to review it remotely, not a website I approved for use in my advertising.

The messages show a detailed email sent August 7, an August 8 reply proposing a new planning call and a September completion timeframe, and further exchanges through August 25. On August 22 I wrote that I was willing to compensate him for attempting the site, even though I was dissatisfied with the result. We also continued discussing it by text and phone. In my view, the requested finished website was never delivered in a usable form for my business, despite months of discussion and revisions.

A question about the wording

The wording speaks for itself.

Joe,

You have a college degree and, as you told me, are enrolled this semester to pursue your master’s degree. If I remember our phone conversation correctly, your field involves internet security and technology.

That brings me to an important question and observation. The screenshot alongside these remarks shows the wording on the one-page website you built. You are pursuing a master’s degree, and I am a high school graduate, but even I can see a problem with the wording.

Do you owe me money? Did you forget to pay me? Or did you simply get the wording wrong on your own webpage? On a page of just four paragraphs and 229 words, that is a significant mistake—especially on a page intended to showcase your work. Given your education at Auburn University, I expected more attention to detail.

I sincerely wish you success in your master’s program and future endeavors. However, I am not going to pay for work that falls below an acceptable professional standard. Paying for subpar work would reward it rather than encourage you to improve.

Shoot for the stars and make Rocket City proud—but not on my dime.

The pace of this project

What “warp speed” meant in my experience

Rocket City Help Desk uses the headline “Tech problems, solved at warp speed.” My website project began in early June. By August 7, I had sent a detailed list of fourteen concerns; on August 8, the developer proposed renewed planning and a possible September completion. By August 22, I had built my own replacement. The dated messages below let readers judge the pace of this particular project. I am describing my experience, not evaluating the company’s response times for other customers.

My account

How the project unfolded

This timeline draws on my account, the supplied text and email messages, and a screenshot of a $500 invoice. Original messages and invoice details should be checked before publication.

  1. We began discussing the project. I sent examples of other fence-company websites on June 4, including Pawnee Fence Company and Fence Concepts, and later shared a large photo album, and a text asking whether we could try an Albertville/Boaz fence-builder address. He replied that it was available and that we could use it. After I said I wanted it, he replied that he would get that one set up, then discussed using photos I had supplied. In a later message he said he had decided to keep hooksfencing.com and forward it to hooksfence.com. That was different from the address I had requested.
  2. A June 18 text said the site was live and that hooksfence.com and hooksfencing.com were forwarding to it. I lived roughly 60 miles away and understood the online version to be for my review. I did not advertise or promote that version for Hooks Fence Company because I was dissatisfied with it. In that same message, the developer said he was having trouble with the logo and planned to implement search engine optimization once we were “done.” That evening I said the page seemed good so far as I began reviewing it, asked about logo suggestions, and questioned why it looked like one main page. The developer described this as an initial review stage, explained his preference for a concise landing page, and said he could add multiple pages and make the changes I wanted. I sent more information for the site, including material about the King Plus fence option.
  3. I raised errors and the scope of the site. A July 13 screenshot I sent shows a “Commercial Fencing” card illustrated with what appears to be an ornamental fence rather than a commercial chain-link example; another July 13 screenshot shows a “Gates & Repairs” card illustrated by a straight white vinyl fence, with no gate visible. These are concrete examples of my concerns about how the draft represented my services. On July 17 the developer sent a screenshot preview headed “Choose your privacy fence style,” showing that he had worked on a wood-fence styles section. My requested result was at least eight pages and a gallery of roughly 30 to 50 photos; I did not consider that full scope delivered.
  4. On August 5 I asked why the site seemed to be one page. The developer replied that he had linked pages for individual fence types and added pages for all fence types, the quote tool, and FAQs. He said he kept the front page largely the same to show brief information there while placing more content on individual pages. The screenshots establish his description of the site, but do not independently verify the pages or their contents. On August 7 the developer texted asking whether I wanted more changes, photos, or pages. He said he wanted to send an invoice and offered a year of changes and updates, followed by a login or later discussion of bigger changes. I sent a detailed email that evening listing fourteen concerns about the site. In his August 8 reply, the developer said he had understood the site to be essentially ready apart from minor image changes. He also acknowledged possible miscommunication, proposed a call to establish requirements, and suggested September for completion even with major changes or redesign.
  5. The email discussion continued through August 14, including a proposed rewrite of the homepage and discussion of city pages. On August 13 I asked for a brief call, and on August 15 we agreed on a 4 p.m. call for August 16. I began building a different website on August 16. I also later spoke with the developer by phone.
  6. I texted that I had built a replacement HTML site the prior week, with a gallery and clickable service-area pages, and preferred how it looked. I asked whether he wanted to remove his material from hooksfence.com so I could use that address. I apologized for the inconvenience and said I was willing to compensate him for his attempt to make a website. He replied that my building it myself had been one of the options he intended to discuss, said he was glad I had a site I liked, and offered help moving content during a call. These messages show a disagreement about the result and continued contact, not an agreed payment amount.
  7. The developer texted that he had cleared hooksfence.com and forwarded it to hooksfencecompany.com. I asked whether it was a 301 redirect, how to add an estimate form, and told him to send a bill to my email. He offered HTML for the form and said he believed the redirect was a 301. In a separate email exchange, he offered contact-form code and domain-email login details, and I requested a server-level 301 for hooksfenceco.com. On August 26 he said he did not have access to hooksfenceco.com. The two old domains are distinct; these messages do not prove that a 301 was installed for either one.
  8. I sent Joe a final email, titled “Conclusion of my thoughts on the website,” explaining my decision not to pay the invoice and my reasons concerning the scope and delivery of the project. The screenshot below shows this message in my Gmail Sent folder at 8:22 p.m. It documents a final written response about the business deal; it does not establish whether the recipient read it.
MY FINAL WRITTEN RESPONSE

I explained my decision by email.

On September 18, I sent Joe my final response about the website project and invoice. I acknowledged the time he spent, explained why I did not consider the agreed website delivered, and stated my decision not to pay. This sent-email record supports my account that I communicated my position rather than simply disappearing.

Screenshot supplied by Kevin Hooks, October 2, 2026. The visible email header shows September 18 at 8:22 p.m.; no year or time zone is displayed. This records the message in the Sent folder, not confirmation that it was read.

How the sites are connected

What the domain records show

According to the WHOIS information I obtained, hooksfencing.com lists Joseph Smith as its registrant. The WHOIS record for rocketcityhelpdesk.com uses a privacy registration and does not publicly identify an individual registrant. Rocket City Helpdesk’s public website lists (931) 625-2285 as its business contact number; that same number appears in the hooksfencing.com registration details I obtained.

The matching phone number connects the publicly listed contact information for these domains. The privacy-protected WHOIS record by itself does not establish who legally owns rocketcityhelpdesk.com. I am sharing the connection because readers should know why my response discusses Rocket City Helpdesk alongside the complaint published at hooksfencing.com.

My position

Why I did not pay the proposed price

Scope and delivery

I hired him to deliver a finished fence-company website with multiple pages and a photo gallery showing my work. That is the scope I say we discussed. In a text exchange, the developer acknowledged the version I saw was a landing page and said multiple pages could be added after review. After months of calls, emails, and texts, I did not consider the version shown to me finished, properly configured, or workable as my business website. In my view, Rocket City Help Desk did not deliver the straightforward HTML website I had hired it to build. The developer’s August 8 reply discussed further planning, possible major changes, a logo still unresolved, and a September completion target. A text shown immediately before a June 17 message says he still needed to select photos and add reviews before the site would be ready for my review. On June 18, he said the site was live, but the logo was unresolved and he planned SEO after completion.

Communication

My August 7 email listed fourteen numbered concerns, including the missing gallery, service and city pages, logo, the domain choice, and wording of the quote button. I wrote that substantial work remained before I would use the site. On August 8 the developer proposed another planning call; on August 11 we discussed scheduling one. The thread continued on August 14, we arranged an August 16 call by text, and messages continued through August 25. I later spoke about the project by phone.

Invoice and expenses

According to my account, $1,200 was discussed earlier. The invoice shown in my records is for $500, with one line item labeled “Fence Website Consult and Configuration”; it shows $0 paid and a $500 balance. I did not hire him for a standalone website consultation. I dispute the invoice’s description because it does not describe the finished, multi-page website and photo gallery I hired him to produce. I also dispute the value of the work delivered. In an August 22 text, I offered to compensate him for attempting the project without naming an amount, and on August 25 I asked him to email me a bill.

What I recall from our calls

When I asked about WordPress, Wix, and Squarespace, the developer told me he built sites in HTML because he considered those platforms insufficiently secure. He also said he planned to add SEO and backlinks near the end of the project; his June 18 text likewise says SEO would come once we were “done.” In a later call he said he had about $400 in expenses and had purchased seven years of hosting and domain services. I questioned those costs because I built my replacement for less than $80, by my accounting. I have not seen receipts or account records establishing what he bought, for what term, or how much it cost. These are my recollections of phone conversations, not independently verified expenses.

The outcome

I ultimately built a different site to meet my needs. On August 25 the developer said he had forwarded hooksfence.com to it; I separately requested a server-level redirect for hooksfenceco.com, which he later said he could not access.

This page presents my account of a business disagreement. It does not establish what a contract legally required or whether any amount is owed. The August email thread and August 25 redirect request support continued communication. The full messages, invoice, receipts, hosting records, and site records can be added after checking accuracy and private information. A hosting provider’s SEO tools alone would not establish what SEO work was performed on this project.

My view of the services advertised

Why I would be cautious

Screenshot of the Rocket City Helpdesk services section showing remote support, computer troubleshooting, Wi-Fi and networking, virus and malware removal, software and email setup, and backups and recovery

Screenshot supplied by Kevin Hooks, September 28, 2026. Shown here unchanged.

After reading my account of this project, I encourage you to think carefully before choosing these services. I was dissatisfied with the outcome of a basic website project. Based on my experience, I personally would not entrust more sensitive work to this company. That is my opinion about my experience, not a claim that these listed services were performed for me.

Screenshot
Selected screenshot

A final word from Kevin and Scout

Read “Hibbity, Bibbity” — the closing poem →