SERVICES / BUSINESS AND DEVELOPMENT
Web development for nonprofits and associations
I spent several years working in the French nonprofit sector — UFCV Normandie, EEDF — before moving into development. I know the real constraints: tight budgets, mixed volunteer/staff teams, structural turnover and Excel files holding everything together. Those constraints change how a digital tool has to be designed to actually get used.
When a tailored tool becomes useful
Bespoke web tools for nonprofits: member management, volunteer portals, project tracking, stakeholder coordination.
- Replace an Excel member list with a shared, team-maintainable tool
- Create a secure volunteer or partner space with centralised resources
- Structure project, action or case tracking across several governance instances
What the engagement includes
The scope is defined together, before development. Deliverables depend on the workflows, data and constraints of your organisation.
- Diagnosis of real usage, stakeholders involved and organisational constraints
- Simple journeys designed for volunteers, staff, members or partners
- Development of member management, project tracking, document sharing or reporting tools
- Documentation and knowledge transfer included to avoid prestataire dependency
What it helps make clearer
- A tool that works for teams that change, without depending on one person
- A controlled alternative to SaaS tools whose costs keep rising
- A developer who understands nonprofit culture before proposing a technical solution
Frame before building
- Understand the current workflow, users, constraints and decisions that must become reliable.
- Define a first-version scope with priority business rules, access rights and data.
- Build through short iterations, with regular validation points and useful documentation for future handover.
A technical stack suited to the need
The stack is chosen for the work it needs to support. Readable conventions and useful documentation help the tool evolve and make handover easier.
- Symfony / PHP for business logic and APIs
- API Platform when several interfaces or systems share the same data
- PostgreSQL or MySQL depending on the data context
- Astro, Tailwind CSS or dedicated interfaces for user-facing screens
- Docker and reproducible environments to make maintenance easier
Examples of features
- User roles and access rights
- Workflows, statuses and validations
- Dashboards and filterable lists
- Exports, imports and history tracking
- API connections with existing tools
A FEW POINTERS
Frequently asked questions.
Who is this nonprofits service for?
It is for SMEs, nonprofits, public-sector teams or industrial contexts that need to clarify processes, make data more reliable and build a maintainable web tool.
Do you work remotely?
Yes. I am based in Caen, France, and work remotely with structured teams in France, the UK, Ireland and other international contexts when the project is well framed.
How does a mission start?
It starts with a framing discussion: context, users, constraints, data, priorities and risks. This avoids building a tool disconnected from real usage.
YOUR NEED IS THE STARTING POINT.
Clarify your need before launching the project.
Describe your context, users and constraints. A first conversation helps identify a useful scope and the next steps.