Industries we serve, and what we have shipped in each
Boffin Coders builds software for five sectors: schools and coaching centres, estate agencies, online stores, clinics, and streaming. Each sector page says what is running with a client, what is built and ready to run, and how we approach the rest, because a buyer needs to see the method as well as the proof. The code changes less between industries than the rules and the systems it talks to.
Projects from US$4,000. A dedicated developer from US$2,000 a month, depending on the stack.
Software with the stage stated
A computer-delivered exam platform running live for a coaching institute since June, marking on submission with AI feedback a teacher can overrule. A school management suite with a parent app, finished and ready to run in a school's own accounts. And twenty-nine agreed specifications for everything a school does beyond the classroom, from admissions to the hostel, built to your scope.
Every capability on our education software page says where it stands: running with a client, or built and ready for a school. Anything else is scoped on a call, with the method written down before the quote.
Where it stands
- Live: exam platform with a client
- Built: school suite and parent app
- Built to your scope: admissions to hostel
- You keep the source code
A better front-end for the CRM you already have
For agencies with three to thirty branches whose CRM gave them a template site. The site we build reads listings from Reapit, Alto, Street, Rex or VaultRE through the CRM's documented API, builds property and branch pages that rank on your patch, and writes every enquiry back into the CRM. The CRM stays. The front-end stops embarrassing you.
The method, stated: every CRM we connect to publishes a documented interface, and we test against its sandbox where one exists. That is why the estate agency website page lists those systems by market with the interface each one documents, and labels its mock-ups as design work. Studios that sell sites to estate agents can have it built under their own brand.
Where it stands
- Listings read from your CRM API
- RESO Web API (North America)
- Portal feeds
- Your CRM stays
Build the store, then make it found
We have done Shopify builds for Classy5, Office Furniture Scotland, DATACOM, TITI Atelier and TESPEX, and a custom store on Node, React and MongoDB for Hooaah. We have also run search for an accessories store and published what changed, which is the half of the job most store builders hand to someone else.
Which platform fits depends on the stage you are at: Shopify or WooCommerce to start, headless once a store has outgrown its theme. Our ecommerce development page sets out when each is worth its running cost. It does not promise sales, and neither do we: we make a store fast and findable, and the product and the price still sell it.
Where it stands
- Built: Shopify stores for clients
- Done: search for a store
- Card data stays with the payment provider
- WCAG 2.1 AA target
Clinic and patient software, controls you can check
Patient portals, booking, practice systems, and AI that drafts a note a clinician reviews before it goes anywhere. What is live: Clinevo, a healthcare services website we built in Next.js and Node, and a search and redesign project for Praxis Dreierlei, a physiotherapy practice whose owner reviewed us on GoodFirms.
Much of our client work is under NDA, so we walk you through the architecture on a call: access by role, audit logs, encryption, and the data in your own cloud account. The healthcare software page sets out that approach before the first call, and says what does transfer from other sectors, such as speech to text that keeps the recording on your own server.
Where it stands
- Live: Clinevo healthcare website
- Done: Praxis Dreierlei search and redesign
- Standards: HL7 or FHIR where offered
- No patient data on our side
Streaming apps, from what we have shipped
We have built and shipped Flutter apps on both stores, among them Video Splitter, which cuts video on the phone without uploading it. We also run a speech pipeline that writes text from audio on our own server, which is the job subtitles need.
A DRM-protected streaming platform, TV apps, server-side ad insertion and live events: our OTT platform page sets out how each is built. A managed video provider runs encoding, DRM licences and delivery in your account, we build the apps, accounts and catalogue around it, and the quote says which lines the provider covers and which we build.
Where it stands
- Live: apps on both stores
- Running: speech to text on our server
- DRM: through a managed provider
- TV apps: Android TV and Fire TV
Running a clinic, a trade, a law practice or a garage, and need local customers rather than software? That is our local SEO services line, one monthly package.
The code is similar. The rules and the systems are not
Vendors sell industry expertise as though the software were different. It mostly is not. What differs is what the software has to respect, what it has to talk to, and what the data is. Those three columns are where a project goes wrong.
| Sector | Rules it must respect | Systems it talks to | What the data is |
|---|---|---|---|
| Education | Child-data rules by country, accessibility | LMS and SIS platforms, single sign-on, payment plans | Student records. Access controlled per role, never bulk-exported. |
| Estate agency | Portal feed specs (RTDF, REAXML), local advertising rules | Reapit, Alto, Street, Rex, VaultRE. RESO Web API in North America. | Listings and enquiries, read from and written back to the CRM. |
| E-commerce | Consumer law, payment standards, tax by market | Shopify and Shopify Plus, WooCommerce, ERP, stock and shipping providers | Orders and payment tokens. Card data never touches our code. |
| Healthcare | Health-data law where the clinic operates, advertising rules for clinicians | Practice management and booking systems, records systems over HL7 or FHIR | Special-category. Stays in the client's own accounts. We never host it. |
| OTT and IPTV | Content licensing by territory, age rating, store rules on subscriptions | Managed video providers, CDNs, DRM, players on phones, web and TV | Viewing telemetry, aggregated rather than personal where possible. |
What actually differs, in one paragraph
Industry software differs less in code than vendors suggest. What changes is the rules it must respect, the systems it must talk to and the kind of data it holds. A clinic system handles health data and talks to practice systems. An estate agency site reads listings from Reapit, Alto or Rex and writes enquiries back. A school system holds children's records under role-based access. Boffin Coders prices all of it the same way: projects from US$4,000, a dedicated developer from US$2,000 a month.
What people ask about industry work
Whether we work outside these five, what actually differs, who holds the data, what it costs, and whether we build under an agency's brand.
No. These five have their own pages because each has rules and systems worth writing down. Each page says what is running with a client, what is built and ready to run, and how we build the rest. In education we have a platform in daily use. In healthcare and streaming those pages set out the architecture, the checks and the handover, and where client work is under NDA we walk you through the approach on a call. Work outside the five is priced and built the same way.
Not answered here?
Tell us the system you run now
Twenty minutes with the person who would build it. We tell you what your current system's API can give us before we quote.