Web & SaaS Builder — Tétouan, Morocco · Remote
Shipped in weeks,
built to last.
I build websites and SaaS products with AI in the loop — which is why they ship in weeks. Nine years delivering software for Bell, BMW and Bayer is why they don't fall over afterwards.
Telecom · automotive · life sciences · retail — as engineer, then as delivery lead.
What I build
Four things, done properly. Scoped up front, shipped on a date, handed over with the keys — not a dependency on me.
Websites that rank and convert
Marketing sites, landing pages and portfolios that earn their keep — designed and built from scratch, not dropped into a template. Every build ships with the SEO foundation most sites bolt on too late: structured data, clean semantics, real meta, sitemap, and Core Web Vitals treated as a requirement rather than a cleanup task.
SaaS & MVP builds
A working product, not a prototype that dies in a demo. We scope the smallest version that proves the thing, then I build it — auth, data model, core flows, payments if you need them — deployed on infrastructure that won’t need replacing when it works.
Architecture & technical rescue
Someone built it quickly, it worked, and now every change breaks something else. I audit what’s there, tell you plainly what’s worth saving, and give you a sequenced plan — or do the work. Nine years inside enterprise codebases means I’ve seen how this ends, and how to stop it without a rewrite you can’t afford.
AI-augmented automation
The internal tooling that quietly removes hours a week — LLM workflows, agents, retrieval over your own documents, integrations between systems that don’t talk. Built against your real processes and measured against how long the job took before. If AI doesn’t beat the baseline, I’ll say so.
How I build
No open-ended retainers, no surprise invoices. Every project runs the same four steps, and you know the shape before you commit.
Scope
A call, then a written scope: what gets built, what doesn’t, what it costs, and the date it lands. If I don’t think I’m the right person for it, I’ll tell you here — that’s the whole point of this step being free.
Build
You see it running from week one. Weekly demo, a link you can click, and a channel where you can reach me. AI in the loop is why the timeline looks short; the architecture review at the end of each week is why it holds.
Ship
Live on your infrastructure, your domain, your accounts. Performance, accessibility and SEO verified before launch, not promised for later.
Hand over
The repo, the pipeline, the documentation, and a walkthrough. You can take it to any developer afterwards. If you’d rather I kept building, that’s a new scope — not an assumption.
Shipped products, and this page
I’m not going to show you a wall of client logos for this kind of work, because I’d be borrowing credit I haven’t earned yet. Here’s what I can show you instead — the products I build and run myself, plus this site — all of it checkable in about two minutes.
PawPawCare
001A pet health tracker I founded and built end to end — vaccine and medication reminders, weight trends, vet records, AI scanning of vaccination cards. Live on iOS and Android, with real users. The closest thing I have to a case study: a product, not a mock-up.
pawpawcare.app ↗FitPal
002A gym’s own member app, under its own brand — passkey sign-in, sign-ups the owner approves, class timetable, workout tracking. Installs from the browser, no app store. Built and run by me on an open-source core (openGym): brand, access flow, sessions, deploy pipeline and bilingual site, delivered in days. Live at its first club, FIT’ONE.
fitpal.ma ↗This site
003Designed, built and deployed by me. React, hand-written CSS, no template, no page builder. Scores 100 / 100 / 100 on Lighthouse for accessibility, best practices and SEO — run it yourself.
The source
004The whole thing is public. Read the code, the structured data, the build config, the commit history. If you want to know how I work, that’s the most honest answer I can give you.
github.com/r0b0t007 ↗The track record
005Nine years of production software for companies that audit their vendors — Bell, BMW, Bayer. Verifiable, with certifications to match.
linkedin.com/in/ahmedchioua ↗I’m building the client side of this portfolio deliberately, which means the first few projects go out at founding rates in exchange for a case study and a reference. You get senior work below market; I get proof. Say so when you get in touch.
Where the standards come from
Nine years inside enterprise software — four building it, five making sure teams shipped it. Both halves show up in how I work now.
PresentDelivery
Scrum Master
Jun 2024Delivery
Scrum Master
Dec 2023Delivery
Scrum Master
Jun 2021Infrastructure
DevOps Engineer
2021Engineering
Software Engineer
AI fluency. Engineering discipline.
I build with AI in the loop every day — not as a novelty, but because it’s the difference between quoting six weeks and quoting six months. What it doesn’t change is the part that decides whether software survives contact with users: the data model, the architecture, the tests, the decision about what not to build. Nine years in enterprise delivery taught me that half. AI just made the rest faster.
Build
001AI & Automation
002Ship & Operate
003Delivery
004Straight answers
What exactly do you build?
Marketing websites, SaaS products and MVPs, internal tools, and the AI automation that sits behind them. Full-stack — design through deployment. If it runs in a browser and needs to work properly, it’s in scope.
How fast is "fast"?
A marketing site is typically 2 to 3 weeks. An MVP is typically 4 to 6, depending on scope. You get a date in the written scope before you commit, and a working link from week one. Building with AI in the loop is what makes those numbers real rather than optimistic.
Does building with AI mean lower quality?
It’s the opposite of how most people assume it works. AI accelerates the typing — scaffolding, boilerplate, tests, first drafts. It doesn’t make the architectural decisions, and neither does it review the result. That’s what nine years of enterprise delivery is for. This site is built that way; run Lighthouse on it.
Can I see client work?
Not client case studies yet, honestly — I’ve spent nine years building inside enterprise programmes under NDA, and I’m building the independent client side of this deliberately. What you can see is the products I build and run myself: PawPawCare, a pet health tracker on iOS and Android that I founded and built; FitPal, a white-label gym member app on an open-source core, live at its first club, FIT’ONE; plus this site with its source published. That’s also why the first few projects go out at founding rates — I’m trading price for proof.
What does it cost?
Fixed price per project, quoted in the free scope call, based on what you actually need rather than hours logged. No retainers you can’t exit, no invoices you didn’t see coming. Founding-client rates apply to the next few projects.
Who owns the code?
You do — outright, from day one. Your repo, your infrastructure, your accounts. The handover includes documentation and a walkthrough specifically so you can take it to any other developer without needing me.
Do you work with existing codebases and teams?
Yes. Audits, refactors and rescues are a service in their own right, and five years as a Scrum Master across distributed enterprise teams means dropping into someone else’s process is familiar territory rather than friction.
Where are you based, and does it matter?
Tétouan, Morocco (GMT+1) — remote-first, which is how I’ve worked with Canadian and German teams for the last five years. Overlap with Europe is complete and with US Eastern is most of the working day.
Tell me what you're building
Send me the shape of it and I'll tell you honestly whether I'm the right person, what it would take, and what it would cost. The scope call is free and there's nothing to unsubscribe from.
- [email protected]
- linkedin.com/in/ahmedchioua
- Location
- Tétouan, Morocco · Remote