TutorStack handles inside the workflow
- The parent’s lesson purchase through the workspace
- Tracking lessons bought and completed
- Calculating tutor earnings and preparing pay information
Payments and tutor pay
Parents pay before lessons. Your team stops chasing monthly invoices.
After a tutor is matched, parents buy lessons through their workspace before those lessons are delivered. TutorStack tracks what has been bought and taught, then prepares tutor earnings from the lesson record.
How it works
A no-invoice workflow explained in plain English.
TutorStack does not make money move invisibly. It connects the parent’s purchase, the tutor’s lesson log and the administrator’s pay preparation so each stage has a visible record.
- 01
The family is matched with a tutor
The administrator chooses the tutor and creates the assignment before asking the parent to buy lessons.
- 02
The parent buys lessons
The parent pays through their workspace before the recurring lesson schedule begins. This replaces the monthly invoice in the current TutorStack workflow.
- 03
The available lessons stay visible
TutorStack records how many lessons have been bought and prevents the normal workflow from drifting beyond the paid amount.
- 04
The tutor logs the completed lesson
After teaching, the tutor records the lesson. That log connects delivery to the family’s remaining lessons and to the tutor’s earnings.
- 05
Tutor earnings are calculated
TutorStack uses the completed lesson record and the assignment’s tutor share to prepare the pay information for the administrator.
- 06
The administrator completes payment
The business makes the actual tutor bank payment outside TutorStack, then marks the prepared pay record as paid.
Clear boundaries
Payment tracking is connected. Bank payouts are not autonomous.
Clear wording matters here: TutorStack removes a monthly invoice from this workflow, but it does not independently send money from the agency’s bank account.
The business still handles
- Commercial decisions about each assignment
- Any exception or dispute that needs human judgement
- The actual bank transfer to the tutor
Questions
What tutoring agency owners usually want to know
Why do you call it a no-invoice workflow?
Because the parent buys lessons before they are delivered instead of receiving a monthly invoice afterward. TutorStack then tracks the lessons bought and used.
Is this the same as fully autonomous payments?
No. Parent checkout and lesson tracking are connected, but the agency still controls exceptions and completes tutor bank payments itself.
Can a tutor log lessons beyond what the parent has bought?
The current workflow prevents tutors from logging beyond the lessons available for that assignment. This helps bring the need for another parent purchase into view before more lessons are recorded.
Does TutorStack pay tutors automatically?
No. TutorStack calculates earnings and prepares the pay information. The administrator makes the bank transfer and marks it as paid.
What if our agency handles payments differently?
TutorStack is in early access and we are explicitly discussing payment workflows with the first client cohort. A demo is the right place to compare your current process with what is live today.
Related workflows
See how the rest of TutorStack connects
Enquiries and tutor matching
See the workflow that happens before a family is ready to buy lessons.
Explore the workflow →Supervised communication
Keep payment and lesson questions with the relevant parent or tutor conversation.
Explore the workflow →All TutorStack features
Follow the complete operating flow from enquiry through tutor pay.
Explore the workflow →Five early-access places
Compare the workflow with the way you charge today.
We are taking on five tutoring businesses for TutorStack's first early-access cohort.
Tell us where invoices, lesson records or tutor pay currently need manual reconciliation. We will show what TutorStack connects and what remains under your control.