Composable primitives for your finance operations.
Prebuilt scripts and worker pipelines that already use them — start from a worked example, then shape it into the exact system you need. Yours to own, no lock-in.
$ npm i -g @finopsbricks/fob-cliBring your own AI · query and export your data · start with one module
↓ See a founder’s reconciliation workflowA founder workflow
From a balance mismatch to an explanation
In this founder-provided example, Claude Code compares a bank account in Statements with an external budget in Actual Budget, using configured command-line tools.
The session identifies a double-counted ₹60,000 inflow and a missing ₹29,078 debit, then asks for confirmation before applying the proposed corrections. The tools provide access to the data; the agent reasons over it and the founder reviews the changes.
Formatted excerpt supplied by the founder; identifiers redacted. This is an example, not a guaranteed result or a built-in reconciliation command. The Actual integration remains a supporting tool under review.
Developers first
Built by developers, not accountants.
Accounting software is built by accountants — bloated, clicky, one-size-fits-nobody. fob is accounting built by developers: sharp, composable primitives you script into the exact system you need — one that fits you now and reshapes as you scale.
The primary surface
An API & CLI that get out of your way
Statements, Transactions, Ledger and Orchestrator have dedicated command-line clients. Use their APIs from your own code, or give an agent the same tools. Each module documents its supported operations and authentication.
Finance operations as code
A workflow you can read and change
Our founder’s statement-verification workflow separates deterministic checks from AI analysis. Its handlers and report templates live in a worker repository; Orchestrator coordinates the runs.
- 1.
Fetch data
Load a statement and its account transactions.
- 2.
Run checks
Compare metadata, balances and the statement equation.
- 3.
Analyze findings
Pass check results to an AI analysis step.
- 4.
Save the review
Write findings, check results and review status.
An illustration of the implemented workflow structure. Worker tooling remains under review for public use; this is not an out-of-the-box automation.
The bricks
Each is a standalone app with its own home. Use one, or snap several together.
Built the way you build
Keep your workflow logic in code. Inspect the data it reads and the changes it makes.
No vendor lock-in
Read and export statement and transaction data through documented APIs and CLIs. Keep your own copies and scripts.
Modular
Start with a single brick. Add more as you grow. Each does one thing well — no monolith to adopt.
Flexible & extendable
Use module clients in your own code. Add the checks, transformations and integrations your workflow needs.
Replaceable
Choose your own tools at each boundary. Documented APIs let you build adapters and move data between systems.
LLM-first
Give your own agent the module CLI or API. You choose its instructions, credentials and review process.
Usage-based direction
Our pricing model follows usage rather than seats. Per-brick rates and free allowances are not yet published here.
Priced like a utility, not like SaaS
Our pricing model is pay-as-you-go, with no per-seat or flat per-org plans. We are designing for low-volume personal use as well as growing businesses. See what is decided and what is still to be published.
See how pricing works →- ✓Personal finance is welcomeStart with one account or one module. Low-volume use is central to the pricing model.
- ✓Usage, not seatsOur intended model meters work in units relevant to each module.
- ✓Rates still to comePer-brick rates, free allowances and billing availability are not yet published here.
Explore the docs
Read the contracts before you connect
Explore the available modules’ object models, endpoints and setup instructions. Start with a read command and build from a result you can inspect.
Our belief
Accounting is repeatable work. The hard part was judgment.
Repeatable underneath
Reconcile, categorise, close, report — most finance operations are the same work, over and over.
Judgment was the wall
The exceptions needed a call. That's exactly where the last wave of automation stopped.
A new way through
We believe agents can help reason through exceptions, while developers build the checks, controls and review paths around them.
We build the tools an agentic accountant can use. Developers connect the data, define the checks and decide what needs review. That division of work is illustrated in the reconciliation demo.
Our dream
Everyone gets a CFO.
Strategic finance shouldn't be a privilege of scale.
A CFO is a luxury of scale — you hire one once you're big enough to afford one.
A strategic, always-on agentic CFO — within reach of anyone who builds.
What shape it takes, we're not precious about — maybe our Assistant, maybe a fractional CFO's own agent, maybe a company we've never met. We build the rails it runs on.
Build and automate finance operations that work for you.
Start with one module. Inspect its commands, connect your data, and build a workflow you can understand.