Skip to main content
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 Prototype Mode — generating prototypes, 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 prototype of the proposed solution
  • Apply client branding using the Design System
  • Generate proposal artifacts: requirements documents, project charters, technical approach narratives
  • Share prototypes with clients and stakeholders via a shareable link — no BlueGenAI account required to view
What you produce: Working HTML prototypes, solution narratives, RTM, SOO, SOW, and other proposal artifacts.
The HTML prototypes generated in Design Mode are functional rendered code — not static mockups. They are one click away from becoming a deployed production application via Build Mode.
Where you are in the Government Project Lifecycle: Phase 1 — Pre-RFP Solutioning Where to go next:

Phase 1 Path A

How do I generate a prototype to respond to an RFP, task order, or SOW?

BD & Pre-Sales Guide

Tips and strategies for using BlueGenAI in business development contexts.

​
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 Prototype Mode — 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:

Phase 2 Path A

How do I develop requirements from solicitation materials?

Phase 2 Path B

How do I analyze a legacy system and generate requirements for its replacement?

​
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 Build Mode — 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 Build Mode 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:

Building Web Apps

Generate and deploy a full-stack web application.

Building on Low-Code

Deploy to TAP, ServiceNow, Salesforce, or PowerApps.

​
What if I span more than one role?

Many users contribute across multiple phases — this is expected and supported.
Read both Phase 1 Path A (how to generate a prototype from a solicitation) and the BD & Pre-Sales Guide in Resources. Use Design Mode for BD work and Build Mode for development work — both are available in every project.
Read both Phase 2 (requirements refinement) and Phase 4 (Build Mode). Start with the requirements work in Design Mode, then transition to Build Mode once requirements are approved.
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.

​
How the phases connect across roles

PhaseWho Does the WorkWhat Gets Produced
Phase 1 — Pre-RFP SolutioningSolutioning TeamsPrototypes, proposal artifacts, procurement documents
Phase 2 — Requirements RefinementBusiness AnalystsUser stories, acceptance criteria, architectural blueprint
Phase 3 — System DesignApplication EngineersData models, architecture diagrams, compliance docs
Phase 4 — DevelopmentApplication EngineersDeployed application or platform configurations
Phase 5 — TestingApplication EngineersTest plans, validation results
Phase 6 — DeploymentApplication EngineersLive system, deployment documentation
Outputs from each phase become inputs for the next. The platform is designed for this handoff.

​
Not sure where to start?

Quick Start Guide

New to BlueGenAI? Follow the Quick Start Guide to design, build, and deploy your first application — regardless of your role.