Plan your project
Prepare a brief, compare delivery options and make the assumptions behind an estimate visible.
Bring a one-page solution brief
A short brief gives the conversation something concrete to improve. You can leave unknowns as questions. Copy this template Task and current process: What happens today? What is repetitive, slow or difficult? Desired result: What should someone receive at the end? How will you know it is good enough? Input and volume: What starts the task? What formats, frequency and approximate volume are involved? People and review: Who uses the result? Who checks it? Who can approve a consequential action? Existing tools: Which systems, files or accounts need to connect? Data and access: What information is involved? Who may see it? Where should it be retained or deleted? Workflow draft: List the steps from input to reviewed result. Name likely building blocks and mark unverified assumptions. Exceptions: What should happen when something is unreadable, missing, duplicated or unavailable? Delivery preference: Setup and handoff, help with configuration, or an agreed managed service? Commercial assumptions: Expected usage, setup scope, recurring responsibilities and any budget constraints. Success measure: Baseline time, quality or turnaround, and the improvement you would like to test. Open questions and next decision: What needs to be learned before committing? Save a reviewed version Check the summary before it becomes a project brief. A conversation and an email address do not establish ownership of a customer account. Pat needs the appropriate authorized account context to save commercial planning information there. A planning brief does not approve a quote, begin paid work or create a payment. See estimates and value.
Understand estimates, costs and value
An estimate is useful when you can see what it assumes and what would change it. Keep the cost categories separate | Category | What to establish | | --- | --- | | Setup | The agreed configuration, integrations, testing, documentation and handoff. | | Ongoing management | The tasks Pat will operate, monitor or maintain and the response arrangement. | | Provider usage | The services, volume assumptions, units and current provider prices. | | Software or subscriptions | The required plans, account owner and renewal responsibility. | | Changes | What is included, and how additional scope will be estimated. | A conversation may explore a range. Pat must review the scope and confirm the actual quote. A generated figure is not an approved offer or permission to charge a payment method. Estimate capacity before claiming revenue Use: Monthly hours saved = monthly items × minutes saved per item ÷ 60. For a purely hypothetical example, 660 items each taking three fewer minutes would release 33 hours of capacity. At an assumed value of $40 per hour, that is $1,320 of estimated capacity value before provider costs, management costs and the time needed for review. Those are illustration inputs, not a Product Pat price or a measured result. Released capacity becomes actual cash savings or new revenue only if your business can use it that way. Include uncertainty Compare a conservative case with the expected case. Test the time required to correct errors, the exception rate, the real usage volume and the recurring operating work. For new revenue, describe the causal link and evidence separately. A faster workflow does not automatically produce sales. Bring your own baseline and assumptions into the solution brief.
Choose setup, handoff or ongoing management
The best arrangement depends on who wants to operate the workflow after it is configured. Compare the responsibilities | Arrangement | Typical scope to discuss | Decision to make | | --- | --- | --- | | Guided configuration | Help selecting tools and working through setup. | Which tasks will you complete yourself? | | Setup and handoff | Configure the agreed workflow, test it and document operation. | Who owns accounts, credentials and maintenance afterward? | | Setup and management | Configure the workflow and provide a defined ongoing service. | What is monitored, maintained and included in the service? | | Standalone tool usage | Use a particular available tool under its published terms. | What are the actual limits, units and access requirements? | These are scoping options, not a published rate card or a promise that every tool is currently available. Put ownership in the plan List the owner of each provider account, the people who can access the workflow, where data lives, and how the service can be handed over or ended. Define “done” A handoff should include a usable operating path, an example of successful work, a demonstrated failure or retry path, and instructions for recovering the relevant data. For management, agree on routine responsibilities and how change requests are handled. Avoid assuming that “managed” includes every possible future feature. Use the estimate guide to separate setup, recurring work and provider usage.
Talk with Pat and continue your plan
The chat launcher is a place to discuss a possible workflow and decide on a useful next step. Know who is in the conversation An AI assistant may respond if that feature is enabled. Pat may review the conversation. When Pat joins to speak directly, he should identify himself in the thread. You can ask for a person. Availability and the actual handoff behavior should be clear in the conversation; a chat launcher is not a promise of immediate live coverage. Move to a call when it helps If you and Pat agree, he can share a meeting link or use a supported call feature where it has been configured. A Google Meet window embedded inside this guide is not provided. Pause with a useful summary Before leaving, capture the current problem statement, workflow draft, assumptions, open questions and next step. Copy the important parts for your own reference. The native chat session can retain a conversation in the same browser under its configured behavior. That does not guarantee recovery on another device or establish a signed-in customer project. Turn the conversation into a project Pat can review the useful parts and save a planning brief in the authorized project workspace through the established process. Confirm what should be saved and the correct account first. Saving a brief does not automatically approve pricing, start a subscription, charge a payment method or authorize an email campaign. An actual engagement follows the reviewed commercial process. Use the one-page brief to make the next conversation easier to continue.