MSP software for the business side.

No. Spodus runs the business side: the client list, the ticket queue, the contracts and the billing. Keep your monitoring and remote access tools for the endpoints; this is what replaces the PSA, the CRM and the invoicing tool around them. There is no RMM integration either, so alerts do not become tickets on their own.

Yes. A CRM for MSPs is one record per client company with the contacts, the contract, the renewal date and the open tickets on it. Spodus adds the invoices to that record, so an engineer opening a ticket sees what the client pays for. Deals run through stages you name, and a renewal date can send the follow-up you wrote.

Yes. A CRM for IT services companies needs the account, the project quote and the support queue on one record, because the same client raises all three. Spodus does that. Project work goes out as an estimate and becomes an invoice when it is accepted. Monitoring and remote access stay in your RMM, where they belong.

It covers most of what a PSA for small MSPs does: clients, contracts, a ticket queue with SLAs, recurring billing and a client portal. Two things it does not do: hours on the timesheet do not flow onto an invoice, and there is no RMM integration. If you are under about forty people and bill flat monthly plans, you may not miss either.

Yes. Help desk software for MSPs needs a shared queue, an owner and a priority on every ticket, response targets per priority, and a portal where client staff raise their own. Spodus has each of those, and every ticket shows the account's plan and payment status. Client staff use the portal without holding a seat.

Yes. Every request becomes a ticket in one queue with an owner, a status and a timer against the target you set for its priority. Tickets arrive from the portal or from an email address you forward in. Saved replies handle the questions you answer every week. A ticketing system for IT services also needs the account attached, and here it is.

Yes, for the invoicing side. IT services billing software has to raise the monthly plan on its own and quote project work separately, on the same client. Spodus does both: a recurring template for the plan, an estimate for the project, and payments recorded against each invoice. There is no bank feed and no double-entry ledger, so your accountant keeps theirs.

Yes. Recurring invoicing for MSPs is a template per managed plan. Set the amount, the lines and the day, and the invoice is raised as a draft on that day whether or not anyone signed in; you check it and send it. Record the payment against it and the balance updates. It is not usage metering: a plan that changes with device count is edited by hand.

No. Portal users are free and unlimited on every plan. You pay per engineer and admin doing the work, not per client contact. A client with two hundred staff who raise tickets through the portal costs exactly what a client with two does, because none of them holds an account.

The clients yes, the tickets no. Companies, contacts and deals come in by CSV, a spreadsheet or a guided import, with your stages and custom fields mapped across. Tickets are conversations rather than rows and there is no importer for them, so the queue starts clean and your open ones stay where they are until they close.

Yes. Forward the address your clients already write to and each message opens a ticket in the queue with an owner, a status and a first-response timer. One thing to know first: replies go out from Spodus's own sending address, not from yours. The client sees the reply, and the thread stays on the ticket.

No. Contacts, companies and tasks are there from the first minute; the help desk, invoicing and the HR side switch on when you want them. Turning one on later brings back its screens with whatever is already in them. Start with the queue. Switch billing on at the next month end.