Why Finch.
Building a website has changed more in the last few years than in the twenty before. The way we work on one together hasn’t caught up yet. Finch is our attempt to close that gap.
- No. 1A shorter headline
- No. 2A warmer button
- No. 3More room to breathe
- No. 4The best work first
The tools moved on. The process didn’t.
With Claude Code, a site can go from an idea to a live address in an afternoon. Then someone has an opinion about it, and everything slows back down.
Feedback still travels the old way: a screenshot with a red circle, a long email, a call to explain which blue. The person with the opinion describes the change. The person with the code interprets it. Something gets lost in every round, and every round costs a day.
We think the gap isn’t in the building any more. It’s in the hand-off between the people who care about a site and the code that makes it. Finch lives in that hand-off.
The best feedback isn’t a note about the change. It’s the change.
Four ideas behind every decision.
Point at the real thing
Feedback belongs on the live page, not on a screenshot of it or a copy of it. The real page is where the problems are, so it’s where the conversation should be.
Show, don’t describe
The fastest way to say “a bit bigger” is to make it a bit bigger. When people can make the change they mean, nothing gets lost between what they said and what you heard.
Someone decides
Anyone can suggest. One person chooses what ships. Good collaboration isn’t everyone editing at once; it’s many voices and a clear call.
The code stays yours
Every change lands in your codebase as its own commit, written the way your project already writes things. Nothing is locked in a platform, and anything can be undone.
Small changes add up.
Finches are small, curious and famously good at adapting. Not in one leap, but in many small changes, each one suited to where they live.
Good websites grow the same way. Not through the big redesign, but through a steady run of small, well-chosen changes: a clearer headline, a warmer button, more room around the thing that matters. Finch is built to make each of those changes easy to suggest, easy to choose and easy to ship, right where the site actually lives.
Early, and on purpose.
Today Finch works with Claude Code on the site owner’s computer. Next, we want the same loop to work for people who never open a terminal, and for teams who share the work of deciding. You can follow along in the changelog.
Finch is small, independent and free while it’s in early access. Every email is read by a person: hello@finchnotes.co.
Ready to ship your next change?
Add the plugin to Claude Code and run /finch-install in your project. It takes about two minutes, and Finch is free while it’s in early access.
# needs a paid Claude plan (Pro or higher)> Add the Claude Code plugin finch@finch from the GitHub marketplace usefinch/notes (put it in my Claude Code settings if /plugin isn’t available here), then tell me how to load it and run /finch-install on this site.# or, in the terminal: /plugin marketplace add usefinch/notes# then /plugin install finch@finch# open a new session in your site’s folder> /finch-install# sign in with Google, choose who sees Finch✓ Finch is set up with editing on.# deploy your site the way you usually do# open it and click Edit, change anything, click Apply changes# then, in a new session:> /finch-apply✓ Your changes are live.