Skip to main content

Knowledge & enablement

Scoped per engagement

AI-Powered Intranet

Turn approved company knowledge, SOPs, internal tools, and workflows into one secure employee workspace.

Discuss this service with Valentino AI

What this service does

Give freight employees a governed internal workspace for knowledge, SOPs, dashboards, workflows, and approved AI assistance.

We do not force freight forwarders to replace the systems that run their business. We connect their technology, improve their data, redesign their workflows, and build AI around the realities of freight forwarding.

Who this is for

Operations, HR, IT, and managers improving onboarding, consistency, and knowledge access.

The problem

The SOP exists. Finding the current one is the hard part.

Procedures live across a shared drive, a wiki nobody prunes, an email thread from 2023, and the memory of the person who has been there longest. New coordinators take months to become useful, and consistency depends on who they happened to sit next to.

Multiple versions of the same SOP with no way to tell which is current.

Knowledge concentrated in a few long-serving people and undocumented.

Onboarding measured in months because there is no single place to learn the job.

Content with no owner and no expiry date, so it rots in place.

No visibility into the questions people ask and cannot get answered.

What the service includes

What we build.

Role-based home pages

What a coordinator, a pricing analyst, and a branch manager each need on day one, surfaced by role rather than buried in a shared navigation tree.

Cited knowledge search

Search and assisted answers grounded in approved content, always citing the document and version they came from so the answer can be checked.

Content owners and expiration

Every document has a named owner and a review date. Content past its date is flagged for review rather than quietly continuing to be authoritative.

Embedded tools

The dashboards, forms, and workflows people actually use embedded in the workspace, so the intranet is where work happens rather than a place to read about it.

Unanswered-question analytics

The questions the workspace could not answer, ranked by frequency — a standing backlog of the documentation your operation is missing.

Permissioned access

Role and record-level access so commercially sensitive content, HR material, and branch-specific procedures are visible only to the people entitled to them.

One governed intranet, three role-based home pagesTree diagram with one governed intranet at the root, branching into three role-based home pages — Coordinator, Pricing analyst, and Branch manager — each surfacing what that role needs on day one.Intranetgoverned, cited, permissionedCoordinatorSOP lookup, exception guidancePricing analystpolicy review, cited answersBranch manageronboarding, process improvementONE SOURCEEvery role reads the same governed content — surfaced differently, sourced identically.

Freight workflows

Where it applies in your operation.

  • SOP lookup
  • Customer exception guidance
  • Policy review
  • Onboarding checklists
  • Process improvement

The outcome

One place to find the current answer, and evidence of what is missing.

Time-to-answer drops, onboarding shortens, and the unanswered-question report tells you exactly which procedures to write next — measured rather than guessed.

How an engagement works

The engagement.

01
Audit

Inventory the knowledge that exists, where it lives, who owns it, and what is stale, duplicated, or contradictory. Identify the highest-traffic questions.

02
Design

Build the information architecture and role-based home pages, define the content lifecycle — owner, review cadence, expiry — and set the permission model.

03
Pilot

Launch with a single function and its real content. Ground the assistant in approved documents only, and measure time-to-answer and unanswered questions.

04
Adopt

Roll out by function with training, run the content review process on its cadence, and work the unanswered-question backlog as a standing improvement loop.

What you receive

Deliverables you keep.

  • Knowledge inventory
  • Information architecture
  • Content lifecycle model with named owners
  • Grounded internal assistant
  • Training and review process

Reference architecture and boundaries

Built alongside your systems of record.

The exact stack should follow the client's systems, data rights, skills, budget, and operating model. A useful reference architecture separates transaction authority from data, intelligence, action, experience, and governance layers.

Reference architecture — five layers, systems of record to governanceLayer stack from systems of record at the foundation up through integration and data, intelligence and action, experience, and governance at the top, with intelligence and action highlighted as the focal layer.OVERSIGHTTRANSACTIONS05GovernanceIdentity, permissions, evaluations, traces, incidents, retention, cost, andcontinuous improvement.04ExperienceDashboards, portals, intranet, chat, email, voice, and human-review queues.03FOCALIntelligence and actionRetrieval, semantic definitions, agents, deterministic rules, andpermissioned tools with validation and approvals.02Integration and dataAPIs, webhooks, files, events, normalization, lineage, quality monitoring,and governed freight entities.01Systems of recordTMS, CRM, accounting, rating, carrier, customer, email, telephony, anddocument systems remain authoritative for transactions.FOCAL LAYERIntelligence and action is where agents and rules touch your data — behind explicit permissions and human approval.

Security and human control

The principles every build follows.

  • Use least-privilege identities and explicit tenant, role, and record-level access.
  • Treat email, documents, web content, and model output as untrusted until validated.
  • Keep systems of record authoritative; agents use controlled APIs rather than casually editing copied data.
  • Require human approval for consequential customer, financial, compliance, or system-write actions until reliability is demonstrated.
  • Retain logs, evaluations, failures, approvals, and ownership information for review.

How success is measured

Measured against a defined KPI.

We baseline these before the build starts, so the improvement is a measurement rather than an impression.

Time to answer

Source clicks per answer

Unanswered questions

Onboarding time

Stale content volume

Adoption

Frequently asked questions

The questions forwarders ask first.

Is this a replacement for our existing systems?

Usually no. The service is designed to connect and extend the systems of record the forwarder already uses.

How do you prevent unsafe automation?

Start with narrow workflows, explicit permissions, validation, evaluation, human approval, auditability, and a clear rollback or escalation path.

What is required before publishing results or case studies?

Replace general language with verified client evidence, named systems, measured baselines, and approved proof assets. We do not imply integrations, certifications, or outcomes that have not been confirmed.

Further reading

Go deeper on the thinking behind this.

Source notes

These references support the industry and technical framing on this page. They do not validate claims about any specific client. Claims about client results, integrations, or compliance posture are published only with verified project evidence.

Ready to scope it?

No commitment to start. We'll look at your systems and workflows, then come back with a fixed-scope plan.

Discuss this service with Valentino AIAsk a question first