Client stories
What we've actually built
Our clients' platforms are private by design, so we tell their stories without naming them. Every detail here describes real systems, in production, used every day.
Faith-based community institution
From paper registers to a portal every family uses
A community centre running education programmes, memberships, and events across hundreds of households — on paper registers, spreadsheets, and message threads.
The starting point
Enrolment lived on forms that were retyped by hand. Teachers kept attendance and progress in personal notebooks. Families had no window into their children’s learning, membership dues, or community life — every question became a phone call to the office.
What we built
- A member portal where each household sees its own people, programmes, and community feed
- A learning management system shaped to their actual curriculum — classes, attendance, progress ledgers, and certificates
- Sign-in designed for the real community: students use short codes, guardians their phone numbers
- Onboarding in waves — imported legacy records first, then invitations, so nobody arrived to an empty platform
- Branded email for invitations and account recovery, and a moderated community feed
The shift
Staff, teachers, students, and guardians now work in one place under the institution’s own brand. The office answers fewer “what’s the status?” calls, teachers mark progress where families can see it, and leadership reads live ledgers instead of assembling month-end spreadsheets.
- Records
- Workflows
- Reporting
- Communications
- Portals
Faith-based community institutionTravel & operations firm
An operations desk that runs the whole day
A services firm handling bookings, ticketing, client accounts, and staff payroll — where every job used to travel through phones, inboxes, and disconnected sheets.
The starting point
Bookings arrived by phone and were tracked in whoever-took-the-call’s spreadsheet. Invoices and payslips were typed individually. The financial picture reconciled at month-end, if everyone remembered everything.
What we built
- A production workflow desk where every booking moves through owned, visible stages
- Client and booking records with full history — one source of truth for who, what, and when
- Invoicing and e-ticket generation straight from the booking record
- An accounting desk with bank-account portfolios and reconciliation views
- Payroll with generated payslips for staff
The shift
The day now runs through one console. A booking becomes a ticket, an invoice, and a ledger entry without being retyped — and the owner sees the state of the business live instead of at month-end.
- Records
- Workflows
- Finance
- Reporting
Travel & operations firmWhy no names?
Their platform is theirs — including the credit
Every eiQora platform ships under the client's own brand and domain; most of their communities never see our name, and we like it that way. We extend the same discretion to their stories. If you'd like to speak to a reference during discovery, we'll arrange an introduction directly.
The next story could be yours.
Both of these platforms started as one honest conversation about where the tools were failing.