Stratum Tech Group website
The public website for my IT and repair business, with one door for home users and one for small businesses.
My role
I directed AI (Claude Code) to build the site. I set the audience split, the anti-scam trust rules and the copy voice, and I reviewed the results. The AI wrote the code. No other people are recorded as working on it.
What it is
The site is the public face of Stratum Tech Group. It has a home help door, where someone asks for help in under a minute with no account, and a business IT door with a free IT assessment form and a client portal sign-in by magic link.
Because remote-support scams are common, trust is built into it: a published safety promise, a page where anyone can check whether a message really came from us, and a scam-check page. There are also service pages for computer repair, printers, Wi-Fi and network, and virus and scam cleanup, plus a page for adult children booking help for parents.
It is the same codebase as the Stratum Desk, so a web form creates a ticket directly and a booking creates a call slot and a texted status link. No visitor or lead numbers are documented.
How it was built
- Started from an older resume-style siteBefore 12 Oct 2026 the business had a resume-style site on Vercel. A first business homepage with services, a calculator and a quote form was planned on 5 Oct 2026. The old local copy was not found.
- Put the public pages inside the desk appThe public pages are server-rendered routes in the same Next.js app as Stratum Desk, so forms write to the real ticket system instead of a separate form service.
- Defined two audiences up frontdocs/OPERATING_MODEL.md describes the home help door and the business IT door. Routes include home, five service pages, business assessment and managed IT, book, support, safety, scam-check, verify, family, sms, terms, privacy, sign-in and the portal.
- Wrote trust and safety rules into the productA published safety promise, a rules-only /verify check that never uses AI, no pre-payment, and card-first payment order. Cold-call limits under Texas rules shaped the operating model.
- Rebuilt the front endOn 12 Oct 2026 the visual design was rebuilt with warm sand and gold design tokens, dark mode and a logo mark of nested gold triangles. Git tags keep the previous design versions for rollback.
- Added SEO and spam protectionSEO setup and service-page docs (SEO_SETUP.md, SEO_SERVICE_PAGES.md), Cloudflare Turnstile on forms, and a texting page whose wording had to match the A2P campaign.
- Checked on desktop and phoneA project note records a visual tour end to end test on desktop and phone on 12 Oct 2026.
- Deployed on Vercel with Cloudflare DNSHosted on Vercel Hobby with Cloudflare DNS and Microsoft 365 email. Related repair brand domain: stratumtechrepair.com.
Decisions and why
- Two doors on one site
- Home users want fast help with no account. Businesses want a plan and an assessment. One page for both would confuse each.
- Publish a safety promise and a verify page
- People are wary of remote-support scams, so proof that a message is really from us is the strongest trust signal.
- Same codebase as the desk
- A form submission becomes a tracked ticket with no integration work or copy-paste.
- Voice: never a software product
- The site sells service by a person, so copy avoids software-sales language.
Hardest problems
- Earning trust where remote-support scams are common.
- A published safety promise, a rules-only verify check, a scam-check page, no pre-payment and card-first payment order.
- Texting page content had to match the A2P registration, which took four submissions.
- Rewriting the sms page and campaign docs to agree, plus a spam guard.
- Cold outreach rules in Texas.
- Recorded limits in docs/OPERATING_MODEL.md and kept outreach within them.
Numbers
| Public and portal page routes found in the app | 57 page routes across the whole app (public, portal and desk) | 2026-11-06 |
|---|---|---|
| Service pages | 5 | 2026-11-06 |
Timeline
- 5 Oct 2026First business homepage plan with services, calculator and quote form.
- 12 Oct 2026Live at stratumtechgroup.com on Vercel with a rebuilt front end.
- 12 to 14 Oct 2026SEO service pages, safety wording, Turnstile and the family page added.
What I took from it
- On a trust-sensitive site, safety features such as a verify page carry more weight than visual polish.
- Putting public pages in the same app as the back office removed a whole integration layer.
- Copy rules (voice, no disclaimers, what we never say) are worth writing down before design.