Challenge
One bot is not a product strategy
What problem existed?
Logistics operators need different AI jobs with different risk profiles. Chat is conversational and lead-aware. HS classification needs index discipline and re-rank honesty. Regulatory digests need publish workflows. Forcing all of that into one SaaS black box creates ops pain and political blame when any slice fails.
- ▸Monolith releases block independent improvement
- ▸HS accuracy requirements differ from chat tone
- ▸Content teams need digest publish controls
- ▸Procurement wants modules they can own
What we built
Ship features as products
What PragmaLabs created
Pragma Flow treats each capability as a package with its own README, env contract, and deploy story. They can sit beside each other on Neo’s properties while remaining independently testable.
Neo Assist
Conversational grounded agent with RAG and leads.
HS look-up
Classification assistance with hybrid search + optional AI re-rank over a real code index.
Notifications digest
AI summaries of customs notifications into structured content drafts for human publish.
How it works
Module programme
Simple workflow — how delivery was sequenced
- 1
Feature 1 — Assist
Chat + widget + RAG baseline as the trust foundation.
- 2
Feature 2 — HS
Standalone look-up service; codes must exist in index; AI re-rank optional.
- 3
Feature 3 — Digest
Enterprise digest pipeline with draft/publish stats and educational framing.
- 4
Integration map
Clear contracts so Neo IT can place modules behind their DNS and auth later.
In detail
Key parts of the product
Independent deploys
Improve HS without freezing chat releases.
Honest search contracts
HS path stays modular and index-backed — not free-text invention.
Content-safe digests
Summaries framed as educational drafts, not official CBIC text.
Ownership narrative
Packages Neo can run — not perpetual opaque SaaS rent.
Technology
Technical stack
Monorepo / multi-package layout with explicit workspaces. Shared principles (server-side keys, refusal honesty, env configuration) without forcing shared runtime failure domains. This is how enterprise IT likes to adopt AI: one slice, then another, measured.
- Modular packages
- Gemini Flash
- Hybrid search / RAG
- Content pipelines
- Embed contracts
Result
What improved
- AI capabilities no longer share a single kill-switch deploy.
- HS product stands alone for specialist workflows.
- Digest path supports human-in-the-loop publishing.
- Neo can sequence adoption politically and technically.
Pragma Flow is the opposite of ‘AI transformation’ theatre. It is a catalogue of working modules with the boring virtue of shippable boundaries.
Want something like Pragma Flow for your business?
Book a free discovery call or a deeper working session — we start from your business problem, not a template.