Rebuilding a company website from the inside

Disclosure, up front. Gabe Key works at Secur-Tek in business development and operations. This work was done as an employee, on the company's own systems. Secur-Tek is not a Firmkit client, did not pay Firmkit, and has not endorsed Firmkit or this site.

A company website rebuild should be described by what was built and the role of the person doing it. At Secur-Tek, the public scope includes a website, a Google Business Profile correction, a CRM rebuild and an operating standard. This account stays with those published deliverables. It makes no claim about revenue or conversion results.

The website

The work included a 65-page website rebuild with 13 town pages and full schema. Those numbers describe the scope of the build. They do not establish traffic growth, lead volume or a change in sales.

The public site is at mysecurtek.com. Secur-Tek is a locally owned residential and commercial security and low-voltage company in Apex, serving the Triangle since 1990.

Describing a rebuild does not require a story about what was wrong before it. The deliverable can stand on its own: the site was rebuilt, the town pages were included, and structured data formed part of the work.

The connected public profile

The Google Business Profile was corrected. That is the approved public description of this part of the project. It does not need an invented before-and-after account or an unsupported claim about search placement.

Keeping an account this narrow is useful. Someone reading a case study should be able to distinguish a documented task from a measured result. They are different kinds of evidence.

The CRM and operating standard

The CRM rebuild included eight pipelines, 45 workflows, and forms wired to live routing. The operating standard was written for a team of more than 20. Those are the remaining public outcomes supplied for this account.

The underlying workflow designs, records, staff details and internal procedures are not part of this article. Their absence does not need to be filled with a generalized story about the company's operations.

State the relationship clearly

This was employee work on the company's own systems. Secur-Tek is not a Firmkit client. The case therefore belongs under Gabe Key's company work, with the employment relationship visible before the scope is discussed.

The full work entry keeps the same disclosure. Firmkit's own entry describes a separate offer without borrowing an employer's project as a client result.

A useful project account tells a reader what was built, by whom, and in what capacity. It can stop there.