# SWOT — Internal AI tooling platform (year 1)

## Strengths (internal, positive)
• Strong infrastructure + reliability — 99.9%+ uptime since launch, no major incidents.
• Leadership buy-in confirmed via initial funding; signals top-down support.
• 3 internal teams already using it = early proof of value + testimonial sources.
• Small team (3 people) = fast decision-making, no internal coordination tax.
• Built on org's existing infra stack — no cross-team integration friction.
Strategic implication: Lean into the "reliability + speed of decision" advantages — let those define the platform's identity vs the shadow tooling, which trades reliability for speed-to-features.

## Weaknesses (internal, negative)
• UX is rough — most users describe it as "powerful but I have to learn it".
• No formal product roadmap — features ship reactively to early adopters.
• Documentation is minimal; tribal knowledge dominates.
• Small team is a bottleneck for support; every new adopting team adds onboarding load.
• Free-to-use model means there's no funding pressure to prioritise — and no signal of which features matter most.
Strategic implication: Fix the UX + onboarding friction BEFORE pursuing wider adoption. Pushing adoption with rough UX produces complaints that taint the platform reputation faster than it spreads.

## Opportunities (external, positive)
• Org-wide AI mandate from leadership — every team is being asked to integrate AI; we're the natural choice.
• Each new team that builds shadow tooling validates the problem; they're evidence of demand.
• Frustration with team-built scripts (no support, no reuse) means there's a "stop reinventing this" appetite forming.
• External AI vendors (Workers AI, etc.) keep adding capabilities — the platform can offer "we wrapped this for you" without building from scratch.
• Quarterly tech all-hands gives us a public adoption-pitch venue we haven't used yet.
Strategic implication: Attack the shadow-tooling adoption pattern — pitch the platform as "stop maintaining your own scripts" to teams that have already felt the pain.

## Threats (external, negative)
• Shadow tooling teams build will continue to compete in the short term; if they out-feature us in their narrow use cases, those teams won't switch.
• External AI vendor pricing changes could blow up the cost model.
• If a high-profile team rolls their own and visibly succeeds, the platform loses its "default" claim.
• Leadership buy-in is conditional — if year 2 adoption is slow, funding pressure rises.
• A peer team in another business unit could build a competing internal platform; we end up with 2 instead of 1.
Strategic implication: Defend the "default" position aggressively. Convince leadership to make AI tooling go through this platform first by year 2 (org policy, not just preference).

## Cross-quadrant moves
• S × O: Use the reliability advantage + the leadership AI mandate to make the platform the OFFICIAL default — a soft mandate that all AI tooling either uses the platform or justifies why not. Strength (reliability) meets opportunity (mandate) = institutional traction.
• W × T: Fix UX + add docs (W) before a high-profile shadow tooling effort (T) becomes visible. If a shadow effort goes viral while our UX is rough, we lose the narrative.

## Three things to do in the next 90 days
1. Ship a UX overhaul focused on the top-3 most-used flows. Bring in a designer for 4 weeks. Specific success: 80% of new users can complete the first task without asking for help (current = ~30%).
2. Land the "platform as default" pitch at the next tech all-hands. Get a verbal commitment from leadership that new AI tooling work goes through us first.
3. Identify the 5 teams most likely to adopt next quarter; do a personalised 30-min pitch + onboarding-week commitment to each. Convert at least 3.