Operations
January 2025
·
6 min read

"We Do Not Have the IT Resources": What Implementation Really Requires

The IT Resource Concern

"We don't have IT resources for AI implementation" is a common objection. Understanding actual IT requirements versus perceived needs prevents this from blocking valuable automation.

Reality: Implementation requires 5-10 hours IT support total, not dedicated staff.

What IT Actually Does

Activity 1: API Credentials (1-2 hours)

What's needed:

  • Create service account in ERP
  • Generate API credentials (key/secret or OAuth)
  • Provide credentials to implementation partner
  • Verify test environment access

IT skill level: Junior to mid-level administrator

When needed: Week 1 of implementation

Complexity: Low. Standard procedure for most ERPs.

Activity 2: Security Review (1-2 hours)

What's needed:

  • Review integration approach
  • Approve external system access
  • Confirm data privacy compliance
  • Sign off on security measures

IT skill level: IT manager or security lead

When needed: Week 1, one-time approval

Complexity: Low to moderate depending on security policies

Activity 3: Troubleshooting Support (2-4 hours total)

What's needed:

  • Investigate occasional connectivity issues
  • Verify firewall rules if needed
  • Check service account permissions
  • Assist with production deployment

IT skill level: Mid-level administrator

When needed: Sporadically during weeks 2-12

Complexity: Low. Standard troubleshooting.

Activity 4: Production Deployment Support (1-2 hours)

What's needed:

  • Provide production credentials
  • Verify production connectivity
  • Confirm monitoring alerts configured
  • Sign off on go-live

IT skill level: IT manager approval, admin execution

When needed: Week 8-10

Complexity: Low

Total IT Time Required

Discovery phase: 1 hour (explain current systems, data access)

Implementation phase: 2-3 hours (credentials, security review)

Testing phase: 1-2 hours (troubleshooting, verification)

Deployment phase: 1-2 hours (production setup)

Post-deployment: 1 hour (occasional support)

Total: 6-9 hours over 12 weeks

Average: 30-45 minutes per week

What IT Does NOT Do

NOT Required: Custom Development

Responsibility: Implementation partner handles all development

IT role: None (unless custom ERP requires API development)

NOT Required: Project Management

Responsibility: Business team (AR, AP, Controller) leads project

IT role: Supporting participant only

NOT Required: AI Configuration

Responsibility: Implementation partner configures AI platform

IT role: None

NOT Required: Ongoing Management

Responsibility: Business team monitors and refines

IT role: Minimal (occasional technical support only)

IT Resource Availability Scenarios

Scenario 1: Dedicated IT Team

Availability: IT manager + 2-3 administrators

Implementation impact: Minimal. 1-2 hours total from IT manager, 5-7 hours from administrator.

Timeline: No delay. IT can provide support when needed.

Recommendation: Standard implementation approach

Scenario 2: Outsourced IT

Availability: MSP or outsourced IT provider on retainer

Implementation impact: Low. Request 8-10 hours IT support in implementation scope.

Timeline: Coordinate timing with MSP. May add 1-2 weeks if MSP scheduling delays.

Recommendation: Notify MSP early, include in their monthly hours

Additional cost: $0 if within retainer, $800-$1,500 if billed separately

Scenario 3: Part-Time IT Person

Availability: IT person 2-3 days weekly or consultant on call

Implementation impact: Moderate. Need to coordinate availability.

Timeline: May add 2-3 weeks to accommodate IT schedule

Recommendation: Plan IT touchpoints in advance, batch requests

Scenario 4: No Dedicated IT

Availability: Controller or operations manager handles basic IT, consultant for complex needs

Implementation impact: Higher. May need outside IT consultant for specific tasks.

Timeline: Add 2-4 weeks for consultant engagement

Recommendation: Engage IT consultant for implementation support

Additional cost: $1,500-$3,000 for consultant time

Managed Service Alternatives

Implementation Partner Handles IT Coordination

Approach: Partner coordinates directly with your IT provider (internal or external)

Your role: Introduction and approval only

Benefit: Minimal business team involvement in IT coordination

Cost: Included in standard implementation

Fully Managed Implementation

Approach: Partner handles all technical aspects including IT coordination

Your role: Business process definition only

Benefit: Zero IT coordination burden

Cost: Standard implementation pricing

Suitable for: Companies with very limited IT or IT resistance

Common IT Concerns and Responses

Concern 1: "We don't allow external system access"

Response: AI platforms don't require direct ERP access. API calls go through standard authentication. Same security model as mobile apps or other integrations.

Solution: Security review confirms standard integration approach

Concern 2: "We're too busy for new projects"

Response: Total IT time is 6-9 hours over 12 weeks (average 30-45 minutes weekly). Can be scheduled around other priorities.

Solution: Batch IT requests, provide advance notice, schedule at IT convenience

Concern 3: "We don't understand AI technology"

Response: IT doesn't need AI expertise. Implementation partner handles AI configuration. IT provides standard ERP access only.

Solution: Clear scope documentation showing IT tasks are standard ERP administration

Concern 4: "What if something breaks?"

Response: AI accesses ERP read-only mostly (writes notes/tasks only). Cannot modify customer data, transactions, or configurations. ERP integrity unaffected.

Solution: Technical documentation showing safe integration approach

IT Liaison Role

Recommended Approach

Identify one IT liaison: Person who coordinates IT support during implementation

Time commitment: 1-2 hours monthly for 3 months

Responsibilities:

  • Attend kickoff meeting (1 hour)
  • Provide API credentials when ready
  • Troubleshoot connectivity if issues arise
  • Approve production deployment

Suitable person:

  • ERP administrator
  • IT manager
  • MSP account manager
  • Technology-comfortable operations person

NOT required:

  • Deep AI knowledge
  • Programming skills
  • Dedicated project time

When IT Effort Increases

Scenario: Custom ERP with No API

Additional IT work:

  • API development: 40-80 hours
  • Or database integration setup: 20-40 hours

Timeline impact: +4-8 weeks

Cost impact: +$15,000-$40,000

Alternative: ERP upgrade or standardize before AI implementation

Scenario: Highly Restricted Security Environment

Additional IT work:

  • Extended security reviews: 5-10 hours
  • Custom security configuration: 5-10 hours
  • Penetration testing: 10-20 hours

Timeline impact: +2-4 weeks

Cost impact: +$5,000-$15,000

Industries affected: Healthcare, financial services, government contractors

The Reality

AI implementation requires 5-10 hours total IT support over 12 weeks. Average 30-45 minutes weekly.

IT provides: API credentials, security approval, occasional troubleshooting.

IT does NOT: Custom development, project management, AI configuration, ongoing management.

Limited IT availability adds 2-4 weeks timeline but doesn't prevent implementation. Outsourced IT or consultant alternatives available.

"We don't have IT resources" typically means "We don't understand minimal IT requirements." Actual needs are modest and manageable.

ABOUT THE AUTHOR

This content is published by ERP AI Agent.

ON THIS PAGE

Related Articles

See All →