6,385
messages delivered out of one clinic's system — and not one failed delivery in the log
COUNTED IN THE DATABASE
Two things I do. Pick the one you came for — the page rewrites itself, right down to the demo below.
I connect the systems your business already runs on — and make them behave like one product.
I build fast websites that rank — and keep ranking after launch.
Most businesses don't have a code problem. They have six tools, three spreadsheets, and a person copying data between them at 11pm. I design the layer that removes that person — login, data, workflows, alerts — and then I keep it running.
Marketing sites and content platforms built on Astro. This page is the sample: 100 across performance, accessibility, best practices and SEO — measured, not claimed.
Free, no pitch. If I'm not the right person, I'll say so on the call.
Don't take my word for it — run one of my systems Don't take my word for it — watch a page load
A real booking, moving through a system I built. Press the second button too — that one is the reason a client can stop checking whether it worked. The same page, built two ways. The difference is what a visitor sees while they wait — and what a search engine sees at all.
CLINIKO → GOHIGHLEVELThe second button is the one that matters. Most reminder systems fail exactly there — the appointment moves and yesterday’s promise still goes out. In this system that has been caught 1,816 times.
What that has been worth What the sites actually score
Measured, not claimed1,816
reminders retired before they could send, because the appointment had already moved
WRONG MESSAGES PREVENTED
5 brands
restaurant storefronts running on one codebase, one deploy, five real kitchens
GROWKU · MULTI-TENANT
~80%
of one team's manual admin removed by putting five separate tools on one database
GROWKU · REPORTED BY THE TEAM
100
Lighthouse performance — on this page. Not a screenshot of someone else’s site.
MEASURED ON THIS BUILD
100
SEO — structure, metadata and crawlability, which is what AI search reads too
MEASURED ON THIS BUILD
100
accessibility — the same discipline that keeps the SEO score standing
MEASURED ON THIS BUILD
0 KB
of framework JavaScript. The interactive parts here are hand-written and tiny.
ASTRO · ISLANDS ONLY WHERE EARNED
What actually changes
The clinic you just traced, in plain terms — before I touched it, and after. The page you just watched load, in plain terms — the site you have, and the site after.
CLINIKO → GOHIGHLEVELBefore
Reception was the integration
A patient books in Cliniko. Someone then opens the CRM and types the same details in again, so reminders and follow-ups can go out.
- Every patient existed twice, kept in step by hand
- "Where is this patient up to?" meant opening two systems
- Two Cliniko accounts, so the same person could exist twice on the clinical side alone
- Reminders ran through a third-party tool nobody could audit
After
The booking is the trigger
A scheduled run reads both Cliniko accounts, resolves the patient to one timeline by email, and drives the CRM from what actually happened.
- Bookings, arrivals, no-shows, notes and forms arrive on their own
- 67 messaging rules live in a table the client owns, with a log of every send
- Plans are recalculated every run, so a moved appointment cannot get yesterday’s reminder
- Staff work in one system; the clinical record is never written to
6,385 SENT · 0 FAILED · 1,816 STOPPED
The site you have
Slow, invisible, and needs a developer
Heavy JavaScript, everything rendered in the browser, images the size of the page itself. It looks fine on the developer's laptop and loses visitors on a phone.
- Slow first paint — visitors leave before it renders
- Content invisible until scripts run, so crawlers and AI assistants see nothing
- No structured data, so nothing gets quoted or featured
- Every text change is a ticket for a developer
The site after
Fast, readable, editable
Static HTML first, interactive parts loaded only where they are actually needed, images sized and modern-format, structured data in place. The score is a build gate, not a launch-day screenshot.
- 100 performance, 100 accessibility, 100 best practices, 100 SEO
- Content readable with JavaScript switched off, so AI search can quote it
- Editors change content without a deploy
- Speed that survives the fortieth page the marketing team adds
100 / 100 / 100 / 100 LIGHTHOUSE
The shape of what I build And what sits behind the website
Every box is something I have actually built. Pick one. A fast site in front of a broken back office only makes the mess visible faster. Pick any box.
InteractiveA system I'd build for you
← pick a box
Three systems I manage end to end
Architecture, build, and the part nobody advertises — keeping them alive afterwards.
MY OWN CLIENTHEALTHCARE
Cliniko → GoHighLevel sync
The system traced at the top of this page
Clinic bookings become CRM contacts, appointments and message sequences on their own — matched on email across two Cliniko accounts so a returning patient is never a new one, and driven by 67 rules the client owns rather than a product they rent.
6,385 MESSAGES, NONE FAILED
EMPLOYED · GROWKULED THE TEAM
Creator platform with AI inside
Supabase, n8n, GoHighLevel, Telegram, OpenAI
Five tools behaving as one product. The first fix was identity — one account per person — because automation built on top of four unlinked records does the right thing to the wrong person, at scale.
~80% OF THE MANUAL WORK GONE
EMPLOYED · GROWKU5 TENANTS
Restaurant ordering, five brands
One codebase, five storefronts, real kitchens
Ordinary online shops finish at payment. This one isn't finished until a ticket prints in a kitchen — so every order is checked against five integrity rules before payment is taken, and anything suspect reaches a manager on Slack with the order attached.
5 BRANDS · ONE CODEBASE
What working with me is like
The part a diagram can't show, told through things that actually happened.
-
I lead, not just build
At Growku I lead the engineering team — splitting the work, reviewing it, and being the one accountable when it ships.
-
I can run the client relationship
TalentStream went from a first phone call to a delivered platform with no project manager in between. I scoped it, priced it and shipped it.
-
I work with designers, not around them
At Yalla Cooperative I built the shared component system with the design team, so the same button stopped being renegotiated every sprint.
-
I explain trade-offs without jargon
Across six client projects in Amsterdam, most of the job was making non-technical stakeholders comfortable with a technical decision.
-
I hand over things people can use
At uPet I built automations that let marketing run their own campaigns without an engineer. Fewer tickets for me, faster for them.
-
I'm reachable and I write things down
Documentation and a diagram come with the work, in Arabic or English, so the next person is not dependent on a call with me.
Stack
Used on production systems with real customers on them.
- Websites
- Astro, Next.js, React, TypeScript, Tailwind — SEO and performance as a build gate
- Interfaces
- React, Material UI, design systems on Bit.dev
- Services
- Node.js, NestJS, Express, Python, FastAPI
- Data
- PostgreSQL, Supabase, TypeORM
- Connecting
- n8n, webhooks, OpenAI API, GoHighLevel, Cliniko, Telegram, SSO
- Running it
- Jest, AWS S3 & Serverless, Docker, GitHub Actions, Netlify
Career history
Where this came from — five years, four companies, and work of my own
- 2024 → NOW GrowkuFull-stack engineer, then leading the team. AI products, systems integration, multi-tenant commerce, Astro content platforms. FULL-TIME
- ONGOING My own clientsThe Cliniko → GoHighLevel clinic sync, the TalentStream candidate-data platform, and Astro site builds. FREELANCE
- 2022–2024 uPetUS e-commerce. Testing from unit to end-to-end, shared UI library, automations for non-technical teams, gradual migration to React and NestJS. FULL-TIME
- 2023 Yalla CooperativeReact survey platform and its shared design system, built alongside product and design. PART-TIME
- 2021–2022 Kiitos Technologies, AmsterdamSix client projects, startup through enterprise. Server-side rendering with Next.js for discoverability. FULL-TIME
- 2020 Gaza Sky Geeks Code AcademyFull-stack programme: eight weeks intensive, then sixteen weeks building for real clients. Civil engineering degree before that. TRAINING
Tell me which two systems refuse to talk to each other. Send me the URL. I'll tell you what's slowing it down.
Thirty minutes, free, and an honest answer about whether I am the right person for it. Thirty minutes, free, and a straight answer about whether a rebuild is worth it or whether a few fixes would do.