Commit
From first outreach to payment, in one tool. We use it every day.
Our internal tool for AI prospecting, proposals, project tracking and getting paid, all in one place.
At a glance
- 2 weeks
- from the first commit to the version we use every day
- Lead → $
- finding clients and getting paid happen in the same tool
- Claude
- drafts the proposals and blocks any that are missing data
The problem
We were finding clients with scripts and spreadsheets, then tracking each project somewhere else: quotes, contracts, installments and expenses. We wanted one place for everything from first outreach to payment, one both of us could use at the same time.
What we built
Commit has three parts. The database lives in Supabase (Postgres, Auth, Realtime and Storage), with hand-written SQL migrations and access locked down by row-level security policies. The interface is built in React 19 with shadcn/ui and talks to Supabase directly, so it keeps working even when the engine is off. The engine is dependency-free Python running on our own machines.
The engine uses Claude to find and qualify leads, draft outreach messages and generate documents (quote, contract, delivery report and a draft website for the client). Anything the AI doesn’t know gets flagged, and a document can’t be sent while data is missing. Emails go out through a queue with a daily cap, and each send is claimed before it leaves so nothing goes out twice.
The money side covers installment plans per project type, invoices, expenses, profitability per project, the daily dollar rate from Uruguay’s central bank and a monthly CSV summary for the accountant.
Where it stands
It’s the tool we use every day. The contact form on this site goes straight into Commit.