Client research
Manual prospecting takes time and source records are easily lost.
Identify candidates in public sources, check the evidence and create a structured lead list.
AI · OPERATIONS · BUSINESS
I build tools for client research, request processing and work planning. I start with the business task and deliver a working interface.
I am Grigory Safarov. I am completing a degree in logistics and use my knowledge of transport operations to build digital tools. I spent six months at Ingosstrakh working with transport risk and cargo insurance.
At LCT, our team developed Polet for a Beeline Business challenge; I reached the Logus Nova semifinal. I also participated in SPIEF 2025 and TransRussia 2026.
Logistics is a core area of expertise; I also build tools for other business workflows.
Automation begins with a specific loss of time or quality, not with a technology choice.
Manual prospecting takes time and source records are easily lost.
Identify candidates in public sources, check the evidence and create a structured lead list.
Routes and shifts change during the day and manual plans are hard to revise.
Build a plan with constraints and show options when conditions change.
Emails, messages and files need manual review and re-entry.
Extract information, sort requests, flag discrepancies and assign follow-up tasks.
Clients struggle to understand the offer or take the next step.
Build a clear website or a practical tool for a specific workflow.
A bot for prices, timelines and terms that hands complex cases to a person.
Parse emails and messages, update a CRM and create tasks.
Draft posts, product descriptions and emails in the company voice.
Summarize recurring themes from reviews and recorded calls.
Public prototypes and digital products. Model results are clearly separate from deployment impact.
For a specialized business: research across websites, Instagram and Telegram with source-linked contacts.
Outcome: awaiting confirmation
Explore projectFor a Beeline Business LCT challenge: field request allocation and engineer routes.
81.0 → 191.6 assigned requests in a one-day test model; eight-run average
Explore project
Website redesign for a carrier: services, fleet and a clear path to contact.
Outcome: awaiting confirmation
Explore projectTiming and scope are agreed after reviewing the process and available data.
Map roles, available data, constraints and the metric to improve.
Deliver a working tool and test it on sample data or a pilot scenario.
Compare with current work, train the team and agree on support.
Deliverables: a working tool, team guidance and an agreed support plan. Timing depends on data, integrations and pilot scope.
Describe the process and the desired outcome. I will suggest a starting point and the data needed.