Work
Clients anonymised. Numbers not.
We took the client figures straight from their running systems, or reproduced them on the live sites. The one reference build is clearly marked as a reference build.
An admissions CRM that runs alongside the school's existing ERP instead of replacing it
K-12 school group, nine campuses
- Campuses live
- 9
- Campuses live
- Signature to go-live
- 4 weeks
- Signature to go-live
- Insights charts across two dashboards
- 20
- Insights charts across two dashboards
- Manual configuration steps at deploy
- 0
- Manual configuration steps at deploy
Outcome
All nine campuses went live four weeks after signature, with a runbook the client's team can follow without a developer on call.
Frappe CRM
Frappe Insights- WhatsApp Business API
- Meta Lead Ads
- Frappe Cloud
Replacing a legacy HRMS with a payroll run that reconciles to the rupee
IT services firm, Delhi, 30 employees
- Slips in the verified run
- 30
- Slips in the verified run
- UAT cases passing
- 100%
- UAT cases passing
- Statutory heads computed and proven
- 5
- Statutory heads computed and proven
- Per-user licence fees
- 0
- Per-user licence fees
Outcome
In the verified month all 30 slips reconciled to the rupee and every UAT case passed, and there's no per-seat licence to pay.
Frappe HR
ERPNext- India payroll
- Frappe Cloud
An SEO audit of six web properties on four different stacks, five of them with no analytics
Multi-campus education group
- Findings, all reproduced live
- 40
- Findings, all reproduced live
- Properties audited
- 6
- Properties audited
- Carrying no analytics at all
- 5 of 6
- Carrying no analytics at all
- Heaviest mobile page found
- 45 MB
- Heaviest mobile page found
Outcome
Forty findings, each backed by evidence you can reproduce, ranked by how much it costs to leave each one unfixed.
- Technical SEO
- Core Web Vitals
- Google Business Profile
- GA4
- GEO and AEO
A full school group ERP, built to show that fees and accounts can share one ledger
Reference build, not a client deployment
We built this in our own environment to test the design, so the figures below come from seeded data rather than a real school's records.
- Students seeded
- ~3,500
- Students seeded
- Attendance rows
- 68,740
- Attendance rows
- Timetable periods
- 8,580
- Timetable periods
- Database for fees and the ledger
- 1
- Database for fees and the ledger
Outcome
Campus profit and loss, receivables ageing and procurement all sit in the same database as each child's timetable.
- ERPNext
- Frappe Education
- Frappe HR
- Frappe CRM
- Custom PWA
Let's start with a call.
Thirty minutes, free of charge, and you won't sit through a sales deck.