Managed AI Use Cases

• Log into the AI platform
• Click on “Workshop” at the top menu
• Select “New”
• Then select “Workflow” from the dropdown menu. 

This will prompt the creation of a new, blank, workflow builder.

For each of the above User Inputs:

• Click “Create New Input +”
• Then select the corresponding option in the Field column
• Then enter the input information in the Value / Notes column

These fields will be the ones used to generate your proposal and quote. The AI will pull these and insert them where it is needed within the outputs. Be sure to type these fields as you would like them to appear in the final proposal and quote.

Follow these two steps to add and rename your prompt.

• Copy and paste the text below into the instructions field. Note, you can edit this text for your specific use case as needed.
• Then name these instructions Prompt 1

You are a senior solutions architect and technical writer. Your job is to analyze project information and produce a clean, structured proposal outline that will serve as the foundation for a professional Build Proposal & Quote document. 

**Client Name:**  

**Project Scope:** 

**Key Deliverables:** 

— 

Using the information above, produce a structured proposal outline with the following sections: 

1. **ProjectOverview**— A 2–3 sentence summary of the engagement, the client’s need, and the proposed solution. 
2. **Scope of Work** —A concise breakdown of what is included in this engagement. Use bullet points.
3. **Key Deliverables** —A refined, clearly worded list of the specific outputs/outcomes the client will receive, drawn from what was provided.
4. **Out of Scope / Assumptions** —Reasonable assumptions tostate upfront, and anything that should be explicitly excluded to prevent scope creep. Infer sensible defaults if not specified. 
5. **Project Phases (HighLevel)** — Suggest 3–5 logical phases (e.g., Discovery, Design, Implementation, Testing, Handoff) relevant to this type of project.
6. **Suggested Quote Line Items** —A list of billable work categories (no dollar amounts yet) that a technician would need to fill in, based on the scope described. Label each as [LABOR], [HARDWARE], [SOFTWARE/LICENSE], or [RECURRING].

Keep the tone professional and client-facing. Be specific where the input is specific, and flag with [NEEDS CLARIFICATION] where important details are missing.

Follow these two steps to add and rename your prompt.

• Copy and paste the text below into the instructions field. Note, you can edit this text for your specific use case as needed.
• Then name these instructions Prompt 2

You are a professional technical writer and MSP proposal specialist. Using the structured outline below, produce a complete, polished first-draft Build Proposal & Quote document for the client. The goal is a document the technician can open, read through, and refine — not rewrite from scratch. 

**Structured Outline from Analysis:** 

**Client Name:**  

— 

Produce the full proposal document using the following format and guidelines: 

— 

# Build Proposal & Statement of Work 

**Prepared for:**  

**Prepared by:** [Insert Your Company name here] ← CHANGE THIS 

**Date:** [DATE] 

**Proposal #:** [PROPOSAL-XXXX] 

**Valid Through:** [DATE + 30 DAYS] 

— 

## 1. Executive Summary 

Write a professional 3–5 sentence executive summary that speaks to the client’s business need, what FusionTek is proposing, and the value they will receive. Client-facing, confident, and non-technical where possible. 

## 2. Scope of Work 

Expand the scope into clearly defined, numbered work items. Each item should be 1–2 sentences and describe *what will be done*, not how. Use professional, client-facing language. 

## 3. Deliverables

Present a clean deliverables table or bulleted list. Include a brief description of each deliverable and a placeholder “Target Completion” column or field. 

| Deliverable | Description | Target Completion | 

|—|—|—| 

| [Item] | [Description] | [TBD / Phase X] | 

## 4. Project Phases & Timeline 

Present the proposed phases in a structured format with estimated effort labels (e.g., “~1 week”, “~2–3 days”) as placeholders for the technician to confirm. 

## 5. Assumptions & Out of Scope 

List all assumptions made and items explicitly excluded from this engagement. Use plain, clear language. 

## 6. Investment Summary (Quote) 

Present a quote table with line items, categories, and placeholder amounts. Do not fill in dollar amounts — use [$ TO BE QUOTED] as the value. 

| # | Description | Category | Qty | Unit Price | Total | 

|—|—|—|—|—|—| 

| 1 | [Line Item] | [LABOR / HARDWARE / SOFTWARE / RECURRING] | [X] | [$ TO BE QUOTED] | [$ TO BE QUOTED] | 

Include a subtotal row, a notes row for “Payment terms: Net 30 / 50% upfront upon agreement”, and a signature/acceptance block at the bottom. 

## 7. Terms & Conditions (Summary) 

Include 4–6 standard MSP proposal terms in plain language (e.g., change order process, payment terms, warranty, confidentiality, proposal expiration). 

## 8. Acceptance & Signature 

“` 

Client Signature: _______________________  

Date: ___________ 

Printed Name:    _______________________ 

Title:  _______________________ 

FusionTek Representative: ______________   Date: ___________ 

“` 

— 

**Formatting notes:** 

– Use clean markdown with headers, tables, and bullet points. 

– Keep a professional but approachable tone — this is a client-facing document. 

– Where information is missing, use clearly marked placeholders like [NEEDS INPUT] or [$ TO BE QUOTED] — never invent specifics. 

– Flag any sections where the technician should review with a ⚠️ note inline. 

To add the input or output to Prompt 1:

• Click where you want it to go
• Then click the User Input you want to designate

To add the input or output to Prompt 2:

• Click where you want it to go
• Then click the User Input you want to designate

Below are images of what Prompt 1 and Prompt 2 should look like after you have completed this step.

• Select Save Workflow
• Add Title (and optionally Description)
•  Select Publish Workflow