~/nisosapps $ ls ./projects
Any project, not just Telegram
Mini-apps are easy to put in a showcase: you can open them and tap around right in the browser. They are not all I write. If the job can be solved with code, I will take it — Telegram or no Telegram.
I reply within the hour: whether I am taking it and why. If it is not for me, I say so straight away.
01Websites and web services
A landing page, a full site, a catalogue, a customer account, an admin panel. Built on the same stack as this site.
02Bots and automation
Taking enquiries, sending reminders, scheduled reports. The routine somebody is doing by hand every day right now.
03Integrations and data flow
Wiring together CRM, stock, till, delivery, payments, spreadsheets. Exports, imports, APIs in both directions.
04Internal tools
Bookkeeping, rotas, a client database, a panel for your staff. The things that usually live in Excel and fall apart at the third employee.
05Data and reporting
Collect it, clean it, count it and show it in a form you can read. On a schedule, without you touching it.
06Finishing someone else's project
The developer disappeared and the code stayed. I will get into it, finish it and keep it running — or tell you honestly that a rewrite is cheaper.
Everything is negotiable: budget, timing, scope, the order things are done in, in stages or all at once. Nothing is off the table in advance — there are jobs I take, and jobs I will tell you honestly I will not.
What people actually order
From a price calculator on a website to an app in the stores. Grouped by how long it takes, so you can place your own task on the scale. If it is not on the list, that does not mean I will not take it.
A day or two
- A price calculator for your site
- An enquiry form that pings you on Telegram
- A one-page site with a booking button
- A script that does a routine job on schedule
- Pulling data out of a service into a spreadsheet
- Fixing what broke after someone else's change
About a week
- A mini-app for bookings or a catalogue
- A bot that answers the questions you keep repeating
- A customer account with order history
- A staff panel: enquiries and schedule
- Connecting your site to a CRM, stock or till
- A landing page with payments and a mailing list
A month or more
- A web service with subscriptions and payments
- A catalogue with search, filters and a map
- A mobile app for iOS and Android
- A system built around your process, not a template
- Moving an old project onto a stack that holds
- Finishing someone else's project and keeping it running
What I build it with
The same stack on every project, this site included. Servers and database sit in Frankfurt, so your customers' data never leaves the EU.
- Go
- Node.js
- TypeScript
- Python
- REST
- GraphQL
- React
- Next.js
- TypeScript
- Tailwind
- React Native
- Vite
- PostgreSQL
- MySQL
- SQLite
- MongoDB
- Redis
- ClickHouse
- Docker
- Docker Compose
- Linux
- Nginx
- Caddy
- GitHub Actions
- Telegram Bot API
- WhatsApp Business API
- Stripe
- PayPal
- Revolut
- Apple Pay
- Playwright
- Vitest
- Jest
- Testing Library
- TypeScript strict
- ESLint
How it works
- Describe the job in two or three sentences, in your own words. No spec needed.
- I reply within the hour: whether I am taking it and why. If it is not for me, I say so straight away.
- Then I size it up and give you a fixed price and deadline. Neither grows while we work.
- The code and the data are yours: take them whenever you want. At the end of the project I hand over everything — database, access, sources — and keep nothing.
- Payment: USDT directly, or by card through Upwork, where the platform holds the money until the work is delivered. Whichever suits you.
Tell me what you need
A couple of sentences is enough for me to say whether I am taking it and what it costs.