Fatbunny Digital
Discuss your project

Applied AI / engineering automation

Turn existing business workflows into controlled AI-operated tools.

CLI and MCP tools connect documents, email, spreadsheets, CRM and internal systems to Codex or Claude Code.

We convert repeatable enterprise work into bounded tools that Codex or Claude Code can operate with clear permissions, human approval and evidence.

Delivery
Repository-aware
Scope
Test-gated
Control
Human-reviewed

Codex delivery loop

Reviewable change set
  1. 01Issue
  2. 02Context
  3. 03Plan
  4. 04Change
  5. 05Verify
  6. 06Review

The operating problem

An unrestricted coding assistant can produce code quickly while increasing review risk. Useful Codex automation needs repository context, explicit authority and gates that fail closed.

System mechanism

Codex and Claude Code at work inside a real business process

A task becomes a bounded change only after repository rules, tool permissions, tests and human review agree.

A business work request combines approved company context with CLI and MCP tools, prepares bounded changes, pauses for review and returns a review-ready result.

  1. 01
    Business inputBusiness work request

    A recurring reporting, document, research or coordination task starts with a known owner and result.

  2. 02
    Retrieval engineApproved company context

    Policies, files, templates and prior evidence are retrieved inside the permitted scope.

  3. 03
    Business toolsCLI and MCP tools

    Email, documents, spreadsheets, CRM and internal systems expose narrow operations.

  4. 04
    Agent-operated workflowControlled work sequence

    Codex or Claude Code follows the agreed steps, rules and stop conditions.

  5. 05
    Decision pointDraft business action

    A report, updated record, prepared message or document pack is assembled with evidence.

  6. 06
    Human gateAccountable approval

    A person approves consequential communication, data changes or external release.

  7. 07
    Business valueReview-ready business result

    Completed work reaches the team with sources, changes, exceptions and next ownership visible.

Fatbunny responsibility

Fatbunny maps the existing business process, converts approved operations into CLI and MCP tools, defines information and permission boundaries, builds review states and measures the completed work.

Capabilities

  1. 01

    Existing workflow and exception mapping

  2. 02

    CLI and MCP tools for documents, email, spreadsheets, CRM and ERP

  3. 03

    Retrieval over approved company information

  4. 04

    Codex and Claude Code operating instructions

  5. 05

    Human approval, audit evidence and outcome measurement

Delivery decisions

  1. 01

    Automate a repeatable business result rather than an open-ended assistant

  2. 02

    Expose only the business operations the workflow needs

  3. 03

    Separate read, draft and consequential action permissions

  4. 04

    Keep external communication and irreversible changes accountable

Expected outputs

  1. 01

    A mapped business workflow with owners, exceptions and evidence

  2. 02

    Reusable CLI and MCP tools connected to approved systems

  3. 03

    A review-ready automation with operating controls and measurements

Honest limits

  1. !

    Codex and Claude Code cannot repair unclear ownership or unreliable source information.

  2. !

    Systems without suitable APIs, exports or safe command surfaces need integration work first.

  3. !

    Sensitive data and consequential external actions remain separately permissioned and reviewed.

Start from the work people repeat

The strongest candidates are recurring workflows where skilled people collect the same information, move it between the same systems and prepare the same kind of reviewable output.

Examples include monthly reporting, tender preparation, document processing, customer-case follow-up and controlled research.

Turn existing systems into bounded tools

CLI commands and MCP tools give Codex or Claude Code narrow operations for email, documents, spreadsheets, CRM, ERP and internal services. The agent does not receive broad authority simply because it can see the system.

Every tool has a defined input, output, failure state and permission boundary that the business can inspect.

Deliver completed work with evidence

The useful result is not a conversation. It is a report, prepared document pack, updated draft record or structured handoff that shows its sources, unresolved exceptions and accountable next step.

Direct answers

Common questions

Is this a software development service?

No. Codex and Claude Code are used as enterprise work operators connected to approved business tools. The target workflow may involve reports, documents, email, CRM, ERP or internal operations rather than programming.

What business work can be automated?

Good first candidates include recurring reporting, tender preparation, document processing, controlled research, customer follow-up and other evidence-heavy workflows with repeatable steps.

Can the agent send emails or update business systems?

Yes, when the operation is exposed through a narrowly scoped tool and its read, draft, approval or execution authority is explicitly defined.