Product Portfolio
Camryn Jackson
Product Builder · Founder @ PNEUOMA · 0→1 Systems Designer
I identify operational problems inside real-world environments and build the systems that solve them. As a former Dean of Students and Athletic Director, I operated inside the constraints that most software ignores — limited time, high stress, fragmented workflows, and people making decisions under pressure. That experience shapes how I design products: start with the constraint, scope tight, and ship systems that reduce friction across AI tools, education platforms, and workflow automation.
11+
Products Built
8
Shipped
10
Domains
0→1
Core Focus
How I think about product
Environment
Identify the real-world system where friction lives
Schools, teams, workflows
Friction
Isolate the specific constraint people work around
Time, attention, regulation, clarity
System Design
Build the minimum product that removes that friction
Scope tight, ship fast, measure
Better Decisions
People make faster, clearer decisions under constraints
The product disappears; the outcome stays
PNEU
↗Nervous system regulation in under 60 seconds
Problem
In school environments, dysregulated students and teachers cause classroom disruptions, teacher burnout, and learning loss. Most interventions happen after problems escalate — there are no fast, proactive tools available during the 60-second windows between transitions.
Insight
Short breathing exercises can restore nervous system balance in under a minute. Schools have the need and the time window — they just don't have an accessible tool designed to fit into it.
Solution
A mobile app delivering guided micro-resets — haptic breathing synced to 65 BPM, voice guidance, and grounding exercises. Designed for the reality of school schedules: fast, minimal, and usable under stress without any training.
Environment
School transitions cause dysregulation with no proactive tools
Friction
Existing interventions don't fit the 60-second window
System
Guided micro-resets with haptic breathing, zero onboarding
Outcome
Daily adoption through speed, simplicity, and schedule fit
Key Decisions
Hardest Product Decision
Limiting sessions to 60 seconds instead of building deeper meditation or extended wellness features.
Why
Longer sessions would improve regulation depth, but the operating reality is that teachers and students rarely have more than a minute between transitions. A 5-minute feature that never gets used is worse than a 60-second tool that becomes a daily habit. Optimizing for speed and consistency over depth made real-world adoption possible.
Impact / Expected Impact
What I'd Measure
Next Steps
- →Classroom dashboard for administrators to track regulation patterns
- →School district integration and bulk licensing
- →Teacher-specific stress monitoring and intervention tools
PNEUOMA Capture
↗Voice-first incident documentation for educators
Problem
Teachers and administrators lose hours each week to manual incident documentation. MTSS and behavioral reporting systems require extensive typing, form-filling, and context-switching — pulling educators away from students. Documentation gets delayed, quality drops, and behavioral patterns go undetected.
Insight
Speech is the fastest input modality humans have. Teachers already verbally describe incidents to colleagues in hallways — they just aren't capturing that information in structured form. The data exists; the capture method is wrong.
Solution
A voice-first documentation tool where teachers speak what happened and AI converts it into structured, exportable incident reports. No typing, no forms, no training — speak and submit in under two minutes.
Environment
Educators losing hours weekly to manual documentation
Friction
Typing-based forms are slow, frustrating, and get skipped
System
Voice → AI-structured incident reports in under 2 minutes
Outcome
More reports, better data, earlier pattern detection
Key Decisions
Hardest Product Decision
Choosing a privacy-first AI architecture instead of faster cloud-based transcription services.
Why
Standard cloud AI tools would have been significantly easier and faster to build with. But student behavioral data requires strict compliance and district trust. A privacy-first approach increased development complexity and limited some AI capabilities, but it protected sensitive student information and made district-level adoption viable — which is the only adoption that matters in education.
Impact / Expected Impact
What I'd Measure
Next Steps
- →MTSS system integration for seamless compliance workflows
- →Behavior pattern analytics surfaced to administrators automatically
- →District-level reporting dashboards for cross-school visibility
Playground
Learning objectives embedded inside open play
Problem
Parents want children to learn while playing. But the market is split: pure entertainment games with no learning outcomes, or rigid educational software that kills engagement within minutes. No product successfully merges deep play engagement with measurable learning at scale.
Insight
Children engage deeply with open play environments like Minecraft — not because of the content, but because of the agency. The engagement problem isn't about what to teach; it's about who controls the experience. When teachers can embed objectives inside play without breaking flow, learning happens naturally.
Solution
An open educational game where teachers define learning tasks — math challenges, spelling quests, problem-solving missions — that surface as gameplay objectives. Students experience play; teachers steer learning outcomes through configurable content.
Environment
Kids disengage from rigid educational software within minutes
Friction
Learning tools sacrifice engagement; games sacrifice outcomes
System
Teacher-defined learning objectives embedded inside open gameplay
Outcome
Sustained play engagement with measurable learning progress
Key Decisions
Hardest Product Decision
Keeping the game open-ended rather than building a tightly structured linear curriculum.
Why
Structured curricula are easier to build, easier to sell to schools, and easier to measure. But educational games consistently fail because they feel like assignments. An open-ended environment required building a flexible content system instead of a simple sequence — significantly more complex — but preserved the play engagement that makes the product viable at all.
Impact / Expected Impact
What I'd Measure
Next Steps
- →Teacher content marketplace for peer-created learning objectives
- →AI-generated learning quests aligned to curriculum standards
- →School district pilot programs with outcome measurement
DIBBS Copilot
A quoting treadmill for DLA medical solicitations
Problem
DLA medical solicitations arrive as dense PDFs containing NSNs, line items, due dates, and compliance requirements. Buyers and contractors manually extract this data, track opportunities across stages, reach out to suppliers, collect pricing, calculate margins, and format compliant quotes for DIBBS submission. The process is slow, error-prone, and requires constant context-switching between documents, emails, and spreadsheets.
Insight
The solicitation-to-quote workflow follows a repeatable pipeline: extract structured data, triage opportunities, source supplier pricing, build compliant quotes, and submit. Each stage has predictable inputs and outputs. The entire flow can be systematized into a single guided workflow that eliminates manual data extraction and keeps every opportunity moving toward submission.
Solution
Workflow software that turns solicitation PDFs into structured opportunities, guides supplier outreach with call scripts and draft emails, ingests supplier responses to fill pricing and lead time, builds quotes with margin and freight calculations, and outputs DIBBS-ready text. Opportunities flow through clear stages — Need Line Item, Need Supplier Cost, Need MMS/Drop Ship, Quote Ready, Submitted — with stage-based next actions and shortcuts to keep flow.
Environment
DLA solicitations arrive as dense PDFs requiring manual processing
Friction
Multi-step quoting across extraction, sourcing, pricing, and compliance
System
Guided pipeline: PDF → structured data → supplier outreach → DIBBS-ready quote
Outcome
More quotes submitted faster with fewer errors and less context-switching
Key Decisions
Hardest Product Decision
Building a stage-based workflow engine instead of a simpler PDF-to-quote converter.
Why
A direct PDF-to-quote tool would have shipped faster and been easier to explain. But the real bottleneck isn't extraction — it's the multi-step process of triaging, sourcing, and building compliant quotes across dozens of simultaneous opportunities. A stage-based pipeline with guided next actions meant significantly more architecture, but it addressed the actual workflow problem: keeping every opportunity moving forward without losing track of where each one stands.
Impact / Expected Impact
What I'd Measure
Next Steps
- →Automated supplier matching based on NSN history and pricing patterns
- →Bulk solicitation intake for high-volume quoting periods
- →Win-rate analytics by supplier, NSN category, and margin tier
PilotEngine
↗Automated outreach and workflow orchestration
Problem
Outreach workflows — for sales, partnerships, recruiting, and fundraising — require repetitive manual effort: list building, personalization, sequencing, and follow-ups. Small teams can't compete with organizations that have dedicated ops teams, so they either burn hours on manual execution or send generic messages that don't convert.
Insight
Most outreach follows predictable sequences that can be templated and triggered automatically. The bottleneck isn't strategy — it's execution capacity. AI can handle personalization and sequencing at scale if the workflow logic is well-defined and human checkpoints are preserved.
Solution
An AI-powered outreach engine that automates list building, message personalization, multi-channel sequencing, and follow-up triggers. Users define the strategy and approval gates; PilotEngine handles the execution volume.
Environment
Small teams can't scale outreach without dedicated ops
Friction
Manual personalization and follow-ups consume hours daily
System
AI-orchestrated multi-channel sequences with human checkpoints
Outcome
Enterprise outreach capacity for lean teams, measurably
Key Decisions
Hardest Product Decision
Building a general-purpose workflow engine instead of a narrow, vertical sales outreach tool.
Why
A focused sales product would have shipped faster and been easier to position. But outreach patterns are nearly identical across sales, recruiting, partnerships, and fundraising — the workflow logic is the same, only the context changes. Investing in a flexible orchestration layer meant slower initial delivery and more complex architecture, but created a product that serves multiple use cases without rebuilding.
Impact / Expected Impact
What I'd Measure
Next Steps
- →CRM integration layer for bi-directional data sync
- →AI-generated campaign strategies based on ICP and historical performance data
- →Analytics dashboard for outreach performance and conversion attribution
Veluna
↗Not a period tracker — a regulation system for the menstrual cycle
Problem
Most menstrual health apps are basic period trackers — they log dates and predict the next period. They don't address the fact that the menstrual cycle affects energy, mood, creativity, and decision-making across the entire month. Women are left managing symptoms reactively instead of working with their cycle proactively. Meanwhile, the apps that do exist often sell user data or require accounts that compromise privacy.
Insight
The menstrual cycle has four distinct phases, each with different physiological and cognitive characteristics. If you frame each phase around its strengths — not just its symptoms — cycle awareness becomes a regulation system, not a burden. And if you pair that awareness with guided breathing protocols and actionable daily guidance, you move from tracking to actual support.
Solution
A privacy-first cycle companion that goes beyond tracking. Veluna provides smart predictions with confidence levels, phase-specific breathing protocols with haptic guidance, daily affirmations and superpower framing for each phase, comprehensive symptom and sensation logging, educational content on cycle science, and exportable PDF reports for healthcare providers. All data stays on-device — no accounts, no servers, no data selling.
Environment
Women manage cycle impacts reactively with basic tracking apps
Friction
No tool connects cycle phases to energy, mood, and actionable regulation
System
Phase-aware companion with predictions, breathing protocols, and daily guidance
Outcome
Daily engagement and proactive cycle management, not just period logging
Key Decisions
Hardest Product Decision
Designing the app as a regulation system rather than a feature-rich period tracker.
Why
The market is saturated with period trackers that compete on features — more symptoms to log, more charts to view, more social features. Adding more tracking surface area would have been the obvious play. Instead, I focused on regulation: breathing protocols mapped to cycle phases, superpower framing that changes daily guidance, and a companion layer that supports rather than just records. This meant building multiple engines (cycle intelligence, regulation protocols, meaning framing, affirmations) instead of a single logging system — but it creates a product that women actually open daily, not just when their period starts.
Impact / Expected Impact
What I'd Measure
Next Steps
- →Expanded premium affirmation and ambient music library
- →Moon phase integration for holistic cycle awareness
- →Community-driven symptom pattern insights (anonymized, opt-in)
Product Ecosystem
Everything I've Built
Mobile App
Health / Education
60-second nervous system regulation with haptic breathing
AI Tool
AI / Education
Voice-to-structured-report incident documentation
Game
Education / Gaming
Open play environment with teacher-defined learning objectives
Workflow Tool
AI / Gov Procurement
Solicitation-to-quote pipeline for DLA medical procurement
Automation Platform
AI / Sales
Multi-channel outreach orchestration and workflow automation
Mobile App
Productivity
Personal operating system for daily structure and clarity
Strategy Game
Gaming / Education
Civilization-building strategy game spanning seven historical eras
Platform
AI / Education
Unified operating system connecting regulation, documentation, and workflow tools
Internal Tool
AI / Operations
Automated prospecting and personalized email generation pipeline
Mobile App
Health / Women's Wellness
Privacy-first menstrual cycle companion with regulation protocols and smart predictions
Dashboard
Education / Data
Learning progress visualization and intervention tracking for educators
How I Build
Product Philosophy
Every product I build starts with the same question: where are people losing time, attention, or clarity because the system around them wasn't designed for how they actually work?
My years inside schools taught me that the people closest to problems — teachers, administrators, students — are operating under constraints that software rarely accounts for. They don't have 20 minutes to learn a new tool. They don't have bandwidth to configure dashboards. They need something that works in the next 60 seconds, under stress, with zero onboarding.
That constraint-first thinking shapes everything I build. I scope tight, ship fast, and measure whether the product actually reduced the friction it was designed to address. If it didn't, I cut features — not add them.
Product Principles
Real-World Usage
Products in the Wild
These aren't concepts. They're systems used by educators and school leaders in real operational workflows.
Regulation tools designed for real classroom transition windows — used by teachers between classes
Voice-based documentation tools that let educators submit incident reports in under two minutes
AI copilots built around real MTSS and behavioral documentation workflows
Outreach orchestration systems used internally to manage multi-channel partnership campaigns
Mobile apps shipped to the App Store and actively used for breathing, grounding, and focus
Exploration
Rapid Product Experiments
In addition to larger systems, I regularly run small product experiments to explore new workflows, AI capabilities, and user behaviors. These experiments help identify opportunities quickly before investing in full product builds.
AI documentation assistant for behavioral incident reporting
AI outreach agent for partnership discovery
Automated government contract quoting workflow
Teacher workflow simplification tools
Educational game prototypes with embedded learning objectives
Voice-to-structured-data pipelines for school environments
What I Want to Work On
Problems I'm Interested in Solving
I'm drawn to product roles where the core challenge is reducing friction inside systems that people depend on daily — especially where the constraints are real and the stakes are operational.
Tools that help people operate under real-world constraints — time, attention, regulation, and cognitive load
AI products that remove overhead from workflows, not add complexity to them
Systems that improve decision-making speed and clarity in high-pressure environments
Education technology that supports teachers and administrators rather than creating more administrative burden
Platforms that translate complex human behavior into structured, actionable insights
Currently open to
Collaboration
How I Work With Teams
I operate at the intersection of research, design, and execution — moving between user environments and build cycles to keep products grounded in real needs.
Camryn Jackson
Product Builder · Founder @ PNEUOMA · 0→1 Systems Designer
If you're building systems that help people make better decisions under real-world constraints, I'd love to talk.