conservancy management platform
land & tourism ops | web platform
Built a multi-tenant web platform for conservancies to manage trustees, land parcels, properties, tourism partners, and payments in one place.
The system guides setup, enforces role-based access, handles invoicing (USD/KES), converts FX for bed-night revenues, and sends bulk M-Pesa payouts to landowners with bursary deductions and audit-ready exports.
outcomes
- Single source of truth across trustees, land, properties, tourism partners, and payment contracts.
- Automated FX + bed-night revenue calculations and invoicing (USD/KES) reduce manual errors.
- Bulk M-Pesa payouts to landowners, with bursary deductions and audit-friendly exports for regulators and donors.
what we shipped
- Step-by-step setup for conservancy profile, trustees, land and property records.
- Role-based access for admins, conservancy staff, and trustees.
- Tourism partner registry with document uploads and validation.
- Payments: tourism partner invoicing (rent, entrance, bursary/community/welfare funds), FX conversion, bed-night variable rent calc, and bulk M-Pesa disbursements.
- Notifications and reminders to keep onboarding and billing on track.
- Reporting/export for compliance, donors, and stakeholder sharing.
stack
- Frontend: Vue 3 (Inertia) with responsive dashboards.
- Backend: Laravel + PostgreSQL; payment calc engine for bed-nights, FX, and pro-rata landowner splits.
- Payments: M-Pesa B2C bulk payouts; invoicing PDF/Email flows; audit trails.
- Storage: AWS S3 for documents and proofs; queued jobs for emails/SMS.
- Infra: microservice-ready deployment with Playwright tests for flows.
faq
What results did the platform deliver?
A consolidated record of trustees, land, properties, and tourism partners with exportable audits and fewer onboarding gaps.
What capabilities were built?
Guided setup, role-based permissions, document storage, tourism partner registry, and reminders to keep data complete.
What stack was used?
Laravel + PostgreSQL back end, Vue 3 front end, S3-backed file storage, and notification hooks.
Is it extendable?
Yes—APIs and microservice-friendly architecture let us add GIS layers, payments, or additional compliance workflows as needed.