// Straight answer
Short answer
Build it yourself if the flow is simple, such as notifying staff of a new enquiry or adding a row to a sheet. Hire someone when it touches the WhatsApp Business API, Arabic understanding, customer records that must stay correct, or anything that needs ongoing maintenance. Many people do both: start DIY, hand over what grows.
Answered by Tarek Abou Rjeily, AI consultant & builder in Beirut, for businesses in Lebanon and the Gulf.
Tools like n8n and Zapier let a non-developer connect apps with visual workflows, and they are a good fit for simple, low-risk flows. If a mistake costs you a missed notification and not a lost customer, build it yourself. You will learn what you actually need, which makes any later hiring cheaper and clearer.
Four areas turn a weekend project into a liability. The first is the WhatsApp Business API itself. Both tools offer WhatsApp connections, but getting the number connected, templates approved, webhooks reliable and message categories right is the part that trips people up, and Meta's rules and prices change.
The second is language. Understanding Arabic, Lebanese dialect and Arabizi in free-text messages, and replying sensibly, takes testing on real chats. The third is data integrity: an automation that creates duplicate contacts, overwrites a field or loses a voice note damages your records quietly. The fourth is maintenance. Tokens expire, apps change their interfaces, and a flow that worked in March can stop in October without a visible error.
Ask four questions. What is the cost if this fails silently for a week? Does it send messages to customers on its own? Does it write to the record you rely on? Who will fix it at 9 pm on a Friday? If the answers are cheap, no, no and me, build it yourself.
If the answer to any of those is expensive, yes or nobody, hire help for that part. You do not have to hand over everything. A developer can set up the API connection and the handover logic, and you can keep editing the simple flows around it.
If you hire, ask for things that protect you: a written scope, a test run on your real messages, logs you can read, a handover guide, export of your data, and a named person who fixes problems. Tarek Abou Rjeily, an AI consultant and builder in Beirut, works in fixed-scope packages and uses n8n himself where it fits, including on a WhatsApp and email lifecycle automation for a Lebanese clinic, so he has no reason to push a custom build when a visual tool is enough.
If you are unsure which side you are on, the short version is this. Build the first simple flow yourself. If it grows into customer messages, records or Arabic, stop and get it properly built.
Both offer WhatsApp-related connections, but what each supports changes, so read their current documentation. You still need a Meta business portfolio, a number and approved templates for business-initiated messages. The tool is the easy part.
It removes a subscription but adds a server to run, update, back up and secure. That is real work. Self-hosting suits someone comfortable with servers, and is a poor idea if nobody will look after it.
Yes, and it often works best. Ask a developer to build and document the API connection and data handling, then keep the simple flows yourself. Agree who owns the accounts and credentials at the start.
Anything that sends sensitive information, handles payments or health details, or changes customer records without a check. Those need testing, logging and a review step, which is easier with an experienced builder.
Yes. The tools and the Meta rules are the same. Gulf businesses often add Arabic and English handling and data rules from their own country, which pushes more of the work to the hire side.
Third-party facts can change. These primary sources were checked on the page's update date.
Send the question on WhatsApp and I'll tell you honestly whether it needs building, buying, or fixing by hand.
Ask on WhatsApp →