Category: CFO Insights

  • The Evolution of an AI-Powered CFO Workflow

    The Evolution of an AI-Powered CFO Workflow

    Six weeks ago, I gave my AI assistant £500 and access to my calendar. Not as an experiment — as infrastructure. Here’s what happened.

    —

    ## The Morning Drive Changed Everything

    Every morning at 6:30am, before I’m even awake, my AI assistant (Saul) generates a custom podcast. By the time I’m in the car, it’s waiting.

    Not a generic news summary. A 12-minute audio brief built specifically for me:
    – **Market moves** that matter for PE-backed businesses (not retail noise)
    – **Regulatory updates** from HMRC, Companies House, FRC (the stuff that lands on CFO desks)
    – **Macro context** (why oil spiked, what the Fed actually said, geopolitical risk that affects deals)
    – **Rhetoric lesson** — a different persuasion technique each day from Aristotle to Cialdini

    Two AI voices (James and Claire) present it like a real podcast. Natural conversation, not robotic TTS. It sounds professional enough that I’ve accidentally played it on speaker in front of colleagues who thought it was BBC Business.

    **Why this matters:** I arrive at client sites already briefed. No scrambling through headlines in the car park. No missing the context behind a CEO’s question about currency risk or supply chain disruption.

    The Morning Brief isn’t a nice-to-have. It’s become load-bearing infrastructure. When it failed one morning (rhetoric bug — LLMs need very explicit constraints), I noticed immediately. That’s when you know automation works: when its absence creates friction.

    —

    ## From Chaos to Clarity: The Contact Problem

    I had 3,183 contacts scattered across iCloud and Microsoft 365. Duplicates everywhere. Same person listed three times with different phone numbers. Dead email addresses next to current ones. The digital equivalent of a drawer full of business cards.

    Manual cleanup would have taken weeks. I’d done it before — brutal, mind-numbing work. This time: “Saul, fix this.”

    **What happened:**
    – 1,514 iCloud-only contacts imported to M365
    – 1,669 conflicts merged intelligently (kept superset data, detected different people with same names)
    – 32 kept separate (legitimate duplicates — two “John Smiths” in different companies)
    – 94% success rate, under an hour

    Now my iPhone uses M365 as single source of truth. No more guessing which contact is current. No more duplicate meeting invites. One database, one workflow, zero manual reconciliation.

    **The lesson:** AI doesn’t just automate tasks. It cleans up the mess you’ve been procrastinating for years.

    —

    ## The Sunday Reset: GTD on Autopilot

    Every Sunday at 6pm, Saul runs a Getting Things Done (GTD) review. Not because I ask — because it’s scheduled infrastructure.

    **What it does:**
    – Reviews all open projects (IRIS migration, Crisis Hedge Builder, ebook)
    – Checks waiting-for items (LinkedIn API approval, client responses)
    – Surfaces stale tasks (>7 days with no progress)
    – Prompts next actions for the week ahead
    – Updates project statuses automatically

    David Allen‘s GTD methodology is brilliant. The problem? It requires discipline. Weekly reviews are the first thing to slip when you’re busy.

    **Solution:** Delegate the discipline to AI.

    Saul doesn’t forget. Doesn’t get tired. Doesn’t skip the review because it’s been a long week. Every Sunday at 6pm, the review happens. I get a structured report: what’s stuck, what needs attention, what can close.

    **The result:** My Todoist inbox stays at zero. Projects move forward. Nothing falls through the cracks.

    This isn’t just task management. It’s forcing function for strategic thinking. When an AI assistant asks “What’s the next action on the Crisis Hedge Builder?” you can’t handwave. You have to answer concretely. That clarity compounds.

    **The lesson:** Automation isn’t just about saving time. It’s about enforcing good habits you’d otherwise skip.

    —

    ## Crisis Trading: From Manual to Automated

    When the Iran war started in late February, I manually built a hedged portfolio in 30 minutes: oil futures, defence stocks, currency positions, Polymarket prediction markets. Four out of five legs printed. Oil went from $70 to $118.

    Good trade. But not scalable.

    Now we’re building the system that does it automatically:

    **1. Event Classifier**
    Headline → crisis type (geopolitical / macro / black swan) → affected markets → urgency assessment

    **2. Market Finder**
    Queries Polymarket API, filters by liquidity and time horizon, LLM ranks markets by direct impact + correlation + second-order effects

    **3. Portfolio Constructor** (in progress)
    60% core thesis / 30% correlation plays / 10% hedge. Automatic position sizing, budget controls, stop-loss logic.

    **Not live yet** — we’re in build phase (Week 1 of 3). But the infrastructure is real. When the next crisis hits, the system responds in minutes, not hours.

    **Why a CFO cares:** Geopolitical risk isn’t abstract anymore. It’s in your FX exposure, your supply chain, your credit facility covenants. Having a system that maps events to financial impact — instantly — is a competitive edge.

    —

    ## What Doesn’t Work: The Ollama Lesson

    Not everything succeeds. I tried running a local LLM (Ollama, Llama 3.2) on my VPS to cut API costs. Installed it, configured it, tested it.

    **Result:** 25+ seconds per query. Unusable.

    **Root cause:** Shared VPS CPU is throttled. Local inference needs sustained compute. Cloud APIs (Claude, OpenAI) are worth paying for.

    **The lesson:** Performance matters more than theoretical cost savings. A few extra pounds for speed beats “free” but slow. This applies to finance systems too — penny-wise, pound-foolish automation wastes more than it saves.

    We removed Ollama within 24 hours. No sunk cost fallacy. Test fast, decide fast, move on.

    —

    ## Infrastructure Lessons: When AI Breaks

    Your AI assistant will break things. The question is: do you catch it in minutes or days?

    **Example 1: File corruption**
    Saul was overwriting config files without reading them first. Guessing at structure from memory instead of checking. Silent failures that surfaced days later.

    **Fix:** One rule in AGENTS.md: “Before running any command that modifies files, read the file first. Never assume contents.”

    Error rate dropped 50% overnight.

    **Example 2: Prompt repetition**
    The Morning Brief repeated the same rhetoric lesson four days straight despite tracking it. Root cause: LLMs ignore soft instructions like “don’t repeat this.” They need explicit constraints: “You MUST use this exact topic, NOT that one.”

    Changed the prompt. Problem solved.

    **The pattern:** AI needs guardrails. Not vague suggestions. Hard rules. Read-before-write. Explicit topic selection. Budget caps. Error logging.

    This isn’t prompt engineering. It’s system design.

    —

    ## What’s Next

    **Short-term (this week):**
    – Fix VPN routing (currently blocking all Polymarket trading)
    – Finish Crisis Hedge Builder portfolio constructor
    – Deploy Gateway Health Monitor (automated system checks, conservative auto-repair)

    **Medium-term (next month):**
    – Full automation of crisis portfolio system
    – Polymarket volatility scalping (short-term mean reversion trades)
    – Daily blog automation with SEO linking strategy

    **Long-term:**
    – Multi-device Mission Control dashboard (monitor agent fleet from phone)
    – On-chain flow scanner (track smart money wallet movements)
    – Second-order trade mapper (find derivative effects crypto Twitter misses)

    This isn’t a side project. It’s infrastructure. The Morning Brief alone saves 30 minutes every day. The contact cleanup saved 20 hours of manual work. The crisis trading system will respond to events faster than I can manually.

    **Compound that over a year.** Over five years.

    —

    ## For Finance Leaders: What This Means

    You don’t need to be technical to do this. I’m not a developer. I’m a CFO who got tired of manual workflows.

    **What you need:**
    – Willingness to delegate to AI (start small: email triage, calendar summaries)
    – Tolerance for iteration (things will break; fix them and move on)
    – Clear rules (read AGENTS.md, write down how you want things done)
    – Budget discipline (set spending caps, monitor API costs)

    **What you get:**
    – Time back (hours per week, compounding)
    – Better decisions (context you’d otherwise miss)
    – Scalable operations (systems that work while you sleep)
    – Competitive edge (faster response to market events)

    The question isn’t “Should I automate my workflow?”

    It’s “How much am I losing by not automating it?”

    —

    ## The Morning Brief Test

    Here’s how you know if AI automation is working:

    **Bad automation:** You check if it ran.
    **Good automation:** You notice when it doesn’t.

    The Morning Brief is good automation. When it’s there, I don’t think about it. When it’s missing, I feel the gap.

    That’s the bar. Build systems that become load-bearing. Everything else is just novelty.

    —

    **Mark Hendy**
    Interim CFO | AI-Powered Finance Operations
    [LinkedIn](https://linkedin.com/in/markhendy) | [Blog](https://markhendy.com)

    —

    *Running your own AI assistant? Want to compare notes? Email me at mark@tanous.co.uk — always happy to talk shop with finance leaders building real automation.*

  • Teaching My AI Agent to Trade Prediction Markets

    Teaching My AI Agent to Trade Prediction Markets

    One of the first things I wanted to test with Saul — my AI assistant running on OpenClaw — was whether it could interact with decentralised finance. Not as a gimmick, but as a genuine test of capability. Could an AI agent, running autonomously on a virtual private server I’d spun up a couple of weeks earlier, navigate the full complexity of connecting to a blockchain-based prediction market and execute trades?

    The answer is yes. But the journey to get there was far more interesting than the destination.

    The Goal

    Polymarket is a prediction market built on the Polygon blockchain. You buy shares in outcomes — political events, economic indicators, geopolitical developments — and if you’re right, you get paid. It’s essentially a real-money forecasting platform, and it’s become one of the most liquid prediction markets in the world.

    I wanted Saul to be able to check positions, analyse markets, and eventually place trades. Autonomously.

    The First Problem: Geography

    Polymarket is geo-blocked in the UK. You can’t access it from a British IP address. So before Saul could do anything useful, we needed to solve the networking problem.

    Saul set up a WireGuard VPN tunnel on a virtual private server, routing through an exit node in Ireland. Within minutes, the geo-restriction was bypassed. This wasn’t me configuring network infrastructure — this was Saul reading documentation, writing configuration files, testing connectivity, and troubleshooting until it worked.

    For a CFO reading this: imagine asking your assistant to “sort out the VPN” and having it done before you’ve finished your coffee. That’s what this felt like.

    The Second Problem: Money

    Polymarket runs on USDC — a dollar-pegged stablecoin on the Polygon network. I started with Bitcoin. Getting from BTC to USDC on Polygon is not trivial. It involves:

    1. Finding a cross-chain swap service that supports BTC-in, Polygon-USDC-out
    2. Generating the right wallet addresses
    3. Sending the Bitcoin transaction
    4. Waiting for confirmations
    5. Verifying the USDC arrived on the correct network

    Saul handled the entire process. It researched swap services, compared rates, initiated the transaction, monitored the blockchain for confirmations, and tracked the funds until they landed in the Polygon wallet. The whole thing took about an hour, most of which was waiting for Bitcoin network confirmations.

    The Third Problem: Authentication

    Polymarket uses a non-trivial authentication system. It’s not a simple API key. The platform requires cryptographic signatures using your Ethereum private key, combined with specific API credentials that need to be derived through an on-chain registration process.

    This is where things got genuinely impressive. Saul had to:

    • Read and understand Polymarket’s API documentation
    • Implement the correct signing mechanism using the wallet’s private key
    • Handle the CLOB (Central Limit Order Book) authentication flow
    • Generate and manage API credentials
    • Debug authentication failures by inspecting HTTP responses and adjusting the approach

    There were multiple rounds of troubleshooting. Authentication errors. Wrong parameter formats. Library compatibility issues. Each time, Saul diagnosed the problem, researched the fix, and tried again. No human intervention required beyond “yes, keep going.”

    The Fourth Problem: Actually Trading

    Once authenticated, Saul built a trading script that could:

    • Check current positions and P&L
    • Query available markets
    • Calculate optimal order sizes based on risk parameters I’d set
    • Place and monitor trades

    We established simple rules: maximum position sizes, probability thresholds for entry, and risk limits. Saul follows them without the emotional biases that make human traders do stupid things at 2am.

    What This Actually Demonstrates

    This isn’t really a story about prediction markets. It’s a story about capability.

    An AI agent, running on commodity hardware, navigated VPN configuration, cross-chain cryptocurrency transactions, complex API authentication, and automated trading — all within a few hours of being asked. Each step involved genuine problem-solving, not just following a script.

    For those of us in finance, this should be both exciting and sobering:

    Exciting because the operational grunt work — the data gathering, the reconciliation, the monitoring, the reporting — is genuinely automatable now. Not in five years. Now.

    Sobering because the barrier to entry is collapsing. The technical moat that used to protect specialist knowledge is being bridged by systems that can learn and execute faster than any individual.

    The CFO Angle

    I keep coming back to this: the competitive advantage isn’t in understanding the technology. It’s in having the imagination to deploy it.

    Most people hear “AI agent trading on prediction markets” and think it’s a tech story. It’s not. It’s a story about removing friction between intent and execution. I said “connect to Polymarket.” Everything else was handled.

    That same pattern applies to every operational challenge a CFO faces. Due diligence data rooms. Financial model automation. Regulatory monitoring. Competitor analysis. The question isn’t whether AI can do these things. It’s whether you’re willing to let it try.

    The agents aren’t coming. They’re here. The only question is who’s using them.

  • I Gave My AI Assistant Access to My Email, Calendar, and Financial Data

    I Gave My AI Assistant Access to My Email, Calendar, and Financial Data

    Less than two weeks ago, I deployed an open-source AI agent called OpenClaw. I named it Saul. It runs 24/7 on a local server, connected to my inbox, calendar, task manager, and various APIs. It reads my emails, flags what matters, schedules reminders, monitors news, and handles admin I used to lose hours to every week.

    I’m an interim CFO. I work with PE-backed businesses. My job is to walk into a company I’ve never seen before and get to grips with it fast. Every hour I spend on admin is an hour I’m not spending on the thing I was actually hired to do.

    So here’s what’s changed:

    Email triage is gone. Saul reads my inbox, filters the noise, and surfaces what needs attention. I had 94 recurring junk senders — he purges them automatically every Sunday at 2am.

    I never miss a deadline. Tax renewals, MOT dates, contract milestones — Saul tracks them all and nags me weekly until I confirm they’re done. Not a calendar entry I’ll ignore. An actual message on WhatsApp that won’t stop until I act.

    Board prep is faster. When I need a quick market scan, competitor check, or data pull before a board meeting, I ask Saul. He searches, summarises, and writes it up. What used to take 90 minutes takes 10.

    And the thing nobody talks about: the cognitive load reduction. The mental bandwidth I used to spend remembering things, chasing things, organising things — that’s just gone. It’s like hiring a junior analyst who never sleeps, never forgets, and never needs managing.

    This isn’t science fiction. It’s not even expensive. The whole thing runs on about £50/month in API costs.

    Here’s what I’d say to other CFOs, particularly those in the PE world where speed matters:

    You don’t need to understand how LLMs work. You need to understand what they can do for you. The competitive advantage right now isn’t in the technology itself — it’s in the willingness to use it while everyone else is still debating whether it’s real.

    The CFOs who figure this out first will be the ones PE firms want on speed dial.

    I wrote a longer piece about the AI agent revolution here. But the short version is: this is not a fad, and the window to be early is closing fast.