Proposal Template – AI Factory Project¶

This document provides a reusable skeleton for proposals where the main product is the AI Factory (plus some platforms). It is written for sales and business development teams creating customer proposals.

This is an internal template document. Actual numbers, pricing, and customer-specific details go in external proposals. Use this template as a starting point and customize it for each customer engagement.

Note

This is an internal template document. Actual numbers, pricing, and customer-specific details go in external proposals. Customize this template for each customer engagement.

1. Context and Objectives¶

Customer Context¶

Company: [Customer company name]
Industry: [Industry/sector]
Current State: [Current architecture, challenges, pain points]
Goals: [Customer goals and objectives]

Project Objectives¶

Primary Objective: [Main objective of the engagement]
Success Criteria: [How success will be measured]
Timeline: [Expected timeline]
Budget: [Budget range or constraints]

Business Drivers¶

2. Proposed Solution¶

Solution Overview¶

Factory Access: [Factory access level and capabilities]
Platforms Included: [Identity, Audit, Config, Bot platforms if included]
Support Level: [Support tier and response times]
Training: [Training and onboarding included]

Key Capabilities¶

Code Generation: [Microservices, libraries, pipelines, docs]
Architecture: [Clean Architecture, DDD, event-driven patterns]
Platforms: [Platform capabilities if included]
Integration: [Azure DevOps, external systems integration]

Value Proposition¶

Speed: [Time-to-market improvements]
Quality: [Code quality and architecture benefits]
Consistency: [Consistency across services]
Ownership: [Code ownership and control]

3. Scope and Deliverables¶

Scope¶

Bounded Contexts: [Number of bounded contexts to be designed]
Microservices: [Number of microservices to be generated]
Integrations: [Number of integrations to be built]
Platforms: [Platforms to be integrated]

Deliverables¶

Generated Code: [Code repositories in Azure DevOps]
CI/CD Pipelines: [Pipeline definitions and configurations]
Documentation: [Architecture docs, ADRs, API docs]
Training: [Training sessions and materials]
Support: [Support period and response times]

Out of Scope¶

[Items explicitly out of scope]
[Assumptions about customer responsibilities]
[Limitations and constraints]

4. Timeline and Phasing¶

Phase 1: Setup and Onboarding¶

Duration: [X weeks]
Activities:
Factory setup and configuration
Azure DevOps integration
Team training
Initial project setup

Phase 2: Pilot Project¶

Duration: [X weeks]
Activities:
Design first bounded context
Generate first microservice
Review and feedback
Iteration and refinement

Phase 3: Full Rollout¶

Duration: [X months]
Activities:
Generate remaining microservices
Integrate platforms
Deploy to environments
Documentation and handover

Milestones¶

5. Assumptions and Responsibilities¶

Assumptions¶

Customer Responsibilities:
Azure DevOps access and configuration
Azure subscription and resources
Technical team availability for review
Domain expertise and requirements
ConnectSoft Responsibilities:
Factory access and configuration
Code generation and delivery
Training and support
Platform integration support

Dependencies¶

[External dependencies]
[Customer dependencies]
[Technical dependencies]
[Resource dependencies]

6. Pricing Structure (High-Level)¶

Pricing Model¶

Factory Access: [Subscription/licensing model]
Platforms: [Platform pricing if included]
Support: [Support pricing]
Training: [Training pricing if separate]

Payment Terms¶

Payment Schedule: [Payment milestones]
Currency: [Currency]
Terms: [Payment terms]