imgbot
1
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Allen HouchinsandMike Thomas
|
7f07651f97 |
Add Hawx case study (#50152)
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** N/A # Checklist for submitter This PR adds one markdown file under `articles/` (a customer case study) — no product code, so most of the template below doesn't apply. ## What changed Adds `articles/hawx.md`, a case study on Hawx Pest Control. **The story:** Hawx is a technology-first pest control company whose field technicians can't be dispatched without a provisioned phone. Hiring ramps up hard every summer, so onboarding and offboarding run constantly. With Jamf, phones sat on the MDM screen until the technician logged in, nobody remembered their credentials, and the helpdesk got flooded from personal phones every season. Identifying which device belonged to which technician took 5 to 10 minutes per call, 5 to 10 calls a day. Hawx now drives Fleet entirely through the API, paired with Tines and Okta, so a device lands in the right fleet with the correct profiles, policies, and apps the moment the technician verifies their identity. Offboarding wipes or locks based on role. Migration took a month. **Source:** the 2026-07-20 customer interview with Loren Farr, IT Manager at Hawx. Loren confirmed on the call that Fleet may use the company name and his name and title, and was told nothing publishes without his approval. **Format:** drafted against the proposed `fleet-case-study-formatting` skill in #49917 and the `content-style` skill: - Three-act narrative (the challenge → why Fleet → the solution → the results), headings in sentence case. - Four `attribution-quote` divs spaced through the narrative rather than clustered. - A `checklist` div for the headline results. - Full endmatter including the build-enforced `summaryChallenge` / `summarySolution` / `summaryKeyResults` (semicolon-separated) plus the company and hero-quote tags. - "About Hawx" lives in `companyInfo` / `companyInfoLineTwo` rather than the body, matching every published case study. ## Why Hawx is a strong story in a segment Fleet's published case studies don't yet cover: iOS-only, a small IT team (3 people, ~500 devices), a seasonal workforce, and an API-only usage pattern where the customer never touches the Fleet UI. It's also a clean Jamf migration narrative with a quantified helpdesk result. ## ⚠️ Blockers before this can be published This is a **draft PR on purpose**. Two items must be resolved first: 1. **The quotes are not verbatim yet.** The interview record is bullet notes, not a transcript, so the four quotes are faithful reconstructions of what Loren described, not transcribed speech. The case-study skill's rule is that quotes are verbatim and never reconstructed. **Loren needs to approve these as his words before merge.** Reviewers should not treat them as citable until he has. 2. **Both image assets are missing.** There is no Hawx logo and no Loren Farr headshot in `website/assets/images/`. `companyLogoFilename` and `quoteAuthorImageFilename` are deliberately stubbed with `TODO-` prefixes so the website build fails loudly rather than shipping broken image references. Real files are needed following the `{descriptor}-{css-width}x{css-height}@2x.{ext}` convention. ## Open questions for reviewers - **The "more than 90%" figure was dropped.** An earlier draft said credentials were forgotten in more than 90% of cases. That number isn't in the interview notes (the notes say "nobody knew their username or password"), so it's omitted. If Loren sourced it, it can go back in. - **The warehoused-device problem is omitted.** The notes describe devices offline more than 30 days needing a reset, currently a 30-minute call, listed as a *current* problem. That would fit a "Looking ahead" section if Fleet is the plan for it, but it doesn't belong in results as an achieved outcome. - **Hero quote choice.** `quoteContent` uses the "slam dunk ... control over the phone itself" quote because it names the differentiator. Loren's closer, "As long as you're not shy about getting into the code, this is a fantastic platform," is arguably the more trustworthy line for Fleet's audience. Easy swap if marketing prefers it. - **Follow-up, not in this PR:** the pull quote could be added to `handbook/company/testimonials.yml` for the `/customers` carousel. Left alone since that file is curated by marketing. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. — N/A, website content only, not a product change ## Testing - [ ] Added/updated automated tests — N/A, markdown content only - [x] QA'd manually: cross-checked the structure, custom div syntax, and required meta tags against the published case studies (`articles/fastly.md`, `articles/primo.md`) and against the validation logic in `website/scripts/build-static-content.js`; confirmed `summaryKeyResults` is semicolon-separated; confirmed `articleTitle` matches the H1 exactly; grepped `website/assets/images/` and confirmed both referenced image files are absent (hence the `TODO-` stubs). --------- Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> |