Tell us what’s breaking.

We would rather give you a number here than make you book a call for one. Discovery is a fixed fee, generally $25,000–$60,000 depending on the size of the estate and how many systems we need to map. A first production release with a small team is usually a $180,000–$450,000 range of work. Those are what engagements of this shape cost and what we would expect to quote — not an average of ours, because we are new enough that an average would be three numbers in a trench coat, and you should discount any firm that pretends otherwise. Yours is quoted against a written scope, in phases, with each phase’s cost and exit criteria fixed before it starts, so the decision to continue is yours at every boundary. If your budget is smaller than that, say so on the call: we will tell you whether the problem is buildable for it, including when the answer is no.

Honestly? On résumé, badly, and you should discount anyone who tells you otherwise. There are onshore firms in this space that have been doing it for eighteen, thirty, even fifty years, with senior engineers, named clients in your industry and reference calls we cannot match yet. If your decision rests on track record alone, hire one of them; several are genuinely excellent and we will name them on the call. The difference we would ask you to weigh is commercial rather than technical. We publish what work costs, the method by which we produce an estimate and who pays when it is wrong, and the terms on which you leave — before you talk to us, not in a negotiation. Very few firms in this tier publish the last two, and the reason is that they are commitments rather than claims: they constrain us, they are checkable against what we actually do, and copying them costs something. That is the trade on offer. Longer history and more logos on one side; published commitments and a smaller senior team that will tell you when not to build, on the other.

Discovery usually starts within two to three weeks. A full delivery team typically needs four to six weeks of notice, though we occasionally have earlier availability; it’s worth asking.

Usually between them, and the honest answer is that we want both of them to stay. Your integrator should keep the control layer, the PLCs and everything at or below the line where a mistake stops production; they hold vendor certifications and site knowledge we are not going to duplicate. Your ERP partner should keep everything inside the ERP, where they know the data model and the upgrade path far better than we will. What often has no owner is the layer in between: the browser-facing application your operators actually use, the queue and the retry between the two systems, the identity and audit trail that lets you answer a question about one record on one day. Neither of those firms is structurally set up to own that, and both need it to exist. If your integrator can do it inside their platform and that is genuinely the right answer, we will tell you so and there is no engagement here. And if the cleanest route is for us to sit under your existing vendor’s contract rather than beside it, we will work that way; say so early, because it changes the paperwork rather than the plan.

Preferably. Most of our best outcomes are blended teams. Your engineers know the business; ours bring practices and capacity. It also makes the eventual hand-off almost free.

Often, yes — several of our engagements began as someone else’s half-finished build. We start with a paid assessment of what exists: what the code and data are worth keeping, what the remaining work actually is, and what it would cost to finish versus to replace. Sometimes the honest answer is that the foundation is sound and the project just lost its owner. Sometimes it is that you should throw it away, and we will tell you that too, in writing, before you commit to a build.

Thirty days' notice after the first release, for any reason, with no termination fee. Everything built to that point is yours and deployed in your accounts. We’d rather you were able to leave easily and chose not to.