Offerings
Hardpoint delivers advisory and implementation work across knowledge, traffic, infrastructure and operations. Each offering produces written artifacts your team keeps and can operate without us.
Start here
Six fixed-scope entry engagements. Each states its deliverables, its boundary, and the condition it is meant for.
All layers
Environments where the overall architecture, ownership, or sequence is unclear.
Written deliverables
Engagement boundary
Assessment and design only. No production changes are made during the engagement.
Knowledge
Fragmented knowledge that enterprise agents cannot reliably discover, trust, or maintain.
Written deliverables
Engagement boundary
No bulk extraction and no custody of production content. Selected domains only.
Knowledge
One business domain ready to be modeled, governed and consumed by agents or retrieval.
Written deliverables
Engagement boundary
Bounded to the agreed domain, sources and corpus. Not a universal enterprise conversion.
Traffic
Multiple providers, subscriptions, APIs, local models, tools or human-review paths with no consistent routing model.
Written deliverables
Engagement boundary
Design of the routing model. Production routing is not changed during the assessment.
Traffic
Evaluating candidate routes alongside the current production path before changing consequential behavior.
Written deliverables
Engagement boundary
Candidate routes run alongside production; user-facing behavior is unchanged until promotion is approved.
Operations
Systems missing clear evaluation, observability, failure handling, ownership, rollback or operating documentation.
Written deliverables
Engagement boundary
Review and documentation. Hardpoint does not operate the system on your behalf.
Layer 01
Client condition
Nobody can say where the operating truth lives or who owns it.
Hardpoint work
Inventory sources, owners and change cadence; classify sensitivity; identify what is safe to expose to AI systems.
Principal deliverables
Engagement boundary
Review only. No extraction and no custody of production content.
Client condition
Knowledge lives in prompt history and cannot move between tools.
Hardpoint work
Model concepts and relationships, build the extraction and normalization procedure, carry provenance and lifecycle forward, wire Git review.
Principal deliverables
Engagement boundary
Selected domains and approved sources only — not indiscriminate enterprise conversion.
Explore a synthetic OKF transformation— publishing soon
Client condition
Agents cite the wrong source and nobody can prove whether a change helped.
Hardpoint work
Design chunking and indexing, build a fixed question set, and stand up a re-runnable regression harness.
Principal deliverables
Engagement boundary
Evaluation runs inside your environment against your corpus.
Run a governed query— publishing soon
Layer 02
Client condition
Every request goes down the same expensive path by default.
Hardpoint work
Assign each request a class of service with written quality, latency, privacy and cost budgets.
Principal deliverables
Engagement boundary
Design artifact. Production routing is unchanged during classification work.
Test a class-of-service decision— publishing soon
Client condition
One provider, no fallback, and no decision about what users see during an incident.
Hardpoint work
Determine eligibility, rank eligible routes, define fallback chains, timeouts, retry policy and degradation behavior.
Principal deliverables
Engagement boundary
Hardpoint designs and implements inside a gateway you own and operate.
Trigger a failover scenario— publishing soon
Client condition
Spend is visible only as a monthly invoice.
Hardpoint work
Define the Routing Receipt schema and attribute every request to a team, workload class and use case.
Principal deliverables
Engagement boundary
Telemetry stays in your systems; Hardpoint does not host your usage data.
Open the NOC view— publishing soon
Layer 03
Client condition
There is no agreed target state, so every team builds its own.
Hardpoint work
Document the target architecture across providers, private infrastructure, local compute, tools and human workflows.
Principal deliverables
Engagement boundary
Design and decision records. Implementation is scoped separately.
Client condition
A working prototype cannot cross into production.
Hardpoint work
Establish environments, access and secrets model, deployment and rollback.
Principal deliverables
Engagement boundary
Changes are made in your environment under your controls and approvals.
Client condition
Owned hardware is being considered on unit price alone.
Hardpoint work
Evaluate what belongs on provider APIs versus private or local compute, including the operating burden of each.
Principal deliverables
Engagement boundary
Modeled analysis with stated assumptions — not a guaranteed cost outcome.
Try the architecture builder— publishing soon
Layer 04
Client condition
Monitoring reports green through most of an incident.
Hardpoint work
Define signals and thresholds for AI-specific failure modes, write runbooks, and establish the incident review format.
Principal deliverables
Engagement boundary
Hardpoint designs the operating envelope; your team operates it.
Open the NOC view— publishing soon
Client condition
Quality was measured once, at launch.
Hardpoint work
Stand up scheduled scoring and a change-review gate so regressions are detected rather than argued.
Principal deliverables
Engagement boundary
Evaluation content is owned by your subject-matter owners.
Client condition
The system depends on whoever built it.
Hardpoint work
Transfer ownership through operating documentation, working sessions and an explicit checklist.
Principal deliverables
Engagement boundary
Handoff is the exit condition of every engagement, not an upsell.
Inspect a Continuity Capsule— publishing soon
Cross-layer offering
A service, not a product: the routing model is designed, documented and — when commissioned — implemented inside infrastructure you own.
Client condition
Multiple providers, enterprise AI subscriptions, APIs, local models, tools and human-review paths are in use, with no consistent model for choosing between them.
Hardpoint work
Inventory the model portfolio and entitlements, define acceptance contracts per workload class, build the eligible-route matrix, rank routes by verified total outcome cost, and design fallback and continuity.
Engagement boundary
A routing model is designed and, if commissioned, implemented in a gateway you own. Hardpoint does not operate a routing platform on your behalf.
Principal deliverables
Test a class-of-service decision— publishing soon
Scope & terms
Assessment and design work is quoted as a fixed fee with a defined artifact list and a date. No hourly discovery drift.
Implementation and operations support are scoped from the assessment, so effort is estimated against a documented environment rather than a guess.
No AI-seat resale and no model-provider commissions. Knowledge, credentials, repositories and runtime state stay customer-controlled by default; persistent custody of production data is avoided unless an engagement explicitly requires and defines it.
Most engagements start with an architecture triage call. Describe the environment, and we will tell you which layer is actually blocking you.