This is a plain-language summary of how Agent by An scopes work. It is not a substitute for a signed proposal or legal agreement for larger projects.
Every project starts from one workflow: input, output, owner, frequency, tools involved, data sensitivity, review points, and expected result. Vague requests like “automate my whole business” should start with a paid audit or narrower intake.
AI systems can draft, classify, summarize, and assist. Important business decisions, customer-facing replies, financial/legal judgment, code merges, and destructive data changes should keep human approval unless a separate risk review says otherwise.
You are responsible for providing accurate context, safe sample data, access boundaries, timely feedback, and final approval for workflows used inside your business.
Do not submit passwords, tokens, API keys, full private datasets, customer records, or confidential documents through the quote form. Share anonymized examples first.
Paid pilots and sprints use a written scope. Changes outside scope may require a separate estimate. Larger work normally starts with upfront payment before build work begins.
Some workflows should not use AI yet. A trustworthy answer may be “clean up the process first” or “keep this manual.”
Use the quote form first. If the workflow is a fit, the proposal can include a clearer scope and acceptance checklist.
