> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bluegenai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Who is it for?

> BlueGenAI serves three distinct audiences. Find out which path through the platform is right for your role.

BlueGenAI is built for the teams that deliver government modernization projects. Three distinct audiences use the platform — each at a different phase of the project, with different inputs, different outputs, and a different path through the site.

The landing page introduced these three audiences. This page goes deeper — describing what each role actually does in the platform, how their work connects to the Government Project Lifecycle, and where to go next.

***

## Solutioning Teams

Solutioning Teams use BlueGenAI to win government work and support pre-award activities. Your work happens primarily in the Prototype tab — generating Draft Apps, solution narratives, and proposal artifacts from solicitation materials before a contract is awarded.

**What your work looks like in the platform:**

* Upload an RFP, task order, or SOW and generate a working Draft App of the proposed solution
* Apply client branding using the Design System
* Generate proposal artifacts: requirements documents, project charters, technical approach narratives
* Share Draft Apps with clients and stakeholders via a shareable link — recipients must be logged in to BlueGenAI to view

**What you produce:**

Working Draft Apps, solution narratives, RTM, SOO, SOW, and other proposal artifacts.

<Note>
  The Draft Apps generated in the Prototype tab are functional rendered code — not static mockups. They are one click away from becoming a deployed production application via the Build tab.
</Note>

**Where you are in the Government Project Lifecycle:**

Phase 1 — Pre-RFP Solutioning

**Where to go next:**

<CardGroup cols={2}>
  <Card title="Phase 1 Path A" icon="file-contract" href="/building-web-apps/phase-1-path-a">
    How do I generate a prototype to respond to an RFP, task order, or SOW?
  </Card>

  <Card title="BD & Pre-Sales Guide" icon="handshake" href="/resources/bd-and-pre-sales-usage-guide">
    Tips and strategies for using BlueGenAI in business development contexts.
  </Card>
</CardGroup>

***

## Business Analysts

Business Analysts use BlueGenAI to transform existing systems and documents into structured, traceable requirements. Your work happens primarily through CAB (Common Application Blueprint) and the Prototype tab — analyzing legacy systems, generating user stories, and producing compliance-ready documentation.

**What your work looks like in the platform:**

* Upload legacy system artifacts — source code, database schemas, documentation, screenshots — to CAB
* Review the generated architectural blueprint of the existing system
* Generate user stories and acceptance criteria for the future state system
* Produce requirements traceability matrices and compliance documentation

**What you produce:**

Architectural blueprints, user stories, acceptance criteria, requirements traceability documentation, compliance artifacts.

**Where you are in the Government Project Lifecycle:**

Phase 2 — Requirements Refinement

**How your work feeds forward:**

The user stories and system design artifacts you approve in Phase 2 become the inputs for Application Engineers in Phase 3.

**Where to go next:**

<CardGroup cols={2}>
  <Card title="Phase 2 Path A" icon="list-check" href="/building-web-apps/phase-2-path-a">
    How do I develop requirements from solicitation materials?
  </Card>

  <Card title="Phase 2 Path B" icon="arrows-rotate" href="/building-web-apps/phase-2-path-b">
    How do I analyze a legacy system and generate requirements for its replacement?
  </Card>
</CardGroup>

***

## Application Engineers

Application Engineers use BlueGenAI to generate and deploy full-stack web applications or platform-native low-code configurations. Your work happens primarily in the Build tab — taking approved requirements and design artifacts and generating production-ready applications.

**What your work looks like in the platform:**

* Receive approved requirements and design artifacts from Phase 2
* Switch to the Build tab and attach design files
* Prompt the agent to generate the application — frontend, backend, and database
* Review the live deployed application URL
* Iterate: add features, fix issues, extend functionality
* Deploy to web or to a low-code platform instance (TAP, ServiceNow, Salesforce, PowerApps)

**What you produce:**

Deployed web applications with live URLs, or platform-native configurations for TAP, ServiceNow, Salesforce, or PowerApps.

**Where you are in the Government Project Lifecycle:**

Phases 3 through 6 — System Design, Development, Testing, and Deployment

**How your work connects back:**

If the application does not behave as required, return to earlier phases to refine requirements or design before continuing.

**Where to go next:**

<CardGroup cols={2}>
  <Card title="Building Web Apps" icon="globe" href="/building-web-apps/web-apps-overview">
    Generate and deploy a full-stack web application.
  </Card>

  <Card title="Building on Low-Code" icon="puzzle-piece" href="/building-on-low-code/low-code-overview">
    Deploy to TAP, ServiceNow, Salesforce, or PowerApps.
  </Card>
</CardGroup>

***

## What if I span more than one role?

Many users contribute across multiple phases — this is expected and supported.

<AccordionGroup>
  <Accordion title="Application Engineer who also supports BD work">
    Read both Phase 1 Path A (how to generate a prototype from a solicitation) and the BD & Pre-Sales Guide in Resources. Use the Prototype tab for BD work and the Build tab for development work — both are available in every project.
  </Accordion>

  <Accordion title="Business Analyst who also builds applications">
    Read both Phase 2 (requirements refinement) and Phase 4 (Build tab). Start with the requirements work in the Prototype tab, then transition to the Build tab once requirements are approved.
  </Accordion>

  <Accordion title="Solutioning Team member who also does requirements work">
    Read both Phase 1 Path A (BD solutioning) and Phase 2 Path A (post-award requirements development). The platform supports both workflows — your starting point depends on where you are in the project.
  </Accordion>
</AccordionGroup>

***

## How the phases connect across roles

| Phase                             | Who Does the Work     | What Gets Produced                                         |
| --------------------------------- | --------------------- | ---------------------------------------------------------- |
| Phase 1 — Pre-RFP Solutioning     | Solutioning Teams     | Prototypes, proposal artifacts, procurement documents      |
| Phase 2 — Requirements Refinement | Business Analysts     | User stories, acceptance criteria, architectural blueprint |
| Phase 3 — System Design           | Application Engineers | Data models, architecture diagrams, compliance docs        |
| Phase 4 — Development             | Application Engineers | Deployed application or platform configurations            |
| Phase 5 — Testing                 | Application Engineers | Test plans, validation results                             |
| Phase 6 — Deployment              | Application Engineers | Live system, deployment documentation                      |

Outputs from each phase become inputs for the next. The platform is designed for this handoff.

***

## Not sure where to start?

<Card title="How do I get started?" icon="rocket" href="/platform-overview/quick-start-guide">
  New to BlueGenAI? Follow the Quick Start Guide to design, build, and deploy your first application — regardless of your role.
</Card>