About
I'm Cal.
Army veteran. Spent years as a defense-technology executive. The kind of work where data security isn't a marketing claim, it's the constraint everything else gets built inside. Now I run SailQuery LLC, an independent software studio building apps for the human niches the rest of the consumer-software industry is content to overlook.
The arc connects more cleanly than it reads. The discipline that makes defense-grade software work (assume the worst about how data will be handled, minimize what you collect, defend every claim) is exactly what's missing from the consumer apps people rely on for the parts of life that matter most: their health, their fitness, their relationships, their leisure.
What SailQuery builds, and for whom
Migraine sufferers whose neurologists give them ten minutes a year. People rebuilding their relationship with food. Adults tracking rosacea flares the medical system doesn't have time to pattern-match. Lifters with years of training data they don't want to lose to the next acquisition. Cruise loyalty mechanics that nobody publishes plainly because nobody else has the data. Networking burdens the CRM-industrial complex makes worse, not better.
These audiences aren't underserved; they're poorly served. Existing tools disbelieve them, infantilize them, harvest their data, or extract a subscription tax for insights about their own lives. SailQuery is built to operate where that bar is lowest.
Privacy and data, in words I'll defend
You own your data. You don't owe it to me, to a third-party SDK that came along for the ride, to an analytics platform mining your habits, or to a server that holds it because that's what apps do now.
SailQuery apps work on-device first. We don't run silent telemetry. We don't sell or share data. We don't store what we don't need to store. When information has to leave the device (for backup, for sync, for a feature that genuinely requires it), you're told why, you opt in, and the data is yours to take with you when you leave.
This isn't a marketing position. It's the engineering constraint every app in the portfolio is built inside.
What I'll talk about
If you're a journalist, podcast host, conference organizer, or partner reaching out, these are the topics I'll go deep on:
- Data security. What defense-grade standards actually translate to consumer software, and where the rest of the industry is failing on the basics.
- Privacy concerns. Building products around the principle that users own their data. What it changes architecturally, what it costs commercially, and why most apps refuse to do it.
- Application development. Indie iOS shipping cadence, tooling, design discipline, what works and what gets dropped.
- Small business concerns. Running a software LLC as a one-person shop. The operational, legal, and tax realities most indie founders learn the hard way.
- Emerging technologies. Practical assessments of what's actually useful for builders vs. what's hype cycle.
- Artificial intelligence. Building production software with AI as the engineering partner. The role of an operator when most of the keyboard work can be delegated.
- Solo founder operations. Running four live apps and two in development with no team. How the work actually flows.
- The defense-tech-to-indie-iOS pivot. What changed about how I think about software when the customer was no longer a procurement officer.
- Anti-engagement design. Building apps that respect user attention instead of compounding against it.
- Building for chronic-illness and recovery audiences without crossing into clinical territory you don't have credentials for.
- Veteran to founder. The parts that translate, the parts that don't.
Reach me
Press · partnerships · podcast invitations · "have you thought about building X." I read everything.