About Brian Thompson
Brian Thompson is 41 and manages information technology at a roughly 550-person manufacturing-technology company outside Indianapolis, leading four people who own endpoints across two operating systems, identity, device management, conditional access and second-tier helpdesk escalations. He came up through first-tier support, spent eight years as a systems administrator, and has been managing for three of his eighteen years in the field; his technology degree came from an online programme he finished while working. He lives in Carmel with his wife, a school administrator, and their children aged nine and eleven; the finished basement holds a home lab he treats as a second job. This quarter he is rolling out conditional-access policy, resisting a push to move the field sales team onto personal devices, and quietly pricing a management tool after discovering the company pays for thirty-one separate subscriptions across three departments.
He believes good technology work is invisible, is quietly proud of running a tight operation, and is tired of the function being treated as a cost centre. He researches community-first — a systems-administration forum, a practitioner chat group, a helpdesk community — then documentation, then a trial in his own sandbox, and he reads public review sites assuming the scores were bought. A pilot is mandatory and he will not be anyone’s first customer. His register is direct with dry humour: patient with colleagues outside technology, blunt with vendors, short in chat, screenshot-heavy in email, and extensive to the point of runbook when documenting. His answer to a cold approach is a checklist — native single sign-on and directory provisioning, data residency, the audited security report, pricing for six hundred endpoints — followed by a refusal to sit through a discovery call before any of it arrives. Vague automation claims, “single pane of glass”, transformation language, and anyone who cannot distinguish two authentication standards all end the conversation.
He is strong from consideration through renewal for device management, identity, software-spend management, endpoint security and service management in the $10,000 to $300,000 annual range. He is the right subject for testing whether integration-first positioning survives someone who will ask which fields move, in which direction, and how often; for security-posture content; for spend-visibility return narratives; and for per-endpoint pricing curves that quietly punish headcount growth. Renewal risk shows up in him early — a twenty percent increase, a broken integration, or an acquisition that moves a roadmap all put a contract back in play. He is less informative on enterprise procurement, which happens above him, and on grassroots developer-tool adoption.
His channel scores are high on YouTube, Google search, LinkedIn, Reddit and email. Facebook, Instagram, X, podcasts, connected television, direct mail and in-app push are medium; Threads, TikTok, Pinterest, out-of-home, text messages and print are low; Snapchat is minimal. He lurks daily and occasionally posts in a systems-administration subreddit, keeps a practitioner chat community open, follows two hands-on video channels and a security journalist, and reads a trade newsletter. He trusts forum threads that link to actual code, two former colleagues he texts, and his director. Vendor-run practitioner conferences are a real discovery surface; a cold email almost never is.
