Contact options
Email is the most direct way to discuss a workflow, integration, or software project. Write to moez.zhioua@gmail.com. You can also book an initial conversation through my Cal.com scheduling page or review my current professional history on LinkedIn and Upwork before getting in touch.
This site does not use a contact form. Sending an email opens your own email provider, and scheduling opens Cal.com. Those services apply their own privacy terms. Do not send passwords, production API keys, private customer exports, or regulated data in an introductory message.
What to include
A useful first message names one process and the result your team needs. Include the systems involved, who performs the work today, where the authoritative data lives, the volume or frequency, and any deadline or access constraint. If something currently fails, describe the exception and how staff recover from it. A real example is more useful than a broad request to automate the whole business.
- The trigger that starts the process
- The tools, APIs, files, or databases involved
- The person who approves rules and handles exceptions
- The required output and how it will be accepted
- Security, privacy, hosting, or audit constraints
Scope, price, and next steps
The introductory call is used to decide whether there is a practical fit. It is not permission to access a production system. When the workflow is understood, I provide a written proposal that records assumptions, deliverables, exclusions, acceptance checks, timing, and a project price. Access approvals, paid platform accounts, and third-party subscriptions are identified before implementation rather than hidden inside a generic estimate.
If the workflow is not stable enough to automate, I will recommend a process or data audit first. If another specialist or product is a better fit, the useful outcome may be a clear no rather than a forced project. You can review the current service catalog, project examples, and working FAQ before contacting me.