You can begin with a recurring difficulty rather than a complete specification. We can help examine the task and identify the question that needs answering before implementation is proposed.
Choose a useful planning output
A Saudi-connected project might need a service journey map, an account dependency review or a small prototype showing one customer correction. Agree the commissioned output and its limits before work starts.
Planning should distinguish approved facts from assumptions. Provider readiness, Arabic review, commercial authority, privacy and accounting may each need a different owner. A developer should not be left to infer those decisions from a sample screen.
Define the review
Identify who can assess the result and what ordinary or changed case would demonstrate it. A prototype helps explore a decision; it must not be described as a completed live system.
Work is delivered remotely from the United States, normally with English technical communication. Meeting windows, language production, qualified review, timing and price follow the agreed scope and confirmed dependencies.
Read about review windows and provider ownership, or try the service-stage resource. Describe the task that needs a clearer next step, with private material removed.