Founder & Operator
Shared systems, developer experience, and governance layers underneath what customers actually see. The parts that keep things calm when the surface gets complicated are where I’ve spent the work.
Principles, embodied
Rocalyn’s four principles aren’t marketing posture — they describe how I’ve operated for 25+ years.
Bootstrapped product-led cybersecurity from zero, then scaled a team running blue/red-team work, release-gate security review, and SLA'd customer-inquiry response. Shifted product security left — from retroactive retrofit to release-gate discipline. Trust earned through operational outcomes, not compliance theater.
Organizations get enlightened when the invisible starts surfacing before the bill does. Sponsored an Atomic Design system through Brad Frost's project-to-product crossing — dispersed teams spoke one language. Built platforms observability-first, so operators saw what mattered early enough to act — before downtime, repairs, or replacements did the deciding.
Led a cross-functional organization across product, engineering, UX, quality, and security — shipping platform and system-level products for every product line in the company. Connective-tissue work compounds: the asymmetric win isn't reacting faster at release — it's planning quality into the work before any commits land.
Getting product fit right for users is the recipe. That's how platforms earn sovereignty — by keeping agency with the teams and users they serve. Software I've helped launch has stood the test of time; the people who inherited it can still do their work.
Range
Three verticals with wildly different tolerances — and one customer archetype underneath all of them.
B2B2C engagements with global payments networks, major retail infrastructure, worldwide commerce deployments, and top-tier productivity platforms. Fortune 500 buyers set their own bar; success meant meeting it on their terms, learning how each business expected the work done before tailoring architecture, process, or handoffs.
The throughline: observability at board-room reliability. Security as prerequisite, not afterthought.
Deep empathy for campus administrators, IT experts, and teachers focused on curriculum — not the friction between them and the students. Everyone who drives a car needs to know where the headlights, wipers, and speedometer are, regardless of brand, model, or design intent. A mic needs to hear the teacher, content has to reach the screen, operation and maintenance have to scale without breaking the administrator's bank.
The throughline: serviceability at scale — districts and campuses don't have infinite resources. They have a handful of smart folks (in my experience, 5 techs covering 900 classrooms wasn't unusual) triaging technology issues across hundreds of campus spaces.
Security-first integrations with classification requirements. A/V systems living on networks national security operates. Tools for setup, configuration, and management built to exceed requirements — then DOD/JITC-certified so they could move fast once approved.
The throughline: security as the bar; observability and serviceability built within it.
The throughline. Whichever vertical, the recipe was always the same. Empathy was the source — knowing what each operations-leader actually carried, what their business was trying to deliver. Capability was the lever — design criteria that traveled with me: observability at their level, security at the release gate, serviceability at the technician’s level. The product earned its stripes not at launch but on the hundredth quiet Monday morning two years later.
“In my past, I built the products and tools. My customers built what the world’s major organizations run on.”
“Rocalyn carries that stance forward. We’ll help you build the thing behind the thing — so your customers love working with you.”
Current lane
Not a straight line that got me here. IT in the late ’90s, graphics engineering at the turn of the century, a stint in consulting and marketing — part of why I think about platforms as connective tissue rather than as territory. Most of that was seventeen years at Extron, leading platform work across software, firmware, and hardware, plus enough adjacent gaps that I sponsored UX and bootstrapped product-led cybersecurity along the way. Rocalyn is the next early room.
Rocalyn takes three shapes. Fractional product leader when the team needs senior operator capacity. Advisor when you’re too close to the problem to see it — smart outside eyes, no conflict of interest. Design partner when the product is ambitious enough to want a co-builder.
The shape bends to the work, not the reverse. Current focus: AI-amplified platform work — edge intelligence, applied AI agents, privacy-first systems. Small, elite, compounding.
Reach out to Rocalyn
If this sounds adjacent to what you’re building, I’d enjoy the conversation.