00 / Proof

    Numbers, not adjectives.

    Case 01 · Fractional CIO

    From 14 spreadsheets to one decision surface.

    A mid-market logistics company was running strategic decisions through fourteen disconnected spreadsheets. In 90 days, we consolidated reporting into a single governed surface — recovering 120+ executive hours per month and unblocking a capital-allocation decision that had stalled for two quarters.

    Read the case study
    90d
    Time to value
    14→1
    Decision surfaces
    3.1×
    Reporting velocity
    $1.8M
    Capital unblocked
    01 / Services

    Three ways of working.

    Each one ends with something you can measure.

    No 01 — Fractional CIO/CTO

    The function, before the headcount.

    Embedded executive leadership for mid-market companies: roadmap, vendor posture, hiring plan, and a data estate someone can actually be accountable for.

    90-day engagements · 2-3 days/week
    No 02 — Data & AI Strategy

    Numbers as evidence, not adjectives.

    Strategy engagements that end in shipped infrastructure — not a deck. Build-vs-buy calls, platform selection, and the governance to keep it honest.

    4-8 week sprints
    No 03 — Anuba Technologies

    Building the product side.

    Co-founder and CIO. Anuba is where the consulting patterns become software — the proving ground for everything the practice recommends.

    anubatechnologies.com
    02 / Background

    The operator’s arc.

    Enterprise rigor at startup velocity.

    Experience

    Twenty years inside enterprise complexity — Razorfish/Publicis serving Stellantis, Marriott, Samsung, Bridgestone, Southern Glazer’s. Today: CIO of a venture-backed startup.

    Outcomes

    Architected analytics that scaled a B2B platform from $100M to $1.4B+ in 18 months (Southern Glazer’s). Two provisional patents at Anuba. A track record of shipping infrastructure, not decks.

    Operating philosophy

    Numbers are evidence, not adjectives. Build-vs-buy is usually a staffing question. A fractional executive should leave well — with runbooks, a hiring plan, and a system someone else can be accountable for.

    Location

    Miami, FL. Remote-first practice; on-site where the work requires it.

    03 / Process

    Discovery to handover.

    01

    Discovery

    A 30-minute call to scope the question. No pitch deck — just the one workflow costing the most executive hours.

    Day 0
    02

    Diagnostic

    Two weeks on the floor. Every workaround logged, every system inventoried. One governing metric identified.

    Weeks 1-2
    03

    Sprint

    Build the spine, ship the surface. Ugly on day 45, iterated weekly with the desk. Adoption before polish.

    Weeks 3-10
    04

    Handover

    Hiring plan, runbooks, and a data engineer recruited and onboarded. The point of fractional is leaving well.

    Weeks 11-12
    Available · Q3 2026

    One engagement slot open per quarter. Book a discovery call to discuss timing and fit.

    Available · Q3 2026

    Let’s find the signal.

    Book a 30-minute diagnostic call. No pitch deck — just the one workflow that’s costing you the most executive hours per month.

    Book a discovery call