Built for the device the student actually has.
Education software is designed on fast laptops and used on old phones, often shared, often on patchy connections. It is also used by three different people with three different needs, a student, an instructor and an administrator, and most platforms are excellent for one of them. Getting this right is less about features than about weight, clarity, and admitting that the administrator's Tuesday is the hardest problem in the building.
The problems that are specific to this sector.
The device is not the one you tested on
A page that takes eleven seconds on a mid-range phone on mobile data is a page that loses the applicant. Performance is an access issue in this sector, not a polish issue.
Admissions is a seasonal spike
The system sits idle for months and then takes a year's traffic in a fortnight. Building for the average and discovering the peak in public is a very specific kind of bad week.
Three audiences, one system
Students, faculty and administrators want opposite things from the same screens. Separating them properly is the difference between a platform people use and one they email around.
What we build for edtech
- Prospectus and admissions sites with genuinely working enquiry and application flows
- Student portals: results, timetables, fee status, and documents without a phone call
- Learning platforms with courses, assessment, progress tracking and certificates
- Administrative tools for enrolment, attendance, scheduling and reporting
- Payment and instalment handling for fees, with the reconciliation the finance office needs
What shapes the build
Requirements we design against in this sector. These describe obligations that apply to systems like yours — they are not claims that we hold a certification.
- Accessibility to WCAG 2.2 AA, which for public and publicly-funded institutions is frequently a legal requirement rather than a preference
- Student data protection under FERPA in the United States and GDPR in Europe, including who may see a record and how long it is kept
- Performance on low-end devices and constrained connections, treated as a requirement with a number attached rather than as an aspiration
- Safeguarding and age-appropriate design where learners are under 18
The engagements this usually begins with.
Each says who it is for and, more usefully, who it isn't.
Web Development
Custom, responsive websites and web applications that load fast and convert the traffic you already pay for.
What this involves ›Custom App Development
Internal software for the work your business actually does: portals, back offices, and the operations tools no vendor sells.
What this involves ›SEO Services
Technical and on-page work that gets you found by the people already searching for what you sell.
What this involves ›CMS Development
Headless content platforms your marketing team can run at speed, without a ticket and without breaking the layout.
What this involves ›Work we've done in edtech.
Three law campuses, one admissions front door
A law college group running three campuses across Punjab was answering the same admissions questions by phone, all day, from applicants who had found them by word of mouth because there was nothing else to find.
Read the case study ›Enrolment growing, completion flat
An online provider moves every learner through the same fixed sequence, so the ones who already know module three are bored and the ones who did not understand module two are lost. Mastery based pathways fix both without removing instructor oversight.
Read the case study ›The pilot worked. Procurement is a different product
A learning tool with happy users and a successful pilot meets its first institutional buyer and discovers that single sign on, roster sync and a data protection review are the actual product. Getting there does not have to mean the rewrite most pilots trigger.
Read the case study ›The ones this sector actually asks.
Can you integrate with our student information system?
Where it exposes an API or a scheduled export, yes. A good number of institutions run something with neither, in which case the honest options are a narrow integration layer or a defined manual step, and we will name which one applies before quoting.
We are a small college. Is this affordable?
A prospectus and admissions site is a considerably smaller build than a full learning platform, and it is usually where the return is clearest. We scope the first phase to the enquiries you are currently losing rather than to the platform you might eventually want.
Do you build on Moodle or Canvas?
We integrate with them and build around them, and where one of them would do the job we will say so rather than quote a replacement. Custom makes sense when the way you teach or assess does not fit what they assume.
What is the most expensive thing your team still does by hand?
Tell us, and we'll tell you honestly whether software can fix it, and roughly what it would cost. No pitch deck.