How to Write a Brief for Your AI Automation Project

Most Uzbek business owners who reach out to an automation studio start the same way: “We want a Telegram bot with AI, like everyone else has now.” That sentence alone cannot get you an accurate quote. Learning how to write an AI automation brief — even a short, rough one — is the single biggest lever you have over the price, timeline, and quality of what you get built.

A good brief doesn’t need to be a 20-page document. It needs to answer the five or six questions every serious vendor will ask anyway. Do that work up front, in writing, and you save weeks of back-and-forth calls and avoid quotes that swing wildly between 2 000 000 so’m and 20 000 000 so’m for what you thought was “the same thing.”

---

Why a vague brief costs you money

When a vendor gets “we want AI automation” with no detail, they have two options: guess low and renegotiate later, or guess high to cover risk. Either way, you lose. A Tashkent retailer who says “I want a bot that talks to customers” might mean a simple FAQ responder (500 000–1 500 000 so’m) or a full ordering-and-payment flow wired into Payme and a CRM (1 500 000–5 000 000 so’m and up). Those are different projects with different timelines. The brief is what tells the vendor — and you — which one you’re actually building.

Vague briefs also produce vague proposals. If you can’t tell whether a quote is fair, read red flags in an AI automation proposal to avoid before you sign anything.

What problem are you actually solving?

Start with the business problem, not the technology. “I want AI” is not a problem statement. “My sales team spends three hours a day answering the same five questions on Telegram, and we lose customers who message after 8pm” is a problem statement. Vendors who understand automation will translate that into a technical solution far better than you can — but only if you hand them the real problem.

Ask yourself:

• What task, done manually today, takes the most repeated time each week?
• Who currently does that task, and what do they do when they’re overloaded?
• What does it cost you when the task is done late or done wrong?

Answering these three questions honestly is usually worth more than any amount of technical detail about “AI agents” or “LLMs.”

The core sections every brief needs

1. Current process, in plain language

Describe how the task works today, step by step, even if it feels obvious. “A customer messages our Telegram channel, an operator checks stock in an Excel sheet, replies with a price, and if the customer agrees, we ask them to pay via Payme and send a screenshot.” This paragraph alone tells a good vendor 80% of what they need.

2. Channels and tools already in use

List what you actually use: Telegram (the channel ~76% of Uzbekistan’s internet users are on), your CRM (amoCRM and Bitrix24 are the most common locally, alongside IOTA.uz), your payment provider (Payme, Click, or Uzum Bank cover the vast majority of local transactions), and any inventory system like 1C or MoySklad. This avoids a vendor proposing a stack that doesn’t connect to what you already run.

3. Volume and scale

How many messages, orders, or calls per day or month? A bot handling 50 conversations a day is a different build than one handling 5 000. Rough numbers are fine — “maybe 100–200 orders a month” is far more useful than nothing.

4. Budget range and timeline expectation

Uzbek buyers often avoid stating a budget, hoping the vendor will lowball first. This backfires: without a range, a vendor either builds a stripped-down MVP you didn’t want or the full version you can’t afford. State a rough band. For reference, a simple Telegram bot typically runs 500 000–1 500 000 so’m, an ordering-and-payment bot 1 500 000–5 000 000 so’m, and a CRM-integrated AI agent bot from 5 000 000 so’m upward. Ongoing support is often quoted separately, from roughly $50/month.

5. Success criteria

What does “working” look like three months after launch? Fewer missed messages? A measurable jump in orders processed without a human? Vendors who know your success criteria design toward it instead of toward a generic deliverable.

A simple brief template

Section	What to include
Problem	The task costing you time or money today
Current process	Step-by-step, in your own words
Channels & tools	Telegram, CRM, payment provider, inventory system
Volume	Rough daily/monthly numbers
Budget range	Even a wide so’m range is useful
Timeline	When you need it live
Success criteria	What “done well” looks like in 3 months

Fill in even three or four of these rows and you’re ahead of most inbound requests vendors receive.

Checklist before you send your brief

• I described the actual manual process, not just the idea
• I listed the channels and tools we already use (Telegram, CRM, payment provider)
• I gave a rough volume estimate (messages, orders, or calls per month)
• I stated a budget range in so’m, even if approximate
• I gave a realistic timeline, not “as soon as possible”
• I named what success looks like three months after launch

Common mistakes to avoid

Don’t describe the solution before the problem — “build me a chatbot” tells a vendor far less than “customers ask about order status 40 times a day and we answer manually.” Don’t skip the budget range out of negotiating instinct; it usually costs you more in mismatched proposals than it saves. And don’t assume every vendor understands the local landscape — if you’re comparing studios, it’s worth reading how to choose an AI automation company in Tashkent alongside 10 questions to ask before hiring an automation agency so you know what a strong vendor response actually looks like.

If cost is still your main uncertainty at this stage, what business automation actually costs in Uzbekistan walks through real price bands in more depth than any single proposal will.

Frequently Asked Questions

Do I need technical knowledge to write a good brief? No. The most useful briefs are written in plain business language — the vendor’s job is to translate your problem into a technical design. Overly technical requirements from a non-technical founder often cause more confusion than they solve.

How long should a brief be? One to two pages is plenty for most small and mid-size projects. A CRM-scale AI agent project might warrant more detail, but even then, clarity matters more than length.

Should I send the same brief to multiple vendors? Yes. A consistent brief sent to two or three vendors is the fastest way to compare like-for-like proposals rather than apples to oranges.

What if I don’t know my budget yet? Give a range based on the price bands above and say so explicitly — “we’re estimating 1 500 000–5 000 000 so’m but open to discussion” is a completely normal and useful thing to write.

Ready to turn your brief into a working system?

A clear brief is the fastest path to an accurate quote and a project that actually reflects what your business needs — whether that’s a Telegram ordering bot wired to Payme or a full CRM-integrated AI agent. Take a look at Fera Tech’s services and recent work, then get in touch and we’ll help you turn your brief into a scoped, priced plan.