# How to Write a Chatbot Project Brief Before Hiring a Developer

Canonical HTML: https://troymaya.com/chatbot-project-brief-template/
Markdown: https://troymaya.com/chatbot-project-brief-template.md

Published: 2026-10-16T14:00:00+00:00
Author: Troy Ochowicz

![An organized project notebook with checklist cards, simple workflow sketches and a laptop, tangible planning tools in an inviting studio.](https://troymaya.com/wp-content/uploads/2026/10/tm-howto-08-chatbot-project-brief-hero.webp)

A useful chatbot project brief explains what the assistant should help someone accomplish, what information it may use, and how you will decide that it works. You can write the first version on one page. “We want an AI chatbot” is a starting idea; “collect complete repair inquiries after hours and send them to our coordinator” is a buildable requirement.

Write the brief before comparing tools or requesting a fixed quote. A developer needs to distinguish a public FAQ assistant from a system that reads private records, changes appointments, or calculates prices. Those are materially different projects.

## 1. Choose one primary outcome

Name the visitor and the task. For example: “A prospective customer should be able to find the correct service and submit a quote request without waiting for our office to open.” Record a baseline if one exists, such as incomplete contact forms or unanswered routine questions. Do not invent a conversion target without knowing current traffic and follow-up performance.

Choose a secondary outcome only if it supports the first. Answering hours and service-area questions supports quote intake. Adding an unrelated general-purpose companion does not.

## 2. List sources and actions separately

Sources are things the assistant reads: approved service pages, an FAQ document, a price table, or a policy file. Actions are things it does: creates an inquiry, sends an email, checks a calendar, or updates a record. For each action, specify authorization, required fields, a success response, and what happens if the connection fails.

“Can answer booking questions” does not mean “can book an appointment.” Write the distinction explicitly so proposals cover the same work.

![A useful project brief: Business goal; Sources and actions; Limits and ownership; Acceptance checks.](https://troymaya.com/wp-content/uploads/2026/10/tm-howto-08-chatbot-project-brief-workflow.webp)
A useful project brief: Business goal; Sources and actions; Limits and ownership; Acceptance checks.

## 3. Complete this one-page requirements template

```
Project:
Audience and main task:
Where the chatbot appears:
Approved information sources:
Information it must not access:
Actions it may take:
Actions it must not take:
Required inquiry fields:
Human escalation route and owner:
Availability and response-time wording:
Systems to connect:
Budget range and target date:
Who approves answers:
Who maintains the system:
Acceptance questions and expected outcomes:
Handover, hosting, and account ownership:
```

If an answer is unknown, mark it unknown. That is more useful than guessing. Identify who can resolve it before development starts. Budget can be a range; the brief should allow the developer to propose a smaller first phase if the complete workflow does not fit.

## 4. Compare against a completed fictional example

Consider Pine Workshop, an invented furniture-repair business. Its first phase is public FAQ answers plus quote intake on a WordPress website. Approved sources are one service list, one coverage-area table, and ten reviewed FAQs. The bot collects job type, city, a short description, and a contact method. Photos can be requested later through the company’s established workflow.

The bot may submit an inquiry and report whether submission succeeded. It may not promise a repair price, offer discounts, reserve workshop capacity, or access previous customer records. Unusual materials and out-of-area inquiries go to a named coordinator. An illustrative acknowledgment is: “Your request has been received for review. The team will reply during its stated business hours.” Replace that wording with an actual service commitment the business can meet.

Three acceptance cases are especially useful: an ordinary covered job reaches the correct inbox; an unknown material is referred for review without a fabricated price; and a failed delivery produces an honest retry or contact option. This defines observable behavior rather than a vague requirement to “sound smart.”

## 5. Ask for a proposal you can operate after launch

Request separate descriptions of setup, ongoing platform fees, usage, hosting, and maintenance. Ask who owns the chatbot account and source documents, how staff edit answers, and what is included in handover. Define the initial test and revision process. A brief does not replace a contract, but it makes the scope easier to discuss and compare.

Before sending private material, share a public example or redacted sample. A developer can often assess the workflow without seeing customer records. If private access is required later, document the access boundaries as part of the project.

## Ready to discuss your chatbot?

Copy the template into your notes, complete the main task and source list, and [send TroyMaya a project inquiry](https://troymaya.com/contact/). You can review the available [AI development services](https://troymaya.com/ai-services/) first. Include your website, current tools, budget range, and the problem you want the first version to solve.

Prepared with AI assistance. Examples are illustrative unless stated otherwise.
