Notes

Notes from building FinButler.

We write about product choices, checks that caught real bugs, and the people doing the work. No newsletter signup.

A quiet engineering desk with a laptop, notebook, and release notes
  1. engineering

    Shipped while we slept

    FinButler is built by scheduled AI fires: tickets in the morning, a real browser at night, production while we sleep. Here is the machinery and what the humans still do.

    Erick Agrazal, Founder. 7 min read

  2. engineering

    The gates are the product

    An agent once tried to deploy a commit that did not exist. Everything looked fine. This is about the checks that said no, and why production is our least intelligent stage.

    Erick Agrazal, Founder. 8 min read

  3. engineering

    Green isn't green until a browser says so

    A change once passed every test we had, against a field the backend never sent. Tests encode what the author believed. Here is why we make a real browser check the belief.

    Erick Agrazal, Founder. 7 min read

  4. engineering

    There is no daemon

    We built our pipeline as a service, ran it for a few weeks, and deleted it. Its replacement has no running process, which makes failure survivable.

    Erick Agrazal, Founder. 7 min read

  5. engineering

    What the humans actually do all day

    If agents write the code, review it, validate it and ship it, what is left for the people? The answer turned out to be the parts of the job I used to do in the gaps between typing.

    Erick Agrazal, Founder. 7 min read

  6. product

    Why we put MCP at the center of FinButler

    A short, candid memo on making agents and the Model Context Protocol first-class, and what changed when we stopped treating them as a feature.

    Erick Agrazal, Founder. 7 min read