Tellum is a systems integrator
for modular and offsite manufacturers.
Business systems — not the building system.
Your programmes, the line, the yard and your cash live in different places — and someone has to stitch them together every week.
We join what you already run into one live picture.
Nothing gets replaced.
- Revit
- Sage
- Module tracker
- Email & WhatsApp
- +156 systems →
- Programmes — margin live
- Line — modules and WIP
- Cash — month-end builds itself
- Revit
- Sage
- Module tracker
- Email & WhatsApp
- +156 systems →
- Programmes — margin live
- Line — modules and WIP
- Cash — month-end builds itself
The systems your modular and offsite business already runs on.
If it's on this list, we've connected it before. If it isn't, we probably still have — .
You're not unusual. This is what running a contractor at this stage looks like.
“Same module, three systems, three different answers about what stage it's at.”
That's plumbing, not people. We fix the plumbing.
“The change landed at module sixty-two. Sixty-one were already built.”
In a factory, a late change isn't a variation — it's rework times everything in the yard. We log every change against module numbers the day it lands, priced before it multiplies.
“Month-end takes the FD a week and one spreadsheet nobody else understands.”
Month-end shouldn't be a build project. It should already be there.
Wherever you are with your systems, there's a version of this for you.
You're picking or replacing something.
We help you choose the tools that fit how you actually work — not the ones the salesman liked. Shortlist, trial, decision. Then we set them up properly.
You already have the tools. They don't talk, or they don't do enough.
We customise, connect and extend what you run: integrations, missing reports, automations, the layer on top. Then we keep it working and growing with you.
You have the systems. People use half of them.
We teach your team to run the tools you already pay for — properly, and with the automations that make them worth the money.
Most clients start in the middle. Some start with training and never need the rest.
Tools get you level. The layer gets you ahead.
Choosing, connecting and training put the right tools in place — the same tools your competitor can buy. The Tellum Operating Layer is ours: it sits on top of what you run and bends to how you work. A new metric lands in days, a new workflow in a week or two. Nothing gets replaced.
One live picture. Three things on it.
Every programme, cost-to-date against budget — design hours, materials against the BOM, factory hours, site and commissioning — with the change register held against module numbers, priced or not yet.
Nothing gets replaced. Your ERP stays your ERP. We add the layer on top.
Small first step. No migration. Nobody retrains.
We sign an NDA, then walk you through what we'd connect and how. A demo, not a sales call.
We pick the right technical approach and build a working prototype on your numbers — free, typically within 48 hours. Static data at this stage; the live connection comes with the build. You decide if it's worth going further.
Implementation, customisation, the connecting layer, training — the actual engagement begins. Your systems stay where they are; your team keeps working the way it works.
Before and after
Examples of what we can help you with — real engagements, anonymised, names and some details changed.
6 of 6 engagements
About to buy an ERP they'd have spent a year fighting.
Sage 50, a line schedule in Smartsheet, and a dozen spreadsheets in between.
One tracker from order to despatch, Sage kept for the books, the line schedule feeding it — live in six weeks.
Cost per module lived in an eight-tab workbook next to the ERP.
NetSuite for finance, Excel for BOM variance, factory hours and milestone claims.
One portal on top of NetSuite — cost per module live, materials against BOM, changes captured by module number, finance stays in NetSuite.
The line's real pace was a matter of opinion; the yard was a mystery.
Station progress argued at the morning meeting, finished modules counted by walking the yard.
One board: modules per week against takt, WIP by station, blocked stations flagged, yard stock with standing days — pace a number, not an opinion.
Nobody could see enquiries turning into orders and orders turning into factory slots.
Money in QuickBooks, pipeline in HubSpot, the factory schedule on a whiteboard.
One weekly picture: quote conversion, slots booked against capacity, deposits due, cash by client.
Every module needed a handover pack; every pack was assembled the week before delivery.
Station sign-offs in one app, test certificates in folders, photos across phones.
One record per module: sign-offs, tests and photos attached at the station where they happen — handover and vesting evidence ready the day the module is — with workforce and safety reporting alongside.
Three acquisitions, three factories, programmes that didn't line up.
Consolidating P&L and factory load by site took most of the month.
A consolidation layer on Intacct — common module and programme structure, one view of load across factories, month-end in days.
Want to see the layer itself? Same numbers, three front-ends — inside NetSuite, as a modern portal, as Power Apps.
You're probably here the way most of our clients arrive — a colleague passed our name on, or you got a note from me. Either way, good to meet you. If the page doesn't answer your question, ask me directly — I read every reply myself.
Questions we get asked
The stack we see most often in modular & offsite: Revit, Tekla, Bluebeam, Smartsheet, SafetyCulture, Sage — plus Excel, Microsoft 365 and WhatsApp. In total we work with around 160 systems across 21 categories, listed at tellum.works/vendors. If a system has an API, a database or an export, it can be connected.
Pick your first step.
From a free PDF to a working prototype on your own numbers in 48 hours. Pick one — the form below adjusts.