Engineering studio · since 2019

Routine is eatingyour profit.Quietly, every day.

Q: Are you one person or a team?

I run the project and answer for it personally. For design, heavy front-end and mobile I bring in people I have worked with for years. You always talk to me, not to a manager relaying messages.

Q: Why not a forty-person agency?

In a large agency half the quote pays for managers, sales and an office. Here you pay for engineering hours. The honest downside: I take two or three projects at a time, and the queue is sometimes a month deep.

Q: Who owns the code?

You do, from the first commit. The repository lives in your account, servers are registered to your company, keys and access are yours. If we part mid-project, you leave with everything built so far.

Q: What if my budget is below your floor?

I say so immediately, not after three meetings. Often you can cut half the plan and still get a working loop within budget — that is the more honest place to start. If it still doesn’t fit, I point you to someone else.

Q: Do you work with clients abroad?

Yes. Contract and payment in euros or roubles, calls in your timezone, correspondence in English or Russian. We agree on overlapping hours on the first call.

Q: Do you guarantee revenue growth or returns?

No, and nobody honest does. I answer for the system doing what the contract says, on time and without losing data. What you do with it afterwards belongs to your business and your market.

Someone on your team is doing work a machine should be doing right now. I build the systems that take it over: AI agents, bots, websites, apps, integrations, trading infrastructure. From the first call to production, one engineer owns it.

Calculate my losses What I build

Fixed price
Code yours from day one
First call free

Below — what it costs you

Diagnosis

Sound familiar?

None of these looks like a catastrophe on its own. Together they take more out of a business than any failed ad campaign — just slowly, and with no invoice you can point at.

Someone moves data from email to a spreadsheet, and from the spreadsheet to the CRM, every day
You answer the same customer questions dozens of times a week
The report your boss needs by Monday takes half a day to assemble by hand
Leads vanish between messenger, email and sticky notes, and nobody knows how many
You have a website, and customers come from anywhere except it
Your data lives in three systems that never talk to each other
You have a product idea and nobody to take it to a working version
A contractor built something, it half-works, and nobody dares to touch it

Checked0/8

If three or more landed, you are already paying for automation. Just in salaries rather than in software.

168 hours a weekPeople 40System 168

MON

TUE

WED

THU

FRI

SAT

SUN

Hours in a week. The gap is everything you don’t do because nobody is left to do it.

DisciplinesWhat I build

Keep scrolling — disciplines come one after another

S-0101 / 06

AI automation

Takes repetitive work off your team

What you get5 deliverables

Process map with automatable steps marked and hours saved estimated
A working agent or pipeline wired into your systems
Control panel: what was processed, what went to manual review, where it failed
Safety rules: what the model does on its own, what it only proposes
Team handbook and one month of support after launch

Timeline: 3–6 weeks to the first working loop
Stack: Claude API · Python · LangGraph · Postgres · Redis · Docker

HEAN: 36 intelligence modules, 1632 tests Details

S-0202 / 06

Chatbots & assistants

Answers at 3 a.m. the way you would at noon

What you get5 deliverables

A bot trained on your material: price lists, policies, past correspondence, site content
Order taking and booking that lands straight in your CRM or Telegram
One-click handover to a human when the question goes out of scope
A dashboard of conversations: what people ask and where the bot failed
Guard rails: it never invents prices or promises things you do not offer

Timeline: 2–4 weeks to launch
Stack: Claude API · Python · RAG · Telegram Bot API · Postgres · Redis

Details

S-0303 / 06

Websites & web apps

From a landing page to a customer portal

What you get5 deliverables

Design made for your product, not pulled from a template library
Layout from phone to wide desktop, keyboard accessible
An admin panel or CMS so you can edit copy without a developer
Technical SEO, structured data, sitemap, Core Web Vitals speed
Analytics and lead forms wired into your CRM or Telegram

Timeline: 2–5 weeks for a site, 6–10 for an app
Stack: Astro · Next.js · TypeScript · Tailwind · Postgres · Vercel

This site and a photographer site — code is open Details

S-0404 / 06

Mobile apps

iOS and Android from one codebase

What you get5 deliverables

An iOS and Android app with offline mode and push notifications
Backend and data sync across devices
App Store and Google Play submission, including replies to reviewers
One-click update builds and crash tracking from real users
Store listing assets: screenshots, description, icon

Timeline: 8–14 weeks to store release
Stack: React Native · Expo · Swift · Kotlin · FastAPI · Postgres

Details

S-0505 / 06

Software, backend & integrations

Systems that hold load and lose nothing

What you get5 deliverables

An API with documentation, versioning and tests
Integrations with external services and protection from their failures
Docker deployment, automated builds, one-command rollback
Monitoring, logs and alerts — you can see what happens inside
Load testing and a report on where the system’s ceiling is

Timeline: 4–12 weeks
Stack: Python · FastAPI · Rust · Postgres · Redis · Kafka · Docker

HEAN: 13 packages, 11 containers, Rust accelerators Details

S-0606 / 06

Trading & fintech systems

Infrastructure that holds up around the clock

What you get5 deliverables

Exchange and broker connectivity: quotes, order book, execution, position reconciliation
Risk layer: limits, drawdown control, kill switch, deposit protection
Backtesting on historical data with fees and slippage counted honestly
Accounting: trades, fees, realised and unrealised result
Monitoring and alerts: what broke, when, and why

Timeline: 6–12 weeks depending on venue count
Stack: Python · Rust · ClickHouse · Postgres · Redis · Prometheus · Docker

HEAN in production for years — read the case Details

Also

What else gets ordered

Smaller jobs that do not need a full project but close a gap in a week or two. Same fixed-quote logic.

Telegram bots and mini apps
Knowledge base with search across your documents
Invoice, contract and waybill recognition
A voice bot that answers calls
Dashboards and reporting instead of manual spreadsheets
Demand and stock forecasting from your history
Competitor price and offer monitoring
Online store with marketplace integrations
Integration with ERP, CRM, warehouse, banking
Bulk photo and video processing
A product MVP in three weeks
Audit and rescue after another contractor

Calculator

What your routine costs

Automation either pays back or it doesn’t — that’s arithmetic, not faith. Put in your numbers and see the annual cost of manual work and the payback period.

People on routine work4

140

Routine hours per week, each12 h

1 h40 h

Cost per hour, per person30 €

10 €120 €

Share that can be automated60%

10%90%

ReadoutLIVE

Manual work costs per year: —
Freed up per year: —
Hours returned to the team: —

The formula is open: people × hours × rate × 47 working weeks. Taxes, and the fact that some freed time goes to other work rather than profit, are not included — the number shows the order of magnitude, not an exact sum.

Check this against my process

Why me

Why this works

Not because I say so. Because the risk is removed exactly where clients usually get burned.

The price will not drift

The quote is fixed before work starts. If I misjudged the effort, that is my loss, not your change order. Which is why my estimates take longer than usual.

You do not get locked in

The repository is in your account, servers registered to your company, keys yours from day one. You can walk away at any point and take everything with you.

You see results in two weeks

The narrowest working version comes first. You steer by looking at a live system, not a mockup and not a percentage-complete report.

I say no

If the problem is solved by configuring what you already pay for, I say so on the first call and take nothing. Losing a project is cheaper for me than losing a reputation.

How it runsHow a project works

Steps change as you scroll

The call

60 minutes, free

We look at the process as it actually runs. Often it turns out the problem is solved by configuring what you already pay for — I say so and we part ways.

Scope and quote

3–5 days

I write down what is in and what is out, with a fixed price and date. It reads in ten minutes and never uses the word “iteration”.

First working loop

2–4 weeks

I build the narrowest version that already helps and put it in your hands. From there you steer by looking at a live system, not a mockup.

Build-out

scope-dependent

Features grow week by week. Every Friday a short report: what shipped, what’s next, where my estimate was wrong.

Handover

1 week

Code, access, documentation and a recorded walkthrough go to you. Nothing stays on my servers or in my personal accounts.

Watch

first month included

For the first month I watch the system and fix my own mistakes for free. After that it’s monthly, optional, no lock-in.

Selected work

What’s already built

2026Algorithmic trading

HEAN — an autonomous trading system

My own product: infrastructure that collects market data, executes orders and holds risk around the clock with nobody at the console.

50: instruments tracked in real time
11: services running together
<1 ms: event bus latency under load
24/7: operation without manual intervention

PythonRustPostgreSQLRedisDockerPrometheus

Read

Money

How the price is built

There is no price list, on purpose. The same-looking task costs differently at two companies: different data volumes, different systems, different state of what is already written. First we take your task apart, then I name the number — and fix it in the contract before we start. It does not grow afterwards.

P-01

Recon

When it’s unclear whether the thing is worth building

Process breakdown or audit of an existing system
A document: what can be automated, what can’t, in what order
Timeline and cost estimate per piece
A one-hour call to answer questions
The fee is deducted from the project if it goes ahead

Start a project

P-02most chosen

Project

When the task has a definite end state

Everything in Recon plus the build itself
Fixed price and date — overrun risk is mine
A demo every two weeks
Source code and all access yours from day one
One month of post-launch support included

Start a project

P-03

Embedded

When the work never ends and you need your own engineer

Dedicated hours every week for your queue
You reset priorities without renegotiating a quote
Incident duty and system monitoring
A voice in product planning, not just execution
Cancel any time with one month’s notice

Start a project

Questions

Asked before we start

Are you one person or a team?

I run the project and answer for it personally. For design, heavy front-end and mobile I bring in people I have worked with for years. You always talk to me, not to a manager relaying messages.

Why not a forty-person agency?

In a large agency half the quote pays for managers, sales and an office. Here you pay for engineering hours. The honest downside: I take two or three projects at a time, and the queue is sometimes a month deep.

Who owns the code?

You do, from the first commit. The repository lives in your account, servers are registered to your company, keys and access are yours. If we part mid-project, you leave with everything built so far.

What if my budget is below your floor?

I say so immediately, not after three meetings. Often you can cut half the plan and still get a working loop within budget — that is the more honest place to start. If it still doesn’t fit, I point you to someone else.

Do you work with clients abroad?

Yes. Contract and payment in euros or roubles, calls in your timezone, correspondence in English or Russian. We agree on overlapping hours on the first call.

Do you guarantee revenue growth or returns?

No, and nobody honest does. I answer for the system doing what the contract says, on time and without losing data. What you do with it afterwards belongs to your business and your market.

Contact

Tell me what hurts

Describe the task in two paragraphs. I reply within one business day and tell you on the first call whether I take it and what it costs.

I reply within one business day, usually sooner
On the first call I tell you honestly whether I take it
Your details go nowhere else and into no mailing list

Reply: within one business day
Hours: Mon–Fri, 10:00–19:00MSK (UTC+3)
Languages: Русский, English
Contract: Always, at any budget

We sign a contract before starting. The rules — scope, payment, rights to the code — are on a separate page.Terms of engagement