One desk for a whole tutoring operation.
Starline Scholars is our first technology partner. We build and run the systems the business operates on: a Windows operations desk for the founder, the hosted system behind it, and the onboarding and payment flow parents actually touch.
Last updated
01 — AT A GLANCE
At a glance.
screens in the desk, from the roster to tutor pay
automated tests over the rules that cost money to get wrong
parts, sharing one definition of the domain
AI models, because the job did not need one
02 — THE PARTNERSHIP
TUTORING
WEEKLY SEATS
FIXED-HOUR COURSES
ONE-TIME PAYMENT
The partnership.
Starline Scholars is a tutoring business. A pupil holds a weekly evening seat with a tutor, works through a course of a fixed number of hours, and finishes. Parents pay once, at the start — no subscription, no invoice to chase later.
That is simple to describe and unforgiving to run. Seats have to be allocated against tutor availability and subject. A pupil leaving has to free their hour, cancel what was scheduled and tell the parent. Tutors have to be paid for what was actually delivered, not what was planned. All of it lands on the founder's week.
AnotherAgent is Starline Scholars' technology partner: one partner across software, cloud and data, from the first build through to keeping it running.
03 — WHAT WE BUILT
FOUR PARTS
ONE DEFINITION
What we built.
The desk the founder works in, the rules behind it, the flow a parent sees, and one shared definition underneath all three.
A Windows application the founder opens each day. The roster, the weekly hour grid, tutors, parents, sessions, payments and tutor pay in one place, with the timetable and the money reading from the same source.
Every rule the business runs on lives server-side rather than on the desktop, so the rules cannot drift between machines and a change takes effect everywhere at once.
A single link takes a parent through their child’s details and the one-time payment. Stripe hosts the payment page itself, so card details never reach our system at all.
The hour grid, seat occupancy, tutor supply, pay rules and course progress are defined once and used by both the desk and the server — so the two can never disagree about what a seat is or what a tutor is owed.
04 — THE DESK, AT WORK
The whole operation, on one desk.
A pupil holds two hours a week for sixteen weeks, then finishes and frees the seat. Around that sit the roster, the week’s sessions, what each tutor is owed, the link a parent uses to enrol and pay, and the payments themselves. Six of the desk’s screens, and the work each one takes off the founder’s week.
Paid for what was delivered, not what was planned — a no-show still accrues, a cancellation does not.
If the confirmation never arrives, the system asks Stripe directly when the parent returns. Nobody who has paid is left looking unpaid.
A schematic of what the desk does — not a screenshot, and not anyone's data. Pupil references are invented for the diagram; the subjects, year groups, 32-hour course and session outcomes are the real model the system runs on.
05 — THE DECISIONS THAT MATTER
The decisions that matter.
This system holds children's names and parents' contact details. That fact shaped the build more than any feature did.
The desktop app holds nothing
No local database, no payment handling, no forms of its own. The desk is a window onto the hosted system, which means a lost or stolen laptop is an inconvenience rather than a data breach.
Personal data is protected at rest
Pupil and parent details are encrypted in the database, and sign-in links are never stored in a readable form. The founder’s own account supports a second factor at login.
Nobody who has paid is left looking unpaid
The payment path is built so a completed payment is always reconciled against the right child, without the founder checking by hand or a parent having to prove they paid.
Tested where it would be expensive to be wrong
The automated tests cover seat allocation, course hours, tutor pay, the payment path and the access rules. They run before anything reaches the business.
06 — FAQ
Frequently asked questions
What did AnotherAgent build for Starline Scholars?
A Windows operations desk for the founder, the hosted system and database behind it, and the onboarding flow a parent completes to enrol a child and pay. The roster, the weekly hour grid, tutors, sessions, payments and tutor pay all run in one place rather than across separate files.
Is there any AI in the Starline Scholars system?
No, and that was the right call. We are AI-first, not AI-only. This work needed a system that does the same thing every time, and a language model would have added risk to work that has to be exactly right.
Where does pupil and parent data live?
On hosted infrastructure we manage, behind a login, never listed or indexed. Personal details are encrypted at rest, and sign-in links are never stored in a readable form.
Does the Windows app hold the data?
No. The desk has no local database and handles no payments — it is a window onto the hosted system. A lost or stolen laptop is an inconvenience rather than a data breach.
Who owns the software at the end?
Starline Scholars does. The accounts, the documentation and the running product are theirs. We stay because they want us to, not because the system cannot run without us.
Tell us the job you would take off your plate first.
Send a few details and we will come back with whether it is a strong fit and what it would take. No obligation, no jargon.