Some of what we have built

Parish offices carry a great deal of responsibility on very little infrastructure: census and household records, contributions, sacramental registers, groups, cemeteries, and the reporting a diocese needs at year end, much of it kept in spreadsheets, paper registers and the memory of whoever has been there longest.

Emily Helps replaces that with one system. Each parish sees only its own records, data protection is designed into the structure, and reporting works at parish and diocesan level. Charitable tax rebate returns are generated rather than assembled by hand.

Emily Helps is a sister company, founded in 2025 by the AMDG partners with a third co-founder who leads its development. AMDG’s part is the architecture, hosting and operations, and the data protection work: the impact assessment, the processing agreements, and sign-off with a diocesan data protection officer.

In brief

• Multi-tenant, with each parish isolated from every other
• Hosted in the EU and administered over a private network, with no inbound ports open to the internet
• Records migrated from legacy parish databases and checked on the way
• In use in Irish parishes since 2025

A diocese’s public website carries parishes, churches, Mass times, clergy, schools, news and often a podcast archive, and it has to be kept current by a small office. We are building sites for Irish dioceses from one shared codebase, fed from the records they already hold in Emily Helps, so that a page updated once is updated everywhere.

Every page is checked automatically for accessibility to WCAG 2.2 AA, and the build fails if performance drops below budget. There is no cookie banner, because there is no third-party code on the page: no analytics, no hosted fonts, no embedded players. Podcast and video archives are served from the diocese’s own site.

In brief

• One codebase, several dioceses, each with its own look
• More than a thousand pages on the largest site, in English and Irish
• Accessibility and performance budgets enforced on every build
• Site search that sends nothing to a third party

A national, volunteer-governed organisation with a committee structure, an older membership and no communications staff. Since April 2026 we have run its communications. Members submit event notes and photographs through a form on the organisation’s own website, and we turn them into articles, a monthly newsletter and posts across its social channels, working to a written routine and an approval workflow so that nothing depends on one person.

For the same organisation we built a members’ portal with automated levies and integrated messaging.

In brief

• Member-submitted content through the organisation’s own site
• A monthly newsletter and five social channels
• A written routine and an approval workflow
• No new software: built on the platform the organisation already had