Starter stack
AI stack for software engineering teams
Code, review, delivery speed
The stack
| Tool | What it is for | Price | 10-person cost |
|---|---|---|---|
| GitHub Copilot Free plan | In-editor coding assistant | Free · Pro $10/mo · Pro+ $39/mo · Business $19/user/mo | $30/mo |
| ChatGPT Free plan | Architecture questions and code explanation | Free · Go $8/mo · Plus $20/mo · Pro $200/mo | $60/mo |
Pilot total $90/month ($1080/year) — the everyday assistant for the pilot group, the specialist tools for a smaller set of people who need them.
Enterprise
Buy this stack for your team
$190per month
Enterprise covers the software engineering rollout end to end for everyone on the team: the 2 recommended tools set up in a shared workspace, the 90-day plan, the training path and the usage policy. Billed at $19 per person per month. Tool subscriptions themselves (about $90/month) stay on your own accounts.
seats (minimum 3)
Billing
- Shared workspace with this software engineering stack pre-loaded
- The 90-day rollout plan assigned to owners
- Training path and certificates for every seat
- Usage policy, spend tracking and stack reviews
How to roll it out
Days 1–30 — pilot
Start with 3 people, not everyone
- Pick 3 volunteers who already do software engineering work daily and give them GitHub Copilot.
- Name the two tasks each of them will use it for, and write down how long those tasks take today.
- Agree the data rules before the first login: what may be pasted in, and what may not.
- Book a 45-minute kick-off around the tool’s video walkthrough and written steps on this site.
Days 31–60 — prove it
Measure the saving and fix what got in the way
- Compare the before-and-after time on those same two tasks and record the difference in hours.
- Collect the failures as well as the wins — that list becomes your review checklist.
- Add the supporting tools (ChatGPT) only where the pilot showed a clear gap.
- Publish one short internal write-up from a colleague, not from management.
Days 61–90 — roll out
Extend to the remaining 7 people
- Buy seats in one batch so billing and admin stay in one place.
- Run the same 45-minute onboarding for each new group, using the prompts your pilot proved.
- Set a monthly review of spend against value in the cost calculator, and cancel anything unused.
- Assign one owner per tool who answers questions and watches for pricing changes.
What usually goes wrong
- Confident-sounding errors: every tool here scores below 100% on accuracy, so the review step is not optional.
- Shadow usage: if you do not approve something usable, people will use their own accounts with company data.
- Seat creep: paid seats keep billing after people stop using them — the monthly review catches this.
- Overreach: starting with a company-wide rollout is the most common way an AI project quietly dies.
Train the team
- What is AI, really?Beginner · Everyone in the pilot, week one
- AI Fundamentals & TerminologyBeginner · Pilot group, month two
- Prompt Engineering that worksIntermediate · Owners and power users