Legacy Stack AI Readiness Checklist

of 15 Yes answers

Section 1 — Data Accessibility

1. Can you pull a list of open work orders, part requests, or service tickets from your ERP without running a custom report or asking IT?

2. Is your key operational data (inventory, equipment history, customer records) stored primarily in one or two systems — not scattered across spreadsheets, shared drives, or email threads?

3. Do your records use consistent identifiers (part numbers, asset IDs, customer codes) across systems — without significant duplication or naming conflicts?

Section 2 — System & API Availability

4. Does your ERP or field service platform have an accessible API, ODBC connection, or data export that your IT team (or a vendor) can connect to without a major upgrade?

5. Are your core systems actively maintained — i.e., still receiving vendor support or under a managed services agreement?

6. Can a new software connection be added to your environment without requiring a multi-month IT security review or executive approval for each integration?

Section 3 — Workflow Documentation

7. Can you describe, in plain steps, how a specific high-value workflow (e.g., parts triage, work order dispatch, warranty lookup) is handled today — including who does each step?

8. Do you know which 2–3 workflows consume the most manual hours per week for your team?

9. Are your standard operating procedures (SOPs) written down and reasonably up to date — or do key processes live primarily in people's heads?

Section 4 — Change Control & IT Environment

10. Does your organization have a defined process for deploying and validating new software tools — even lightweight ones?

11. Is there an IT contact (internal or external) who can support new integrations without a months-long queue?

Section 5 — Team Readiness

12. Is there at least one operations leader willing to own a new tool's rollout and hold the team accountable for using it?

13. Have your frontline staff (techs, dispatchers, coordinators) used any new software tool in the past two years — even something simple like a new scheduling app or mobile checklist?

Section 6 — Compliance & Risk

14. Do you have a general sense of any regulatory or data handling requirements that would govern what an AI tool can access or store (e.g., ITAR, ISO, customer data restrictions)?

15. Would you be comfortable with an outside engineering team accessing a read-only connection to your ERP data under a signed NDA and SOC 2-compliant environment?

✅ 10–15 Yes — Ready for a Pilot Implementation

Your environment has the fundamentals in place. You have accessible data, identifiable workflows, and a team that can absorb a new tool. Start with an AI Discovery Sprint to confirm your top opportunity and lock in a measurable success metric — then move straight into a Pilot Implementation.

Book an AI Discovery Sprint →

🔵 6–9 Yes — Start with an AI Discovery Sprint

You have real opportunities, but there are gaps that need to be mapped before building. Data may be fragmented, workflows may be undocumented, or your environment needs some prep work. The AI Discovery Sprint is designed exactly for this stage.

Book an AI Discovery Sprint →

🟡 0–5 Yes — Foundational Prep Needed

You're earlier in the journey than an AI build requires. That's not a problem — it just means the right move is foundational work first. Rushing to build on a shaky foundation is how pilots fail. Contact us for a free 30-minute conversation — we'll tell you honestly what to prioritize.

Get a free 30-min consult →