Before meeting an IT consultant, prepare a short summary of what your business wants to accomplish, where technology gets in the way, and what constraints a solution must respect. You do not need a technical specification. Aim to give the consultant enough context to discuss options without assuming that new software or automation is necessarily the answer.
Start with business goals, not a software wish list
Write down one to three outcomes you want to improve. Instead of leading with “we need a new application,” describe the underlying need, such as reducing duplicate data entry or making order status easier to track. Explain how you would judge progress, and distinguish essential outcomes from optional improvements.
Document recurring technology problems
Choose a few concrete examples rather than trying to inventory every frustration. For each problem, note who encounters it, when it happens, and what work stops or becomes harder. If you do not know its frequency or impact, mark that information as unknown rather than guessing.
- What task was someone trying to complete?
- What went wrong, and which system was involved?
- What workaround is used today?
- Is there a redacted screenshot or sample that illustrates the issue?
Map one or two important workflows
Describe a process from its starting event to its final result—for example, from receiving a customer request to completing the work. List the people, tools, handoffs, and approvals involved. Include exceptions: missing information, rejected requests, and tasks that require judgment.
For a possible automation project, identify which steps follow clear rules and which should remain subject to human review. Note what should happen if an automated step produces an unexpected result.
List current systems and data dependencies
Prepare a simple inventory of the applications, spreadsheets, databases, and outside services used in those workflows. Record what each one does, who manages it, and whether information moves between systems manually or through an existing connection.
Flag contractual, privacy, security, or retention requirements you already know about. Do not include passwords, access keys, or unredacted sensitive records in meeting materials. Ask what information is needed and how it should be shared before providing access.
Identify users, decision-makers, and owners
Name the person responsible for the business outcome, the people who perform the work, and whoever approves spending. Identify who can answer technical questions and who would maintain a future solution. If those responsibilities are undecided, bring them forward as open questions.
Set budget and timeline boundaries
Bring a working budget range, even if it is provisional. Clarify whether it must cover discovery, implementation, ongoing services, and support. Separate firm deadlines from preferences, explain what drives each deadline, and note how much staff time is available for interviews, testing, and training.
Leave with a defined next step
Bring your summary, system list, workflow notes, and a few safe examples. Ask which assumptions need validation, whether existing tools could address the problem, and what further discovery would involve. Before ending the conversation, agree on the next deliverable, who owns it, and which questions remain unanswered.
Editorial status: Unpublished draft requiring human factual and editorial review. This checklist provides general preparation guidance, not an assessment of any specific business or provider.