Order programming: bots, scripts, integrations and websites
Start with the result, not the technology
Most people know they need a “bot for booking customers”, a “price scraper” or an “export to Excel”, and don't know what to write it in. That is fine: the main thing is to describe what the program should do, who will use it and what it must work with (CRM, Telegram, a website, a database).
It is better to choose the technology (Python, PHP, JavaScript) together with the developer, especially if you don't plan to maintain the code yourself. But if your system already runs on a certain technology, be sure to say so.
How it works on BlaBlaPrice
You write one request in your own words. There is no need to write a twenty-page brief. Programmers and studios reply in the chat: they judge the complexity and name a price or what it depends on, the timelines and the approach. They see their place among the other offers and can improve their terms. Reviews are visible next to each, and you pass your contacts only to the provider you choose.
What to put in your request
- What you need — a bot, scraper, script, integration, website, bug fix.
- Scope — number of pages, screens or features.
- Requirements — mobile-friendly, CRM integration, export to Excel, speed.
- Brief — whether you have a spec, a Figma design or at least a description in words.
- Technologies — if already chosen (for example, Python), otherwise write “provider's choice”.
- Deadline — the date you need the result by.
- Experience — a portfolio of similar projects.
- Budget — if you want to name one.
Example: “I need a Telegram bot for booking customers at a barbershop in Chennai: choice of barber and time, reminders, integration with Google Sheets. I have a spec, technology is the provider's choice, Python preferred. Needed in a week, budget up to ₹20,000.”
How to compare offers
Different prices often mean a different scope. Find out what is included: only the code, or also deployment on a server, documentation, testing, training. Ask whether you will get the source code and access, not just a finished service. This matters if the provider disappears.
Check whether the work goes in stages and when you see an interim result. That lets you fix misunderstandings in time. Ask for examples of similar projects or links to working solutions, and for the warranty terms: how long they fix errors for free.
Common mistakes
- A vague task like “make it work” without acceptance criteria.
- Paying everything upfront.
- Not taking the source code and access to the hosting or repository.
- Adding new requirements along the way without agreeing the price.
If you need a website on its own, see website development, and for apps, mobile app development. For automation with AI there are chatbots and AI automation. Read how the service works on the “How it works” page.
