Jaime Daza

Available

Business Strategy & Analytics Leader

Turns ambiguous business problems into decision-ready analysis, scalable workflows, and measurable performance improvements. Built Python and n8n systems across a 25-location coffee chain with $3M in rotating inventory; now manages supplier operations, transaction reconciliation, and platform migration work at Odeko in DC.

AI AI Workflow Consulting Resume

Blitz

GitHub

DC Multilateral Jobs

dcmultilateraljobs.com

Live

Built and operate a Washington, DC job board for World Bank, IMF, IDB, PAHO, and OAS careers. Validates coverage across five official sources before publishing searchable listings, with qualification filters, direct employer links, and career guides.

Python SQLite JavaScript GitHub Actions Vercel GoatCounter

Blitz

blitzgroup.io

Live

Website for Blitz's web design and digital presence services. Presents business websites, professional email, and Google Business Profile setup, with service plans and a WhatsApp inquiry flow.

React Vite Tailwind CSS

ForecastHub

github.com/chipidaza23/ForecastHub

Open Source

Open-source demand forecasting dashboard with AutoARIMA and Seasonal Naive forecasts, prediction intervals, inventory reorder logic, and a natural-language inventory advisor.

FastAPI Next.js TypeScript StatsForecast Vercel

Spotify-To-Me

github.com/chipidaza23/Spotify-To-Me

Open Source

Python desktop app for turning Spotify playlists into tagged MP3 libraries for DJ software using yt-dlp. Playlist processing, including BPM and key tags, requires Spotify audio-features API access. Open source (MIT).

Python Pandas Spotipy yt-dlp CustomTkinter Mutagen FFmpeg

Jaime Daza

DC Multilateral Jobs

Blitz

ForecastHub

Spotify-To-Me

A Retry Needs New Evidence

A short operating note on why automation should retry only after the failure is classified and a relevant condition has changed.

A Recommendation Needs a Decision Rule

A short operating note on turning analysis into repeatable action with explicit decision rules, boundaries, and feedback points.

A Variance Is a Question, Not an Answer

A short operating note on turning mismatched records into decision-ready analysis by separating the signal from timing, definitions, and data quality.

A Forecast Is a Range, Not a Promise

A short operating note on turning forecasts into decisions by making uncertainty, assumptions, and response thresholds visible.

A Control Needs a Failure Path

A short operating note on designing controls that make failures visible, owned, and recoverable.

Access Is a Workflow

A short operating note on why access design needs a defined need, an approved role, a decision record, and a review trigger.

A Metric Needs an Owner

A short operating note on why a useful metric needs a definition, a source, an owner, and a response.

Ambiguity Needs a Ledger

A short operating note on why ambiguous work needs a visible owner, evidence, next action, and close condition.

The Operating Question Comes First

A short operating note on why analysis, reporting, and automation should start with the decision the business is trying to make.

Source of Truth Beats Memory

A short operating note on why fast-moving work needs one trusted source of truth before automation or reporting can help.

Make the Close Condition Visible

A short operating note on why good process work defines what closed means before work starts moving.

The Deadline Is a Design Tool

A short operating note on using deadlines to clarify decisions, dependencies, ownership, and the first reliable version of a system.

The Decision Record Is the Work

A short operating note on why useful decision records protect context, tradeoffs, and ownership after the meeting ends.

Migration Is Translation

A short operating note on why moving data into a new system is really translation between records, workflow, and trust.

The First Output Is a Test

A short operating note on why early automation output should be treated as evidence, not authority.

The Checkpoint Is the Product

A short operating note on why recurring checks are part of the system, not cleanup after the system ships.

Automate After the Walkthrough

A short operating note on why automation earns trust only after the team can explain the manual workflow.

The Constraint Is the Brief

A short operating note on why useful systems start with the real constraint, not the ideal workflow.

The Handoff Is the Process

A short operating note on why process quality shows up most clearly when work changes hands.

The Exception List Is the System

A short operating note on why useful process work starts with a clear list of exceptions, owners, next actions, and close conditions.

Dashboards Don't Fix Operations

A short operating note on why reporting only works after the team agrees what the numbers mean and how the underlying work gets recorded.

When the Phone Is the Business

Full project lifecycle — from a vague problem to a production IVR system, a vendor feature request that shipped, and a business that outgrew its own phone line.

You Can't Automate a Broken System

How I rebuilt trust in a drifting inventory system at Compass Coffee, then automated the workflow only after the numbers were reliable.

You Build It, You Own It

5 café buildouts on fixed deadlines with a two-person tech team — full network, POS, security, and equipment setup from scratch.

Automation & Scripting

Enterprise Systems

Web & Deployment

Infrastructure

Data & Reporting

Security & Risk

Languages