Skip to content

FAQ

This page answers fifteen questions about the engagement, your ERP, AI agents, the people who do the work today, security and commercials. Each answer links to the page that covers the topic in full.

By the end of the two-week Discovery Sprint, the Working Prototype runs the top workflow on your real data. It is a prototype: it reads your data and writes nothing to your ERP. During the Embedded Build, our forward-deployed engineers release working software every week to the people who use it. See Discovery Sprint and Embedded Build.

Yes, by default, in the Discovery Sprint and the Embedded Build. An engineer has to watch an order being keyed, and ask why at each step, to see the work as it is. The Discovery Sprint is two weeks on site. For the Embedded Build, the on-site schedule is agreed before the build starts. In Operate & Automate they come back on site for one week each quarter. See A week on site.

A sponsor who owns operations, a workflow owner for each workflow, access to the floor and the offices, read access to the ERP and its data, a place to sit, a safety orientation and decisions within a week. We do not need a requirements document. See What we need from you.

You can stop after any stage. After the Discovery Sprint you keep all four deliverables. After the build you own the custom code and the data built for you, and we hand over the documentation and runbooks so that an in-house team or another vendor can take over. Your contract gives you the right to keep running and changing the parts that come from our reusable tooling. See Handover and exit.

No. The ERP you already run stays the system of record, and we build what it does not cover, around it. That holds for an ERP such as SAP Business One, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Epicor, Infor, Sage, Acumatica, SYSPRO, QuickBooks Enterprise or whatever you run. If there is no usable ERP, we build an ERP-like core that you own. See Attaching to your existing ERP and When there is no usable ERP.

Not its configuration. We read from the ERP and write to it only through interfaces it supports. When a workflow needs a change inside the ERP, such as a new field or a database view, our engineers write the request, it goes through your change control and your ERP administrator or ERP partner makes it. We work alongside your partner. See Working with your IT team and ERP partner.

Fully digital work: work whose inputs and outputs are all digital, such as emails, documents and ERP transactions. In sales order entry, an agent reads the emailed purchase order, matches the part numbers and drafts the order for your order desk to check. Agents do not do physical work and do not operate machinery. See How agents work for your team.

Who decides when an agent does more on its own?

Section titled “Who decides when an agent does more on its own?”

The workflow owner, through a promotion review. A workflow moves up the autonomy ladder one level at a time. The review checks measured accuracy on real work against a threshold set in advance, the cost of a wrong action, that every action is logged and reversible, and the workflow owner’s sign-off. Not every workflow should reach Level 4 (Autonomous). Some stay at Level 2 (Prepared) or Level 3 (Supervised) for good. See The autonomy ladder and Promotion reviews.

What happens when an agent gets something wrong?

Section titled “What happens when an agent gets something wrong?”

It depends on the level. At Level 2 a person reviews and approves every transaction before anything is entered. At Level 3 the agent completes work within its limits, people spot-check it and a case outside the limits goes to a person as an exception. Every action is in the audit trail, and a promotion review requires that every action be reversible, so a wrong one can be traced and put right. The stop switch halts an agent at once, and the workflow owner can move the workflow down a level, for example back to a person approving every transaction. See Guardrails and limits and Approvals and exceptions.

What happens to the people who do this work today?

Section titled “What happens to the people who do this work today?”

The digital work does get automated, step by step, and their work changes with it. The people who do that work today decide how it should work, approve what agents prepare, handle the exceptions and audit the results. Their knowledge is what the software is built from, and each workflow has a workflow owner who is one of your employees. The hours that keying took are measured and shown to you, and what your team does with them is your decision. See How agents work for your team.

Only the data a workflow step needs. To read an emailed purchase order, the model receives that email and its attachment, not the rest of the inbox and not your ERP. The provider is agreed with you in writing, and its terms on training and retention are reviewed with you, before any document of yours reaches a model. For the Working Prototype that is before day one of the Discovery Sprint. For an agent it is before its workflow goes live. See AI providers and your data.

No. We are a new company and hold none. We work to five principles: least access, credentials you control, everything logged, your data stays yours and people own the limits. Security terms, hosting location and support response times are agreed in each contract, and Stages and terms lists what your contract records. See Security principles.

Each stage is priced a different way. The Discovery Sprint is a fixed fee. The Embedded Build is priced per engineer per month. Operate & Automate is a monthly fee with a starting price: it depends on how many workflows we run and support, and the proposal states it before you commit. Travel and AI model usage are billed at cost. Hosting, and any extra ERP licenses your vendor requires, are not in our prices. The figures are on the pricing page, and Stages and terms explains what is fixed and what varies.

You do. You own the custom code and the data built for you. We keep our reusable tooling, which supplies common parts such as the work queue, the approval screens, the audit trail and the stop switch. Your contract gives you the right to keep running and changing the copy inside your software after we leave, with no license fee. See Handover and exit and Data ownership and portability.

Can we speak to companies you have worked with?

Section titled “Can we speak to companies you have worked with?”

Not yet. We are a new company, with no customers so far and no results to report. What you can judge is the work itself: the Discovery Sprint is two weeks for a fixed fee, and you keep its four deliverables whether or not you continue. See Is this a fit?.