One customer
CRM · invoicing · support · bookings · ecommerce · projects · education
The same record, wherever the relationship shows up. Their unpaid invoice is visible from the support ticket because it is the same customer, not a lookup.
The platform
Separate strengths.Shared purpose.
Every module YionStack ships, on one core.
That every one of them runs on that same core is the only claim on this page that matters, and it is the one you should test — here is how.
The strongest businesses are built from specialists.
Sales focuses on customers. Finance protects the business. HR develops people. Operations delivers the work. Every department has its own strengths, and the software they use should respect that — a finance tool that pretends to be a CRM serves neither.
So the modules below are genuinely specialised. What they do not have is their own private version of the truth. Each one is deep in its own domain and shallow about everything else, because everything else already exists, once, in the core.
That is the whole trick, and it is why this reads as a list of products but does not behave like one.
The map
Every module you need, in one business.
Not a marketplace. Not a constellation of bolt-ons. One product, one database, one operator that knows them all.
YionLedger
Invoices, VAT, statutory accounts, Corporation Tax, Companies House.
YionPayroll
RTI, statutory pay, pensions, auto-enrolment.
YionPeople
Onboarding, leave, shifts, reviews, cases, right-to-work.
Cash
Live position, 30/60/90-day forecast, alerts when runway dips.
Bookings
Appointments, slots, customer-facing booking pages.
25 modules. One database. One operator that knows them all.
Which is the whole point
YionStack is not a bundle of modules sold together. It is one operating system whose modules were never apart — which is why using one of them moves all the others.
YionStack. The future, made possible today.
02Composition
A module is only as good as what it sets off.
The interesting question about any module here is not what it does on its own — it is what happens elsewhere when you use it. That is the difference between a capability and a product.
Sell something in the shop and the stock moves, the ledger posts, the customer record updates, the VAT treatment is applied and the cash position changes. You did one thing.
- An order
- stock movement
- invoice
- ledger entry
- VAT
- cash forecast
- A new hire
- HR record
- right-to-work check
- payroll
- pension duty
- access granted
- An enrolment
- learner record
- tuition invoice
- portal access
- timetable
- attendance
03Where they live
One product, several front doors.
Modules are grouped behind their own workspaces — finance, people, customers, commerce, content — so a bookkeeper is not wading through a marketing calendar and a tutor is not looking at supplier invoices.
These are lenses, not silos. They decide what you see first, never what you are allowed to reach. Ask Yion for something from another part of the business and it answers; it never tells you that you are in the wrong mode.
04Nothing half-wired
The standard every one of these is held to.
A control that does not do the thing it names is worse than a missing one, because it reads as covered. So a module is not finished when its screens exist. It is finished when every action on it completes its full chain of consequences, when the numbers it shows come from real records rather than a placeholder, and when Yion can perform the same action through a typed operation.
That is not an aspiration written on a wall. It is the bar work has to clear before it ships, and it is the reason the list above is shorter than it could be.
One bill, one login, one system
With YionStack you are not buying modules. You are buying the fact that they were never apart.
YionStack. The future, made possible today.
Keep reading