Before choosing an AI tool, choose a process you can test.
A useful first project begins with recurring work, accessible information and a business owner who can approve the result. Use these checks to compare proposals and decide whether to start.
1. Describe the work as it happens today
Choose a trigger: a new inquiry, a quotation request or a system update. Explain who handles it, what information they need and where the output should go. If every instance follows a different process, stabilize the workflow before accelerating it.
2. Define success you can check
Replace “add AI” with a concrete case: a valid inquiry reaches the right person with the required details; a question without an approved source goes to a person. Collect real examples and remove identifying information before sharing. To measure time savings, first measure how long the current work takes.
3. Compare the boundaries of each proposal
Two proposals with the same label can include very different work. Ask for outputs and acceptance checks, rather than only a list of tools.
- What is built and what stays manual?
- Which systems and channels are included, and who checks access?
- What hours and meetings are included, and how are scope changes priced?
- What acceptance checks apply and who approves them?
- Who controls accounts, documentation and data access?
4. Separate implementation, usage and maintenance
Development is one cost. Models, messaging providers, hosting and connectors may add separate usage charges. Agree who pays providers, how usage can be reviewed and who handles information updates or incidents. An AI assistant does not imply unlimited support availability.
5. Choose the engagement around the missing work
When the workflow, information and result are clear, a focused project may suffice. When the business needs help deciding, scoping and supporting adoption, a collaborative engagement may fit. Monthly maintenance makes sense when there is defined ongoing work to price and review.
What to bring to the first conversation
A business description, recurring process, tools involved, desired outcome and timing. Say whether a budget exists or you are exploring feasibility. Do not send passwords, API keys or customer records.