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.

Start here

Choose a useful first workflow

A useful first workflow has a recognizable beginning, a result you can inspect, and a person who can decide whether the result is good enough. Write down the current process 1. Trigger: What starts the task? For example, a new document arrives. 2. Input: What information is available? Name its format and where it comes from. 3. Work: What does someone do with that information today? 4. Result: Where does the finished work go? 5. Review: Who checks mistakes and exceptions? Choose a task you can describe with a small synthetic example. Leave confidential material out of the initial example; you can agree on the right handling and destination before using real data. Make success observable “Use AI in the business” is difficult to evaluate. “Prepare a reviewable draft of these five intake fields from a sample document” gives you something to check. Useful measures include time per completed item, items needing correction, turnaround time, and the amount of work someone must redo. Record the baseline before deciding what improvement is realistic. Keep the first version small Start with one input type, one review step and one destination. Agree on what happens when the tool is unsure or fails. A reliable exception path is part of the workflow. For a personal project, the same approach works: turn a set of hobby notes into a checklist, organize a collection, or prepare a plan you can edit. The desired result and review process still matter. Use the solution brief template to bring those details into the conversation.

Start here

How to read a Space card

A Space card should help you decide whether a tool fits your task before you invest time in it. Read the availability label first | Label | What it should mean | | --- | --- | | Blueprint example | An explanation of a possible tool or workflow. No working endpoint or paid access is promised. | | Preview | A specific working preview is available under its stated limits. Treat it as a test experience. | | Available | The listed access path, limits and support arrangement have been checked. | | Managed service | Pat operates an agreed service under a defined scope and commercial arrangement. | Every Space in this starting guide collection is a blueprint example. Ask Pat about the current availability of a particular implementation. Check the whole card A useful card describes the task, input, output, review step, compatible destinations, limits and cost basis. It should also say what the tool does when it cannot complete an item. For a paid tool, review the actual offer before use: what is counted, whether retries count, any minimum or recurring charge, and what happens when you reach a limit. A demonstration article is not a checkout agreement. Think in building blocks A document tool can produce text for a search tool. A search result can support a draft. A reviewed draft can enter an existing business system. The connections and permissions matter as much as the individual tools. See how tools connect and how estimates are prepared.

Example Spaces

Document intake and OCR

Availability: blueprint example. This article describes a possible workflow. It does not provide a live upload tool or promise that a specific document format is supported. The job Turn scanned pages or document files into text and a small set of fields that a person can review. | Part | Example | | --- | --- | | Input | A synthetic scanned form or document file. | | Output | Extracted text, selected fields and a link back to the source. | | Human review | Check uncertain text, field values and missing pages before accepting the result. | | Possible next step | Add the reviewed record to an approved system or make the text searchable. | Where it can help The useful part is reducing repetitive copying and making the source easier to work with. OCR reads visible text; it does not by itself decide whether a document is correct, complete or suitable for a particular decision. Questions to settle Which file types and languages matter? Are pages handwritten? Do you need tables or only a few fields? How long should the source be retained? Who can open it? How will duplicates and failed jobs be handled? Ask for a preview with a synthetic sample before treating the workflow as available for your own material. Follow the intake walkthrough or bring this building block into your solution brief.

Example Spaces

Search your own knowledge

Availability: blueprint example. This article describes a possible tool, not a connected search service. The job Find useful information in an approved collection and show the source behind an answer. | Part | Example | | --- | --- | | Input | A question and a collection you are allowed to search. | | Output | Relevant passages, source links and an optional draft answer. | | Human review | Open the source and check whether it supports the answer. | | Possible next step | Use the reviewed result in a report, procedure or draft response. | What makes the result useful The collection needs clear ownership, access permissions and a process for updates or deletion. Search should respect those permissions. An answer should say when the available sources do not support a confident response. Questions to settle Where do the files live? Who should see each collection? How fresh must the result be? Can the source be linked directly? What should happen after a source changes or is removed? You can combine this idea with document intake, but extraction and search solve different steps. Agree on the contract between them using the connection walkthrough.

Example Spaces

An everyday planning assistant

Availability: blueprint example. This article is a planning example, not access to a hosted assistant. The job Turn a collection of notes into an organized draft you can use and change. | Part | Example | | --- | --- | | Input | Your notes, constraints and a description of the result you want. | | Output | A checklist, comparison, outline or draft plan. | | Human review | Check facts, priorities and whether the plan fits your circumstances. | | Possible next step | Copy the reviewed result into the calendar, document or task system you already use. | Work, personal productivity and leisure The same pattern can help prepare a weekly planning outline, organize a home project, structure research for a hobby, or compare options for a creative project. Start with drafting and organization. Taking an external action—such as sending a message, making a booking or spending money—needs its own connected tool and explicit decision. Questions to settle What information should the assistant remember? What should it forget? Which sources does it need? What is a helpful output format? Which actions should always remain with you? Use the first-workflow guide to keep the initial version focused.