TL;DR
To automate an internal process with Claude, write down the steps the way you would explain them to a new hire, and ask Claude to build an app that does them. Most processes need four pieces: a form, a table, a rule, and a schedule. floo runs all four, with sign-in for the people involved.
- Pick a process that repeats every week and has one owner.
- Describe the inputs, the rules, who approves, and what should happen on a schedule.
- Build it in Claude chat with the floo connector, or in Claude Code from a repository.
- Keep a person in the loop for anything that spends money or messages customers.
Most internal processes are already software, just badly hosted. A spreadsheet holds the data, a chat thread holds the approvals, and a person remembers to send the Monday summary. Claude can turn that into an app with the same steps, written down once and run every time.
1. Pick the process
Good first candidates repeat on a schedule, follow the same steps each time, and cost someone an hour a week:
- Approvals. Discounts, refunds, purchase requests, time off.
- Weekly numbers. The report someone builds by hand every Monday.
- Request intake. Asks that arrive in chat and get lost.
- Follow-ups. Renewals, overdue invoices, contracts about to expire.
- Counts. Inventory, equipment, licenses.
Pick one. A second process is easier once the first is running.
2. Write it down like a runbook
Claude builds what you describe, so describe the process, not the software:
Sales reps request discounts over 15%. A request has the customer, the deal size, the discount, and a reason. Anything up to 25% goes to the sales lead; above 25% goes to finance. The approver approves or rejects with a note. Every Friday at 4pm, send the sales lead a list of requests still waiting.
That paragraph names the data (a request and its fields), the rules (who approves what), the people (reps, sales lead, finance), and the schedule (Friday at 4pm).
3. Map it to four pieces
| Piece | In the example | On floo |
|---|---|---|
| A form | Reps submit a request | A page in the app |
| A table | Requests and their status | A Postgres database ([managed.default]) |
| A rule | Who approves which request | Code Claude writes |
| A schedule | Friday's reminder | A cron job ([cron.<name>]) |
Plus sign-in, so only the reps, the lead, and finance get in. On floo that is access_mode = "accounts", and the app knows who each person is from the request headers, which is what the approval rule needs.
4. Build it
In Claude chat: connect floo in Claude's directory and paste your runbook. Claude creates the app with sign-in and Postgres, writes the code, deploys it, and sends you the link. Ask for changes in the same chat.
In Claude Code: paste the runbook to build the app, then Read https://getfloo.com/docs/introduction.md and deploy this app to floo. The scheduled part is a block in floo.app.toml:
[cron.waiting-approvals]
schedule = "0 16 * * 5"
command = "node scripts/remind-waiting.js"
service = "web"
Schedules run in UTC, so convert your local time.
5. Roll it out
- Invite the people involved. "Invite the sales team" in chat, or
floo apps invitefrom a terminal. - Run it next to the old way for a week. Check the numbers match before you retire the spreadsheet.
- Keep a person on anything risky. Let the app prepare the refund or the customer email, and have a person approve it.
- Give the app's secrets to the app, not the code. An email or chat API key goes in with
floo env set, and the app reads it from its environment.
What to automate next
Once one process runs, the next is a copy with different fields. Teams usually find the second one inside a week: the report the approvals data now makes possible, or the follow-up nobody owned. For more on when a recurring task should become an app, see when a task you run through your agent should become an app. For which steps should still wait for a person, see when an agent should need human approval.
Frequently asked questions
Can Claude automate a business process?
Yes, when the process is a set of steps with clear inputs and rules. Claude writes a small app that holds the data, applies the rules, and runs the scheduled parts. floo runs the app with sign-in, a Postgres database, and cron jobs, so it keeps working when your laptop is closed.
What internal processes are good to automate first?
Ones that run every week, follow the same steps, and live in a spreadsheet or a chat thread today: approval requests, weekly numbers, request intake, renewals to chase, inventory counts. Start with one that wastes an hour a week and has one owner.
Do I need a developer to automate a process with Claude?
Not for a small one. In Claude chat with the floo connector, you describe the process and Claude builds and deploys the app. A developer can take over later by moving the app to a GitHub repository.
How does the automation run on a schedule?
As a cron job in the app's floo.app.toml. floo runs the command at the times you set, in UTC, with the app's database and secrets, and keeps a log of each run.