Intelligence software costs: how to compare the capability you will actually use

The price on a software licence is only one part of the cost of an intelligence capability. A buyer also pays for installation, integration, infrastructure, assurance work, training, support and the time analysts spend making the workflow usable. An attractive initial quote can leave several of those responsibilities with the customer.

AIC Constellation lets buyers examine six specialist products against separate intelligence tasks. All are available for customer demonstrations. The useful commercial question is how each proposed configuration compares with the alternatives over the period in which the organisation expects to use it.

Specify the result you need to buy

Write down the work before asking suppliers to price it. Name the users, source formats, daily workload, output and operating environment. Include the most difficult routine conditions: a large imagery collection, a revised source, an unavailable network or a recipient whose access has changed.

A requirement such as “support intelligence analysis” leaves too much room for different interpretations. A requirement to reconstruct a reviewed report from its sources, preserve its earlier revision and prevent restricted material appearing in search gives suppliers something concrete to demonstrate.

Map the requirement to a capability. CORTEX addresses the intelligence lifecycle. NERVE addresses source preservation and discovery. Establish whether the purchase needs one, both or a different product before comparing a broad platform bundle with a smaller deployment.

Separate software licences from delivery work

Ask for a quotation that identifies the software entitlement and the work needed to install, configure and support it. Record how users, environments, connectors, storage or other usage measures affect the price. Where a measure does not apply, have that stated clearly in the proposal.

Integration and implementation deserve their own scope. Define who prepares source material, configures identity, establishes retention, creates exports and deals with unsupported formats. A supplier can quote a low licence fee while leaving substantial engineering work outside the agreement.

The Constellation procurement guidance separates licensing from project delivery. Use that distinction when discussing the proposal with AIC. It makes the commercial boundary easier to inspect and gives procurement teams a way to compare the same responsibilities across competing bids.

Price the operating environment

Infrastructure choices change the cost of ownership. A team may already have suitable workstations and private infrastructure, or it may need new storage, processing capacity and operational support. Include installation, monitoring, backup, recovery, updates and the people responsible for running the environment.

For GTK 2.0, representative imagery and target hardware are essential inputs to the cost discussion. Measure the workload and storage demand that matter to the geospatial team. Check the resident data, models, indexes and other dependencies required for an agreed disconnected workflow.

The same discipline applies to identity and licensing dependencies. A package that can be installed without an internet connection may still need access to a separate service to perform its work. The deployment and assurance overview provides questions to settle before assigning an infrastructure cost to the proposal.

Make integration a named work package

“Integration included” is difficult to assess without a contract for the exchange. Identify the source, destination, supported versions, information being transferred, permissions, error handling and acceptance evidence. Record who maintains the connection after either system changes.

PAL.NET gives .NET teams a specific comparison: supported SDK access versus the cost of writing and maintaining their own platform clients. Check the required operations against the compatibility manifest. Include model changes, regression testing, licence entitlement and the customer’s existing Palantir dependencies in the estimate.

LINC introduces a different exchange discussion, covering routing, policy and delivery state. Price each required flow against its demonstrated scope. Test interruptions and recovery as part of acceptance. A connection that works during the initial demonstration still needs defined behaviour when permission changes or a receiving system stops acknowledging messages.

Measure analyst effort and correction costs

Staff time can dominate an otherwise modest software purchase. Measure how long it takes to locate a source, verify a citation, prepare an assessment, complete a review and correct an earlier edition. Use representative analysts and approved material, with the same workload for each option.

Use the CORTEX workflow and NERVE source-to-search scenario to define comparable tasks. Time the same work with representative inputs and record whether each output meets the agreed review criteria. That gives the buyer evidence about effort and quality together.

For PULSE, define the area, intelligence questions, cadence, reviewer responsibilities and delivery channel. Compare the recurring assessment service with the work your organisation would otherwise commission or perform. Include corrections, recipient management and changes in the requirement, so the comparison reflects a complete reporting cycle.

Record elapsed time, operator effort and quality separately. A faster output is only useful when it answers the requirement and remains reviewable. Rework caused by missing evidence, unsupported inputs or unclear release authority belongs in the cost assessment too.

Compare quotes against the same acceptance record

Use one evaluation record for each proposal. It should identify the release, inputs, hardware, user roles, observed results, failures and work still required. Ask suppliers to price the gaps explicitly. This makes a cheaper configuration easier to distinguish from a quotation that simply covers less of the requirement.

Choose a common ownership period and show one-off and recurring charges separately. Include foreseeable upgrades, support, data export and the effort required to change supplier or infrastructure. State assumptions about workload growth instead of hiding them inside a single headline figure.

Request an itemised competitive quotation from AIC for the same users, workloads, integrations, deployment and support period as the alternatives. Ask for the assumptions, exclusions and charges for future changes in writing. Compare the total commitment against the agreed acceptance criteria, including the work the customer would still need to fund.

To arrange that comparison, email commercial@aicuk.ltd or contact AIC. Send a non-sensitive task description, expected users, operating environment, ownership period and the evidence required for acceptance. Ask for a scoped demonstration and an itemised commercial proposal.