Your site or SaaS, live in weeks. Fixed price. Date in writing.
A working link in 10 days. A launch date you can plan around. A price that doesn’t move. Built by an engineer with nine years shipping production software for Bell, BMW and Bayer.
- Day 0Kickoff, after a free scope call
- Day 10Your first working link
- Weeks 2–3Launch, for a marketing site
- Weeks 4–6Or launch, for an MVP
- +30 daysAfter launch: fixes included
Telecom, automotive, life sciences and retail. First as an engineer, later as a delivery lead.
The cheapest developer is the one you pay twice
Here’s how most founder builds go. You hire fast and cheap. The demo looks fine. Then users arrive, something breaks, and nobody can find why. The fix is a rebuild, at full price, plus the months you lost. That isn’t a developer problem. It’s a standards problem.
I spent nine years building and running delivery on platforms for Bell, BMW and Bayer, through NTT DATA and a consulting engagement. Programmes where every vendor gets audited and “we’ll fix it after launch” isn’t allowed. Those standards ship with your build. They’re the insurance policy on your capital.
Architecture reviewed every week
Not “cleaned up later”.
Speed that turns into debt you inherit isn’t speed. The review is how it stays yours.
Performance, accessibility and SEO verified before launch
Not promised for after.
You see the numbers before it goes live, the same way you can see this page’s.
Tests, docs and a deploy pipeline
The boring parts that decide whether it survives month three.
They ship with the build, not as an add-on.
What I build
Two things, done end to end. Scoped up front, shipped on an agreed date, and handed over so you can maintain them without me.
Websites that rank and convert
Marketing sites, landing pages and portfolios, designed and built from scratch. Structured data, clean semantics, proper meta tags and a sitemap all go in during the build, and I measure Core Web Vitals before launch instead of leaving them as cleanup for later.
Full details (Website development) →SaaS & MVP builds
We agree on the smallest version that proves the idea, then I build it: auth, data model, the core flows, payments if you need them. It goes out on infrastructure that can take growth, so you’re not rebuilding the foundations the month it starts working.
Full details (SaaS & MVP development) →Already have a codebase that won’t move, or a process eating hours a week? Architecture rescues and AI automation are services too. Mention it in the scope call and we’ll price it the same way.
A working link in 10 days. Then every week after.
Agencies go quiet for six weeks and come back with a surprise. You don’t get to say “that’s not what I meant” until it’s expensive to fix. Here, every project runs the same four steps, and you can see it running from the first one.
Scope
A 30-minute call, then a written scope: what gets built, what doesn’t, what it costs, and the date it goes live. If I’m not the right person for it, I’ll say so here. That’s why it’s free.
Build
Day 10, you get a URL. It’s rough. It’s real. You click through the core flow, react, and we adjust while changes are still cheap. Every week after: a demo, an updated link, a direct line to me. AI in the loop is why the timeline is weeks, not months. The weekly architecture review is why it holds.
Ship
Live on your infrastructure, your domain, your accounts. Performance, accessibility and SEO verified before it goes out, and you see the numbers. If I miss the date in your scope, I keep building until it ships, and the overrun is on me.
Hand over
The repo, the pipeline, the documentation, a walkthrough, and 30 days of post-launch fixes. Any developer can pick it up after me. If you’d rather I kept going, we scope that separately.
You lift zero technical fingers. You own everything.
Most hand-offs are a zip file and a goodbye. This one is a stack.
Pure asset ownership
Your GitHub repo, in your name, from day one.
Written documentation plus a recorded walkthrough.
Any developer can pick it up tomorrow. You are never locked in, including to me.
Infrastructure, configured and transferred
Hosting, domain, database, auth, payments: set up on your accounts (Vercel, AWS, Supabase, Cloudflare).
Deploy pipeline live. Push code, it ships.
Analytics wired before launch, not after. Nobody “holds the keys for you”. You hold them.
Launch insurance, 30 days
Bugs surfaced in the first 30 days: fixed, included.
Small tweaks as real users hit it: included. The direct channel stays open.
The first month is when things break. I stay for it.
Don’t take my word for it. Take two minutes.
I won’t show you client logos I haven’t earned. I’ll show you things you can look up: two products I built and run, this site, its source, and the track record behind it.
PawPawCare
A pet health tracker I founded and built end to end: vaccine and medication reminders, weight trends, vet records, and AI that reads photos of vaccination cards. In early-access preview, onboarding waitlist members ahead of the app-store launch. It is the closest thing I have to a case study.
pawpawcare.app ↗FitPal Coach
Software for independent personal trainers coaching 5 to 40 clients. The coach gets a dashboard that shows adherence against the plan; each client gets a training app under the coach’s name that installs from the browser, works offline and signs in with a passkey. I built and run it on an open-source core (openGym). Sold through a call at fitpal.ma.
fitpal.ma ↗This site
Designed, built and deployed by me, in React with hand-written CSS. No template, no page builder. It scores 100 / 100 / 100 on Lighthouse for accessibility, best practices and SEO. Run it yourself if you want to check.
Read the build log →The source
The whole repository is public: the code, the structured data, the build config and every commit since the first one. It answers the question of how I work better than anything I could write here.
github.com/r0b0t007 ↗The track record
Nine years of production software for Bell, BMW and Bayer, delivered through NTT DATA and a consulting engagement. It’s all on LinkedIn, with the certifications alongside it.
linkedin.com/in/ahmedchioua ↗Fixed. Premium. Quoted once.
The figures below are starting points. Your number is fixed once, in the free scope call, in writing, with a date attached, and it doesn’t move after that. It covers the build, the infrastructure, the hand-off and 30 days of launch insurance. No hourly meter. No change-order ambush.
| Scope | From |
|---|---|
| Marketing site or landing page | €3,000 |
| SaaS product or MVP | €12,000 |
What moves the number: how much of it is new rather than adapted, and whether auth, payments or third-party integrations are in scope.
“AI writes the code. Why isn’t it cheaper?”
AI makes me faster. It doesn’t make the decisions that keep your product alive: what to build, what to leave out, and who answers when it breaks at an awkward hour. You’re paying for those.
Cheap development is the expensive option. You just pay for it later, as a rebuild.
Lock in a price and a dateWhere the standards come from
Nine years inside enterprise software: about four building it, and five leading the teams that 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
What I work with
I use AI every day in the build, and it’s the difference between quoting six weeks and quoting six months. What it hasn’t changed is the part that decides whether software survives real users: the data model, the architecture, the tests, and knowing what to leave out. That half came from nine years of enterprise delivery.
Build
AI & Automation
Ship & Operate
Delivery
Straight answers
What exactly do you build?
Marketing websites, SaaS products and MVPs, internal tools, and the AI automation behind them. Full-stack, from design through to deployment. If it runs in a browser and has to hold up under real use, it’s in scope.
How fast is "fast"?
A marketing site is usually 2 to 3 weeks. An MVP is usually 4 to 6, depending on what goes in it. You get a date in the written scope before you commit, and a working link within the first 10 days. Building with AI is what makes those numbers realistic.
Does building with AI mean lower quality?
AI speeds up the typing: scaffolding, boilerplate, tests, first drafts. It doesn’t make the architectural decisions and it doesn’t review its own output. That part is my job, and it’s what nine years of enterprise delivery trained me for. This site was built that way, so run Lighthouse on it.
Can I see client work?
Not for this offer yet. Nine years of my work sits inside enterprise programmes under NDA, and the independent client side is new. What you can look at instead is the products I build and run myself: PawPawCare, a pet health tracker for iOS and Android that I founded and built, now in early-access preview; FitPal Coach, coaching software for independent personal trainers, built on an open-source core; plus this site, with its source published.
What does it cost?
Marketing sites start at €3,000, SaaS and MVP builds at €12,000. The exact figure is fixed per project in the free scope call, based on what the project needs rather than hours logged, and it covers the build, the infrastructure setup, the hand-off and 30 days of post-launch fixes. No hourly meter, no retainers you can’t exit, and no invoices you didn’t see coming.
Is there a founding-client rate?
Yes, for the next 3 projects, and it isn’t a discount. You trade a written case study and a reference for the founding price. Same scope, same date, same hand-off. Say “founding” in the scope call.
What happens if the launch date slips?
It doesn’t come out of your side. The date is in your written scope. If I miss it, I keep building until it ships, and the overrun is on me. Scope changes you ask for mid-build move the date and the price, and we agree both in writing before I continue.
What happens after the 30 days?
Three options, none assumed. Take it to any developer, which is what the documentation and walkthrough are for. Book me for a scoped follow-on at a fixed price. Or a monthly care plan for hosting, updates and small changes, quoted separately. Nothing renews on its own.
Who owns the code?
You do, outright and from day one. Your repo, your infrastructure, your accounts, with hosting, domain, database, auth and payments configured on accounts you control. The hand-off includes documentation and a recorded walkthrough so you can take the project to another developer whenever you want, and 30 days of post-launch fixes so the first month isn’t yours to debug.
Do you work with existing codebases and teams?
Yes. Audits, refactors and rescues are a service on their own. Five years as a Scrum Master across distributed enterprise teams means joining someone else’s process and tooling is familiar ground.
Where are you based, and does it matter?
Tétouan, Morocco, on GMT+1. I’ve worked remotely with Canadian and German teams for the last five years. The overlap with European hours is full, and with US Eastern it covers most of the working day.
Claim your 10-Day Prototype Slot
I run a few builds at a time; weekly demos are why. The scope call is free, 30 minutes, and ends with a written answer: what gets built, what it costs, and the date it goes live. If I'm not the right person for it, I'll tell you on the call.
- +212 626-410-690
- linkedin.com/in/ahmedchioua
- Location
- Tétouan, Morocco · Remote
No retainer. No deposit to talk. A written scope within a week, or a straight “not me”.
Not ready to talk? Read the code first →