ScoutPricing
Scout · one-time acquisition

One product.
One transaction.

Scout is not currently offered as a hosted service or an open-ended consulting engagement. The honest commercial offer is a one-time acquisition of the existing Scout/ProjectHub software and documentation, with the exact rights and included materials written down before any transfer.

Review the acquisition Define the scope Discuss privately ↗

Pricing status: one negotiated transaction. There are no public monthly tiers, unlimited-service promises, or automatic support obligations.

01 / The offer

Acquire the existing Scout implementation.

This is one defined transaction, not a menu of services. The final price depends on the rights being transferred and the materials the buyer needs, but the commercial model stays simple: one written scope, one agreed price, one handoff.

Scout acquisition

Software, documentation, and defined transfer rights

A technical asset sale for a buyer who wants to inspect, operate, extend, or acquire the existing implementation under an explicit written agreement.

single transactionPrice on requestset after rights and transfer scope are agreed

Potentially included

  • Scout/ProjectHub source at the agreed repository commits
  • Architecture, product, API, Learn, and deployment documentation
  • Existing ProjectHub Recruiter Alpha implementation and configuration notes
  • Available tests, audit records, and known limitation notes
  • A defined technical handoff package if included in the agreement

Not included by default

  • Ongoing development, maintenance, or managed hosting
  • Uptime guarantees, response-time commitments, or an SLA
  • Custom integrations, migration work, or buyer-specific feature work
  • Private credentials, provider accounts, personal data, or secrets
  • Your personal identity, portfolio content, domain, or unrelated business assets
Commercial terms are established in a separate written agreement.Start an acquisition discussion ↗
02 / Transfer scope

“All of it” has to be defined.

Source code, ownership, branding, personal data, deployment accounts, and future obligations are separate things. They should not be silently bundled together under a vague promise to “buy Scout.”

01

Source

The repositories, branches, commits, documentation, tests, assets, and configuration files that are actually named in the agreement.

Defined by repository and commit
02

Rights

Permission to use, modify, operate, sublicense, or exclusively own the transferred materials must be stated explicitly.

Not implied by payment
03

Operations

The buyer supplies its own hosting, provider accounts, secrets, domains, credentials, data, and production operating process unless the agreement says otherwise.

Buyer-operated by default
04

Handoff

Any walkthrough, transition period, bug clarification, or limited assistance is listed as a finite deliverable instead of becoming indefinite support.

Bounded and written

Current technical reality.

Scout has real retrieval, semantic planning, session/discourse state, inference, tools, validation, telemetry, deployment controls, tenant-neutral Core behavior, and empty-KB support behind it. It is not being represented as a turnkey hosted SaaS, self-service multi-tenant SDK, or finished domain-package platform.

What a buyer getsAn existing engineering implementation that can be inspected and operated by a capable technical team.
What a buyer must doReview the code, configure its own environment, validate its use case, and accept responsibility for operation after transfer.
What this page does not claimThat Scout is turnkey, universally portable, production-supported for every domain, or ready for self-service customers.
What determines priceRights, exclusivity, included repositories/assets, handoff scope, and any narrowly defined transition work.
03 / Process

How one acquisition is evaluated.

The process is designed to make the asset and the obligations clear before either side commits to a transfer.

01

State the intended use

Explain what you want to operate, extend, or acquire and who will own the technical work afterward.

02

Define “all”

Identify the exact repositories, rights, branding, documentation, data boundaries, and transition materials involved.

03

Inspect the asset

Review the implementation, source history, tests, deployment notes, dependencies, and known limitations.

04

Write one agreement

Record the price, rights, exclusions, payment terms, handoff, and any finite transition assistance.

05

Transfer and close

Deliver the agreed package and complete the defined handoff. No ongoing service is created unless separately agreed.

04 / Questions

Clear answers before a conversation.

This page describes the commercial shape. A final transaction would be governed by its written terms.

Is Scout being sold as a monthly service?

No. This page no longer advertises hosted plans, managed operations, or recurring service tiers.

Is there a public fixed price?

There is one transaction, but the price depends on the rights and materials being transferred. An arbitrary number would imply a scope that has not been defined.

Does paying for source code automatically transfer ownership?

No. Ownership, exclusivity, modification rights, redistribution, and permitted use must be written explicitly.

Does the buyer receive personal recruiter data?

Not by default. Personal identity, portfolio content, private credentials, and personal data are separate boundaries and would need explicit treatment.

Will Bradley provide ongoing development?

Not as part of this offer. Any limited transition help would be finite, separately listed, and agreed before transfer.

Is Scout a turnkey product for any industry?

No. The released runtime now has a tenant-neutral Core foundation and empty-KB support, but formal domain-package contracts, packaged unrelated-domain applications, self-service installation, and the controlled extension/action platform remain productization work.

Acquisition inquiry

Discuss the asset, not a fantasy service plan.

Send the intended use, the rights you need, the technical team that would operate it, and whether you are evaluating source access or an exclusive acquisition.

Contact on LinkedIn ↗
linkedin.com/in/bradmatera

Important: This page is a commercial outline, not a transfer agreement. Final ownership, licensing, privacy, third-party terms, warranties, and obligations require written review before any transaction.