Skip to content

An illustrated example

KerjaBareng for operations and back-office teams

Twenty people keeping daily processes running: billing, reconciliation, reporting, reminders. Small errors here are expensive, and being on time matters more than being fast.

This page is an illustration, not a case study. The company described below is one we made up as a plausible example for this kind of business — not a customer, not a testimonial. The cost figures are computed from our published plan prices.

Team size
20 people across 3 operations teams
Active divisions
Finance & Ops, Sales & CS, Data & Analytics
Tools they use today
An ERP or accounting package, spreadsheets, email, chat groups

Where it usually jams

Three things that hold operations and back-office teams back

Processes depend on the person who remembers them

When that person takes leave a step gets missed. The procedure exists in a document nobody opens.

Routine reports eat a whole working day

Producing a monthly report whose format never changes still ties up one person for hours.

No record of who approved what

When something is questioned later, the trail is scattered across email and chat.

One working day

What a day looks like once it is running

Four moments in sequence over a single day — no grand promises, just the order in which things actually happen once agents share the work.

  1. The schedule runs the process, not somebody’s memory

    A scheduled routine runs the daily step at the same hour, and it is visible when it does not.

  2. The agent builds the report from a stored format

    Format and rules are written as a Skill, so the output is identical every month regardless of who is on duty.

  3. Exceptions escalate to a person rather than being decided alone

    The agent flags what looks wrong and raises an approval; it never decides anything outbound on its own.

  4. Every decision leaves a record

    Who approved, when, and on what basis is stored in one exportable place.

The Routines page: scheduled work with the agent responsible and the next run time.

Product screenshot. Scroll to explore the details; press Escape or Close to return.

The usage page: cost per agent in rupiah, number of runs and tokens consumed.

Product screenshot. Scroll to explore the details; press Escape or Close to return.

The agent line-up

The agents that make sense for a business like this

Each division gets one agent. Names, instructions and permissions are yours to change — what follows is only a sensible starting point.

Rani — Finance & Ops

Runs the daily recaps and reconciliations, flagging the gaps a person needs to look at.

The Reporting agent

Builds the periodic reports from a format stored as a Skill, period after period.

Tania — Sales & CS

Handles reminders and outside follow-ups, always through an approval.

What changes

  • Processes keep running when someone is away
  • Periodic reports come out in the same format every period
  • The approval trail is tidy and exportable

What it would cost

Twenty seats on the Business plan: Rp 3,980,000 a month, with exportable audit records and usage analytics.

The AI figure above is estimated from real run prices (Rp 130–500 per task) and is covered by the plan quota. Your exact number depends on how often your agents work.

See full pricing details

Start working alongside your team and AI agents today.

14 days free, no credit card.