MOUSANew-client onboarding that does not miss a folder
A consulting team was setting up Slack, ClickUp, and Drive by hand. Intake now creates the channel, workspace, and deliverables tree every time.
Repeatable onboarding, fewer missed stepsAutomation studio
Zapier and Make solutions that actually run.
I connect the tools you already use — CRM, forms, billing, Slack, Airtable — then test until the flow is clean. You talk to the person who builds it, not an account manager.
Zapier Expert certified
Make Foundation certified
Independent since 2019
2019First automation clients
2 platformsZapier and Make, in production
20+Public systems in the portfolio
~1 hrTypical first reply
Services
What I build
Same shape as the agencies — strategy, delivery, care — sized for a specialist who still opens the scenario.
Zapier
Multi-step Zaps that stay cheap and readable
Paths, filters, formatters, webhooks, and Tables. Fast when the stack already lives in Zapier.
Zapier work →Make.com
Visual scenarios for the messy middle
Routers, aggregators, iterators, error handlers. Better when the flow is branching or high-volume.
Make work →Rescue
Broken Zaps and scenarios, put back on their feet
Empty bundles, duplicate contacts, silent filters, Copilot leftovers. Diagnose, patch, document.
Fix a flow →AI in the workflow
GPT and Claude inside the tools you already run
Classify, draft, enrich, generate PDFs or audio — with a person still approving anything sensitive.
AI automations →CRM & revenue
Leads, deals, and invoices that match
HubSpot, GoHighLevel, Airtable, Stripe, Xero, QuickBooks — one source of truth, not three.
CRM systems →Care
Keep it running after go-live
Monitoring, small changes, and a short official route when something breaks. No build-and-leave.
Ongoing support →Selected work
Shipped in production
Store contacts that actually land in the CRM
Rebuilt a failing scenario so Shopify customers sync into GoHighLevel with the fields the sales team needs — not empty bundles.
Contact sync restoredRSVPs that show up as HubSpot contacts
Event registrations were stalling in Zapier. Mapping and auth were repaired so every RSVP becomes a usable CRM record.
RSVP pipeline unblockedPrice IDs, invoices, and the catalog in agreement
Stripe price IDs, Airtable, and Xero were drifting. One Make path keeps catalog and invoices aligned after CRM changes.
Billing records that match the catalogFrom Upwork
What a client wrote after a Zapier rescue
★★★★★ 5.0
Mohamed is a WIZARD! He made all my ideas come to life with automating SMS texts to our clients through Zapier. He solved all problems and made everything amazing. Worked extremely fast and efficiently
Upwork client · Field services · booking SMS and job folders · See profile
Blog
Notes from Zaps that had to run
Rescue · Make
Why your Make scenario returns empty bundles
History is green. The next module still gets []. Search, filter, or iterator — not a dead webhook.
Rescue · Zapier
Zapier Copilot built it. The second booking still fails.
First test looks perfect. Live traffic duplicates contacts or skips the Path.
Buy · Shopify
Zapier vs Make for a Shopify store
Stay on Zapier for simple order → CRM. Move to Make when you iterate line items or the task bill hurts.
How it works
Share the stack. I map the flow.
01
Goal
You send tools, a sample record, and what “done” looks like. I reply with a plan and a timeline — not a 40-page deck.
02
Map
Trigger, routers, fields, error paths. We agree the happy path and the failure path before anything is built.
03
Build
I build and test on your real data until it runs clean. Duplicates, empty outputs, and silent filters get handled here.
04
Handoff
Clear notes, ownership of connections, and optional care after go-live. Your team can run it without me in the room.
Why a specialist
Agencies ship volume. I ship the scenario.
GrowwStacks, Blue Precision, and Makeitfuture are strong models: proof, process, and a call at the end. I keep that shape — and drop the layer between you and the builder.
You get Zapier and Make in one person, including rescue work on Copilot-generated Zaps and scenarios that “look fine” and still drop records. If the honest answer is “don’t automate this,” you hear it.
Good fit
Operators, agencies, and product teams who already have tools and need them to talk — or need a broken flow diagnosed this week.
Not a fit
Enterprise RFPs that need a 40-person bench, or “build us a custom SaaS from zero.” I stay in automation, integration, and AI-in-the-workflow.
FAQ
Straight answers
Both. If the stack is already in Zapier, we stay there unless cost or branching says otherwise. If you need routers, iterators, and cheaper volume, Make is usually the better home. I also migrate Zapier → Make when the bill is the problem.
A focused Zap or scenario is often days, not months. Messy CRM history, custom APIs, or several systems in one flow take longer. You get a timeline after I see the tools and a sample record.
Yes. A large part of the work is rescue: Copilot Zaps, silent filters, empty Make bundles, duplicates, and mappings that looked right in the editor. I patch, then write down what was wrong so it does not return.
Fixed scope for a defined flow, or hours if the system is still being discovered. After go-live, optional monthly care for monitoring and small changes. I quote after the first call — no surprise retainers.
Egypt, working in English with clients in the US, UK, and EU. Async by default; calls when the mapping needs a whiteboard.
Start
Tell me the stack and what “done” looks like.
I’ll reply with a plan and a timeline.