PHOENIX STRATEGIES

problem in. product out.

Send me a mess. We'll find the right answer together — not a bare-minimum bandaid. Get back a solution that runs on its own and evolves with you.

you made it!

what are we building today?

No matter what brought you here, you’re in the right place. Need a take on where AI fits, a thing built or connected to another thing, or just want to see what I’ve been making? I can help. Browse the pages below, and reach out when you're ready.

OPERATING THESIS

the model is the easy part.

AI building is everywhere right now. But the hard part usually is not model selection or even building with AI tools. The hard part is deciding how to apply it. My thoughts? There's no one-size-fits-all answer.

AI where it helps.
Operator judgment where it matters.
Boring software where the answer can't be wrong.

Yes, there is value in embracing AI for almost any business. My job is helping you get the shape right: what should be automated, what should stay human, where the facts need to be deterministic, and what kind of system the team will actually trust and use. Where that work usually breaks out:

OPSMAP THE REAL WORKFLOW
AUTOMATIONCHOOSE WHAT RUNS ITSELF
ANALYTICSMAKE THE FACTS VISIBLE
PRODUCTSHAPE THE USABLE SYSTEM
TECHSHIP THE LEVERAGE
AI WHERE IT HELPS

Language, ambiguity, and judgment support.

Use the model for the things models are weirdly good at: classifying messy messages, drafting vendor replies, interpreting ambiguous memos, searching policy docs, summarizing legal news, proposing mappings, or explaining why something looks off.

  • classification and triage
  • drafting and summarization
  • semantic search and RAG
  • edge-case review and anomaly flags
BORING SOFTWARE WHERE IT HAS TO WORK

what needs to be boring, deterministic, and right.

Facts. State. Permissions. Proof. Payment status comes from Stripe — not from a model that's pretty sure. Customer state comes from Salesforce. Access comes from your permissions system. The output ties back to source data. Use code for the parts that can't be fluently wrong.

  • API lookups and source-of-truth data
  • structured workflows and review queues
  • retries, idempotency, audit logs
  • dashboards, exports, and handoff docs
FIELD NOTE FROM A RECENT CLIENT CALL
“The answer is yes. The work is figuring out how.”

AI can almost definitely help. The mistake is assuming that means “add a model” or “launch an agent.” The real work is deciding what to automate, what to keep human, what data has to be trusted and deterministic, and how to make the whole thing useful enough for a team to rely on come Monday morning.

LET’S FIGURE OUT HOW →