TutorCruncher vs Teachworks: Which One Can You Actually Automate?
Both are good tutoring platforms and both publish an API. The difference that matters if you plan to automate is who can get a key, and on which plan.
By the Elevate team · Built and reviewed against our standards.
Key takeaways
- Both platforms publish a real API, which puts them ahead of a lot of practice software.
- TutorCruncher issues an API key from inside any account, with no plan gate and no approval step.
- Teachworks documents its API well but restricts access to its Growth and Premium plans, so automation may mean moving up a tier.
- Pricing models differ in shape: TutorCruncher uses flat monthly tiers, Teachworks charges a base plus a per-lesson amount, so the cheaper option depends on your lesson volume.
There are plenty of TutorCruncher and Teachworks comparisons covering scheduling, invoicing and payroll. This is not that. This is the part almost nobody writes about, and it is the part you cannot easily change later: what each platform lets an outside system do, and what it costs to turn that on.
It matters because the software you pick determines what you can automate for years afterwards. Plenty of Australian practice software publishes nothing at all, so a booking taken on the phone has to be typed in by a human forever. Both of these are better than that.
Do both actually have an API?
Yes, and that is worth saying plainly because it is not the norm in this category. Both publish developer documentation, both cover the objects that matter operationally, and both can be connected to other systems without a private commercial arrangement.
TutorCruncher
The API key is generated from the Integrations area inside your own account and passed in the request header. There is no partner approval sitting between you and getting started, and no plan gate that we found. Webhooks are available, so changes can be pushed out to other systems in real time rather than on a nightly sync, and there is a Socket server that exposes the same surface if that suits your setup better.
Teachworks
The documentation is good and covers locations, services, employees, customers, students, lessons, tutor availability, invoices and payments. The token is self-generated inside your account under Account and Settings, so again no approval step. The catch is the plan: API access is limited to the Growth and Premium plans. If you are on a lower tier, connecting anything means moving up, and that is a cost on the Teachworks side rather than on your integrator's.
So which is easier to automate?
TutorCruncher, on the narrow question of getting started, because any account can issue a key. Teachworks is not harder to build against once you have access, it just puts a plan decision in front of you first.
That is a genuinely small difference if you were going to be on a mid tier anyway, and a real one if you are a small centre on the entry plan who assumed automation was included.
How do the pricing models differ?
The shapes are different, which matters more than the headline numbers. TutorCruncher publishes flat monthly tiers. Teachworks uses a lower base plus a per-lesson amount, so the cost scales with how much teaching you actually deliver.
The practical consequence: a small centre running a modest number of lessons often pays less on a usage model, and a busy centre running a lot of lessons can find flat tiers cheaper. Work it out against your own lesson count rather than comparing the advertised entry prices, because those two numbers are not measuring the same thing. Both publish current pricing on their own sites, and that is where to check it, since figures in an article go stale.
What should I actually ask before choosing?
- 1.Which plan do I need for API access, and is that the plan I was going to buy anyway?
- 2.Can I create and update lessons through the API, or only read them? Read-only means a human still types every booking.
- 3.Are there webhooks, so other systems learn about a change when it happens rather than the next morning?
- 4.Can I scope what an integration is allowed to reach, and revoke it later without support involvement?
- 5.What happens to my data if I leave, and can I export it myself?
That last pair is worth asking of any practice software, not just these two. The answer tells you how much leverage you keep.
Which should a tutoring business pick?
We are not going to pretend there is one right answer, because there is not, and the automation question is only one input. Broadly, TutorCruncher leans toward multi-tutor agencies with more involved billing and multiple branches, and Teachworks leans toward centres that want straightforward scheduling and management with pricing that tracks their actual volume.
If you already run one of them, both are perfectly automatable. We have written up what connecting an AI receptionist looks like for TutorCruncher and for Teachworks, including where the limits are in each.
If you are choosing now and automation is on your roadmap, ask the five questions above of both, and of anything else you are considering. Book a discovery call if you want a second opinion on what is realistic to connect.
Frequently asked questions
Do I need a developer to use these APIs?
To build a custom integration, yes, or an implementation partner. Both platforms also connect to Zapier, which covers simpler automations without code, though Zapier access still depends on having API access on your plan.
Is the Teachworks plan restriction a dealbreaker?
Only if you were planning to stay on the entry plan. It is a cost to factor in rather than a barrier, and the documentation and the API itself are solid once you have access.
Can an AI receptionist book straight into either one?
That is the point of connecting through the API rather than working alongside it, so a lesson agreed on a call lands in your diary rather than becoming a message for someone to re-key. We confirm the exact scope against your own account during a build. See the TutorCruncher and Teachworks pages.
What if I use something else entirely?
Tell us what you run. Australian practice software falls broadly into systems that publish open documentation, systems with an application-gated partner programme, and systems where integration happens through a direct arrangement. We publish where each one sits on the integrations page.