AI applied to the wrong problem is worse than no AI.

The AI hype cycle produces a predictable failure mode: organizations adopt AI because they feel they should, not because they've identified a specific problem where AI is the right solution. The result is AI systems that add complexity, cost, and unreliability to processes that worked fine before.

We've seen construction companies try to use GPT to replace estimators (it can't). We've seen schools try to use AI to replace teachers (it shouldn't). We've seen startups build LLM-powered features that could have been a database query.

The AI pillar exists to apply intelligence where it actually creates leverage — and to have the discipline to say "this doesn't need AI" when that's the honest answer.

Where AI creates real leverage.

AI is powerful when applied to specific, bounded tasks where the value of speed and scale outweighs the cost of occasional errors. These are the patterns we see across every industry:

Extraction

Pulling structured data from unstructured sources. Emails, documents, images, conversations. The bid manager extracts project names, deadlines, scopes, and material lists from free-form RFI emails — work that took a human 30 minutes per email.

Classification

Sorting inputs into categories at scale. >95% accuracy on email classification for the bid manager across hundreds of categories. The key is defining categories precisely and building evaluation pipelines that catch accuracy drift.

Summarization with traceability

Condensing information while maintaining source links. When the document analyzer summarizes a 40-page bid package, every claim cites the exact page and paragraph. Users trust summaries they can verify.

Pattern detection

Finding signals in noise. The Zoom tracker infers camera status from QoS bitrate patterns — a signal that exists in the data but isn't exposed by Zoom's API. AI detects what traditional logic can't express.

Intelligent matching

Connecting items based on nuanced similarity. The Merces app matches watch faces to camera-captured colors using color theory — complementary, analogous, triadic relationships that go beyond simple RGB distance.

Automation with guardrails

End-to-end process automation that knows when to stop and ask a human. The bid pipeline automates email → classification → extraction → filing, but flags low-confidence results for human review instead of guessing.

Every AI output should be traceable.

Black-box AI is a liability. When a system produces an output and nobody can explain why, the system can't be trusted, debugged, or improved. Traceability isn't a feature — it's a design requirement.

In our systems, every AI decision comes with provenance. The bid manager shows which email features triggered a classification. The document analyzer cites specific pages for every extracted data point. The knowledge graph tracks every source document for every node and relationship.

This isn't just about user trust — though that matters enormously. Traceability is how you debug AI systems. When classification accuracy drops, traceable outputs let you identify exactly which input patterns are causing failures. Without traceability, you're guessing.

When we recommend against AI.

Not every problem needs AI, and honest assessment of fit is part of every engagement. We recommend against AI in these situations:

When a regex works

If the input is structured and the rules are clear, a simple rule-based system is faster, cheaper, more reliable, and easier to maintain than an LLM call. A regex that works is better than an LLM that usually works.

When error tolerance is zero

AI systems have error rates. If the domain can't tolerate any errors — financial calculations, legal compliance, safety-critical systems — AI should augment human judgment, not replace it.

When data quality is poor

AI amplifies data quality. Clean data produces useful outputs. Noisy data produces confident-sounding garbage. We'd rather fix the data pipeline than build an AI system on top of broken data.

When the process is simple

Adding AI to a simple process creates complexity without value. If the workflow has 3 steps and clear rules, automate it with traditional tools. AI is for problems that resist simple automation.

Technology follows the problem.

We don't have a default technology stack. We have a problem-assessment process that selects the simplest tool that solves reliably. Across our projects, the tools include:

Large Language Models

Claude (Anthropic) OpenRouter

Used for classification, extraction, summarization, and document analysis. Model selection is task-specific — we benchmark candidates on real data before committing.

ML & Data Pipelines

Python FastAPI Flask

Core pipeline infrastructure. Python for data processing and model integration. FastAPI/Flask for serving predictions and managing API endpoints.

Orchestration & Automation

n8n Google Workspace APIs Zoom API

Workflow automation connecting AI components to real business tools. n8n for visual pipeline design. Direct API integration when precision matters.

Mobile & Frontend

Swift / SwiftUI React Firebase

The interface layer where AI meets users. Native mobile for performance-critical applications. React for web dashboards. Firebase for real-time data and cloud functions.

Where this comes from.

The AI pillar is built on an AI/ML concentration within the Computer Science degree from UNC Chapel Hill, plus over a decade as a Data Scientist. The academic foundation covers machine learning theory, statistical modeling, and algorithm design. The production experience covers everything the theory doesn't — data quality issues, model drift, evaluation at scale, and the gap between benchmark accuracy and real-world performance.

The progression matters: PC era → Data Science → Machine Learning → Modern AI. This isn't someone who discovered AI in 2023. It's someone who watched the field evolve from statistical models to neural networks to transformers to LLM agents — and who understands which techniques actually survive contact with production data.

The AI pillar is deliberately listed third, after CompSci and CogSci. Not because AI is least important — because it's most effective when it sits on a foundation of engineering rigor and human understanding. AI without CompSci breaks in production. AI without CogSci gets ignored by users. AI with both creates genuine leverage.

Let's apply AI where it creates real leverage.

We build AI systems that solve specific problems — not AI for AI's sake. Tell us about yours.

Start a Conversation