# Rigid Body Dynamics > Rigid Body Dynamics builds Velocity, an AI workforce for complex enterprise operations: a team of specialist AI agents that research, decide and execute work across procurement, supply chain, finance and logistics, inside a company's existing ERP, email and documents, under its own approval rules. - Website: https://www.rigidbodydynamics.com/ - Company: Rigid Body Dynamics (legal entity: Begin Becoming Technologies Private Limited), India - Product: Velocity - Book a demo: https://calendar.app.google/BBf57YUkQsQxwzG28 - Last updated: 2026-10-16 ## Key facts - Velocity is not a chatbot and not a new system of record. It is a team of specialist AI agents that works through a named login with defined permissions, like a new employee, inside the ERP (SAP, Oracle), email, Teams, chat, portals and spreadsheets a company already runs. No data migration and no integration project. - It researches, analyses, executes and automates: finds the facts across systems and documents, proposes resolutions against the company's rules and limits, completes approved actions in the client's systems, and runs the pattern continuously. - Every action carries a policy limit, an approval path and an audit trail. Autonomy is set per workflow by the client. Velocity cannot grant itself access or approve its own exceptions. - It runs inside the client's network or in a hosted environment. Client data is not used to train general-purpose AI models. - Engagements start with a paid pilot on one workflow (about four weeks), measured against a baseline agreed before the pilot begins; cross-team processes run twelve to sixteen weeks. - Industries: oil & gas, ports and container terminals, pharmaceuticals, manufacturing, distribution. - Measured in production (an FMCG distributor in India, live since June 2026): order entry fell from 15 minutes to 45 seconds per order; orders needing human review fell from 95% to 5%; 94% order accuracy; 5 hours per person per day given back. - Every other figure on the site is labelled "Pilot target" (the success measure a pilot is held to) or "Worked example" (a walkthrough on representative data). They are not production results. - Clients and prospects are never named; cases are anonymised by industry and scale. ## Frequently asked questions **What is Velocity?** Velocity is an AI workforce built by Rigid Body Dynamics: a team of specialist agents that research, decide and execute operational work across procurement, supply chain, finance and logistics, inside a company's existing systems and under its approval rules. **Which systems does it work with?** The ones your teams already use: SAP and Oracle ERPs, warehouse and transport systems, CRM, supplier and e-procurement portals, email, Teams, spreadsheets and document stores. If a person can do the work with a login, Velocity can work there too. **Is it software we have to roll out?** No. Velocity gets a login and a seat. There is no data migration and no integration project, and your teams keep working in the tools they have. They see Velocity's work as messages and an approvals queue. **What does it decide on its own?** Only what you allow. Autonomy is set per workflow: inside your policy limits it acts; above them, or for anything unusual, it prepares the case with its evidence and routes it to the right approver. It never overrides policy, and any exception it is given is time-boxed and logged. **How does a pilot work?** It starts with one workflow. The baseline and the success measures are agreed with you before the pilot begins, and results are reported against your own numbers on the same cases. A single workflow can be tested in four weeks; processes that span several teams run for twelve to sixteen. **Is our data used to train AI models?** No. Client data is not used to train general-purpose AI models. Velocity can run inside your network with credentials you hold, or in a hosted environment; your IT team decides before anything is connected. **Which industries is Velocity built for?** Large, complex operations in oil & gas, ports and container terminals, pharmaceuticals, manufacturing and distribution — where procurement, procure-to-pay, supplier recovery, credit and order-to-cash work crosses many systems and teams. ## Platform — https://www.rigidbodydynamics.com/platform/ Velocity logs in to your ERP, email and portals like a new hire. It learns how your business runs, does the work, and asks your team before anything important. ### Four parts, working as one - **A team of agents.** One lead agent plans the work and talks to your people. Specialist agents for procurement, finance, supply chain and logistics do the work. - **A map of your operation.** It keeps track of how your orders, plants, contracts and policies connect. Every task it finishes adds to the map. - **A memory of your rules.** It learns your SOPs, approval limits and past decisions. Correct it once, and it remembers. - **The systems you already use.** It logs in to SAP, Oracle, portals, email and Teams, the same way a person does. Nothing new to install or connect. ### What it does - **Research.** It reads the order, the contract, the stock and similar past cases. - **Analyze.** It compares the options against your rules and limits, and recommends one. - **Execute.** It does the work in your systems: books the order, chases the vendor, posts the credit. - **Automate.** It runs the same work every day on its own, inside the limits you set. ### From pilot to scale - **Phase 1 (4 weeks) — Prove it on your own work.** We pick one everyday task, measure how it runs today, then let Velocity run it — and put the two side by side. Steps: Agree the baseline; Give it a login; Run it on real work. - **Phase 2 (12–16 weeks) — Connect it across teams.** Velocity takes on work that crosses teams — order desk to dispatch, buy to pay — with approvals in the right hands. Steps: Work across teams; Your approval rules built in; A review every week. - **Phase 3 (Ongoing) — Let it do more on its own.** As it learns your operation, you choose what it runs alone. Anything above your limits still comes to your team. Steps: Set limits per task; Add teams as you go; A review every quarter. ### Controls - **Its own login, nothing more.** Velocity works through its own account, with the access you give it. It cannot give itself more access or approve its own exceptions. - **Your servers or ours.** It can run inside your network, with credentials you hold, or in our hosted setup. Your IT team decides. - **Every action is recorded.** Each action shows the rule it followed, who approved it and when. You set how much it can do alone. - **Your data stays yours.** We don't use your data to train general AI models. Outgoing messages are checked against your rules, and suspicious replies are held. ## About Rigid Body Dynamics — https://www.rigidbodydynamics.com/about/ Rigid Body Dynamics builds Velocity, an AI workforce for complex enterprise operations: a team of specialist AI agents that research, decide and execute work across procurement, supply chain, finance and logistics, inside a company's existing ERP, email and documents, under its own approval rules. Rigid Body Dynamics is a product of Begin Becoming Technologies Private Limited, a company incorporated in India. The founders are IIT (ISM) Dhanbad alumni with engineering experience in industrial operations and enterprise software. Winner, India–Australia Circular Economy Hackathon 2021 (Atal Innovation Mission, NITI Aayog and CSIRO); the team was recognised by the Prime Ministers of India and Australia. - **Apurva Biswas, Co-founder & CEO.** Former strategist at Goldman Sachs, running production systems and data validation for live commodity indices — work where a wrong number is never a small mistake. Leads product and business strategy, working directly with the operations teams Velocity works alongside. LinkedIn: https://www.linkedin.com/in/apurva-biswas/ - **Manmohan Labh, Co-founder & CTO.** Former software engineer at Postman and Innovaccer. Leads AI research, systems integration and product architecture. Inventor of a patent-pending medical invention, recognised with the Gandhian Young Technological Innovation (GYTI) Award by the Principal Scientific Adviser to the Government of India. LinkedIn: https://www.linkedin.com/in/manmohanlabh/ # Industries ## Oil & gas — https://www.rigidbodydynamics.com/industries/oil-and-gas/ Where an operator's spares, tenders and contracts move as fast as the platform needs them. What it cares about: Uptime, Safety, Traceability. Offshore platforms, onshore fields and refineries run on equipment that cannot wait. When a seal leaks, the work that follows crosses sites, stores, sanctioning committees and a government procurement portal. Most of it lives in drawings, old purchase orders, email threads and the memory of the engineers who were there last time. ### The work, by department - **Spares & MRO.** Identify the exact part from drawings, datasheets and past orders, check stock across stores and raise the indent with an estimate. - **Tendering & vendors.** Ask approved vendors for prices, compare bids on the published criteria and draft tender terms for the buyer to verify. - **Inventory across sites.** See what every platform and store holds before buying, and pool the same requirement into a single requisition. - **Contracts & payables.** Follow each order through receipt and invoice, chase what is stuck and keep every step on the record. ### What changes - **Equipment back in service sooner.** A requirement moves from the site to a sanctioned requisition without the clarifications that used to sit between them. - **One demand across every site.** Sister platforms and stores are asked before anything is bought, so the same part is tendered once. - **Every decision traceable.** Each indent carries its drawings, datasheets, past prices and approvals — ready for the tender committee and for audit. ### Why Velocity - **A login, not a rollout.** Velocity works in SAP, government procurement portals, drawings & datasheets and email, where your site engineers and materials planners already work. No migration, no integration project. - **Specialist agents, not a chatbot.** A team of agents, each with one job — finding, checking, chasing, drafting — that learns your sanction limits, tender rules and approved vendor lists the way a senior hire would. - **Inside your controls.** Sanctions, tenders and awards stay with your committees. Velocity prepares each case and keeps the record. - **Measured against your numbers.** The baseline for your oil & gas work is agreed with you before the pilot begins, and every result is reported against your own numbers. ### Questions **What does Velocity do in oil & gas?** Velocity is a team of specialist AI agents from Rigid Body Dynamics. In an oil & gas operation it carries this work: Spares & MRO — Identify the exact part from drawings, datasheets and past orders, check stock across stores and raise the indent with an estimate. Tendering & vendors — Ask approved vendors for prices, compare bids on the published criteria and draft tender terms for the buyer to verify. Inventory across sites — See what every platform and store holds before buying, and pool the same requirement into a single requisition. Contracts & payables — Follow each order through receipt and invoice, chase what is stuck and keep every step on the record. **Which systems does it work in?** Velocity works in SAP, government procurement portals, drawings & datasheets and email, where your site engineers and materials planners already work. No migration, no integration project. It logs in with its own account and the permissions your IT team grants. **Who does it work alongside?** Site engineers, Materials planners, Buyers and Engineering reviewers. Velocity learns your sanction limits, tender rules and approved vendor lists and takes on the chasing, checking and drafting between systems; your people keep the judgement and the final say. **What stays with your people?** Sanctions, tenders and awards stay with your committees. Velocity prepares each case and keeps the record. **How is a pilot measured?** The baseline for your oil & gas work is agreed with you before the pilot begins, and every result is reported against your own numbers. Use cases: https://www.rigidbodydynamics.com/use-cases/spares-requirement-to-pr/ ## Ports & terminals — https://www.rigidbodydynamics.com/industries/ports-and-terminals/ Where a terminal's purchasing and payables keep pace with the quay. What it cares about: Throughput, Control, Uptime. Quay cranes, straddle carriers and reefers run around the clock. The back office behind them runs on requisitions raised without item codes, approval chains many levels deep and invoices waiting for a receipt nobody posted. Every gap is small. Together they hold up spares for the equipment and payments to the suppliers who keep it moving. ### The work, by department - **Requisitions & item master.** Match each request to the right item code from the master and past orders, with the evidence on the requisition. - **Procure-to-pay exceptions.** Find why an invoice is stuck — a missing code, an unposted receipt — and work it back into the payment run. - **Approvals & delegated authority.** Route every purchase by the approval matrix, decide what policy allows and escalate the rest. - **Receiving & quotations.** Capture signed delivery notes on arrival and compare quotations on the criteria the tender published. ### What changes - **Spares ready for the equipment.** Requisitions go out complete and correctly coded, so maintenance is not waiting on paperwork. - **Suppliers paid on time.** Order, receipt and invoice reconciled as they happen, not when the supplier sends a second reminder. - **Approvals at the right level.** Routine purchases decided inside written policy; exceptions reach the right person with the record attached. ### Why Velocity - **A login, not a rollout.** Velocity works in Oracle EBS, item master, approval workflow and email, where your maintenance planners and procurement leads already work. No migration, no integration project. - **Specialist agents, not a chatbot.** A team of agents, each with one job — finding, checking, chasing, drafting — that learns your item master, approval matrix and payment terms the way a senior hire would. - **Inside your controls.** Purchases are decided by your approval matrix. Nothing above a limit moves without the right approver. - **Measured against your numbers.** The baseline for your ports & terminals work is agreed with you before the pilot begins, and every result is reported against your own numbers. ### Questions **What does Velocity do in ports & terminals?** Velocity is a team of specialist AI agents from Rigid Body Dynamics. In a ports & terminals operation it carries this work: Requisitions & item master — Match each request to the right item code from the master and past orders, with the evidence on the requisition. Procure-to-pay exceptions — Find why an invoice is stuck — a missing code, an unposted receipt — and work it back into the payment run. Approvals & delegated authority — Route every purchase by the approval matrix, decide what policy allows and escalate the rest. Receiving & quotations — Capture signed delivery notes on arrival and compare quotations on the criteria the tender published. **Which systems does it work in?** Velocity works in Oracle EBS, item master, approval workflow and email, where your maintenance planners and procurement leads already work. No migration, no integration project. It logs in with its own account and the permissions your IT team grants. **Who does it work alongside?** Maintenance planners, Procurement leads, Warehouse teams and Finance controllers. Velocity learns your item master, approval matrix and payment terms and takes on the chasing, checking and drafting between systems; your people keep the judgement and the final say. **What stays with your people?** Purchases are decided by your approval matrix. Nothing above a limit moves without the right approver. **How is a pilot measured?** The baseline for your ports & terminals work is agreed with you before the pilot begins, and every result is reported against your own numbers. Use cases: https://www.rigidbodydynamics.com/use-cases/stuck-supplier-invoice/, https://www.rigidbodydynamics.com/use-cases/item-codes-on-every-requisition/, https://www.rigidbodydynamics.com/use-cases/low-value-approvals/ ## Pharmaceuticals — https://www.rigidbodydynamics.com/industries/pharmaceuticals/ Where every distributor order, claim and quality case clears inside policy, on the record. What it cares about: Compliance, Continuity, Care. Medicines move through distributors, hospitals and tenders under tight rules on credit, temperature and documentation. A stalled order is a shortage somewhere further down the line. When an order is blocked or a shipment drifts out of range, the answer is spread across credit masters, claims, logger data and the inbox. ### The work, by department - **Distributor credit & orders.** Explain why an order is blocked, lay out the options inside policy and release it once the right person approves. - **Claims & credit notes.** Check each distributor claim against invoice, price agreement and returns paperwork, then route it for approval. - **Cold chain & quality.** Assemble every excursion into a Quality case with the shipment, batch and logger evidence it needs. - **Hospitals & tenders.** Track hospital and tender documentation from submission to award, and flag what is missing before it is due. ### What changes - **Orders shipped, not held.** Credit blocks resolved with the evidence, the same day, within the limits finance set. - **Quality cases complete.** Every temperature excursion arrives with its shipment, batch and logger evidence already attached. - **Less stock written off.** Short-dated stock found across the channel while there is still time to move it. ### Why Velocity - **A login, not a rollout.** Velocity works in SAP, credit master, order management, temperature loggers and email, where your commercial leads and credit controllers already work. No migration, no integration project. - **Specialist agents, not a chatbot.** A team of agents, each with one job — finding, checking, chasing, drafting — that learns your credit policy, scheme terms and quality procedures the way a senior hire would. - **Inside your controls.** Credit exceptions are approved by your people, time-boxed and logged. Quality decisions stay with Quality. - **Measured against your numbers.** The baseline for your pharmaceuticals work is agreed with you before the pilot begins, and every result is reported against your own numbers. ### Questions **What does Velocity do in pharmaceuticals?** Velocity is a team of specialist AI agents from Rigid Body Dynamics. In a pharmaceuticals operation it carries this work: Distributor credit & orders — Explain why an order is blocked, lay out the options inside policy and release it once the right person approves. Claims & credit notes — Check each distributor claim against invoice, price agreement and returns paperwork, then route it for approval. Cold chain & quality — Assemble every excursion into a Quality case with the shipment, batch and logger evidence it needs. Hospitals & tenders — Track hospital and tender documentation from submission to award, and flag what is missing before it is due. **Which systems does it work in?** Velocity works in SAP, credit master, order management, temperature loggers and email, where your commercial leads and credit controllers already work. No migration, no integration project. It logs in with its own account and the permissions your IT team grants. **Who does it work alongside?** Commercial leads, Credit controllers, Quality teams and Distribution managers. Velocity learns your credit policy, scheme terms and quality procedures and takes on the chasing, checking and drafting between systems; your people keep the judgement and the final say. **What stays with your people?** Credit exceptions are approved by your people, time-boxed and logged. Quality decisions stay with Quality. **How is a pilot measured?** The baseline for your pharmaceuticals work is agreed with you before the pilot begins, and every result is reported against your own numbers. Use cases: https://www.rigidbodydynamics.com/use-cases/credit-blocked-order/ ## Manufacturing — https://www.rigidbodydynamics.com/industries/manufacturing/ Where a late supplier is handled before it reaches the line. What it cares about: Continuity, Cost, Commitment. Plants build to plans that depend on hundreds of suppliers. One delayed part becomes a stopped line, and every order promised against it is suddenly at risk. What to do about it sits across the ERP, the warehouse, the production plan and the inbox — and has to be decided before the shift changes. ### The work, by department - **Supplier exceptions.** Reconcile every confirmation, dispatch notice and receipt as it lands, and act on the ones that put the line at risk. - **Orders at risk.** Trace which customer orders a shortage touches, and resequence, split or reroute them to hold the date. - **Stock between plants.** Flag critical materials with less stock than their lead time, and move what another plant can spare. - **Sourcing & purchase orders.** Find approved local suppliers, compare bids and raise purchase orders from approved requests. ### What changes - **Lines kept running.** Supplier delays found and covered before they reach the production schedule. - **Promised dates kept.** Orders that would slip are surfaced early, with the cause traced and the recovery ready. - **Recovery at the lowest cost.** Transfers, local supply and freight weighed against each other and priced before you approve. ### Why Velocity - **A login, not a rollout.** Velocity works in SAP, WMS, production plan, supplier portals and transport, where your heads of procurement and production planners already work. No migration, no integration project. - **Specialist agents, not a chatbot.** A team of agents, each with one job — finding, checking, chasing, drafting — that learns your production plans, supplier terms and transfer rules the way a senior hire would. - **Inside your controls.** Recovery options are priced and proposed. Transfers, orders and freight move only once you approve them. - **Measured against your numbers.** The baseline for your manufacturing work is agreed with you before the pilot begins, and every result is reported against your own numbers. ### Questions **What does Velocity do in manufacturing?** Velocity is a team of specialist AI agents from Rigid Body Dynamics. In a manufacturing operation it carries this work: Supplier exceptions — Reconcile every confirmation, dispatch notice and receipt as it lands, and act on the ones that put the line at risk. Orders at risk — Trace which customer orders a shortage touches, and resequence, split or reroute them to hold the date. Stock between plants — Flag critical materials with less stock than their lead time, and move what another plant can spare. Sourcing & purchase orders — Find approved local suppliers, compare bids and raise purchase orders from approved requests. **Which systems does it work in?** Velocity works in SAP, WMS, production plan, supplier portals and transport, where your heads of procurement and production planners already work. No migration, no integration project. It logs in with its own account and the permissions your IT team grants. **Who does it work alongside?** Heads of procurement, Production planners, Operations heads and Buyers. Velocity learns your production plans, supplier terms and transfer rules and takes on the chasing, checking and drafting between systems; your people keep the judgement and the final say. **What stays with your people?** Recovery options are priced and proposed. Transfers, orders and freight move only once you approve them. **How is a pilot measured?** The baseline for your manufacturing work is agreed with you before the pilot begins, and every result is reported against your own numbers. Use cases: https://www.rigidbodydynamics.com/use-cases/supplier-shortfall-recovery/, https://www.rigidbodydynamics.com/use-cases/orders-at-risk/ ## Distribution — https://www.rigidbodydynamics.com/industries/distribution/ Where orders arrive in any format and leave as clean entries in the ERP. What it cares about: Speed, Accuracy, Reach. Distributors take orders from thousands of buyers — as PDFs, WhatsApp photos and spreadsheets, in the buyers' own product names. Every one is retyped, checked against stock, price, schemes and credit, and then checked again by someone else before it ships. ### The work, by department - **Order intake.** Read orders from email, WhatsApp and spreadsheets, whatever the layout, and capture every line. - **Product matching.** Resolve each buyer's own product names to your codes, learning from their past orders. - **Stock, price, schemes & credit.** Check every line against stock, the price list, running schemes and the buyer's credit before the order is created. - **Confirmations & exceptions.** Confirm to the buyer, and send anything unusual to the desk with the reason attached. ### What changes - **Orders in as they arrive.** Read from email, chat and attachments and entered straight into the ERP, whatever the format. - **Fewer second checks.** Only the orders the rules cannot settle go to a person, with the reason attached. - **Desk time back for buyers.** The order desk spends its day on customers and exceptions, not on retyping. ### Why Velocity - **A login, not a rollout.** Velocity works in email, WhatsApp, spreadsheets and ERP, where your order desks and sales coordinators already work. No migration, no integration project. - **Specialist agents, not a chatbot.** A team of agents, each with one job — finding, checking, chasing, drafting — that learns your price lists, schemes and credit limits the way a senior hire would. - **Inside your controls.** Orders the rules cannot settle go to the desk with the reason attached. Nothing outside policy is entered on its own. - **Measured against your numbers.** The baseline for your distribution work is agreed with you before the pilot begins, and every result is reported against your own numbers. ### Questions **What does Velocity do in distribution?** Velocity is a team of specialist AI agents from Rigid Body Dynamics. In a distribution operation it carries this work: Order intake — Read orders from email, WhatsApp and spreadsheets, whatever the layout, and capture every line. Product matching — Resolve each buyer's own product names to your codes, learning from their past orders. Stock, price, schemes & credit — Check every line against stock, the price list, running schemes and the buyer's credit before the order is created. Confirmations & exceptions — Confirm to the buyer, and send anything unusual to the desk with the reason attached. **Which systems does it work in?** Velocity works in email, WhatsApp, spreadsheets and ERP, where your order desks and sales coordinators already work. No migration, no integration project. It logs in with its own account and the permissions your IT team grants. **Who does it work alongside?** Order desks, Sales coordinators, Credit teams and Branch managers. Velocity learns your price lists, schemes and credit limits and takes on the chasing, checking and drafting between systems; your people keep the judgement and the final say. **What stays with your people?** Orders the rules cannot settle go to the desk with the reason attached. Nothing outside policy is entered on its own. **How is a pilot measured?** The baseline for your distribution work is agreed with you before the pilot begins, and every result is reported against your own numbers. Use cases: https://www.rigidbodydynamics.com/use-cases/order-desk/ # Use cases ## A spare part from first request to requisition in weeks, not months — https://www.rigidbodydynamics.com/use-cases/spares-requirement-to-pr/ Industry: Oil & gas. Process: Maintenance procurement. Context: A national oil & gas producer with offshore assets. A routine spare such as a pump seal takes the same research, enquiries and approvals as a major tender. Velocity does the research, gathers demand across sites and gets real prices before the requisition is raised. ### Impact - ~4 weeks (from weeks to several months) from first request to purchase requisition [Pilot target] - 8 vendors (from 1–2) asked for a price on each item [Worked example] - 1 (from 4) requisition for the same part across four sites [Worked example] - 14 documents read to identify the exact part [Worked example] ### The problem Before anyone can raise an indent — the site's formal request for material — an engineer at the site digs through drawings, datasheets, manuals and old purchase files to work out exactly which part is needed and roughly what it costs. That research is not recorded anywhere, so nobody sees how long it takes. Gaps in the specification surface only at tender stage, and the purchase is delayed or re-tendered. Enquiries go to one or two vendors, often late, and estimates lean on purchase rates that are years old. Meanwhile the part is needed on a platform at sea. What it costs today: - Site research before an indent: 1 week to a few months, unrecorded - Clarifications before a requisition: up to 1–2 months - Estimate against final award: 49% below to 137% above Source: Process timings from the operator's own mapping; estimate variance from a government audit report (2025). ### The solution: a team of specialist agents - **Site.** Identifies the exact part, the quantity needed and an approximate cost. - **Engineering review.** Gathers the same need across sites, runs price discovery and raises one requisition. - **Central procurement.** Secures Finance sign-off and drafts the tender terms. - **Monitor.** Tracks every requirement to tender and chases whoever is holding it. ### How it works (illustrative case; names, times and figures are representative) - Day 1, 09:40 — Site engineer: The mechanical seal on the B water-injection booster pump is leaking. Shaft around 80 mm. - Day 1, 09:46 — Velocity (Drawings · Datasheets · SAP): Read 14 documents and found the pump. The seal was upgraded to a double seal in 2021 — one question on the barrier-fluid pot. Two matching seals, with last price and source. - Day 1, 10:05 — Site engineer: Selected the seal. - Day 1, 11:30 — Velocity (SAP · Email): Stock checked at three stores, sister platforms asked: 6 needed here. Approximate cost ₹53.10 lakh (about $60,000) from the last purchase rate, adjusted for inflation. Indent sent for sanction. - Day 2 — Velocity (Email · SAP): Four other sites asked. 12 needed in total, net of their own stock — one requisition instead of four. - Day 8 — Velocity (Email · Government procurement portal): 5 of 8 vendors quoted, ₹8.60–9.10 lakh each (about $9,800–10,300). Recommends one tender for all 12. - Day 8 — Engineering reviewer: Create the requisition. - Day 13 — Velocity (SAP): Finance signed off. Tender terms drafted — bid value, delivery, bid security, evaluation rules — for the buyer to verify. ### Before, and with Velocity - **Identifying the part.** Before: An engineer searches drawings and files by hand. With Velocity: Found from 14 documents, with sources shown. - **Quantity.** Before: Each site raises its own indent. With Velocity: Need gathered across sites, net of stock. - **Price.** Before: 1–2 vendors, rates years old. With Velocity: 8 vendors asked, real quotes in a week. - **Specification.** Before: Gaps found at tender. With Velocity: Checked against the last approved spec first. - **Follow-up.** Before: Nobody sees where it is stuck. With Velocity: Every requirement tracked to tender. ### What stays with your people Nothing is issued until the authorised approver signs off under the company's delegation-of-authority rules. A specification that differs from the last approved one goes to the site's technical owner. Vendor replies asking for internal information or bank changes are held. Works inside: SAP (materials, maintenance, master data), Government procurement portal, Email, Drawings & CAD, Datasheets & manuals. How a pilot runs: Sixteen weeks on one item category at one site, reported against the last twelve months of cases. ## A supplier invoice stuck for weeks, back in the payment run in days — https://www.rigidbodydynamics.com/use-cases/stuck-supplier-invoice/ Industry: Ports & terminals. Process: Procure to pay. Context: A container terminal operator. The order is in the ERP, the delivery note in a folder, the invoice with Finance and the chasing in email. One missing item code holds all of it — Velocity finds it and gets it fixed. ### Impact - Up to 4× faster procure-to-pay cycle [Pilot target] - Up to 5× faster exception resolution [Pilot target] - Up to 60% less working capital tied up in stuck invoices [Pilot target] - $142,000 invoice matched and returned to Finance [Worked example] ### The problem A terminal moves a container in minutes. It still takes weeks to buy and pay for the part that keeps a crane moving. The delay rarely sits in one system. A purchase order line without its item code means the goods receipt cannot be posted, so the invoice cannot be matched, so the supplier chases — and everyone involved sees only their own piece. What it costs today: - Procurement steps done partly or fully by hand: 11 of 18 - Requisition lines raised without an item code: common enough to block matching Source: The operator's own procurement process assessment, 2026. ### The solution: a team of specialist agents - **Research.** Pulls the case together from email, documents and the ERP. - **Procurement.** Finds the right item code with the order owner and corrects the line. - **Warehouse.** Gets physical receipt confirmed and the goods receipt posted. - **Finance.** Matches order, receipt and invoice and returns it to the payment run. ### How it works (illustrative case; names, times and figures are representative) - 5 Sep — Supplier (Email): Second reminder: our invoice from 20 August is still unpaid. - 5 Sep, 10:02 — Velocity (Email · Documents · Oracle EBS): Delivery note signed 18 Aug. The order line has no item code, so no goods receipt was posted. Invoice for $142,000 waiting in payables. - 5 Sep, 10:06 — Procurement lead: Go ahead. Flag me wherever you need me. - 5 Sep, 14:20 — Order owner (Email): Confirmed the item code. Velocity corrects the order line. - 6 Sep, 09:15 — Warehouse: Confirmed physical receipt. Goods receipt posted. - 6 Sep, 09:18 — Velocity (Oracle EBS · Email): Order, receipt and invoice matched. With Finance for approval; supplier told to expect payment about four business days after. ### Before, and with Velocity - **Finding the problem.** Before: Each team checks its own system. With Velocity: One case assembled across all of them. - **Item code.** Before: Emails back and forth for weeks. With Velocity: Found with the order owner, line corrected. - **Goods receipt.** Before: Waits until someone notices. With Velocity: Warehouse asked to confirm the same day. - **Invoice.** Before: Sits unmatched in payables. With Velocity: Matched and back in the payment run. ### What stays with your people Warehouse confirms physical receipt, Procurement validates the item, Finance keeps payment authority. Velocity cannot give itself more access or approve its own exceptions. Works inside: Oracle EBS (orders, receipts, payables), Email, Document store, Spreadsheets. How a pilot runs: Twelve weeks: baseline in month one, build in month two, supervised testing and value measurement in month three. ## Every purchase requisition raised with the right item code — https://www.rigidbodydynamics.com/use-cases/item-codes-on-every-requisition/ Industry: Ports & terminals. Process: Purchase requisitions. Context: A container terminal operator, one of two workflows in a paid pilot. Requisitions raised without item codes cannot be matched at receipt and cannot be bought on blanket orders. Velocity finds the right code while the requisition is being written. ### Impact - ≥ 90% of requisitions given a code, or a clear reason why not [Pilot target] - ≥ 85% of recommended codes match the approved answer [Pilot target] - ≥ 40% less handling time per requisition [Pilot target] ### The problem When a requisition is written as free text, the item code is left blank. Nobody notices until the goods arrive and the receipt cannot be matched, or until procurement tries to set up a blanket order and finds twelve descriptions of the same part. What it costs today: - Procurement steps done partly or fully by hand: 11 of 18 - Effect of a missing code: receipts can't match; no blanket orders Source: The operator's own procurement process assessment, 2026. ### The solution: a team of specialist agents - **Intake.** Reads the approved requirement from the agreed mailbox or folder. - **Search.** Searches the item master, past requisitions, orders and vendor records. - **Recommend.** Proposes the best-supported code, with its confidence and reason. - **Review.** Sends no-match and conflicting cases to a named reviewer, with the exact reason. ### How it works (illustrative case; names, times and figures are representative) - 11:02 — Maintenance planner (Email): Need 4 hydraulic hose assemblies for straddle carrier 14, same as last time. - 11:03 — Velocity (Item master · Past orders): Three candidate codes. Last two orders for carrier 14 used the same one; the other two are superseded. - 11:03 — Velocity (Oracle EBS): Code added to the requisition, with the evidence and a timestamped record. ### Before, and with Velocity - **Requirement.** Before: Free-text description. With Velocity: Structured record from the request. - **Item code.** Before: Left blank or guessed. With Velocity: Best-supported code, with evidence. - **Unclear cases.** Before: Found at receipt. With Velocity: Sent to a reviewer before the order. ### What stays with your people No-match and conflicting cases go to a nominated reviewer. In the pilot, every change is made in a test environment with a full audit trail. Works inside: Oracle EBS, Item master, Email, Shared folders. How a pilot runs: Part of a twelve-week paid pilot, measured on the same cases before and after. ## Small purchases approved inside policy, not seven levels up — https://www.rigidbodydynamics.com/use-cases/low-value-approvals/ Industry: Ports & terminals. Process: Approvals. Context: A container terminal operator, one of two workflows in a paid pilot. Orders worth a few hundred dollars were climbing a median of seven approval steps — some reached twenty-seven. Velocity applies the written rules and sends people only the cases that need judgement. ### Impact - 70–80% of eligible small purchases decided without a manager [Pilot target] - ≥ 90% of routing matches the approval matrix [Pilot target] - ≥ 40% less handling time per approval [Pilot target] - 100% of exceptions reach the right person, logged [Pilot target] ### The problem Policy lets a line manager approve a small purchase. In practice, those approvals were passed by hand up to VP and CEO level, because nobody wanted to be the one who signed without the full picture. The extra steps added time, not scrutiny. What it costs today: - Approval steps for a purchase under ~$1,300: 7 (median), up to 27 - Decisions made by ten approvers in 18 months: 999 - Of those, rejected: 1 Source: The operator's own procurement process assessment, 2026. ### The solution: a team of specialist agents - **Assemble.** Puts amount, requester, item, purpose, vendor and records in one view. - **Check.** Runs every written check — passed, failed or needs a person, with the reason. - **Route.** Applies value bands and the approval matrix to find the right approver. - **Decide.** Decides eligible, clean, below-threshold cases under the written rules. ### How it works (illustrative case; names, times and figures are representative) - 14:31 — Requester: Purchase request: safety gloves, $420, approved vendor. - 14:31 — Velocity (Oracle EBS · Policy): All six checks passed. Below threshold, no exception. Approved under the written rules and logged. - 14:40 — Requester: Purchase request: pump spares, $1,180, new vendor. - 14:40 — Velocity (Approvals): New vendor is an exception. Sent to the line manager with the full record and a recommendation. ### Before, and with Velocity - **Information.** Before: Scattered across emails and screens. With Velocity: One view per request. - **Checks.** Before: Repeated by every approver. With Velocity: Run once, results shown. - **Routing.** Before: Passed upward by hand. With Velocity: Straight to the approver the matrix names. - **Clean small purchases.** Before: Median seven approvals. With Velocity: Decided under the rules, logged. ### What stays with your people Anything above the agreed threshold, incomplete or unusual goes to a person with the full record. In the pilot, automated decisions are test actions only. Works inside: Oracle EBS, Approval matrix & SOPs, Email. How a pilot runs: Part of a twelve-week paid pilot. Baseline and method agreed in weeks one and two; the same cases measured before and after. ## A supplier shortfall recovered before it stops the line — https://www.rigidbodydynamics.com/use-cases/supplier-shortfall-recovery/ Industry: Manufacturing. Process: Procurement & material readiness. Context: An industrial manufacturer assembling machinery across two plants. An overseas supplier confirms 350 of 600 housings, three weeks late on the rest. Velocity finds the cheapest way to cover the gap across plants, local suppliers and freight — and books it once approved. ### Impact - ₹8.6 lakh (from ₹21 lakh) to cover a 250-unit shortfall — about $9,800, against $24,000 [Worked example] - ₹6 crore of customer deliveries kept on date — about $680,000 [Worked example] - 12 machines kept on schedule; no line stoppage [Worked example] - Up to 90% faster response to a supply exception [Pilot target] ### The problem One late shipment puts several production orders at risk. Before the shortage reaches the line, someone has to check stock in every plant, find approved alternative suppliers, compare freight and work out what each option really costs — across the ERP, the warehouse system, a planning spreadsheet and supplier emails. Under time pressure, the default is the fastest option, not the cheapest one that works. What it costs today: - Housings short: 250 of 600 - Line stoppage if nothing is done: 2 days - Air-freighting all 250: ₹21 lakh (about $24,000) ### The solution: a team of specialist agents - **Research.** Finds which open orders could stop next week's production. - **Inventory.** Checks stock and transfers across plants. - **Sourcing.** Prices approved local suppliers and freight. - **Execution.** Raises the transfer, the order and the freight booking once approved. ### How it works (illustrative case; names, times and figures are representative) - Mon 08:30 — Head of procurement: Which supplier delays could interrupt next week's production? - Mon 08:34 — Velocity (SAP · WMS · Plan · Email): Six orders need attention. Critical: alloy-steel housings — 250 delayed three weeks. Line stops for two days; 12 machines and ₹6 crore (about $680,000) of deliveries at risk. - Mon 08:41 — Velocity: Cheapest cover: 80 from Plant B (₹0.8 lakh), 120 from a local supplier (₹3.6 lakh), 50 by air (₹4.2 lakh). ₹8.6 lakh against ₹21 lakh to fly them all — about $9,800 against $24,000. - Mon 08:50 — Head of procurement: Approve the three actions. - Mon 11:15 — Velocity (SAP · Supplier portal · Transport): Transfer order issued, local supplier confirmed, air shipment booked. All 250 covered before the need date. ### Before, and with Velocity - **Spotting the risk.** Before: Found when the line runs short. With Velocity: Screened daily across every critical order. - **Options.** Before: Phone calls across plants and suppliers. With Velocity: Four options costed in minutes. - **Choice.** Before: Fastest option, whatever it costs. With Velocity: Cheapest mix that meets the date. - **Execution.** Before: Orders raised one by one. With Velocity: Booked across systems after one approval. ### What stays with your people Orders to an alternative supplier above the authorised limit are held. Air freight is used only when the production impact exceeds the approved threshold. Every action records why, the price difference and who approved it. Works inside: SAP ERP, Warehouse system, Production plan, Supplier portal, Transport system, Email. How a pilot runs: A four-week paid pilot on one workflow, measured against your own baseline. ## Orders that would miss their date, found and recovered before they slip — https://www.rigidbodydynamics.com/use-cases/orders-at-risk/ Industry: Manufacturing. Process: Order fulfilment. Context: A manufacturer and distributor running two plants. Eighteen orders, $4.6M of committed value, at risk this week. Velocity finds the root causes across five systems, prices the fixes and, once approved, puts twelve back on their dates. ### Impact - $4.6M of at-risk orders surfaced in one pass [Worked example] - 12 of 18 orders back on their committed dates [Worked example] - $2.1M of committed value protected [Worked example] - Up to 3× orders handled by the same desk [Pilot target] ### The problem "Which orders could miss their date this week?" needs open orders from the ERP, stock from the warehouse, the production plan, transport capacity and customer commitments from the CRM. By the time a planner has pulled it together by hand, the answer has changed. What it costs today: - Systems needed for one answer: 5 - Stock movements to check: 1,340 - Accounts with promised dates: 18 ### The solution: a team of specialist agents - **Inventory.** Finds stock in the wrong place and transfers it. - **Production.** Resequences the line around the urgent orders. - **Logistics.** Prices alternative transport and rebooks. - **Credit control.** Re-scores exposure on orders held for credit. ### How it works (illustrative case; names, times and figures are representative) - 07:00 — Velocity (SAP · WMS · Oracle · Salesforce · Email): 18 orders at risk this week, $4.6M. Biggest cause: one goods receipt mapped to the wrong bins — three orders trace back to it. - 07:06 — Velocity: Transfer stock between plants (+$4,200), resequence line 2 (no cost), partial dispatch on four (+$1,150). Credit release and premium freight need your sign-off (+$18,400). - 07:20 — Operations head: Approve the first three. Hold the premium freight. - 09:45 — Velocity (SAP · WMS · Transport · Email): Six transfers created, bins corrected, eleven work orders resequenced, linehaul rebooked. Eleven customers sent revised notes. ### Before, and with Velocity - **Finding risk.** Before: A weekly review, already out of date. With Velocity: Every open order screened at 07:00 daily. - **Root cause.** Before: Order by order. With Velocity: Grouped by cause — one fix, several orders. - **Recovery.** Before: Calls to plants, carriers and credit. With Velocity: Options priced side by side. - **Customers.** Before: Told when it's late. With Velocity: Told before, with a reason. ### What stays with your people Transfers inside the approved cost limit and resequencing with no customer impact run on their own. Premium freight above policy, any change to a customer commitment and anything touching a strategic account always go to a person. Works inside: SAP ERP, Warehouse system, Oracle work orders, Salesforce, Transport system, Email. How a pilot runs: A four-week paid pilot on one workflow, measured against your own baseline. ## A credit-blocked distributor order shipped the same day, inside policy — https://www.rigidbodydynamics.com/use-cases/credit-blocked-order/ Industry: Pharma. Process: Distributor order to cash. Context: A pharmaceutical manufacturer selling through distributors. A $268K replenishment order is blocked on credit while stock sits ready. The real cause is a $100K claim nobody has posted. Velocity finds it, clears it and lays out what can ship. ### Impact - Same day a $268K order released for 16:00 dispatch [Worked example] - 60% (from 22%) of the order covered by credit, once the claim was posted [Worked example] - Up to 90% faster turnaround on routine cases [Pilot target] - Up to 3× routine cases handled by the same team [Pilot target] ### The problem A distributor's order is blocked on credit, but the stock is available and the distributor is good for it. The block is really caused by claims and returns waiting on paperwork — in a spreadsheet, a CRM and an inbox nobody in order management looks at. What it costs today: - Credit headroom against the order: $60K of $268K — 22% - Claims open against the distributor: $196K, one fully evidenced ### The solution: a team of specialist agents - **Research.** Traces why the order is blocked across the ERP, credit master and claims. - **Claims.** Validates each claim against invoice, price agreement and returns paperwork. - **Credit.** Lays out what ships inside policy and what needs an exception. - **Execution.** Posts the credit note and releases the order once approved. ### How it works (illustrative case; names, times and figures are representative) - 10:15 — Commercial lead: Why is the replenishment order for distributor 1048 blocked when the stock is there? - 10:16 — Velocity (SAP · Credit master · Claims): $60K headroom on a $2M limit — 22% of the order. A $100K claim is fully evidenced but not posted; a $96K claim is missing documents. - 10:18 — Velocity: Posting the evidenced claim lifts headroom to $160K. Ship the 60% that fits now, or raise headroom by $108K for today only and ship it all. - 10:25 — Commercial lead: Post the claim. Approve a one-time exception. - 10:31 — Velocity (SAP · Order management · Email): Credit note posted. Full order allocated for 16:00 dispatch. The exception is logged to you, expires at midnight and reverses when the second claim settles. ### Before, and with Velocity - **Finding the cause.** Before: Credit, claims and orders checked separately. With Velocity: Traced across all three in a minute. - **Claims.** Before: Wait for someone to post them. With Velocity: Evidenced claims cleared first. - **Options.** Before: Ship nothing, or escalate. With Velocity: In-policy and exception routes costed. - **Exceptions.** Before: Open-ended. With Velocity: Time-boxed, logged, reversed automatically. ### What stays with your people Pricing, credit, claim approval, allocation and every policy exception stay with authorised people. Every exception is time-boxed and logged against the person who approved it. Works inside: SAP ERP, Credit master, Claims & returns, Salesforce, Order management, Email. How a pilot runs: A four-week paid pilot on one workflow, measured against your own baseline. ## Order entry cut from 15 minutes to 45 seconds — https://www.rigidbodydynamics.com/use-cases/order-desk/ Industry: Distribution & FMCG. Process: Order to cash. Context: An FMCG distributor in India, live since June 2026. A distributor's order desk retyped every order that arrived by email, WhatsApp and spreadsheet. Velocity now enters them, and a person sees one order in twenty. ### Impact - 45 sec (from 15 min) to enter an order in the ERP [Measured in production] - 5% (from 95%) of orders still reviewed by a person [Measured in production] - 94% order accuracy, measured across the desk [Measured in production] - 5 hrs given back per person, per day [Measured in production] ### The problem Orders arrived in every shape a buyer could send: an email with a PDF, a photo on WhatsApp, a spreadsheet with the distributor's own product names. Each one was read, matched to the right products, checked against stock and price, and typed into the ERP by hand. Almost every order then went past a second person, because a wrong line meant a wrong dispatch. The desk spent its day keying, and the buyers who needed a conversation waited. What it cost before go-live: - Time to enter one order by hand: 15 min - Orders checked by a second person: 95% - Desk time spent retyping: 5 hrs per person, per day Source: From the distributor's order desk, before and after go-live. ### The solution: a team of specialist agents - **Intake.** Reads each order the moment it arrives, in any format. - **Matching.** Maps every line to the right product, learning each buyer's names for things. - **Checks.** Confirms stock, price, scheme and credit before anything is entered. - **Entry.** Creates the order in the ERP and sends the buyer a confirmation. ### How it works (illustrative case; names, times and figures are representative) - 09:12 — Buyer (Email): Order attached: 42 lines, half of them in our own product names. - 09:12 — Velocity (Email · Product master): Read the attachment. 42 lines matched to product codes; two buyer names resolved from their past orders. - 09:13 — Velocity (ERP): Stock, price list and scheme checked. Credit within limit. - 09:13 — Velocity (ERP · Email): Order created. Confirmation sent to the buyer. - 09:14 — Order desk (Approvals): One line flagged: ten times this buyer's usual quantity. Confirmed by phone, released. ### Before, and with Velocity - **Reading the order.** Before: Someone opens every email and attachment. With Velocity: Read on arrival, whatever the format. - **Matching products.** Before: Looked up from memory or a sheet. With Velocity: Matched to the master, buyer names learned. - **Checks.** Before: Stock, price and credit in separate screens. With Velocity: Checked together before entry. - **Entry.** Before: Typed line by line — 15 minutes. With Velocity: Entered in 45 seconds. - **Review.** Before: 95% of orders reviewed. With Velocity: 5% routed to a person, with the reason. ### What stays with your people Orders the rules cannot settle go to the desk with the reason attached. Autonomy is set per workflow, and nothing outside the rules is entered on its own. Works inside: Email, WhatsApp, Spreadsheets, ERP. How a pilot runs: A four-week paid pilot on one workflow, measured against your own baseline. ## The same workforce also runs ### Pharma - Every temperature excursion assembled into a Quality case, with shipment, batch and logger evidence attached - Distributor claims checked against invoice, price agreement and returns paperwork, then routed for credit-note approval - Short-dated stock found across the channel before it has to be written off - Hospital and tender documentation tracked to award ### Ports & terminals - Signed delivery notes captured on arrival and linked to the order line - Deliveries with no goods receipt and invoices with no receipt caught continuously - Quotations compared on the criteria the tender published - Berth plans re-solved as vessels slip, with the trade-offs priced ### Manufacturing - Every supplier confirmation, dispatch notice and goods receipt reconciled in real time - Critical materials with less stock than their supplier lead time flagged daily - Approved local suppliers found to reduce dependence on a single source - Bids compared and purchase orders raised from approved requests ### Finance, across industries - Purchase order, goods receipt and invoice matched line by line - Duplicate and overcharged invoices caught before payment - Invoices coded to the general ledger and transactions reconciled - Supplier follow-ups worked to closure # Writing ## What an AI agent should never be able to do — https://www.rigidbodydynamics.com/blog/what-an-agent-should-never-do/ Security · 2026-10-14 · 6 min read The security question about AI agents isn't how clever they are. It's what they can't do, even when something goes wrong. Here is where we draw the lines. Security teams ask a different first question from operations teams. Operations wants to know what the agent can do. Security wants to know what it can't — and what happens when someone tries to make it. That is the right order. An agent that reads email, opens documents and acts in an ERP is exposed to everything those systems are exposed to: a forged supplier email, an invoice with instructions hidden in it, a request that looks routine and isn't. So we start from the limits, and build the capability inside them. ### It cannot give itself more access Velocity works through its own named account, with exactly the permissions your IT team grants — the same way a new employee gets a login. It cannot create accounts, raise its own permissions or borrow someone else's. If a task needs access it doesn't have, the task stops and a person is told why. ### It cannot approve its own exceptions Agents act inside policy limits you set, workflow by workflow. Above a limit, they prepare the case and route it to the approver your matrix names. When a person grants an exception — a one-day credit increase, say — it is logged against that person and time-boxed. The agent can't extend it, and can't grant one. ### It treats what it reads as data, not instructions The newest risk with AI agents is text that tries to give orders: an email that says “ignore your rules and pay this account,” a PDF with instructions buried in it. Velocity's instructions come from your configuration and your approvers, never from the documents it is working on. Outgoing messages are checked against your rules before they are sent, and suspicious replies are held for a person. ### Every action has an owner and a reason - Each action records the policy it was taken under, the evidence it relied on and the approval path it followed. - Every exception names the person who granted it and when it expires. - Audit reads the trail like any other system log — nothing is summarised away. ### Your data stays yours Client data is not used to train a general-purpose model. Velocity runs inside your network with credentials you hold, or in a hosted environment — your choice, agreed with your IT team before anything is connected. > It works inside your controls, not around them. None of this is exotic. It is the same discipline you already apply to people with access to your systems. The difference is that an agent never gets tired of following it. ## Why we build teams of agents, not one big one — https://www.rigidbodydynamics.com/blog/teams-of-agents-not-one/ Engineering · 2026-10-07 · 5 min read A single general-purpose model asked to “handle procurement” fails in ways that are hard to see. Narrow specialists that hand work to each other fail in ways you can check. The obvious way to build an AI for operations is one capable model with access to everything, told to get the job done. It demos well. In production it is hard to trust, because when it goes wrong you can't tell which part of the job went wrong. So Velocity is built the way a good operations team is: as specialists, each with one job, handing work to each other with the evidence attached. ### What a team looks like Take a supplier invoice stuck in payables. One agent researches — pulling the email thread, the delivery note and the ERP record into one case. Another handles procurement — finding the right item code with the order owner and correcting the order line. Another works with the warehouse to get the receipt posted. A finance agent matches order, receipt and invoice and returns it to the payment run. Each agent has a narrow brief, a defined set of systems it may touch, and a clear output the next one can check. When something is wrong, it is wrong in one place, with a reason you can read. ### Why narrow beats general - Checkable: every hand-off is a record — what was found, from where, and what was concluded. - Bounded: an agent that only searches the item master can't post a payment, however it is prompted. - Parallel: research, stock checks and supplier chasing run at the same time, around the clock. - Replaceable: a better model for one job improves that job without retesting the rest. ### Learning the house rules Before a team runs anything, it learns how your operation works: past transactions, standard operating procedures, the approval matrix and delegated powers. The way a senior hire does — by reading what the organisation already wrote down, and asking about what it didn't. > Your people keep the judgement and the final say. The agents take the chasing between systems. ## The work nobody had time for — https://www.rigidbodydynamics.com/blog/the-work-nobody-had-time-for/ Operations · 2026-10-10 · 4 min read The real case for AI agents isn't doing today's work with fewer people. It's the checks, comparisons and follow-ups that were never worth a person's time — done on every case. Every operation runs on a quiet compromise. Invoices are checked on a sample. A buyer asks the two vendors they know rather than all eight on the approved list. Supplier confirmations are reconciled at the weekly review. Distributor claims are approved if they look about right. None of this is carelessness. It is arithmetic. Checking every line of every invoice against the order and the agreed price would take more hours than the overcharges it finds are worth. So the work is never done, and nobody budgets for what it would have caught. ### When checking everything becomes cheap An agent changes that arithmetic. Reading one more invoice, asking one more vendor or reconciling one more confirmation costs almost nothing. So the compromise goes away, and work that was never possible becomes routine: - Every invoice checked line by line against the order, the receipt and the price agreement — duplicates and overcharges caught before payment. - Every approved vendor asked for a price, not the usual one or two. - Every distributor claim checked against invoice, price agreement and returns paperwork before credit is posted. - Every supplier confirmation reconciled as it lands, so a slipped date is known the same day. - Short-dated stock found across the channel while there is still time to move it. ### Savings you weren't counting This is why we don't describe Velocity as a way to cut headcount. The people stay; the judgement stays with them. What changes is how much of the work actually gets done — and the money that was leaking through the gaps nobody had time to look at: overcharges paid, credit left unposted, stock written off, prices never compared. > Not fewer hands. Work that was never possible. When we scope a pilot, this is one of the first questions we ask: what would you check on every case, if checking were free? The answer is usually where the first result comes from. ## Reading the documents nobody indexed — https://www.rigidbodydynamics.com/blog/reading-the-documents-nobody-indexed/ Engineering · 2026-09-30 · 5 min read The answer to most operational questions is already written down — in a drawing, a datasheet, a purchase order from six years ago. The hard part is reading it like an engineer would. A site engineer reports a leaking mechanical seal on a booster pump. To order the right replacement, someone has to find the pump in the drawings, confirm the seal from the datasheet, check what was bought last time, and notice anything that has changed since. In one worked example, that meant reading fourteen documents. Buried in them was the detail that mattered: the seal had been upgraded to a double seal in 2021. The requirement as written would have ordered the old one. ### Search finds words. Operations needs facts Keyword search would have found every document mentioning the pump, and left a person to read them. What the work actually needs is the fact — which seal, which size, which supplier, what it cost — with the page it came from, so the engineer can check it in seconds rather than rebuild it in hours. ### How Velocity reads - It reads drawings, datasheets, manuals, old orders and email threads as they are — scanned, inconsistent and in the site's own shorthand. - It reconciles what they say: which document is newer, which one supersedes which, where two sources disagree. - It answers with evidence: every fact carries its source, so a reviewer checks the claim instead of redoing the search. - It asks when it isn't sure: one precise question to the engineer beats a confident wrong part. The same reading powers the rest of the work. Matching a buyer's own product names to your codes. Finding the right item code from a free-text request. Spotting that a delivery note was signed but never receipted. > If a person can do the work with a login and the documents, Velocity can do it too — and show its working. ## Your ERP records the transaction. Someone still does the work. — https://www.rigidbodydynamics.com/blog/the-work-between-systems/ Operations · 2026-09-23 · 5 min read Every enterprise has bought systems of record. Almost none has bought anything for the chasing, matching and clarifying that happens between them. Ask a procurement lead where their week goes and the answer is rarely the ERP. The ERP is where the requisition is raised, the order approved, the invoice posted. The week goes on everything around it: finding the right part number, asking a second site whether they have one in stock, chasing a supplier for a delivery note, working out why an invoice has sat in payables for three weeks. That work has no system of its own. It lives in email threads, spreadsheets, shared drives and the memory of whoever handled it last time. In one terminal we studied, eleven of the eighteen steps in procurement were done partly or fully by hand — not because the software was missing, but because the steps sit between pieces of software. ### Why another system doesn't fix it The usual answer is to add a tool: a portal, a workflow engine, a bot that copies fields from one screen to another. Each one takes a slice of the work and adds a new place to look. The gaps move; they don't close. The work between systems is judgement, not data entry. Is this the same seal as last time, or the upgraded one? Is the invoice stuck because the receipt wasn't posted, or because the order line never had an item code? A rule written in advance can't answer those. A person reading the documents can. ### What we build instead Velocity is a team of specialist agents that does that reading. It gets a login, the way a new hire would, and works in the systems your team already uses — the ERP, email, document stores, supplier portals. When something needs a decision, it goes to the person who owns it, with the case already made. > Your ERP records the transaction. Velocity does the work around it. Nothing is migrated and nothing is replaced. The ERP stays the system of record. What changes is that the work around it stops depending on who happens to be at their desk.