Contact

Start in writing so the task, available materials, and expected result are recorded from the first exchange. A finished specification is not required — a clear description of the situation and a useful outcome is enough.

What to include

• What the system is and who uses it
• What is blocked or holding development back
• The result you need
• Materials that are already available
• Known stack, versions, and important integrations
• Timing constraints and how budget is approved

If a fact is unknown, say so. Do not replace it with an assumption.

Contact

Email: info@orilix.dev

After the first review we can agree a call, video meeting, or another working channel if needed.