Services
What we do
Most of our clients are institutions and smaller organisations with real obligations and no technical staff of their own. The work is usually some combination of the six things below.
Systems architecture and modernisation
Organisations arrive with systems that have accumulated a decade of workarounds. The expensive problem is usually the data model underneath the feature being asked for. We work out what the organisation actually needs to hold and do, design a model that will still be maintainable in five years, and write the roadmap that gets there in steps a committee or a board can approve and fund one at a time.
Where records about people are involved we prefer steady upgrades to big launches, and we keep the old system running until the new one has earned its place.
Typical work
- Replacing spreadsheets and ageing databases with one properly modelled system
- Consolidating several platforms into one or two
- Technical roadmaps and architecture reviews
- Migrating records from legacy systems, with the data checked on the way
Data protection by design
Data protection is a design decision. If it is added at the end, the structure underneath is already wrong. We build it into the model: each office or branch sees only its own records, retention rules and consent are part of the data rather than a policy document, and backups are encrypted.
We also do the paperwork that goes with it. We have taken systems through data protection impact assessments and sign-off with clients’ data protection officers, and we write the processing agreements in plain language.
Typical work
- Multi-tenant systems with per-organisation data isolation
- Data protection impact assessments and data processing agreements
- Retention, consent and anonymisation built into the system
- Advice on hosting, backups and third-country transfers
CRM and back‑office systems
Between us we have deployed CRM and back-office systems on most of the products people argue about, somewhere past twenty of them, and we favour none. The choice of product matters much less than whether the model underneath it is right, and many expensive mistakes begin with choosing the software first and working out the requirements afterwards.
A fair part of this work is finding what an organisation is already paying for: unused licences, capacity nobody is using, and a smaller change that would do.
Typical work
- Selecting and implementing a CRM or membership system
- Salesforce architecture and development
- Licence reviews and platform consolidation
- Reporting and dashboards that a board can read
Custom software and platforms
Sometimes nothing off the shelf fits, and one thing needs to be built properly. We have built a records and administration platform for organisations with many small local branches, a reporting and statistics application for a financial firm, and members’ portals with automated payments and messaging.
Everything we build is designed to be run by the people who will actually use it, with written routines and no dependence on us for the day to day.
Typical work
- Multi-tenant platforms with a central office and many local branches
- Members’ portals, payments and levies
- Reporting and statistics applications
- Integrations between systems that were never meant to talk to each other
Websites and communications
We build websites that are fast, accessible and easy to keep current, in English and Irish where that is wanted, with no cookie banner because we put nothing on the page that needs one.
For organisations run by volunteers, we can also run the communications: member-submitted content, a monthly newsletter and the social channels, to a written routine, so nothing depends on one person finding a free evening.
Typical work
- Public websites for institutions, clubs and small businesses
- Bilingual sites, accessible to WCAG 2.2 AA
- Newsletters and social channels run on your behalf
- Being found by search engines and AI assistants, for local businesses
A second opinion
Before you sign for a rebuild, a migration or a new platform, an independent look at what you have is worth the day it takes. We will tell you if the change being proposed is bigger than the problem, and whether what you have can be made to work for less.
Sometimes the honest answer costs us the larger job.
Typical work
- Reviews of proposals and quotes
- Technical due diligence
- Architecture and data-model reviews
- Requirements and scoping before a purchase
Not sure which of these you need
Describe the situation and we will tell you. Working out what the problem actually is comes first.