Skip to content
AVERIQ
LanguageRUEN
Discuss a project

Digital development

I builddigital productsthat turncomplex ideasinto working systems.

Websites, web services, CRM and ERP, mobile apps, games, and automation — shaped around a specific business, not someone else's template.

Remote · agreement before work starts · source code is handed over

01 — Format

Short, without invented numbers

Directions
Websites, CRM and ERP, services, mobile apps, games, automation, interfaces, support.
Where
Remote. Russian and English.
Engagement
A product from scratch, a module, an MVP, an improvement, a redesign, or support.
You receive
The repository, the build, a short guide, and the handover of access.

02 — Services

Eight directions. One question: what should start working.

Not every task is the same. A site explains the offer. A CRM holds the process. A service gives the user an action.

All services, with the scope of work

03 — Projects

Working systems and laboratory interfaces

All demonstrations

Some cards are modules of a live stretch-ceiling system: requests, cash desk, city websites, and the phone. Next to them are laboratory interfaces you can walk through here. Other companies' amounts and client names are not published.

Reconstructed system

Request board

A request lives on the board, not in the correspondence between the measurer and the manager.

TypeScript · React · Next.js

Cash desk and payments

Payment, the cash desk, and debt look at one request, not at three different spreadsheets.

City sites

A person chooses a city and leaves a request, without entering the internal account.

Field measure

On site, a person closes the job on the phone. The office sees the same status.

Order account

The client needs the status of the order, not the company's whole board.

Shift calendar

The shift is visible as a day: who is going out, who is calling back, and what is already closed.

Slice

An independent concept for analytics. Revenue, cost, and profit are summed from sample rows.

Stall

An independent shop concept: catalog, product, cart, and a sample order with no payment.

Slot

An independent booking concept. A service, a person, and a slot that cannot be taken twice.

Route

An independent delivery concept: statuses, couriers, and an event log. The coordinates are a sample.

Hire

An independent recruiting concept: cards, stages, and a note.

Class

An independent learning concept: lessons, progress, an assignment, and a teacher view.

Request console

A workplace where a request is not lost between email and a spreadsheet.

Catalog storefront

A catalog in which a filter helps you choose, instead of hiding the items.

Site visit

A phone scenario for a shift: what to do on site, and what to mark.

Signal

A short scene in which you can test how the controls respond.

04 — You can walk through it

The request console is open right here

A table, a filter, a card, and a summary on fictional data. That shows what a workplace means more clearly than a screenshot.

Open the CRM

Matcher

Not sure what to commission?

Four questions separate a site from a CRM, a service, an app, or automation. This is a recommendation, not a diagnosis.

Find a format

05 — Approach

What the work stands on

  1. 01

    Process first

    Screens follow how the company sells, counts, and serves. People route around a template that argues with the work, and they do it in a spreadsheet.

  2. 02

    The full path

    From reading the task through launch and handover: architecture, interface, the build, a walkthrough of the scenario, and a guide.

  3. 03

    Room in the architecture

    A new role, a branch, or an integration should not require a rewrite. Module boundaries are set before they are needed.

  4. 04

    Code you can hand over

    The structure is clear to the next developer. Secrets do not sit in the repository. The build can be repeated.

  5. 05

    Talk in the language of the task

    Statuses, money, and exceptions are discussed directly. Technical choices are explained through what will change in the work.

  6. 06

    Business rules stay visible

    Rules such as who can see an amount, and what counts as a refusal, are written in the system. They do not stay in one employee's head.

  7. 07

    The product stays yours

    The repository, access, and the way to launch are handed over. The work is not tied to someone else's laptop.

  8. 08

    After launch, the work continues

    Bugs, speed, and new modules can move as a queue. You do not have to start the acquaintance from zero.

06 — Process

From the first conversation to handover, with no black box

  1. 01

    Introduction and the task

    You describe what should change. I ask about roles, exceptions, and what should not be built.

    Result: A shared reading of the task and its limits

  2. 02

    Requirements

    We look at the current tools, the data, and the places where the process breaks. The first release is separated from wishes.

    Result: A scope of work and the open questions

  3. 03

    Architecture

    We fix the entities, the roles, the integrations, and what stays outside. This is a map, not a stack of screens.

    Result: A map of the system

  4. 04

    Interface

    We assemble the scenarios and the states: empty, error, long, mobile. Visual style serves the action.

    Result: Screens you can build from

  5. 05

    Development

    Code follows the agreed queue. You can look at a live piece along the way, instead of waiting for the final day.

    Result: A working system in an environment

  6. 06

    Testing

    We walk the handover scenarios, including a refusal and someone else's role. We fix what blocks the action from being finished.

    Result: A scenario that has been walked through

  7. 07

    Launch

    A domain or a server, data if it is needed, a way to see errors, and a short guide.

    Result: A product people can use

  8. 08

    Support and further work

    The queue after launch: fixes, speed, the next modules. A new contract is not required to correct a typo in the process.

    Result: A clear way to continue

07 — Stack

Tools the product is built with

The technologies used to build products. No skill-bar scores and no decorative logos.

Interface

  • TypeScript
  • React
  • Next.js
  • Semantic markup

Server

  • Node.js
  • Python
  • REST API
  • Authentication and roles

Phone

  • React Native
  • Publishing builds
  • APIs of existing systems

Data

  • PostgreSQL
  • SQLite for local systems

Launch

  • Docker
  • GitHub Actions
  • Linux

Design

  • Figma
  • Prototypes
  • Design systems

Games

  • Unity
  • Godot
  • Canvas / WebGL

Connections

  • Telegram
  • Email
  • Payments
  • Webhooks and accounting systems

08 — Engagement

Ways to commission the work

Questions people usually ask before starting

Can we start with a small scope?

Yes. The first release should be small enough to finish, and whole enough to use. A landing page, one CRM module, or a link between two services is a normal start.

Who owns the code?

You do. The repository, the build, and the guide are handed over. Access to the domain, the server, and payments stays on your accounts. I do not leave the product hostage to a personal laptop.

What if the requirements change along the way?

Small clarifications stay inside the current scenario. A new role, a new department, or a different way of selling is a change of scope. You see it before it quietly eats the schedule: the queue is rebuilt in the open.

How do the money and the contract work?

Before the start, we fix the scope of the next batch. Payment is tied to stages, not to a feeling that it is almost done. A contract or an offer comes before the work, not after. This is not a public offer of the site: the terms of a specific project are written separately.

Do you guarantee a place in search and growth in sales?

No. I am responsible for a clear scenario, technical quality, page speed, and an SEO foundation. Demand, the sales team, and competition in the search results stay outside any promise.

Have an idea? Let’s turn it into a working product.

For the first conversation it is enough to describe the task in your own words: what should change in the work. The scope appears after the details.