One engineer, one public method
Webotic has no org chart. Every account is run by the same person — the one who wrote the tracking code, read the Cloud Run logs and debugged the Purchase event at 2 a.m. No junior in between, no commercial layer between you and the Ads console.
Marouane Mohachtou
Founder & media engineerFull-stack engineer by training, ten years writing production code before crossing over to the acquisition side. It wasn't a career pivot, it was a reaction: too many campaigns running next to me were broken at the root — misplaced pixel, events deduplicated backwards, conversions credited to the wrong channel. Nobody was looking under the hood.
Since 2021 I've been running Webotic as a studio: Google Ads, Meta, TikTok, programmatic, and above all the plumbing that makes the numbers actually mean something. GTM Server-Side hosted on Cloud Run, Meta CAPI in production, BigQuery for the truth, Looker for the read. Tracking is not an option added at the end of a project — it's the foundation everything else sits on.
What makes the difference today: I can read a network tab, write a Cloud Function, calibrate a target CPA and negotiate a commercial brief in the same day. Bridges between engineering and acquisition are rare in Morocco. Webotic exists because both worlds speak better when one person inhabits both.
The agency model is broken for performance
A classic agency sells billable hours. It stacks juniors, invoices their learning curve and calls it a service. On performance work, that model produces impressive reporting and mediocre campaigns — because the person who understands the account is never the one touching it.
Webotic does the opposite: one engineer, few parallel clients, direct access to the accounts and the code. You're not buying an account manager who relays your questions to a media buyer who relays them to a tech lead. You talk to the person who executes.
The counterweight is documentation. Everything I do on an account is versioned, explained, reproducible. If tomorrow you bring it in-house, you don't inherit a black box — you inherit a git repo, a Looker dashboard and a written method.
- 01
Public methodology
Playbooks, benchmarks and case studies are written openly on the site. No trade secrets — the value is in execution, not in hoarding information.
- 02
One person in charge
The account is run end-to-end by the same operator. No hand-off, no billable internal kick-off, no junior learning on your budget.
- 03
Tracking first
Before the first campaign, the server-side GTM is installed, events are validated on the server and BigQuery is wired up. A campaign without clean tracking is a poll, not an investment.
- 04
ROI measured, not reported
Dashboards show attributable revenue, not impressions. If spend doesn't translate into pipeline or traceable revenue, it stops.