Audit or scoping before a project
- Working days
- 3 to 8 days
- Indicative budget
- €1,000 to €3,500
- Duration
- 1 to 2 weeks
CAEN / NORMANDY / REMOTE
Based in Caen, I design business applications, APIs and internal tools for organisations in Normandy and remote teams. I start by understanding the context before writing code.
Based in Caen, I understand the local context, Norman organisations and the concrete constraints of businesses in the region.
My background in territorial coordination taught me to understand context before proposing a solution.
I develop applications that answer real needs: business logic, data, APIs and user interfaces.
The price of a custom web application or business software is simple to work out: a number of working days multiplied by a day rate. My day rate is €350–450 depending on the mission.
As a guide, here are orders of magnitude by project type, calculated from that day rate and a number of days, then rounded. The actual figure comes from a quotation prepared after a first conversation: an estimate without project knowledge is an unfounded promise. Amounts are net: VAT does not apply at present.
A FEW POINTERS
Yes. I work fully remotely with teams in the UK and Ireland. Distance does not change the method: structured kickoff, regular check-ins, documented deliverables and all communication in English.
Yes. I am available for freelance and contract engagements with UK and Irish companies, either on a project basis or for ongoing development work. I am based in Normandy, France, and operate on a remote-first basis.
Yes. I can frame, design and build a business application with business rules, data, user roles, workflows, APIs and interfaces adapted to team usage.
Yes. My background combines full-stack development, industrial projects and territorial coordination. I am comfortable in environments where technology has to deal with human, business and organisational constraints.
Yes. I start by understanding the current behaviour, business constraints, user pain points and priorities before proposing an evolution or technical rebuild.
YOUR NEED IS THE STARTING POINT.
Describe your workflow, users and the difficulties you face. These are the first steps towards a useful tool.