Secur-Tek. The whole kit, built from the inside.

The company had a working site and a page builder underneath it. The rebuild kept the WordPress install and the URLs, and replaced the page builder output with hand-written HTML, one document per page: homepage, twelve service pages, about, team, testimonials, FAQs, user guides, alarm registration, careers, five contact and form pages, a blog index and seventeen posts.

Each page is roughly 97 KB with the logo embedded, so there is no builder stack loading behind it. Fifty JSON-LD blocks validated. Real Google reviews on the homepage, the testimonials page, the service pages and the city pages, in place of the placeholders that were there before. Seven duplicate and orphan pages were found and mapped for redirects.

The rule that survives the longest is the smallest: the site says "since 1990" and "35+ years" everywhere, never a year count that goes stale.

A pre-wire walk-through in a new build. One of the frames that runs on the careers page.

Thirteen city pages, one for each town the company actually drives to: Apex, Cary, Raleigh, Holly Springs, Fuquay-Varina, Morrisville, Wake Forest, Garner, Durham, Chapel Hill, Knightdale, Clayton and Pittsboro. The same page template thirteen times would have been a doorway farm, so each one names its own neighborhoods, landmarks and ZIP codes, carries a new-construction pre-wire callout, and answers the question every security customer secretly has: does the monitoring company watch my cameras? It does not, and every page says so.

The Google Business Profile audit found three things a customer would have seen before ever calling. The company name was written "MySecurtek" three times in its own description. The service area listed Holly Ridge, a beach town three hours away, instead of Holly Springs. And the hours showed open 24 hours, because the default was never changed. All three fixed.

The profile audit, drawn. Three lines a customer reads before deciding whether to call.

Residential sales, commercial sales, the tune-up campaign, consultation intake, service requests, referrals, website contact and billing questions. Each one is a pipeline with stages, so a lead sits in exactly one place with exactly one owner. The website's consultation, contact and referral forms post straight into the right pipeline through webhooks, and the first automated reply goes out from there.

One honest limitation, because it is true of every trade company in the state right now: text messaging waits on carrier A2P registration, so the SMS legs of those workflows fire by email until the carriers clear it. That is a registration, not a design flaw, and it is why Firmkit's own guarantee is written around the text-back working before anyone pays for it.

• 8pipelines, one per kind of conversation the company actually has
• 45workflows: first replies, follow-up cadences, status hygiene, internal alerts
• 3website forms wired to pipelines by webhook, so nothing lands in an inbox
• 1call-center playbook, with the camera-privacy answer scripted, because that objection was costing calls

A thirty-five-year-old company has a database it has never really used. The open-account list was cleaned, split into residential and commercial because they are different conversations with different decision-makers, and sorted oldest install first, since the age of the system is the single best predictor of a tune-up yes. Accounts with no phone number were flagged and dropped. Accounts that shared a phone were flagged so nobody gets called twice. Priority bands recalculate live from the install date, and the newest customers go to a courtesy check-in rather than a pitch, because pitching someone who signed last month reads as a money grab.

Then a second list from public records: every single-family sale in Wake County in the last ninety days, with a new-construction flag and a days-since-sale sort, built from the county's own extracts instead of a paid data broker. And a compliance decision written into the file, not left to memory: no scraped phone numbers, no cold calls, direct mail only. North Carolina's telephone solicitation statute is not a footnote.

1. Clean, split, sort

   Residential and commercial separated. Oldest install first. No-phone and shared-phone accounts flagged.

2. Bands that move on their own

   Ten-plus years, five to ten, two to five, and a do-not-pitch band for the newest customers. All formula-driven.

3. A script and a dashboard

   The call script sits in the same workbook as the live tally, so the person dialling and the person reporting look at one thing.

4. Public data, compliant channel

   County sales extracts joined on the parcel id. Direct mail, because that is the channel the statute allows.