Skip to content
How we work together

Three ways this usually starts.

Start with a diagnosis, move into a focused build, or keep a system running after handoff. Each path shows the commitment, the output, and the information we need to begin.

01Assessment

Workflow Audit

We walk one existing workflow step by step and return a written list of failure points and repairs, ordered by risk.

Duration
Days, not weeks
Starting point
Smallest commitment

The written output is yours whether or not you continue with us. It is meant to be readable by another engineer.

What it is

Something is already running. It mostly works, and nobody can say how often it does not. We trace the path the work really takes, mark every step that can fail without telling anyone, and write down what each repair would involve.

What you get
  • A step by step map of the workflow as it runs today
  • Every failure point we find, ordered by risk
  • A proposed repair for each one, with rough effort
  • A short written summary you can forward internally
What we need from you
  • Read access to the workflow and the tools it touches
  • One session with the person who handles the exceptions
  • Any incident history you already keep
Not included
  • Implementing the repairs
  • Rebuilding or migrating the workflow
  • Monitoring after the audit
03Build

Build an automation or API product

One clearly scoped system, built with error handling, alerting, documentation, and a handoff from the start.

Duration
Weeks, not months
Starting point
Quoted after discovery

For API product work, inspect API Indonesia before the fit check.

Inspect API Indonesia
What it is

This covers a focused workflow, internal tool, or the product layer around an API. The build includes the failure paths, named ownership, and the operating notes needed after launch. API product work can include keys, quotas, plans, billing, dashboards, and endpoint documentation.

What you get
  • The working system in your accounts and under your credentials
  • Retries, hold paths, and alerts for the failure cases
  • Documentation and a runbook written during the work
  • A recorded handoff session for the people who will own it
What we need from you
  • An agreed scope, usually from discovery
  • Credentials issued under least privilege
  • A named owner and safe test data
Not included
  • Work outside the agreed scope
  • Third party licences and subscriptions
  • Ongoing monitoring after handoff
05Monthly, and optional

Managed Care

Monitoring, credential upkeep, incident response, small improvements, and a scheduled review. Optional, and we would rather say that plainly.

Duration
Monthly, cancellable
Starting point
Monthly retainer

In scope and out of scope are written into the agreement, so an incident is never the moment we work out who pays for what.

What it is

Systems do not stay working on their own. Credentials expire, providers change their responses, and volumes grow past the limits a workflow was designed for. Managed care keeps someone responsible for that. If you have an internal team who will own it, take the runbook and run it yourself. That is a normal outcome, not a failed sale.

What you get
  • Monitoring on the systems we built, with failure alerts
  • Credential and token expiry tracking, with renewal reminders
  • Incident response inside an agreed window
  • Small improvements within an agreed monthly allowance
  • A scheduled review of coverage, dependencies, and recovery notes
What we need from you
  • Continued access to monitor the system
  • A named contact for incidents
  • Notice of business changes that affect the workflow
Not included
  • New workflows or new systems, which are quoted as builds
  • Systems we did not build, until we have audited them
  • Third party outages, which we report and work around but do not control
  • Round the clock on call cover
Budget

We do not publish a price list for this work.

A number on a page would only be honest if every engagement were the same shape. They are not. Cost depends on how many systems are involved, how much of the process is undocumented, and how much of the work is handling exceptions rather than the normal case.

Diagnose

Smallest commitment

The least you can spend to find out whether there is a real problem and how bad it is.

Build

Quoted after discovery

Automation and API product work is quoted after the scope and dependencies are clear.

Operate

Monthly retainer

A fixed monthly figure set against an agreed scope, and cancellable if you no longer need it.

Where we can publish prices, we do

API Indonesia is a product, so its pricing is public and fixed: a free tier of 1,000 requests a month at 10 requests per second, Pro at Rp 49.000 a month for 50,000 credits at 20 requests per second, and Business at Rp 149.000 a month for 250,000 credits at 60 requests per second. Studio engagements are quoted instead, because no two of them are the same size.

Check the pricing on apiindonesia.id

How the number gets set

Pricing is discussed on the fit check, before anyone writes a proposal. You describe what is breaking, we say which engagement fits and roughly what it costs, and if the range does not work for you then nobody has spent anything. Written quotes follow the conversation, never precede it.

Book a Fit Check
Not sure which one

Describe what is breaking and we will tell you which of these fits.

Sometimes the answer is none of them, and we say so. If you want to start, book a fit check and bring one workflow you are tired of babysitting.