Skip to content

Based in Casablanca, working with Europe

Technical audit before your fundraise, rewrite or next hire

An honest review of your codebase and architecture, with a prioritised plan. For teams preparing a fundraise, a rewrite or a new hire, and for founders taking over code they did not write.

What a technical audit with me covers

A technical audit is an independent review of a software product, done before a decision that depends on it. When I audit a product, I review the code and the architecture, check performance, security and SEO, and hand over a written report with clear priorities, so you know what to fix first and what can wait. It suits teams preparing a fundraise, a rewrite or a new hire, and founders taking over a codebase they did not write. It is also how I usually start when a client asks me to take over an existing codebase: the audit gives us a shared plan, and from there I can lead your team or take the build forward myself. An audit gets a written scope, timeline and fixed price after the intro call, so you know exactly what you are buying before we start. I work remotely from Casablanca, Morocco, with teams in Morocco, France and Europe, in English and French.

When it fits

  • You are preparing a fundraise and want a clear picture of your codebase before technical due diligence.
  • You are weighing a rewrite and need to know what is worth keeping.
  • You are about to hire and want the next developer to start on solid ground.
  • You are taking over a codebase you did not write.

After the audit, the plan is yours: act on it with your own team, or with me.

Need technical leadership after the audit?See fractional CTO

What you get

A fixed price after the intro call, with a written scope and timeline.

  • Code and architecture review

    How the system is built, how the code holds up, and where it will slow your team down.

  • Performance, security and SEO checks

    The issues that cost you users, data or search traffic.

  • Written report with clear priorities

    A prioritised plan: what to fix first, and what can wait.

How it works

  1. Intro call

    30 minutes on your product, team and goals. You leave with a clear next step either way.

  2. Proposal

    A written scope, timeline and price, so you know exactly what you are buying.

  3. Kickoff

    Access, team rituals and the first milestone agreed in the first week.

  4. Ship

    Weekly demos and visible progress, through launch and beyond.

The experience behind the audit

Wasal Marketplace

My role

Helped keep the architecture consistent across a growing marketplace codebase, and set up the CI/CD pipelines for faster, safer deployments.

Read the case study: Wasal Marketplace

Questions about the technical audit

What does a technical audit cover?

A review of your code and architecture, performance, security and SEO checks, and a written report with clear priorities, so you know what to fix first and what can wait.

When should a startup get a technical audit?

Before a decision that depends on the codebase: a fundraise, a rewrite or a new hire. It is also the first step when you want someone to take over an existing codebase.

How much does a technical audit cost?

An audit gets a written scope, timeline and fixed price after the intro call. You know exactly what you are buying before we start.

What happens after the audit?

You get a prioritised plan. Your team can act on it alone, or I can lead your team or take the build forward myself.

Which technologies do you work with?

Mostly TypeScript, React, Next.js and Node.js on the web, React Native on mobile, Spring Boot where a Java backend fits, and PostgreSQL or MongoDB for data. I pick the stack for the product, not the other way around.

Newsletter

Notes on building products and leading teams

An occasional email with what I learn on real projects. No spam, unsubscribe in one click.