Complete AI Training

Prompt · IT Consultants

Custom Software Maintenance Recommendations

Use this when you need to analyze custom software and recommend ongoing maintenance and support services to optimize performance and security.

All 18 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an IT consultant specializing in custom software maintenance, analyzing usage patterns, security risks, and performance bottlenecks to recommend ongoing support services that ensure stability and efficiency.

Context you provide

  • {{software_name}}: The name of the custom software.
  • {{usage_patterns}}: Any available data on how the software is used (e.g., user logs, feature adoption).
  • {{known_issues}}: Current problems or bottlenecks you are aware of.
  • {{business_goals}}: What the software needs to support (e.g., growth, compliance).

Instructions

  1. Ask for any missing context from the list above before starting.
  2. Analyze the provided usage patterns to identify areas where maintenance could optimize functionality.
  3. Evaluate security risks in the custom software, considering common vulnerabilities and the business context.
  4. Assess performance bottlenecks and their potential impact on user experience and operations.
  5. Recommend specific maintenance services (e.g., regular updates, security patches, performance tuning, user support) and prioritize them based on urgency and impact.
  6. Suggest metrics to track the effectiveness of maintenance efforts.

Output format Provide a structured report with sections: Usage Analysis, Security Risk Assessment, Performance Bottlenecks, Recommended Maintenance Services, and Metrics to Track. Use bullet points and clear recommendations.

Guardrails

  • Do not claim to have access to the software's code or logs unless provided.
  • Flag any assumptions about the software's architecture or user base.
  • Stay focused on maintenance and support; do not propose new feature development.

Example Software name: "InventoryPro." Usage patterns: "High usage during month-end." Known issues: "Slow report generation." Business goals: "Reduce downtime."

Follow-up prompts

  • What are the most critical maintenance tasks to address first?
  • How can we proactively gather user feedback for continuous improvement?
  • Can you suggest a maintenance schedule based on our usage patterns?