I don't know what to ask for — is that a problem?

Question

VX-N · Accepted Answer

No — that is the normal starting point. Problems do not arrive labeled by department, so you don't need to diagnose your own stack before the first call. Describe the mess and VX-N will tell you what it actually needs. Operators almost never arrive saying 'I need a CRM integration.' They arrive saying leads go quiet, quotes take three days, two systems disagree about the same customer, or one person is the only one who knows how anything works. Those are symptoms, and symptoms are the right input. Translating symptoms into a technical scope is the first real piece of work in any engagement — it should never be homework the client does alone before being allowed to talk to someone. There is a quiet danger in self-diagnosing: a vendor who takes your self-diagnosis at face value will happily build it. If you walk in asking for a new CRM, most firms will sell you a new CRM — even when the actual fault was a process nobody wrote down, which the new platform will faithfully reproduce. A builder who accepts your prescription without examining the symptoms is not saving you time; they are transferring the diagnostic risk to you. On the first call, describe how work actually moves — where things get re-typed, where they wait, what breaks and who fixes it. Within 24 hours that becomes a written plan naming the real problem and the smallest system that fixes it, in plain language. The call and the plan cost nothing, so the diagnosis is on paper before any money or commitment enters the conversation. Sometimes the plan's honest conclusion is that the fix is small enough to do yourself; that is a legitimate outcome, and it is stated plainly when true.