Skip to content

Services

Bespoke software and bots

Telegram bots, scrapers, desktop utilities and internal tools.

The category for work that fits neither a website nor an app: a bot taking orders in Telegram, a scraper collecting prices every night, a utility three people in accounting use that quietly holds up a week's work. These are almost never public and rarely pretty, but their value counts directly — in hours that stop being spent by hand.

What the work covers

  • A Telegram bot: intake, payment, notifications, an admin panel, exports
  • Data collection: scheduling, resilience to the source changing its markup, export to a spreadsheet or database — within what the source's rules and the law allow
  • An internal tool: an interface over your database or spreadsheets so data stops being edited by hand
  • A Windows desktop utility on Tauri: local file processing where the web is awkward or impossible
  • Glue between services that ship no integration for each other: CRM ↔ spreadsheets ↔ messenger
  • One-off migrations and data untangling: turning somebody else's export into something workable

Who this fits

  • A fit: the task is narrow, repeats, and is done by hand from a written instruction today
  • A fit: the tool is for your own people, not the market — so design is something you can deliberately skip
  • A fit: you are willing to count the payoff in hours saved rather than in how the interface feels
  • Not a fit: collection that works around a source's rules, its paywall or the law. I do not take that work
  • Not a fit: a bot expected to replace the website and the support desk at once — three tasks, three budgets
  • Not a fit: "clone that service" without any right to the data it stands on

Stack

  • Python
  • aiogram
  • Playwright
  • PostgreSQL
  • TypeScript
  • Tauri

What moves the price

  • How many scenarios the bot has, and whether they include payment, roles and an admin panel
  • How resilient collection must be: a source with stable markup, or a protected site that changes weekly
  • The volume and quality of the source data that has to be untangled before anyone can use it
  • Where the result goes: a file, a spreadsheet, your database, or someone else's closed and undocumented API
  • How long it must run without me: a single execution, or a nightly schedule with alerts on failure
  • Whether support is needed: collection breaks when the source changes — that is not a defect, it is the nature of the task

What you keep

  • Sources and run instructions in your repository
  • A deployed, running instance on your server or in your cloud — not on my machine
  • Bot tokens, keys and access on your own accounts
  • A description of the schedule and the alerts: exactly how you find out the nightly run did not happen
  • A clear plan for the day the data source changes

Packages

Daemon

Custom software / bots

Custom software: a bot, a routine automated, a data collector, an internal tool.

from $5,000

Timeline
2–5 weeks
Payment by stage
50 / 50

Included

  • A bot on Telegram or another messenger of your choice
  • A routine operation automated, with an execution log
  • Collecting and normalising data from external sources
  • A control panel where the process needs a human operator
  • Deployment on your own server and handover of the source

Not included

  • Working around another service's technical limits or captchas
  • Collecting personal data without a lawful basis
  • Bulk messaging and engagement farming
  • Support after handover — that is Retainer
Discuss this package

Retainer

Ongoing

Ongoing support: a block of hours every month and an agreed response window.

from $2,000/mo

Timeline
minimum 3 months

Included

  • Twenty hours a month for fixes and development
  • Incident response within two working hours — weekdays, 10:00 to 19:00 Moscow time
  • Dependency updates and triage of new vulnerabilities
  • Backups watched, and restores tested
  • A monthly report: what was done and where the hours went

Not included

  • Rolling unused hours into the next month — the fee reserves capacity rather than buying a pack of hours; for one-off work there is Hour
  • Round-the-clock on-call
  • A new product from scratch — that is a project of its own
  • Hosting, licences and third-party services
Discuss this package

Hour

Ongoing

Hourly work: one task, a consultation, a review of someone else's code.

$120/hr

Timeline
minimum block 4 hours

Included

  • A four-hour minimum block
  • A time report describing what the hours went on
  • A review of existing code and infrastructure, with written findings
  • A consultation on architecture, on the stack, or on someone else's quote

Not included

  • A whole project — past a few days of work a package costs less
  • Scheduled on-call — that is Retainer
  • Availability on a given day without booking it in advance
  • Work that starts before the task is written down
Discuss this package

Indicative pricing. Nothing on this page constitutes a binding offer.

Prices are in US dollars. The Russian site carries a separate rouble price list: a list in its own right, not a conversion at today's rate.

Timelines are indicative: they count the studio's working time and depend on scope, on how fast approvals come back, and on your data being ready. The binding date is set in the contract once the brief is understood.

Tax regime: sole proprietor on НПД. No VAT; every payment is receipted.

Payment: bank transfer or card. Settlement details are issued with the invoice.

This is not a public offer