Bordeaux and Nouvelle-Aquitaine, remote across France
Freelance business analyst (AMOA)
Between what the business asks for and what engineering delivers, someone is usually missing to translate. That is the business analyst role: turning an expressed need into usable specifications, then verifying that what is delivered truly matches what was asked.
Book a free callThe problem I solve
Without business analysis, two scenarios recur. The business describes a solution rather than a need, and the technical team builds the wrong thing. Or acceptance testing is rushed for lack of written scenarios, and defects surface in production, in front of users. In both cases the cost of fixing far exceeds the cost of framing.
How I work
Requirements gathering
Workshops with business teams to trace back to the real need behind the request, and write what is expected in language engineering can execute.
Functional specifications
Writing the specs and business rules, including edge cases and the translation of regulatory constraints into concrete requirements.
Acceptance test assets
Designing test scenarios and the acceptance plan: what objectively defines whether a delivery is compliant, before it reaches the user.
Testing and defect tracking
Running acceptance tests, qualifying and tracking defects through to production release.
Real example
Concrete figures: on La Banque Postale's onboarding journeys, I ran the framing workshops, wrote the functional specifications (account opening, minor/adult journeys, Livret A) and designed the acceptance scenarios. Result: fewer than 3 production incidents per year, under KYC and GDPR constraints.
Read the case studyWho it is for
- IT and business departments in banking or insurance
- Projects under regulatory constraints (KYC, GDPR)
- Technical teams receiving requests too vague to build
- Organisations where defects are discovered in production
Deliverables
- Formalised requirements document
- Functional specifications and business rules
- Acceptance test plan
- Acceptance report and defect tracking
- Support through production release
Frequently asked questions
What is the difference between a business analyst and a Product Owner?+
A business analyst works through contractual deliverables: requirements, specifications, acceptance plans, with formal governance. A Product Owner works in continuous flow on a prioritised backlog. The former fits regulated projects and client/supplier relationships, the latter fits products that evolve continuously.
Do you work on regulated projects?+
Yes, that is my main ground. Since 2024 I have been steering banking journeys subject to KYC and GDPR, and I led a 500-million-document migration under GDPR constraints.
Do you run the acceptance testing yourself?+
Yes: designing scenarios, executing them, qualifying defects and tracking them to closure. I also trained as a software tester, which helps write test cases that actually find defects.
How much does it cost?+
On a quote basis, daily rate or fixed price depending on scope. The first call is free.
A need to frame
Book a free first call. We look at your project and what is missing between business and engineering.