Independent developer · Lebanon & remote GCC delivery
Connect enquiries, documents and your business tools.
I design and build workflows that route enquiries, prepare documents for review and keep business systems in sync. Work directly with an independent developer in Lebanon, serving teams remotely across the UAE, Saudi Arabia and Qatar.
Discuss your projectShare a short outline. I’ll review the fit, discuss your tools and requirements, then propose a paid scope before implementation.
See my independent n8n workflow-analysis project →Start with the business problem.
Start with one repeatable process and its exceptions. We can map where information arrives, who checks it, which systems need an update and what happens when an input is missing. Rules handle predictable steps; AI is considered only where classification, extraction or language understanding adds value.
What we can scope
- Enquiry intake, assignment and CRM updates
- Booking requests, confirmations and human handoff
- Document intake, field extraction and review queues
- Scheduled reporting and synchronization between systems
What the delivery can include
- A process map with trigger, inputs, outputs and an accountable owner
- Scoped connections to tools with suitable APIs and authorized access
- Validation, exception handling and agreed approval points
- Acceptance checks, handover documentation and an operating-cost discussion
Illustrative workflow · not a client case study
Example: an enquiry reaches the right person
For a team handling enquiries across an inbox and a business system, start with routing and ownership. A model is optional; clear rules may be enough.
- Receive an enquiry
- Validate required details and check for duplicates
- Assign an owner using agreed rules
- Update the connected system
- Flag failed or unassigned handoffs for review
What needs engineering: Before release, test missing details, duplicate submissions and unavailable APIs. Agree who reviews failures and how a retry avoids creating a second record.
If requests need interpretation rather than fixed routing rules, scope a bounded model step with human review. When an AI agent may help →
What shapes the project quote?
- The number of systems, API access and authentication requirements
- Workflow branches, exceptions, approvals and duplicate handling
- Monitoring, hosting and the agreed handover or support scope
Scope and boundaries
The scope covers the named process and integrations. Platform subscriptions, usage charges, ongoing support and additional workflows need an explicit agreement. Automation does not fix missing process ownership or authorize access to a system.
Is this a useful first project?
A good first project has a process owner, repeated work and a way to check whether the output is correct. A broken process or an existing product that already solves the problem may need a simpler fix before a custom workflow.
Relevant engineering work
The portfolio includes an n8n workflow-analysis tool and personal agent systems. They demonstrate engineering approaches; they are not presented as client savings or a promise of a particular business result.
Read the n8n workflow analysis project walkthrough →Explore the project portfolio →Before we start
- Do we need to replace our current software?
- Not necessarily. The starting point is the tools you already use, their API access and the process that needs improvement. An integration may be enough; any replacement should have a specific reason.
- What costs continue after delivery?
- Hosting, automation-platform, messaging and AI usage can create ongoing costs. The relevant services, account ownership and support scope should be agreed alongside the build quote.
- Can someone approve important actions?
- Yes. Approval points, exception queues and handoff can be included in the workflow scope, especially before sending messages or changing business records.
- Do we need AI or n8n for this workflow?
- Neither is automatic. Stable rules and a small API integration may be sufficient. n8n can be considered where its supported nodes, hosting and operating model fit; a model step is useful only where interpretation or extraction needs it. The independent n8n project demonstrates workflow analysis, not a promise that every integration is supported.
- What happens if an integration fails or runs twice?
- The scope should define timeouts, bounded retries, duplicate detection and an exception queue with an owner. Test failed and repeated deliveries before release; a successful acknowledgement alone does not prove the work reached the right system or person.
- What should we share for a workflow automation quote?
- Describe one process, its current tools, approximate volume, exceptions and approval owner. Share anonymized examples first, without credentials or customer records. API access, platform fees, hosting and support responsibilities help determine a practical paid scope.
Bring a workflow or application brief.
Share your company, current tools and the work you want to improve. Smaller projects are welcome. We can discuss fit, scope, integrations and a quote before work starts.
Describe your project