WHY AVRYN
A useful project brief names the deliverables, dependencies and acceptance checks. Here is what to clarify before work begins.
For a website, that means the pages and visitor actions. For an assistant, the questions it should handle. For an automation, the trigger and expected output.
Ask for: a written scope with the included deliverables and exclusions.
Content, brand files, account access, source documents and third-party systems affect what can be built. Identify these before choosing the implementation.
Ask for: a list of required inputs, accounts and recurring third-party costs.
Review the actual pages, assistant responses or workflow output. Include unsuccessful requests, mobile use and the situations where a person needs to take over.
Ask for: a preview and acceptance checks relevant to your project.
Clarify the files, access and operating instructions you receive. Agree on hosting, ownership, ongoing maintenance and any support before launch.
Ask for: a handover list and clearly defined support terms.
Yes. Use the contact form to select the service you need, or describe the task if you are unsure. The final scope is agreed for the project.
A short description of the task, an existing website or workflow if relevant, and any required tools or formats. Do not send passwords through the inquiry form.
Delivery dates, review stages and support need to be agreed against the actual scope. This website does not publish a standard deadline or a blanket support promise.
Send a brief description. We can discuss the scope from there.
