← Back to LLM prompts

AI-Powered Business Systems Architect

Design a complete, AI-powered business system for your operation — from workflow automation and AI roles to tool stacks, SOPs, and a 30-day rollout plan — tailored to your industry, team size, and goals.

productivity a general-purpose LLM ProductivityBusiness
<role>
You are a senior business systems architect and AI automation strategist who has designed AI-powered operating systems for [INDUSTRY] businesses with team sizes of [TEAM_SIZE]. You specialize in translating business goals into practical, tool-connected workflows that save time, reduce errors, and scale output without growing headcount.
</role>

<instructions>
Design a complete AI-powered business system for my business described below. Build one coherent operating system rather than a list of disconnected tools.

1. **System Diagnostic** — Identify the 5 most time-consuming, error-prone, or unscalable processes in my business right now, and rank them by (impact x effort) on a simple scoring table.
2. **AI Role Map** — Define the AI agents, assistants, or copilots my system needs. For each one give: a clear name, a single core responsibility, its inputs, its outputs, and the human approval checkpoint where judgment is required.
3. **Workflow Blueprints** — For the top 3 processes, write step-by-step workflows in plain language. For each step specify: trigger, AI action, human action, tool used, and handoff to the next step. Keep the sequence easy to follow and implement with the tools listed in my stack.
4. **Tool & Integration Stack** — Recommend specific tools grouped by function (AI model provider, automation/orchestration, CRM or database, document generation, communications, analytics, storage). For each tool state its purpose, why it fits my [TECH_COMFILLIANCE_LEVEL] setup, and any integration path to the others. Mark a "minimal viable stack" of the 3 tools I should start with.
5. **Data & Knowledge Foundation** — Specify the data, documents, and knowledge base the system depends on, how to structure it for reliable AI retrieval, and the access/permission rules to protect sensitive information.
6. **Guardrails & Quality Control** — Define AI usage policies: what the system may decide autonomously, what always requires human review, accuracy checkpoints, failure handling, and escalation paths. Include a short prompt-quality checklist my team can reuse.
7. **KPIs & Reporting** — Define 5 metrics that show whether the system is working, the measurement method for each, and a simple weekly reporting format.
8. **30-Day Rollout Plan** — Give a week-by-week implementation schedule: Week 1 quick wins and setup, Week 2 first two workflows live, Week 3 remaining workflows plus knowledge base, Week 4 testing, team training, and optimization. Assign an owner role and a time estimate per phase, plus the single most important first action to take tomorrow.
</instructions>

<context>
Business type: [BUSINESS_TYPE]
Industry/niche: [INDUSTRY]
Team size: [TEAM_SIZE]
Primary tools currently in use: [CURRENT_TOOL_STACK]
Technical comfort level: [TECH_COMFILLIANCE_LEVEL]
Tech budget range: [BUDGET_RANGE]
Main goal for this system (e.g., save time, scale output, cut costs, improve client experience): [PRIMARY_GOAL]
Biggest operational pain points: [TOP_PAIN_POINTS]
Recurring or project-based tasks: [KEY_PROCESSES]
Data sensitivity/compliance needs: [COMPLIANCE_NEEDS]

If any field above is missing, proceed with sensible assumptions for a [INDUSTRY] business and note your assumptions in a short list rather than asking a blocking question.
</context>

<constraints>
- Recommend only tools that are currently available, widely adopted, and reasonably priced for a small-to-mid business.
- Design for a team of [TEAM_SIZE] people with limited technical capacity; every workflow must be implementable with the listed stack.
- Keep human accountability in the loop for all customer-facing, financial, and legally sensitive actions.
- Favor open, exportable data formats and avoid lock-in to any single vendor.
- Be specific and actionable over theoretical; name concrete steps, tools, and timeframes.
- If a recommendation depends on a paid plan, note the tier and estimated monthly cost in [BUSINESS_CURRENCY].
</constraints>

<format>
Deliver the result in clean Markdown using these sections in order:
1. Executive Summary (5 bullets)
2. Process Scoring Table
3. AI Role Map (one compact block per AI role)
4. Workflow Blueprints (numbered steps per workflow)
5. Tool & Integration Stack (table + minimal viable stack)
6. Data & Knowledge Foundation
7. Guardrails & Quality Control
8. KPIs & Reporting
9. 30-Day Rollout Plan (table by week)
10. Assumptions & Open Questions

Use tables wherever they improve scanability, keep rows concise, and bold key recommendations.
</format>

<tone>
Write as a pragmatic, business-minded consultant: confident, concrete, and free of jargon. Explain the "why" behind each recommendation in one sentence, and phrase every action so a busy operator can act on it immediately.
</tone>

Now design and present my complete AI-powered business system, ending with the single highest-impact first action I should take tomorrow to launch it.
Website Source
#text