Built on Systems Thinking. Focused on Real Outcomes.
FiCelia Labs was founded on a simple idea: Most AI implementations fail—not because the technology isn't powerful, but because it isn't applied correctly.
Many organizations experiment with AI tools, but those tools rarely connect to real workflows, real data, or real business needs.
The result is minimal impact.
At FiCelia Labs, we take a different approach.
We design and build Operational AI Systems—systems that are embedded into how work actually gets done.
What Makes This Different
We don't focus on prompts. We focus on systems.
This is the difference between experimentation and implementation.
Technical Foundation
Founder Background
FiCelia Labs is built on a deep technical foundation—not just AI enthusiasm. Years of rigorous training in computational systems, mathematics, and engineering inform every solution we create.
Cornell University
M.S. Computational Fluid Dynamics
Advanced study in numerical methods, computational systems, and simulation engineering. Built complex solvers from the ground up.
Physics & Chemistry
Scientific Foundation
Deep understanding of physical systems and their mathematical representations. This foundation shapes how we model complex processes.
Applied Mathematics
Rigorous Problem Solving
Training in numerical analysis, optimization, and algorithm design. Mathematical rigor informs every system architecture.
Complex Systems
Engineering Experience
Years of experience building production systems that handle real-world complexity. From numerical solvers to AI pipelines.
Evolution to AI Systems
Foundation
Physics, chemistry, and applied mathematics background
Graduate Research
Computational Fluid Dynamics at Cornell—building simulation systems
Systems Building
Production software development and complex system architecture
AI Transition
Applying systems engineering to AI workflows and operational systems
From Engineering to AI Systems
A Natural Evolution
The transition into AI wasn't about chasing trends—it was a natural extension of systems thinking.
Over time, I've built:
These systems are designed to do more than generate outputs—they are designed to operate.
Real-World Experience
Teaching & Working with Real Users
Beyond engineering, years of teaching experience have shaped how we approach system design. Working directly with students and learners provides constant feedback on what actually works.
Robotics & AI
Teaching students how to build, program, and deploy robotic systems with integrated AI components.
AP Business / Personal Finance
Practical financial literacy and business fundamentals—making complex concepts accessible and actionable.
Project-Based Learning
Emphasis on hands-on projects where students build real systems, not just study theory.
How This Informs Our Systems
Teaching isn't just a background—it's a design philosophy. Every system we build reflects what we've learned about how people actually interact with technology.
Usability First
Systems must be intuitive. If users struggle, the system fails—no matter how sophisticated the technology.
Clarity Over Complexity
The best interfaces hide complexity while exposing capability. Users should understand what they can do instantly.
Real-World Application
Every system must solve an actual problem. Theoretical elegance without practical value is worthless.
Iteration & Feedback
Systems improve through use. Building for real users means building for continuous refinement.
Evolution & Learning
Early AI Systems & Interfaces
Before building Operational AI Systems, we spent years exploring how users interact with AI. These early systems formed the foundation for everything we build today.
AI Chatbot Systems
Built with Gradio
Early conversational AI interfaces that explored how users interact with language models. Learned what works—and what doesn't—in chat-based AI applications.
Key Learnings
- Conversation flow design
- Context management
- User expectation handling
Interactive AI Interfaces
Experimental Prototypes
Developed various interfaces for AI interaction beyond simple chat. Explored forms, structured inputs, and multi-step workflows.
Key Learnings
- Input validation patterns
- Progressive disclosure
- Error handling UX
User Interaction Research
Iterative Development
Studied how different user groups interact with AI tools. Built multiple iterations to understand what makes AI interfaces effective.
Key Learnings
- User mental models
- Feedback loops
- Trust building in AI
These experiments shaped our current approach
Every early system taught us something about building AI that works for real users. The failures were as valuable as the successes—they revealed what NOT to do.
Proof of Capability
Pestal: Our Operational AI System
Pestal is not just a product.
It is a demonstration of how we build AI systems.
It represents the same approach we bring to every client engagement—combining structured pipelines, intelligent interfaces, and human-AI collaboration into a cohesive operational system.
Pestal Combines
The Goal
What This Enables
The goal is not just to use AI. It's to improve how work gets done.
Faster Iteration
Move from idea to implementation quickly with systems designed for refinement.
Consistent Outputs
Structured systems produce reliable, repeatable results.
Scalable Workflows
Processes that work for one person scale across teams.
Human + AI Collaboration
AI becomes part of the workflow—not a separate tool.
Mission
To help businesses implement AI that actually works
We believe AI has enormous potential to improve how businesses operate. But that potential only becomes reality when AI is properly integrated into real workflows, connected to actual data, and designed to produce consistent, measurable outcomes.
Our mission is to bridge the gap between AI experimentation and operational value. We build Operational AI Systems that businesses can rely on—systems that drive efficiency, speed execution, and improve decision-making.