{
  "video": {
    "id": "gpmze-6ueGU",
    "title": "We Let Our Financial Planners Write the Agents — Matthew Ragone, Range",
    "duration": 534,
    "upload_date": null,
    "channel": "AI Engineer",
    "source": "AI Engineer",
    "event_format": ""
  },
  "analysis": {
    "video_id": "gpmze-6ueGU",
    "title": "We Let Our Financial Planners Write the Agents — Matthew Ragone, Range",
    "one_liner": "Range's non-engineer financial planners build their own Claude agent skills with a five-step method (pick, teach, pack, test, ship), and the key move is to write down the firm's judgment, the questions the agent must ask and its hard limits, not just the steps.",
    "summary": "Matt Ragone is a certified financial planner who leads AI adoption for the planning team at Range, an all-in-one wealth management company. He argues that a planner's real constraint is being in only one place at a time, not typing speed, so the value of agents is drafting work (like a cash flow or insurance analysis for one client) while the planner is on a call with another. A planner still reviews every recommendation before a client sees it. He lays out a no-code, five-step build guide for 'skills', which he defines as the firm's way of doing one specific piece of work, written down so an agent can follow it. He reports that six months in, Range has 24 skills, all written and maintained by non-engineers, and that adoption spread to other departments without any mandate.",
    "key_points": [
      "They started with AI as a chatbot (pasting in client messages to make them clearer or friendlier). It saved minutes, but the planner was still doing all the work manually, just a little faster.",
      "The real bottleneck is that a planner can only be in one place at a time. Agents now draft a full cash flow or insurance analysis for one client while the planner is on a call with another, and the planner reviews and adjusts the draft afterwards.",
      "Two things had to be true: the agent works where the work lives (not in a separate chat window you copy-paste into), and it knows how Range does the work, not how financial planning works in general.",
      "The five steps are pick, teach, pack, test and ship. None require writing code; all require knowing the work well, so the people doing the work should build the skills.",
      "Pick: don't choose the flashiest or most complex work. Choose something you do every week, where you know what good looks like and can spot a bad draft at a glance, ideally low complexity but high manual effort (for Range, cash flow analysis and insurance reviews).",
      "Teach and pack: walk several real past client cases start to finish, narrating your judgment out loud. Then pack it into a skill that defines the questions to ask before starting and the limits it must respect. The biggest limit: it never sends anything to a client.",
      "Test and ship: run it 5–10 times on real cases before anyone else sees it, fixing it after each run. Then ship it with an owner who keeps it current as processes and tax rules change, and a reviewer who is not the author.",
      "Six months in: 24 skills across the company, 17 of them in planning. They spread to sales, product and marketing without a mandate, and all are written and maintained by planners, marketers and salespeople rather than engineers. The skills became more specific, and peer review came naturally because planners already review each other's plans."
    ],
    "takeaways": [
      "Start with a frequent, low-complexity, high-manual-effort workflow whose output you can judge quickly. If you can't judge the output quickly, you can't test it or trust it.",
      "When teaching an agent, narrate the 'why' and what would make you stop and ask, not just the steps, because the judgment is what makes it your firm's work.",
      "Write into every skill the questions it must confirm instead of guessing, plus hard limits (e.g., it drafts but never sends to a client).",
      "Run a new skill 5–10 times on real cases and fix it after each run before handing it to 15, 20 or 100 colleagues.",
      "Assign every shared skill an owner to keep it current and a reviewer other than the author, and have subject-matter experts build the skills for their own area (e.g., the insurance expert builds the insurance skill)."
    ],
    "topics": [
      "agents",
      "agent skills",
      "non-engineer builders",
      "financial services",
      "human-in-the-loop",
      "regulated industries",
      "ai adoption",
      "skill testing"
    ],
    "tools": [
      "Claude",
      "Range"
    ],
    "quotes": [
      {
        "text": "A planner's constraint was never typing speed, for example. It's that we can only be in one place at a time.",
        "at": "01:37",
        "url": "https://www.youtube.com/watch?v=gpmze-6ueGU&t=97s"
      },
      {
        "text": "That narration is the whole game.",
        "at": "04:49",
        "url": "https://www.youtube.com/watch?v=gpmze-6ueGU&t=289s"
      },
      {
        "text": "Same as a plan, you don't grade your own work.",
        "at": "06:48",
        "url": "https://www.youtube.com/watch?v=gpmze-6ueGU&t=408s"
      },
      {
        "text": "Whether a model can draft a cash flow analysis, that question's already been settled. It can.",
        "at": "08:13",
        "url": "https://www.youtube.com/watch?v=gpmze-6ueGU&t=493s"
      }
    ],
    "words": 1619
  },
  "summary_url": "/#gpmze-6ueGU",
  "transcript": {
    "html": "/transcripts/gpmze-6ueGU.html",
    "txt": "/transcripts/gpmze-6ueGU.txt",
    "vtt": "/transcripts/gpmze-6ueGU.vtt"
  }
}