Projects & Systems
Selected works in automation, infrastructure design, and marketing technology.
Last updated: May 2026
Even the best strategy needs reliable infrastructure. These are the systems I built to solve problems I kept running into.
GetViajo.com
This platform is my primary R&D Lab. I chose the high-volume niche of language learning because it offers the perfect level of complexity to stress-test marketing infrastructure in a live environment.
It serves as a live production environment for my methodology. The platform runs on three proprietary engines I engineered: an enterprise-grade analytics pipeline, an AI content workflow that eliminates hallucinations, and a secure digital asset network to protect revenue.
Helios Console (Local AI Studio)
Standard AI chatbots forget your rules the moment you close the tab. After months of manually re-uploading strategy documents and watching my documentation drift out of sync with my decisions, I built a local-first tool to fix it.
Helios connects to Gemini's API but runs entirely on my local machine. It maintains persistent memory of my project blueprints and lets me swap between specialized "personas" to stress-test ideas. Most importantly, it can read AND write directly to my local files, so my source of truth updates the moment I make a decision.
I use it daily to manage the documentation for GetViajo.com and my other projects.
The Content Factory
AI hallucinations are a business risk. To mitigate this, I built a proprietary AI content workflow that functions as a "credibility-first" engine. It performs verifiable, journalistic research *first*, then grounds all text and arguments in those citable sources.
This is a complete 'idea-to-publish' configuration. After using a fine-tuned GPT model to draft the content, the workflow leverages a custom-built scheduler. This removes external dependencies and gives me programmatic control over the distribution queue.
This enforces total autonomy. A custom CRON job scans the local file system every 15 minutes, identifies scheduled content, and automatically deploys it via API. This creates a 'set-and-forget' pipeline that decouples content creation from distribution mechanics.
Headless SEO CMS
After 8 years of cleaning up messy internal link structures for clients, I decided to solve the problem before it started. I built a headless CMS using Obsidian that visualizes the structural health of my site's links in real-time.
The setup uses Obsidian's graph view as a live map of my topic clusters, with custom dashboards that flag orphaned pages, dead ends, and content that needs refreshing. At build time, Astro resolves all the internal wikilinks into SEO-friendly URLs automatically, so I can reorganize categories or rename files without breaking a single link.
The result: I can publish content indefinitely without ever worrying about link rot or crawlability issues. No more reactive audits.
Markdown to Email Converter
I identified a recurring friction point in the publishing workflow: converting my Markdown articles into email-safe HTML for newsletters. The manual process was tedious and the results were inconsistent.
So I built a tool to fix it. This public-facing utility (hopefully) demonstrates strategic product thinking. Its core feature is an intelligent truncation engine that proactively calculates final email size to prevent client-side clipping in platforms like Gmail—solving a problem many marketers don't know they have until it's too late.
Offline Flashcards App
Mobile retention relies on habit formation. To reduce friction for users with unstable connectivity, I engineered a Progressive Web App (PWA) with an 'Offline First' architecture.
It loads decks directly from a Google Sheet endpoint, enabling user-generated decks via a simple spreadsheet interface. The app is context-aware, providing intuitive keyboard shortcuts on desktop and a native app-like experience when saved to a mobile home screen.
Help With Your Hustle (2017-2024)
For eight years, I ran an SEO/Content Marketing consultancy. Inside dozens of businesses, I observed the same pattern: companies hired me to drive traffic, but they struggled to convert it because of disconnected tools and manual workflows.
That friction inspired my pivot. I closed the agency to focus on the engineering side. Now, I build automations that generate traffic and the analytics pipelines that guide decisions. The goal is to prove that with better infrastructure, you can do more with less.
Interested in discussing the thinking behind any of this? I'm always open to swapping notes on infrastructure and strategy with fellow builders.
For Systems Thinkers
Get (occasional) insights on marketing infrastructure, automation, and the reality of building in public.