1
Business and offer
What you sell, where you operate, and what must not be promised.
Timing and final form depend on scope, content readiness, technical access, integrations, timezone coordination, and review speed. The process stays visible so risk, decisions, and responsibility do not disappear.
We agree on the workflow first, then build and test the website and AI around it.
We map the offer, traffic sources, customer questions, and the way your team follows up.
Page structure, key information, qualification questions, calls to action, and answer boundaries are agreed together.
The website, conversations, and integrations are built and tested against the main scenarios before launch.
After approval, the system launches, is handed over, and is reviewed during the agreed support period.
Project brief checklist
You do not need a polished document. Bring the facts you have, mark what is unknown, and identify who can approve business information.
What you sell, where you operate, and what must not be promised.
Who should arrive, current traffic sources, and any available baseline data.
Questions prospects ask before they are ready for a person.
Approved services, policies, pricing rules, content, and owners of updates.
Useful context to collect and the human channel that receives it.
Topics AI must avoid, limit, verify, or escalate immediately.
Current website, domain, analytics, integrations, consent, and security constraints.
Required languages, budget range, target timing, reviewers, and final approver.
The client supplies or approves the business facts used by the system.
High-risk, unknown, or time-sensitive topics are limited and routed to people.
Someone must keep facts current and review quality after launch; maintenance terms follow scope.
Share the facts you have and mark what still needs verification. The first conversation is non-binding and does not promise business outcomes.