Skip to content
Support

We set it up.After that it is yours.

This is a self service product on purpose. We do the build with you once, then we get out of the way. No monthly retainer, no ticket queue to wait behind, and nobody sitting between you and your own system. What replaces all of that is printed further down this page, module by module, with the runtimes.

$210kFive years of a modest retainer

A retainer is a symptom. Platforms that need a permanent services relationship usually need one because they cannot be changed by the people who use them. The monthly fee is not buying you expertise. It is buying you access to the only people who can operate the thing you already bought.

At thirty five hundred a month, which is modest, that is forty two thousand a year and two hundred and ten thousand over five. The number is illustrative. The shape of it is not, because the one thing every retainer has in common is that it never ends.

So the product has to carry it instead. The training has to be complete rather than partial, the walkthroughs have to be there at the moment of confusion rather than in a scheduled session, and changing a workflow has to be safe enough for a non technical administrator to do unsupervised.

Kastor University

The whole curriculum, printed rather than described.

Saying the training is comprehensive costs nothing. Publishing the module list and the runtimes is a commitment, which is why it is here. Seven tracks, one per department, every module indexed by the task rather than by the feature.

Course catalogueAvailable to everybody you hire, on every plan7 tracks · 32 modules
KU 01CRMRevenue teams38 min
Stages, weighting, and what a stalled record looks like7:20
Building a quote and sending it for signature9:05
Ranking and routing, and what the score is made of6:40
Forecasting you can defend in a meeting8:15
Campaigns, and which customers they actually produced6:40
KU 02OperationsDelivery and service41 min
Templates, triggers, and the shapes of work you repeat8:30
Assigning from live capacity rather than from memory7:45
The week view, and how to read an overload6:15
Service cases and the context sheet9:20
Time, materials, and what the job actually cost9:10
KU 03FinanceFinance leads46 min
The period bridge, line by line11:05
Receivables ageing, and what the buckets mean7:50
The forecast, and why it disagrees with your terms8:25
Writing a variance note a board will accept10:40
Margin by customer, by job and by channel8:00
KU 04BillingControllers and receivables33 min
Escalation ladders, set per relationship8:10
Matching, part payments and combined settlements9:35
When the agent stops, and who it hands to6:05
Disputes, refunds and the evidence trail9:10
KU 05PartnersChannel owners29 min
The four relationship types and their terms7:25
Attribution, captured at customer creation6:50
Statements, workings and the awkward adjustment8:35
Reading a partner run rate before it goes to zero6:10
KU 06PeopleHiring managers35 min
Writing a scorecard that holds up under review9:40
Reading a screening record, including one that says no8:20
Onboarding and offboarding checklists7:30
Time off, cover and approvals9:30
KU 07ControlAdministrators52 min
Roles, and what an agent inherits from one9:15
Writing a rule in plain language12:20
Dry running a rule against last period8:45
Approval thresholds, and who gets handed to10:00
Reading the audit trail11:40
Everything, end to end, if one person watched all of it4h 34m

Runtimes are illustrative of the shipped library and each track total is the sum of its modules. Nobody is expected to watch all of it. A finance lead takes forty six minutes and is done.

It is four in the afternoon and somebody is stuck

Three routes to an answer, none of which is a ticket.

This is the only moment that matters. Not the launch week session, not the onboarding pack, but the Thursday afternoon when one person cannot find one thing and has a customer waiting.

Under a minuteAsk in the product

The walkthrough opens the right screen, points at the field, and does the first one alongside you. Available at eleven at night, which is when most owners actually have the time.

Ninety secondsPull the clip

The library is indexed by the thing you are trying to do rather than by feature name, because nobody searches for a feature name when they are stuck.

An afternoonTake the track

When it is not one question but a new seat. The whole track for that role, in one sitting, and then you are the person other people ask.

How setup actually goes

Four phases, and we end at zero on purpose.

Read the bars rather than the words. Our share falls to nothing and yours rises to everything, which is the only arrangement under which the previous section is true.

Who is doing the work
UsYou
DiscoveryOne session
80%20%
Which departments go first, what has to come across, and what your existing systems are. We are looking for the shapes of work you repeat, not a requirements document.
Build and migrateThe bulk of it
55%45%
Records brought across, connections configured, stages and templates set to match how you actually work. Done with you rather than for you, because whoever builds it is whoever can change it.
Train by roleA track each
30%70%
Each team takes the track for their seat. Short, specific, and available afterwards whenever somebody new joins rather than only during launch week.
HandoverWe step back
100%
Your administrator owns roles, automations and workflow changes from here. We step back on purpose, and the walkthrough agent stays inside the product for everybody else.

The last bar is entirely yours. That is not us being unhelpful, it is the test of whether the build worked. If you still need us after handover, something in the first three phases was done to you rather than with you.

How the library behaves

Six things worth knowing about it.

A track per departmentSeven of them, matching the seven departments. A finance lead is not made to sit through the recruiting module to find the close checklist.
Short modules, not long coursesIndexed by the task rather than by feature area, and every one of the thirty two has its runtime printed above.
Updated with the productWhen something changes in the platform the module changes with it, so the library does not quietly become a museum of an older version.
Available to everybody you hireNew starters take the same track their predecessor did, without anyone running an internal session that only happens when somebody has time.
The agent knows the libraryAsk a question in the product and it can point you at the ninety seconds that answers it, or just do the thing with you instead.
Nothing behind a support tierThere is no version of the training reserved for a higher plan. If you cannot operate it, we have not finished building it.
Before you commit to anything

Ask us what happens after go live.

It is the question most platforms answer with a services proposal. Bring it to the call and we will show you the curriculum, the handover point and the day we stop being involved.

KastorBook a demo

See your own week run on one record.

Bring one department and a real week of work. In about thirty minutes we put it through Kastor: an enquiry arriving, moving through your stages, becoming a signed agreement, becoming an invoice, and landing in margin. The same record the whole way, with agents doing the parts nobody should be doing by hand.

  • Your enquiry to cash loop on one record, with the handovers taken out
  • Agents that write the invoice and chase it, not agents that answer questions
  • What your receivables number is today, and what it looks like after
  • Your model running inside your own environment, with the data staying there
No trial signup and no card details One follow up, then we stop Your data stays in your environment We bring the questions, you bring one real week

Request your demo

Five fields and a consent box. We reply within one business day.

How did you hear about Kastor?

We use this to prepare the call and to reply. We do not sell it on or add you to a list you did not ask for.

What happens next

Three steps, and no sales process hiding behind them.

A demo request usually buys you a discovery call, then a qualification call, then a demo. This is one call, and the useful part of it happens in the first ten minutes.

01

A reply within one business day

Two or three times to choose from, and one question back so the call starts in the right place rather than starting at the beginning.

02

Thirty minutes on your own numbers

Not a slide deck. One department, one real week of work, and the loop running against it while you watch. Bring whoever argues with the numbers.

03

You keep the map either way

A written view of every point where your current setup asks a person to carry something between two systems. That is yours whether you go further or not.

Not ready to book anything?

Fair enough. Read the lead to cash page instead. It makes the whole case in about six minutes and asks nothing of you. When it stops being theoretical, the form is still here.

Read that first