Before the number, we tell you what goes into it

We confirm three things — the scope of work to automate, the systems to connect, and the document and data formats — then size the effort and add any complexity factors that apply. We quote a project total, excluding VAT.

A number given before the scope is clear hardens into a benchmark, which makes an honest quote awkward for both sides later. Once we confirm those three items in the consultation, we size the work and tell you right away.

We have no standard project duration. A rough number given before the requirements are clear gets treated as a promise. We confirm the scope first, then tell you.

Source for the deliverables transfers on final payment by default. What counts as a deliverable is fixed against the requirements at the contract stage.

The contract specifies a free warranty period that starts when acceptance is complete. We separate defects from new requirements by the acceptance criteria: if it does not behave as agreed, that is a defect; adding behavior that was never agreed is a new requirement, and we scope that separately.

Not as a fixed percentage of development cost. Basic fault handling and running the system for you are very different commitments, so we measure the hours your scope actually needs.

No. We simply do not take a deposit up front, and the work built at this stage is counted in the final quote. We begin it once you accept the preliminary estimate, and its purpose is to confirm that both sides are picturing the same thing.

It does not have to. Documents such as purchase orders and contracts, which carry counterparty names and unit prices, are often rejected in internal review, so we can design for a closed network or on-premises deployment. Before work begins we document what data leaves and what stays inside.

No. The first call, the workflow assessment, and the assessment report with priorities and an adoption plan all cost nothing. Timeline and cost come after the scope is set, not from the assessment itself.