Enterprise is the tier where the software gets built around you. We map how your business actually runs, build whatever is missing, and do the move alongside your team. Nothing about how you work gets bent to fit somebody else's product, and what you need next is what we build next.
We take on a few build partners at a time, and we will tell you where the queue is before you commit to anything.
The parts of your operation that no product covers stop being a spreadsheet and a person who remembers. We build them as real apps inside your workspace, on the same customers as everything else.
We map how you actually work, configure it, do the move alongside your team and train your people on your process. Nobody hands you a login and wishes you luck.
Every place you operate runs the same way, reached from one login rather than a password per site. Each one has every app already working off the same customers, instead of nine tools that email each other. Open a new location and it starts where the others are.
Every business of any size has three or four things no product covers, held together by a spreadsheet and somebody who remembers. That is the part we build. It lands in your workspace as a real app, on the same customers as everything else, and we keep it working.
Discovery is somebody sitting with your team and writing down how the work really moves, including the bits that only happen because Denise knows to do them. That document is what gets built, and you keep it either way.
What we build appears beside the apps everyone gets, on the same customer profiles, in the same permissions model, in your brand. Not a bolted-on portal with a separate login and its own version of the truth.
The twenty-year-old system your industry still runs on, the supplier who sends a fixed-width file, the machine in the yard with a serial port. If it can be reached, it can be wired in.
What we build for you is maintained as part of the platform, not left as a project that rots the first time something upstream changes. It gets the same updates everything else does.
What you need lands as a commitment with a name against it. Build partners get the things they asked for first, because they are the reason those things exist.
The reason most rollouts fail is not the software. It is that the move never quite finished and half the team went back to the old way. So we do the move.
A few sessions with the people who do the work. We come out with a written map of how your business runs, what it runs on now, and what is costing you time nobody has ever measured.
Your apps switched on and set up around that map, plus whatever we are building for you. You see it working on your own data before anyone is asked to use it.
Customers, history, open jobs, invoices and files brought across together and reconciled against what you had, with your team checking the parts only they would spot. Not a CSV template and good luck.
Courses built around how your business works, assigned to your people, so a new starter three months from now learns your way of doing it rather than our menus.
We are there the week you go live, and afterwards you have somebody who knows your setup on a channel you can actually reach.
None of this is the reason to come, but all of it is the reason procurement signs. It is running today, on every workspace, including yours before you speak to anybody.
One customer, one record, however many places you operate from.
A person can belong to more than one workspace already, switch between them from the same login, and each lives at its own address with its own team and data.
An order, a booking, an invoice and a support ticket all land on the same profile, so any app you open already knows them and nobody re-types a customer.
The portal, reviews, chat, help centre, emails and the sites they live on carry your logo, colour and domains. Where you turn it on, CustoDesk is not mentioned.
People arrive with the access they should have, and lose it the day they leave.
Owner, admins and per-member access set area by area: None, View or Manage on each part of the business. Enforced on the server action, not by hiding a button.
Turn it on for the whole workspace and anybody without it is stopped at the door until they enrol, with recovery codes stored only as hashes.
Suspending a member or resetting their password kills every live session on every device immediately, not at their next login.
What procurement will ask for before they sign.
Every data path is scoped by workspace, and a cross-workspace read returns a 404 rather than an error that would confirm the thing exists.
API keys kept as a hash plus a prefix. Connected credentials, email accounts and tax IDs encrypted with AES-256-GCM. Passwords bcrypt, with lockouts on the account and the IP.
One button exports the whole workspace as spreadsheet files, including during a trial, and turning an app off never deletes anything.
Everywhere else, getting bigger is the thing that costs you. Here it is the thing that gets you a better rate.
Headcount never moves the bill, on any of the 27 apps, at any size. For an organisation that is hiring, this is usually the largest single difference from whatever it is replacing.
Per-app rates set for you specifically, flowing through billing automatically rather than living in a side agreement somebody has to remember.
Annual terms cost two months less across every app, with purchase orders and payment terms your procurement team will recognise.
Add one mid-month and it is prorated. Drop one and it stops. Nothing is a twelve-month commitment you argue your way out of.
The published prices we start from are on the pricing page, in the open, like everything else.
A build partnership is people's time, and there is only so much of it, so we take on a small number of businesses at once and we are honest about the queue. Tell us what you run and what you are trying to replace.