Skip to content

Getting Started with AI Squads

This guide explains how to engage with ConnectSoft AI Squads — virtual teams of AI agents that deliver defined outcomes on a subscription basis. It is written for product managers, CTOs, and teams evaluating or starting with AI Squads.

AI Squads combine specialized agents (Architect, Developer, QA, DevOps, Product) to deliver microservices, features, and integrations monthly. They provide predictable output with consistent architecture and quality.

Tip

Squads are ideal when you want managed outcomes without operating the Factory yourself. They deliver production-ready code, tests, and documentation every month.

Who This Guide Is For

  • Product Managers planning product development
  • CTOs evaluating managed development services
  • Technical Leads coordinating with squads
  • Stakeholders understanding squad deliverables

What You Get from a Squad

Squads deliver outcomes, not just hours:

Monthly Deliverables

  • Microservices - Production-ready microservices with clean architecture
  • Features - New features and enhancements in existing services
  • Integrations - External system integrations and data pipelines
  • Infrastructure - CI/CD pipelines, IaC templates, deployment automation
  • Documentation - ADRs, API docs, integration guides

Quality Standards

  • Clean Architecture - All code follows DDD and Clean Architecture patterns
  • Tests - Comprehensive unit and integration tests
  • CI/CD - Automated pipelines for build, test, and deploy
  • Observability - Logging, tracing, and metrics built-in
  • Documentation - Complete documentation and ADRs

Step 1 – Choose the Right Squad Type

Select the squad that matches your needs:

Squad Type Monthly Output Ideal For Minimum Commitment
Starter SaaS Squad 1 microservice + 2 epics MVPs, early-stage products 3 months
Growth SaaS Squad 2 microservices + 4 epics + 1 integration Scaling SaaS products 6 months
Platform Squad Platform capabilities + governance Enterprise platform teams Enterprise agreement
Integration & AI Bot Squad 2 pipelines + bot implementations Integrations and AI capabilities Monthly

For details, see Squads Overview and Squads Business Model.

Step 2 – Define Scope and Outcomes

Clearly define what you want the squad to deliver:

Create a Backlog

  • Epics - High-level features or capabilities
  • User Stories - Detailed requirements
  • Acceptance Criteria - Definition of done

Example Backlog

Epic 1: Subscription Billing Service - User Story: As a tenant admin, I want to manage subscriptions - User Story: As a system, I want to generate invoices automatically - Acceptance Criteria: Service follows Clean Architecture, includes tests, has CI/CD

Epic 2: Payment Integration - User Story: As a system, I want to process payments via Stripe - Acceptance Criteria: Integration tested, error handling, observability

Prioritize

  • Must Have - Critical for launch
  • Should Have - Important but not blocking
  • Nice to Have - Can wait if needed

Important

Clear scope definition helps squads deliver exactly what you need. Vague requirements lead to rework and delays.

Step 3 – Engagement Cadence

Establish regular communication rhythms:

Weekly Check-Ins

  • Status Review - What was completed this week
  • Next Week Plan - What's planned for next week
  • Blockers - Any blockers or questions
  • Demo - Show completed work

Review Cycles

  • Sprint Planning - Plan monthly deliverables
  • Mid-Month Review - Check progress, adjust if needed
  • End-of-Month Review - Review deliverables, plan next month

Communication Channels

  • Slack/Teams - Daily async communication
  • Weekly Calls - Synchronous status updates
  • Email - Formal communications and decisions

Step 4 – Deliverables and Acceptance

Define what counts as "done":

Code Deliverables

  • ✅ Code in Azure DevOps - All code in your repositories
  • ✅ Tests Passing - All tests pass, coverage meets standards
  • ✅ Build Passing - CI/CD pipelines successful
  • ✅ Documentation - README, API docs, ADRs updated

Quality Gates

  • Code Review - Review generated code before merging
  • Architecture Review - Verify architecture matches requirements
  • Integration Testing - Test integrations work end-to-end
  • Performance Testing - Verify performance meets requirements

Acceptance Process

  1. Squad Completes Work - Code, tests, docs ready
  2. You Review - Review code and documentation
  3. Provide Feedback - Request changes if needed
  4. Squad Iterates - Squad addresses feedback
  5. Accept - Approve and merge to main branch

Tip

Set clear acceptance criteria upfront. This reduces back-and-forth and ensures deliverables meet your expectations.

Step 5 – Working with Squad Outputs

Once deliverables are accepted:

Review Generated Code

  • Understand Structure - Review project structure
  • Review Domain Logic - Verify business logic is correct
  • Review Tests - Ensure tests cover critical paths
  • Review Documentation - Check docs are complete and accurate

Extend and Customize

  • Add Domain Logic - Add business-specific logic
  • Customize Integrations - Adjust integrations for your needs
  • Add Features - Extend with additional features

Deploy

  • Use Generated Pipelines - Deploy using generated CI/CD
  • Monitor - Use observability dashboards
  • Iterate - Continue working with squad on next features