FOR THE PERSON WHO OWNS FINANCE AUTOMATION

Your job description says build this. Don't.

You're technical enough to build the orchestration, the approval engine, the audit log. You're also senior enough to know what maintaining them in production means. Start on Artifi and spend your mandate on the workflows only you can build.

A REAL EXTENSION, NOT A DIAGRAM

Patch a workflow block. Ship it today.

Workflows are made of blocks. You override the block, not the platform: your patch runs inside the same dry-run, lanes, and audit trail as everything else. Versioned on deploy, diffable, revertable — and visible to the finance team who'll live with it.

→Pipelines deploy from your own git repo
→Scheduled jobs and HTTP callouts for the edges
→MCP surface — your tooling composes against it
blocks/vendor-match.patch.jsDEPLOYS FROM YOUR GIT
// Override one block of the bill-processing workflow.
// Everything else — dry-run, lanes, audit — stays core.

export default definePatch({
  workflow: "bill-processing",
  block:    "vendor-match",

  async run(doc, ctx) {
    // your logic: fuzzy-match against the group CRM first
    const hit = await ctx.http.get(CRM_URL, doc.vendorName);
    if (hit.confidence > 0.92)
      return ctx.resolve(hit.vendorId);

    // fall through to the core matcher — never skip it
    return ctx.next(doc);
  },
});

// $ artifi deploy → versioned v15, dry-run replay, lane review
ILLUSTRATIVE — the mechanism (patches from git, versioned, dry-run replay) is real; exact API per docs
THE CONTRACT

You extend the edges. The core stays invariant.

YOURS TO EXTEND
Agents — new ones, tuned ones
Workflow blocks & patches
Plugins — governed tools
Skills — procedures Claude follows
Scheduled jobs & HTTP callouts
Pipelines from your git repo
CORE — NOT EVEN YOU
Ledger invariants — double-entry, immutability, typed transactions
The governed gateway — the only write path, for humans and agents alike
The approval engine — lanes can be configured, never bypassed

This is the part your auditor is glad you can't touch — and the part you'd otherwise spend a year building badly under deadline.

THE HONEST COMPARISON

What year one actually contains.

CONCERN
BUILDING IN-HOUSE
STARTING ON ARTIFI
Day one
Starts with orchestration code — queues, retries, state machines.
Starts with finance objects, workflows, and controls that already exist.
Governance
Logging, permissions, approvals recreated as side projects around the pipeline.
Governance is the runtime — every action already dry-runs, routes, and logs.
Audit
An audit trail you design, defend, and backfill when the auditor asks.
Immutable audit rows by construction; the auditor reads the same trail you do.
Continuity
Key-person risk: the platform lives in one person's head.
Versioned, supported platform; your extensions live in your git repo.
Path to production
Fast demo, then months of hardening: edge cases, permissions, rollbacks.
Controlled production in weeks: read-only → thresholds → production waves.
Your leverage
You maintain plumbing; workflow asks queue behind infrastructure work.
You build agents, blocks, and pipelines — the work that's actually yours.
The platform your job description asks you to build —
so you can build what it actually hired you for.

Bring a workflow you'd have to build.

A technical working session: your repo, our runtime, one real extension deployed against your real data, read-only.

Book a working session
// works through Claude and any MCP client