LexorConsulting

Web products · Automation · AI · Infrastructure

Technology thatmakes work simpler.

Lexor Consulting designs and ships web products, automation, applied AI and infrastructure. We show working results at every stage.

See our work
Remote teamOpen for new projects
lexor:~/brief

$ lexor --scope

→ products · automation · AI · infrastructure

$ lexor --process

→ context → slice → production → signal

$ status

open for new projects

Quick brief

Web products and portals

We design and build web services, customer portals and complex forms — from scope to production.

  • 01Context and scope
  • 02Prototype
  • 03Development
  • 04Production

Expertise

What we do

Four practices that cover the path from idea to a product that lives on after release.

01

Products and portals

Web services, customer portals, complex forms and analytics — with one coherent user journey.

  • Web services
  • Customer portals
  • Complex forms
  • Analytics
02

Applied AI

Image, document and speech recognition, AI search and agents — with verification and sources.

  • Vision / OCR
  • Speech and text
  • AI search
  • Agents
03

Process automation

Integrations, roles, approvals, bots and notifications. The system runs the process instead of adding another manual step.

  • Integrations
  • Roles
  • Bots
  • Notifications
04

Infrastructure

Deployment, monitoring, databases and secure perimeters for a product that must live on after release.

  • Deployment
  • Monitoring
  • Databases
  • Security

Products

Our own products

Projects we originated and run ourselves — from idea to public releases.

HealthTech · AIOpen demo

CalorioAI

Complex AI behind a simple action

Show your food by photo, voice, text or barcode — get a nutrition record you can verify and edit.

  • 01

    Photo, voice, text and barcode

  • 02

    Calories, sugar and fiber

  • 03

    Web, iOS, Android and Max

Process

How we work

Every stage ends with a tangible result, not a slide deck.

  1. 01

    Understand the context

    We pin down the process, the user, the constraints and the success criterion. We don't start with a screen if the problem sits deeper.

    Process map and success criterion
  2. 02

    Build a working model

    We test the key scenario on a prototype or a vertical slice — with real logic where it defines the product.

    A working vertical slice
  3. 03

    Take it to production

    We connect interface, data, integrations and infrastructure. The full path is verified, not just the pretty screens.

    The product in real operation
  4. 04

    Improve on signals

    After launch we watch real failures and behaviour. We improve what affects the product.

    Metrics and managed improvements

FAQ

Common questions

01How much does it cost and how is the budget set?
It depends on the slice: a small automation tool and a full product are different orders of magnitude. After reviewing the context we give a range and fix the stages — you pay for verified steps, not for wasted hours.
02How soon will we see results?
The first working slice is shown in the second week: a real scenario with real logic, not a screen mockup. After that — short cycles with live demos.
03Do you work with existing code?
Yes. We start with an audit of the current system: what to keep, what to rewrite, what to automate. We rewrite only where it beats maintaining.
04Who owns the code and data?
You do. The repository, infrastructure and data are handed over from day one — with documentation and access. No vendor lock-in.
05What if the product turns out to be unnecessary?
We will say so honestly before starting: if the task can be solved with an off-the-shelf tool or a small script, that is exactly what we will propose. An early negative result is still a result.
06What about support after release?
We watch real failures and user behaviour and fix what affects the product. Incident response within one business day; further development is driven by metrics.

Preliminary estimate

Pick a task type and scale — we will show an indicative range: timeline, first slice and team size.

First slice
A single feature or tool
Timeline
1–2 weeks
Team
1 engineer

This estimate is indicative: a planning range, not a commitment. Exact scope and timeline are fixed after the brief.

Contact

Tell us about your task

Two sentences are enough — we will come back with questions and a first estimate.

Contact

Tell us about your task

This form does not send data to a server: the button opens a draft email in your mail client. Nothing is sent until you confirm it in your mail app. lexor1984@yandex.ru