CiviCRM for nonprofits
Setup, repairs, extensions and migrations for CiviCRM, the open-source CRM that associations and NGOs can run on their own terms.
Most nonprofits I meet keep their members in one spreadsheet, their donors in another, and their newsletter in a third tool that charges per contact. CiviCRM puts all of that in one place, it is free software, and the data stays on a server you control. The catch: setting it up well takes someone who has done it before.
That is the part I do. I run CiviCRM for a handful of organisations, from a volunteer-run association to a national advocacy group, and I maintain a few open-source extensions along the way. If your organisation is too small for a CRM, or your needs are better served by a hosted product, I will say so in the first call.
What I do
New installations
Standalone or on Drupal, on your hosting or on mine. Backups, upgrades and a rollback path are part of the setup, not an extra. I configure membership types, contribution pages and mailings for the way your team actually works rather than shipping a template.
Fixing an existing setup
Slow pages, duplicate contacts, mailings that land in spam, an upgrade nobody dares to run. I start with an audit, write down what I found, and fix things in an order that keeps the system usable throughout.
Extensions and integrations
Custom extensions in PHP when the built-in options run out: payment providers, webhooks, the REST API, FormProcessor flows. A common request is newsletter signup with double opt-in on an existing website, which I have written up in detail.
Migrations
Out of spreadsheets, Airtable, an old CRM or an outdated CiviCRM. Import scripts are written so they can be re-run, duplicates are merged by rules we agree on first, and nothing is deleted before you have signed off on a test import.
How an engagement works
A first call is free and takes about twenty minutes. Tell me what your organisation does, what you use today, and where it hurts. Then I send a short written proposal with a fixed price for the first step. Larger setups run as a retainer of a few days a month.
Extensions and scripts I write go on GitHub under an open licence unless there is a reason not to. Your contact data never leaves your systems; I work over a VPN or on your server, and I do not keep exports.
If what you are after is a custom web application or a public data platform rather than a CRM, the development page is the better starting point.