Skip to content

Available for new projects

I design and buildthe systemsyour business runs on

Data pipelines, AI automation, dashboards, websites and apps — engineered end-to-end, by one person who ships.

5.0Top Rated on Upwork100% Job SuccessEU-based
Freelance AI automation & data engineer — n8n, scraping, dashboards | Oussama Abassi
SCRUB77 FRAMES

They trusted me with their systems

What I build

Eight disciplines. One person to talk to.

No agency, no subcontracting, no coordination overhead. You talk to the person writing the code.

  • Data & pipelines

    Scraping, cleaning, deduplication, enrichment, syncing. From raw source to data you can actually use.

    How

    The API when there is one, a driven browser when there isn't. Queued jobs, retry after failure, fingerprint deduplication: running it twice never creates a duplicate.

  • AI automation

    n8n, autonomous agents, LLMs in production. Repetitive work disappears from the calendar.

    How

    n8n for orchestration, and the model called with a structured output — an enforced format, not free text to guess at. Every step is logged, every failure replayable on its own.

  • Dashboards & control centers

    An interface built to operate a system, not to admire it.

    How

    Aggregates computed in the database, not in the browser: the page stays fast across years of history. Access rights enforced at database level, refresh without a page reload.

  • Web development

    Next.js, TypeScript, from design to deployment.

    How

    Next.js 16, server components by default, fonts and images served from your own domain. Core Web Vitals measured before launch, not discovered after.

  • Mobile & desktop apps

    Cross-platform, wired into the systems you already run.

    How

    One codebase for iOS, Android and the desktop. Offline-capable with a sync queue: the user enters data, the app sends it when the network comes back.

  • Chatbots & AI assistants

    Qualification, support, lead capture. The one on this page is one of them.

    How

    A deterministic qualification script first, the model as a fallback when the question falls outside it. Streamed answers, every conversation stored, and one hard rule: never invent a price or a deadline.

  • E-commerce

    Catalogues, payments, stock and back-office syncing.

    How

    Payments delegated to a certified provider — no card data ever passes through your systems. Stock synced by webhooks with your back-office, product pages server-rendered so they stay indexable.

  • Design & branding

    Interfaces and visual identity that match the product.

    How

    A token system rather than isolated mockups: colours, scales and spacing defined once, applied everywhere. Contrast checked, motion switched off when the visitor asks for it.

Selected work

Real clients. Systems in production.

For each project: the problem, the architecture, the stack, and what it produced.

How I work

Five steps. No surprises.

The same sequence on every project, from a 200-line script to a full platform.

  1. 01

    Signal / brief

    You describe the problem. I ask the questions nobody asks — the ones that reveal the real problem is somewhere else. Reply within 24 to 48 hours.

  2. 02

    Architecture

    System diagram, stack decisions, failure points identified. Before the first line of code. You sign off on a plan, not a promise.

  3. 03

    Build

    Delivered in visible increments. You watch the system run on your own data long before it's finished. No black box.

  4. 04

    Handover

    Documentation, access, walkthrough. You're independent. The code is yours, with no hidden dependency on me.

  5. 05

    Maintenance

    Optional. Monitoring, fixes, evolutions. Some clients never needed it — that's the point.

Technical stack

Production tools. Not fragile prototypes.

The same building blocks used by companies processing millions of events a day.

  • n8n
  • Make
  • Zapier
  • Apify
  • Playwright
  • OpenAI
  • Anthropic
  • Groq
  • Gemini
  • Vercel AI SDK
  • PostgreSQL
  • Supabase
  • Airtable
  • AWS RDS
  • Redis
  • Next.js
  • TypeScript
  • React
  • Tailwind
  • React Native
  • Vercel
  • AWS EC2
  • Docker
  • GitHub Actions
  • Cloudflare
  • Resend
  • Stripe
  • Twilio
  • Lemlist
  • Google APIs
  • Automation
  • AI & LLMs
  • Data
  • Web & apps
  • Infra
  • Delivery
Oussama Abassi

Oussama Abassi

About

One person. That's the strength, not the limit.

I'm Oussama Abassi, a freelance engineer based in Paris, working across Europe: industrial SMEs, consumer platforms, independents, startups. The size and the sector change, the starting point never does — someone shows me a process eating their week, and I turn it into a system that runs on its own.

Working with me means one point of contact, no project-management layer, and the person designing the architecture is the person writing the code and answering your messages. On a four-day project as much as a three-month one.

What interests me are systems that don't break the moment I stop watching them.

Start a project

Verified reviews

Public, verifiable, all 5.0.

Every review links back to its public source on Upwork or Malt.

Frequently asked

The questions people ask before signing.

Honest answers, including the ones that don't flatter me.

Do you really work alone?

Yes. One point of contact, no project-management layer, and the person designing the architecture is the person writing the code and answering your messages. On very large projects I can bring in trusted partners, but you keep a single point of contact: me.

How long does a project take?

It depends entirely on scope, and I won't quote a number before I understand it. For a sense of scale: an autonomous sales pipeline shipped in 4 days, a large-scale data project ran across two months. After our first conversation you get a reasoned estimate — not a figure pulled out of the air.

How does billing work?

Fixed price on a defined scope, or time-based on longer engagements. A deposit is required to start. Budget is discussed once the need is framed: I'd rather quote fairly after understanding the problem than publish a rate card that fits nobody.

What happens if the system breaks after delivery?

You get the documentation, the operations runbook and full access to the code — you're independent, with no hidden dependency on me. A maintenance contract is available but optional. Some clients have never needed one, and that's exactly what I aim for when building.

Is my data safe?

NDA signed on request, before any detail is exchanged. API keys stay server-side, never in the browser. On a recent project the client's IT lead required strictly read-only banking access: the scope was honoured to the letter, no write route exists in the codebase.

Do you take over existing projects or only new builds?

Both. A good share of my work is picking up infrastructure already in place, fixing its blind spots and making it operable. Taking over existing code often demands more rigour than starting from scratch.

Another question? Write to me.

Start a project

Describe your project.

I read every message myself and reply within 24 hours. No automated quote, no form disappearing into a void.

Project typerequired
Budget rangeoptional
  • Reply within 24h
  • NDA on request
  • EU-based

Assistant · live demo

The assistant at the bottom right of your screen is an example of what I build. It qualifies, it records, it never sleeps.