THE OWNERSHIP MODEL

Own your software.
Know what you get.

Custom application development and licensed products are different engagements. Both run on your hardware. What you pay for—and what you receive—depends on which one you choose.

CUSTOM APPLICATION DEVELOPMENT

Your application.
Source included.

For custom work, including AIMS-based applications, you pay for development—not a product license. You receive the finished application and its final source code.

Our internal AIMS workflow and templates are not included.

LICENSED PRODUCTS

Ready to run.
Build included.

When you license a product such as Clean Assist or Tracker, you receive the final executable, compiled build, or installer. The product source code is not included.

You receive the usable software, not its development source.

Product-specific terms still apply: Tracker uses per-seat signed license tokens; Clean Assist has no per-seat fee. These product licenses are separate from the fee for custom application development.

A DIFFERENT TRADE-OFF

Control comes
with responsibility.

Software on your hardware.
Handover and support defined for your project.

The decisionOngoing access modelThe Quad City AI model
Software paymentA recurring subscriptionCustom-development fee or one-time product license
Core operationDepends on the provider’s serviceRuns on your own hardware
Business dataHosted by the service providerStored locally at your site
OperationsA provider-managed serviceResponsibilities defined in your agreement
Major changesOn the provider’s release scheduleScoped separately when you request them

A comparison of operating models, not a claim about every hosted product. Source-code delivery follows the engagement type described above.

SCOPE BEFORE SOFTWARE

Your project.
Your agreement.

Deliverables, handover, training, and support are defined in the agreement for each project or deployment.

01 The software you receive

  • Custom development: the finished application and its final source code; not our internal AIMS workflow or templates
  • Licensed product: the final executable, compiled build, or installer; no product source code

02 Defined for your project

Configuration, data import, documentation, training, operating responsibilities, and support are scoped for the customer and deployment. There is no universal handover or support package.

COMMON QUESTIONS

No fine-print
guesswork.

Do I receive the source code?

For custom application development, including AIMS-based projects, yes: you receive the finished application and its final source code. You pay for development, not a product license. For a licensed product such as Clean Assist or Tracker, you receive the executable, compiled build, or installer; the product source code is not included.

Does custom development include your AIMS workflow and templates?

No. You receive the final source code for your custom application. Our internal AIMS workflow and templates are not included in that handover.

Are there any per-seat fees?

AIMS-based custom work is charged as application development, not a product license; there are no AIMS per-seat or runtime license fees. Licensed products have their own terms: Clean Assist has no per-seat fee, while Tracker uses a per-seat signed license token with no renewal server. We agree the applicable terms before work starts.

What happens after the handover?

Deliverables, handover, training, and support are defined in the agreement for each project or deployment. This includes agreeing the documentation, operational responsibilities, and any ongoing assistance needed.

What if something needs fixing?

Support and bug-fix arrangements are defined in your project or deployment agreement. Any additional work is scoped and agreed separately.

Do updates happen automatically?

Update arrangements and any feature changes are defined and agreed for the project or deployment.

What hardware do I need?

It depends on the product. Tracker runs as a Windows executable without a server. Clean Assist is a local Windows application. AIMS runs on customer hardware. Requirements are agreed during scoping.

Does every product use AI?

AI-assisted development is our build method. AIMS, Tracker, and Clean Assist do not embed a language model for core operation. Additional AI capabilities can be scoped separately.

YOUR NEXT TOOL

A better fit?
Let’s find out.

Tell us what you need to run. We’ll start with the scope, not a subscription.

See if this fits your business