orca
Get early access
Campaign delivery for agencies

Deliver more client work with the team you have.

Turn your agency's process into repeatable workflows. Your team defines the work, your agents do their share, and clients get one clear next step.

Get early accessSee how it runs
Built with media, SEO and creative teams. Agents run on your own setup.

Nobody drags these. ORCA moves work when its inputs land, when an agent returns it, and when a reviewer approves it.

Follow one task

From your team, to your agent, to review, to the client.

Example

Your team

Defines the work

Your agent

Does it, outside ORCA

Account lead

Reviews before sharing

Your client

Gets the result and one next step

1 / 4Your team defines the work and attaches the context.Your agent does it, where it already runs.Your account lead reviews it before anything is shared.Your client sees the result and one next step. Nothing else.
Scroll to follow the work
What ORCA does, live

One place where the work, the context and the review stay together.

Five things ORCA does on every piece of work. Each one plays through once. Click any to replay.

Readiness is checked against the task's inputs, not a status someone set.

Your process, repeated

Start the next project without starting from scratch.

Define each service once: the steps, who owns them, where approval sits. Every client project runs on it with its own brief, files and decisions.

Nothing here is built in. Click an owner to change it, click a step to rename it, add one.

Example service
harbour.meetorca.io
Campaign reportingDefined once. Runs for every client that buys it.
1Gather results
2Prepare report
3Account review
4Share with client
Client projects2
Client AAccount review Account leaddue today
Client BShare with client Clientwith client
Your rules

Delegate the work. Keep the review.

Bring the agents you already run. Choose the task, set how far it can reach, and decide who signs it off.

  • Agents run on your setup. ORCA holds the task and the context.
  • A role, a permission list and a campaign boundary. The server checks every request against them.
  • Review points live in the workflow, so they hold whether a person or an agent did the step.
Connect an agent
harbour.meetorca.io
Client A · AssignmentReady for Claude
Prepare weekly performance report
Agent
Role
Permissions
Read campaigns
Read and download files
Submit workflow tasks
Approve campaign output
Campaign access
Selected campaigns · Client A
access boundary
Review step
A
Account lead
set in the workflow, not on the agent
Client Portal

Your team sees everything. The client sees what you choose.

The Client Portal is a projection of the same campaign: progress, shared work and the decisions you need. Internal edits, who prepared the work and agent access stay with your team unless you decide otherwise. Try the switches in the workspace.

Agency Workspace
harbour.meetorca.io/campaigns/…/workspace
Client A · Spring launch · Workspace
Weekly performance reportApproved
Campaign recordClient sees
Findings and recommendationShared
Prepared by Claude · 3 min 40 s
Reviewer: Tobias Wren · trimmed the channel breakdown
Agent access: this campaign onlyInternal
Next step for the client: Agree priorities
Client Portal
harbour.meetorca.io/campaigns/…
Spring launch
Weekly performance report
Findings and recommendationReady
Shared by your agencyWed 09:12
Your decision · due FriAgree priorities
Weekly performance report.pdf

Never shown to the client: workflow controls, owner assignment, agent permissions and scope. Hidden until you switch them on: who prepared the work, internal review notes.

ORCA for the way your agency works

Same product. Same review step. A different service each time.

Pick the one closest to yours and see the workflow, the assignment and the client view shaped for that kind of work.

Start with one service. Build from there.

Run one repeatable service with your team, refine it, then hand selected steps to an agent when you are ready.