What does the system do?
Who uses it, what business workflow it supports, and what must keep working.
START A DIAGNOSTIC
Send the system context first.
You do not need a polished requirements document. A concise description of the current system and what is going wrong is enough to decide whether this is a useful fit.
What is going wrong?
Failures, slowdowns, manual recovery, unreliable integrations, operational risk, or uncertainty.
What is the stack?
Languages, frameworks, databases, hosting, external providers, and deployment environment.
What have you already tried?
Include previous fixes, logs, hypotheses, constraints, and anything the team cannot safely change.
SYSTEM CONTEXT
Tell me what is happening.
This form is designed for existing-system, integration, backend, SQL, and production reliability problems. Most people can complete it in a few minutes.
Typical first engagement: US$300–800
The first step is a scoped diagnostic, not a sales call. I will confirm whether the problem fits the engagement before proposing any implementation work.