AI implementation: RAG, assistants, ERP

Glowing knowledge graph of nodes and paths

Ship assistants, RAG, document recognition, compact model training, and ERP-connected AI that survive real traffic—not demos. Vertical slice in weeks, then expand with evaluation and cost controls.

Discuss this scopeContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

Technologies. Data. Results. I implement AI that connects to your real systems—not a demo chat in a vacuum. Assistants for staff and customers, document recognition and model training, Python file contours, forecasts, and hooks into ERP (CRM, warehouse, finance, manufacturing)—including 1C integration when that is your core.

Typical delivery: define the business outcome, pick a narrow first scenario (one document type, one FAQ domain, one forecast), ground the model on your APIs and metadata, then expand. Stack: TypeScript/Node.js or Python for orchestration, CV and OCR, mainstream LLM APIs or on-prem where required, audit logs and role boundaries from day one.

Representative work

Recent deliveries include ai-vision (form recognition and model training), thinklens-bot, and cursor-telegram-integration—systems where ai implementation skills (LLM, RAG, chatbots, OCR, document AI, forecasting, TypeScript, Node.js, Python, ERP APIs, 1C, data security, process automation) were applied end to end.

Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.

Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.

After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

Acceptance criteria

Done when

  • Pilot scenario meets agreed quality checks on sample data
  • Model calls are logged with role boundaries
  • Fallback / human path exists when confidence is low

Deliverables

  • Prompt / eval notes + access to staging assistant
  • Data source list used for grounding

Out of scope

  • Unlimited LLM token spend
  • Guaranteed model accuracy on all documents

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Selected portfolio work

All projects
ai-vision

ai-vision

Local pipeline for reading handwritten ultrasonic thickness (UT) inspection draft forms: CV preprocessing, PaddleOCR, multi-pass vision LLM, confidence fusion, and review HTML/CSV for operators before ERP handoff.

Details
thinklens-bot

thinklens-bot

Telegram assistant bot using OpenAI APIs for reflective prompts and summarization. Python orchestration with conversation memory controls.

Details
cursor-telegram-integration

cursor-telegram-integration

Integration tooling between Cursor IDE workflows and Telegram notifications or commands. TypeScript Node services for lightweight automation around dev events.

Details
mydev-news-bot

mydev-news-bot

Live Telegram bot for developers: thirty-plus sources (official JS/React/frontend blogs, AI and engineering feeds, Hacker News, Dev.to, GitHub releases), AI ranking, Squeeze, digests, EN/RU/UK.

Details
image-gen-extension

image-gen-extension

Browser extension for image generation workflows inside the editor context. TypeScript MV3 extension with focused UX for prompts and previews.

Details
refactor-analyzer

refactor-analyzer

Static analysis helper to suggest refactors using AST insights. TypeScript Node CLI for scanning codebases and emitting actionable hints.

Details

How I work

Request

You describe the goal, constraints, timeline, budget, and infrastructure.

Clarify

I ask questions, review existing code or a brief when needed, and lock scope.

Plan

I propose stages, priorities, and a timeline range; we agree on reporting.

Build

Iterations with intermediate results: commits, demos, and feedback.

Handoff & support

Deploy and docs as needed; we agree on maintenance or targeted follow-ups.

FAQ

Tap a question to expand the answer.

Do you build generic chatbots or tied to our data?

Grounded assistants on your APIs, docs, and ERP metadata—RAG or tool-calling—not a public ChatGPT wrapper. Scope and data boundaries are defined before the first prompt ships.

Which ERP systems can AI connect to?

1C, custom ERP, and module-level links to CRM, warehouse, finance, manufacturing via HTTP APIs and queues. See also 1C integration for the accounting core.

How do you handle document recognition errors?

Confidence thresholds, validation rules against ERP, and a human review queue for low scores—no silent posting to the ledger.

Can models run on-prem or in our VPC?

Yes when policy requires it: on-prem or private cloud LLM/OCR, no training on your data without contract, encryption and access logs by default.

What is a realistic first phase?

One vertical slice in 3–8 weeks: e.g. internal FAQ bot, one document type, or one forecast metric—then expand modules and channels.

Materials

Discuss this scopeContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.