ACQI Technologies

Services

Software that arrives with the people who know how to land it.

An installed product needs an installation. These are the engagements we run, what each one produces, and how long it takes. Everything is quoted against a scope; nothing here is a fixed public price, because a number without scope is a marketing device.

I

Engagements

Service catalogue
Engagement What it is You receive Typical duration
Deployment Install, connect, prove it reads.
Environment review, credential design, service host build, a pilot collector run against a non-production slice, then production scope. Ends with your operators running a discovery cycle unaided.
Working installation, run book, credential register 2 to 4 weeks elapsed
Estate read A diligence-grade picture without a licence.
A fixed-scope discovery and consolidation engagement. We install, run the collectors you authorise, consolidate the estate and hand over the record with its evidence. Useful when the deal may not close and a full licence is premature.
Estate record, conflict register, evidence archive 3 to 6 weeks elapsed
Integration engineering Collectors and exports for systems we do not cover.
Custom collector development against your internal systems, or an export pipeline into your data platform, CMDB or reporting stack. Built to the same provenance rules as the shipped collectors.
Collector package, tests, documentation Scoped per system
Migration delivery support An engineer in the room for the parts that hurt.
Wave design, mapping review, rehearsal analysis, cut-over command and hypercare. We support your programme; we do not take ownership of your tenant.
Wave plan, rehearsal report, cut-over log Per wave or per programme
Enablement Make the internal team self-sufficient.
Operator training for discovery, consolidation, assessment and migration surfaces, plus administrator training for roles, policy and evidence retention.
Training record, operator handbook 2 to 5 days
II

How an engagement runs

  1. Scoping call. The target estate, the timetable, the systems in scope, the people who will operate the product. No slides.
  2. Written scope. A short document listing what we will do, what you will do, what is explicitly out of scope, and the assumptions we are relying on.
  3. Environment access. Your team provisions the hosts and the credentials. We never hold standing access to a customer environment.
  4. Delivery in slices. Each slice ends with something you can inspect: an installation that runs, a pilot that reads, a record you can query.
  5. Handover. A run book your team can follow without us, and a named engineer for the support period.

We do not run production cut-overs for you. Migration execution belongs to the customer's change process. Our role is to prepare the plan, prove it in rehearsal, and stand beside the operator during the window.

Access to a customer environment is granted per engagement, time-boxed, and revoked at handover. Where remote access is required it is brokered through your own privileged access tooling, not ours.

Ask for a scope

III

Working terms

Sizing

Engagements are sized from the estate, not from headcount. A 4,000-seat estate with three source systems is smaller than a 900-seat estate with fourteen.

Change control

Scope changes are priced before work starts, in writing. We do not bill discovery of a problem we should have found at scoping.

Confidentiality

Mutual NDA before environment access. Findings from your estate are yours. We do not reference your engagement, sector or outcomes without written permission.