Invitation only
We are bringing teams on a few at a time.
Every new MADDOX workspace is set up on the team’s own recorded calls and pipeline, with us in the room. That takes attention, so we open the door by invitation. Get on the list, and you will hear from a person when your team’s turn comes.
What happens next
- A person reads your request. Not a queue, not a sequence. What you write is what they read.
- Your invitation comes by email. From an address you can answer, with a real person behind it.
- Setup happens on your data. Your recorded calls, your deals, your team — not a demo dataset that was built to look good.
Already have an invitation? Sign in. Have a question first? Ask it in the form — the same people read it.
Get on the invitation list
What an invitation gets you, and what to expect.
Most teams that ask are looking at whether this replaces a stack of tools they are already paying for. Say what the stack is; it makes for a faster first reply than a demo request.
There is one form on this site and a person reads everything sent through it. Below is what an invitation actually provisions, what a conversation first looks like, and where to go if you are already in.
Get on the list
Tell us about your sales team and what you run today. When your invitation comes, the workspace is set up on your own deals, not a demo dataset. No card.
Talk to us first
Bring a pipeline you already argue about. Say so in the request and we will walk it with you before anything is set up, and tell you plainly whether MADDOX helps.
Already have an invitation?
Sign in and pick up where you left off. Support runs inside the product, on the record, with the same audit trail as everything else.
Why invitation only
Because the setup is the product.
A MADDOX workspace is not a login and an empty pipeline. It is your recorded calls, your deals and your coaching loop, set up so that the first question you ask it has a real answer. We do that with you, a few teams at a time, and it is worth doing properly.
What an invitation provisions.
The workspace, its activity-outcome vocabulary, the six compliance expectation rules switched on at creation, the coaching advice library so the one-on-one engine has words to render, the module registry, your administrator account and a subscription row on the default rung. Provisioning runs as one transaction that either all lands or none of it does, and nothing is seeded lazily on first read.
The expectation rules are activated forward rather than backdated, so a brand-new workspace does not open onto a list of breaches for a period in which nothing happened.
What we do not do to your data first.
No card. Tell us what you want to connect and we stand the workspace up; then put your own pipeline through it, because the fastest way to find out whether this is a fit is to look at records you already argue about rather than at a demo dataset that was built to look good.
If you would rather talk first
Bring a pipeline you already disagree about.
Say so in the request. The useful version of that conversation is not a feature tour. It is us walking your actual deals with you and telling you plainly where MADDOX helps and where it does not.
What we will ask for.
How your team is structured, what is recorded today and by whom, what your managers do in a one-on-one now, and which of your current systems is the source of truth for what. That last one decides more of the answer than anything else.
What you will get back.
Which rung you would need and why, what is switched off by default and would stay off, and the parts of the product we would tell you not to turn on yet. If the honest answer is that you are not ready for this, we would rather say so than send an invitation that goes quiet in week three.
Already a customer
Support runs inside the product, on the record.
Not a separate portal with a separate identity and a separate history.
A ticket is an object in your workspace.
It carries routing rules, a service-level policy and a breach record if that policy is missed, and it sits in the same audit trail as everything else. When a support operator has to look at your workspace to answer something, that session is recorded with their name, their written reason, when it started, when it ended and how many writes it made — and there are surfaces they cannot reach at all regardless of what you ask them to do.
If you are a partner rather than a customer.
Reselling MADDOX to your own clients is a different conversation with a different console behind it. Start there rather than here, and say so in the request.
Questions
The things people actually ask.
Why is MADDOX invitation only?
Because every new workspace is set up on the team’s own recorded calls and pipeline, with us involved, and that is worth doing well rather than fast. Opening the door by invitation is how we keep the setup as good for the fortieth team as it was for the first.
Do I need a card to get on the list?
No. Asking for an invitation costs nothing and commits you to nothing. When the invitation comes, the workspace it provisions is a real one — the module registry, your administrator account, the coaching library and a subscription row on the default rung — not a sandbox with the interesting parts removed.
How long until I hear back?
A person reads every request, and invitations go out by email from an address you can reply to. We would rather not publish a number we cannot keep; what we can promise is that the reply, when it comes, is from someone who read what you wrote.
Can I see it before I commit to anything?
Yes. Say in the request that you want a conversation first and bring records you already disagree about. Walking your own pipeline with us is a better test of the product than a scripted dataset, and a much faster conversation.
Can I import from ConnectWise before deciding?
Yes, through an early-access connector we switch on for your workspace rather than one that runs by default. Once connected, your companies and their agreements sync — names, sites, industry, headcount, contract values, renewal dates and terms — so you can evaluate against your own client list rather than sample data. Autotask and QuickBooks connect the same way. Tickets and dispatch stay in the PSA.