SOLO PRODUCT DEVELOPMENT
Websites, Telegram bots, internal tools, and AI assistants — from structure and prototype to a working application, testing, and launch.
I work in stages. Source code and documentation are handed over to the client.
A website that doesn't just represent the company — it gets the visitor to submit a lead.
Example project: LeadFlow
A bot that walks the client through a flow — booking, a lead, support — right in the chat.
Example project: BookingBot
A tool for the team: tickets, roles, statuses, and history — instead of chats and spreadsheets.
Example project: ServiceDesk Lite
An assistant that answers based on your documents, not the model's general guesses.
Example project: DocuMind
Connecting services together — leads, notifications, and data move without manual work.
Example project: LeadFlow
Demo projects — illustrative builds, not client work. Each one is honestly labeled as a demo project.
A website for a service business with cost estimation and automated lead handling.
A Telegram booking service with service, slot, and notification management.
An internal ticketing system with roles, a status workflow, and a change history.
An AI assistant for technical documents, with semantic search and source-grounded answers.
Project interface will be added once materials are ready.
What's happening now, and what needs to be automated.
Scenarios, constraints, and criteria for done.
I show the structure before deep development starts.
Work happens in small, verifiable stages.
Testing the core user scenarios.
Deployment, source code, and documentation.
For finished projects, the result can be checked through the available demo, source code, tests, and documentation.
It works, so it can be checked.
Core scenarios can be seen in action, not just in screenshots.
Code and documentation are handed over to the client once the work is done.
Core user scenarios are covered by tests before launch.
The client gets not just the product, but an understanding of how it works.
Example: ServiceDesk Lite
0
Lint
findings
0
Typecheck
errors
572 / 572
Unit tests (Vitest)
passed, 49 files
Successful
Build
8 / 8
E2E smoke (Playwright)
passed
About
I build compact digital products for small businesses and technical companies: websites, Telegram bots, internal tools, process automation, and AI assistants.
I take on the scenario design, interface structure, development, integrations, testing, and documentation handover.
I use AI tools as part of the development process, but I verify the key scenarios and the solution's limits separately.
Stack
Not every project uses the whole stack — it's a toolkit a solution gets assembled from for the task at hand.
FAQ
Work goes in stages: structure and a prototype first, then implementation, testing, and launch. Each stage is signed off before moving to the next.
Yes. It often makes sense to validate the structure and key scenarios on a prototype before moving to the full build.
Yes — the source code and documentation are handed over to the client as part of finishing the work, not as a separate service.
Further support or changes can be discussed separately after launch — they aren't included in the build by default.
Yes, AI tools speed up part of the code and routine work, but architectural decisions, review, and responsibility for the result stay with the developer, not the model.
Yes, if it's a separate codebase — it takes some time to go through the existing code first, before the scope of the work can be estimated.
The price depends on the scope and complexity of the task and is discussed individually once the details are clear — there are no fixed rates on the site.
Contact
Describe the task in your own words — I'll reply with how I'd approach it.