Scoped, built, and documented.
So you're never dependent on me.
Four automations built end to end for your agency, not just advice about them. New assets in your shared Drive get auto-tagged by client, content type, and format. A recurring reporting pipeline pulls performance data and uses Claude to write a narrative summary, not just raw numbers, then delivers it to Slack, email, and Drive. An AI draft-response system writes replies for common inquiries with a human approving every send, and a new-client onboarding flow handles the repetitive setup. Built on Make or Zapier with Claude, connected to Drive, Slack, Notion, and Rella, and documented so your team can tweak everything without me.
You don't need advice. You need it built.
You already know what you want automated. The gap is someone who understands how an agency runs and can scope, build, and hand it over cleanly.
Advice is not a system
Plenty of people will tell you what to automate. Far fewer will scope it, build the working automations, and hand you something you can actually run day to day.
Agency workflows are specific
Content approval, client reporting, asset management. If the builder does not already understand how an agency operates, you spend your time explaining instead of getting time back.
Niche tools break the easy path
Tools like Rella often expose only an API or webhook, not a native Zapier or Make app. Handled wrong, that quietly balloons scope or stalls the whole build.
Four automations, handed over clean.
I scope the work first, then build all four automations and document every one. Auto-categorization watches your shared Drive and tags each new file by client, content type, and format, using AI classification where filenames alone are not enough. The reporting pipeline pulls performance data on a recurring schedule, has Claude write a narrative summary a client would actually want to read, and delivers it to Slack, email, and Drive automatically. The draft-response system generates replies for common comment, DM, and email types and routes every one through a human approval step, so nothing ever posts autonomously. The onboarding flow automates the repetitive admin and setup when you bring on a new client. Everything runs on Make or Zapier with Claude for the AI steps, and I handle Rella through its API or webhook directly, which is exactly the kind of niche integration that trips up a native-app-only approach. Each automation ships with written documentation and a troubleshooting guide, plus a handoff call, so your team can adjust and extend without depending on me.
What you get. Automation by automation.
Scope first, then each automation built and documented, then a clean handoff. Nothing sends autonomously, and nothing is left undocumented.
- Map your content approval, reporting, and asset management workflows
- Confirm Rella's API or webhook and flag any scope impact upfront
- Recommend Make or Zapier per automation, with Claude where AI adds value
- A written scope and build plan you approve before I start
- New files in your shared Drive auto-tagged by client, content type, and format
- AI classification where filenames alone are not enough
- Consistent naming and folder logic your team can rely on
- Documented rules you can adjust as clients change
- Recurring pull of performance data from your sources
- Claude writes a narrative summary, not just raw numbers
- Delivered automatically to Slack, email, and Drive
- Templated so adding a client is a config change, not a rebuild
- AI drafts responses for common comment, DM, and email types
- A human approval gate so nothing sends autonomously
- New-client onboarding flow automating the repetitive setup steps
- Notion and Slack wired in where your team already works
- Written documentation and troubleshooting for every automation
- A short handoff call walking you through all of it in plain English
- Everything owned by you and editable without depending on me
- Optional maintenance retainer if you want ongoing support and new builds
Scope to clean handoff.
Each stage ships a working, documented automation. Click any stage to see what it delivers.
What this stage delivers
- Content approval, reporting, and asset workflows mapped
- Rella API or webhook confirmed, with scope impact flagged upfront
- Make or Zapier recommended per automation, Claude where it adds value
- A written scope and build plan you approve before any build
What this stage delivers
- Drive files auto-tagged by client, content type, and format
- AI classification where filenames alone fall short
- Recurring reporting pipeline with a Claude-written narrative
- Reports delivered automatically to Slack, email, and Drive
What this stage delivers
- AI drafts for common comment, DM, and email types
- A human approval gate so nothing sends autonomously
- New-client onboarding flow automating the repetitive setup
- Notion and Slack wired in where your team already works
What this stage delivers
- Written documentation and troubleshooting for every automation
- A short handoff call in plain English
- Full ownership, editable without depending on me
- Optional maintenance retainer available if you want ongoing support
Let's scope this together.
Over an Upwork call I'll walk through how I'd scope these four automations, confirm the Rella integration path so there are no surprises, and give you a clear order of build. You'll come away knowing exactly what gets built, in what order, and how it will be documented. Message me on Upwork whenever you're ready to talk it through.