AI Squads Overview¶
This page provides an overview of ConnectSoft's AI Product Squads — virtual teams of AI agents that deliver defined outcomes on a subscription basis. It is written for product managers, CTOs, and teams evaluating managed development services.
AI Squads are subscription-based virtual teams that combine specialized AI agents (Architect, Developer, QA, DevOps, Product) to deliver microservices, features, and integrations on a monthly basis. They run on the ConnectSoft AI Factory and deliver consistent, high-quality outputs.
Tip
Squads are ideal for teams that want managed outcomes without operating the Factory themselves. They provide a predictable monthly output with defined scope and quality standards.
What Are AI Squads¶
AI Squads are virtual teams of specialized AI agents that work together to deliver software development outcomes:
- Composition - Mix of Architect, Developer, QA, DevOps, and Product agents
- Delivery Model - Monthly subscription with defined outputs
- Quality Standards - All outputs follow ConnectSoft templates and best practices
- Factory-Powered - Squads run on the Factory infrastructure
- Human Oversight - Optional human architect-in-the-loop for complex decisions
Squad Types¶
ConnectSoft offers four squad types, each optimized for different use cases:
Starter SaaS Squad¶
For: MVPs and early-stage products
Output: 1 microservice + 2 feature epics per month
Commitment: 3 months minimum
See: Starter SaaS Squad
Growth SaaS Squad¶
For: Scaling SaaS products
Output: 2 microservices + 4 epics + 1 integration per month
Commitment: 6 months minimum
See: Growth SaaS Squad
Platform Squad (Enterprise)¶
For: Internal platform teams
Output: Platform capabilities + governance artifacts
Commitment: Enterprise agreement
See: Platform Squad
Integration & AI Bot Squad¶
For: Integrations and AI capabilities
Output: 2 integration pipelines + AI bot implementations per month
Commitment: Monthly subscription
See: Integration & AI Bot Squad
When to Use Squads¶
Squads are ideal when:
- You want managed outcomes - Don't want to operate the Factory yourself
- You need predictable output - Monthly deliverables with defined scope
- You want consistent architecture - All outputs follow ConnectSoft patterns
- You lack internal capacity - Need a virtual team without hiring
- You want to accelerate - Faster than building in-house
Squads are not ideal when:
- You want full control - Prefer operating the Factory directly
- You have strong internal team - Can build faster/better internally
- You need custom processes - Require non-standard workflows
- Budget is very constrained - Factory-only may be more cost-effective
How Squads Work with the Factory¶
Squads run on the Factory infrastructure:
- Factory Infrastructure - Squads use the same Factory agents and templates
- Consistent Outputs - All squad outputs follow Factory standards
- Knowledge Sharing - Squad learnings contribute to Factory knowledge base
- Scalability - Factory handles the complexity of agent orchestration
Note
Squads are managed configurations of Factory agents. They provide a higher-level abstraction for customers who want outcomes, not infrastructure.
Squad Composition¶
All squads include a mix of specialized agents:
| Agent Type | Role | Typical Responsibilities |
|---|---|---|
| Architect Agent | Design and planning | Bounded contexts, APIs, events, architecture decisions |
| Developer Agent | Implementation | Code generation, tests, pipelines, documentation |
| QA Agent | Quality assurance | Test generation, quality gates, validation |
| DevOps Agent | Infrastructure | CI/CD pipelines, IaC, deployment automation |
| Product Agent | Requirements | Feature specs, user stories, acceptance criteria |
Squad composition varies by squad type. See individual squad pages for details.
Engagement Model¶
Squads operate on a subscription model:
- Monthly Subscription - Predictable monthly cost
- Defined Outputs - Clear scope and deliverables
- Minimum Commitment - Varies by squad type (3-6 months)
- Optional Add-Ons - Human architect hours, additional capacity
- Flexible Scaling - Upgrade/downgrade between squad types
For detailed pricing, see Squads Business Model.
Example Roadmap for 3 Months¶
Month 1: Foundation¶
- Initial microservice with core domain logic
- CI/CD pipeline setup
- Basic observability
- Documentation and ADRs
Month 2: Features¶
- Additional microservices or major features
- Integration with external systems
- Enhanced testing and quality gates
- Performance optimizations
Month 3: Scale¶
- Additional capabilities or integrations
- Platform enhancements
- Advanced features
- Production readiness
Actual roadmap varies by squad type and customer needs.
Related Documents¶
- Squads Business Model - Pricing and business model
- Factory Overview - How squads use the Factory
- Agent System Overview - How agents work
- BDR-0004: AI Squads Pricing Model - Pricing decision