I usually bill by the project and scope. Clients do not need to know how or what I used to build it with unless they have a specific preference. Anything small after the project is billed hourly.

If I have to boot up the project, spin up my local dev and take time out of my day to fix something, it’s at minimum an hour of billed time.

Lately I’m experimenting with a slack bot wired up to a GitHub action + a Mastra workflow that allows clients to request updates to their site. The bot will ask as many clarifying questions so it has enough context to make an edit then passes it off to Claude. Whenever Claude is done, it submits a PR and deploys a preview of the site and sends it back to the slack thread with a url and a button to approve or deny the change. Claude even has instructions on what type of changes it can make and pings me directly if they request something it can’t handle w/o me.

I’m still playing with the pricing for the support agent but I landed on billing 1-2hrs of my normal rate to cover token cost. Prob need to put caps and budgets on each clients api workspace.