A CRM for service companies that run projects and support requests side by side.

Three areas, one system.

The same ticket, the same project and the same invoice all live under the same client, not in three separate tools. For a technical company running development projects AND maintenance contracts in parallel, that means nobody has to open a second tool to see whether a client owes money, whether one of their tickets is pending, or whether their project is close to its deadline.

Work with an estimate first, when you need it.

Every request can start right away, or go through cost approval first. The choice is made when the request is created.

Whatever you build, in the same system as your invoicing.

A support contract keeps its own hour balance.

Recalculated every day

A contract’s balance isn’t a static number. It is recalculated daily from the actual billable time logged on its tickets.

Hosting renewal reminder

Fifteen days before a hosting contract expires, an email goes out to the client automatically with the payment details, so there’s no manual reminder calendar to keep.

Client credentials don’t live in a shared spreadsheet.

Websites, hosting, domains, third-party services: every client has their own password vault inside their portal, with title, URL, username and encrypted password, visible only to people with explicit access. The client adds, edits or deletes entries on their own, so they don’t have to email you their domain password for you to remember it, and the next technician who picks up the ticket doesn’t dig through old messages to find a username.

Which project is at risk, which person is overloaded.

Every active project has a schedule status, calculated from the hours estimated against the hours actually logged, and every team member has their own workload status, from light to overloaded. That matters most when the same technicians handle projects AND support requests together, and a new assignment shouldn’t be made blind: the person in charge sees who has room before assigning the next urgent ticket, instead of asking around one by one.

A client who goes quiet doesn’t go unnoticed.

A client with an active project and no communication for 30 days, or with an active contract and no contact for 20 days, is flagged automatically in a weekly report, before they have to ask “what happened with my site?” or, worse, don’t ask at all and simply leave. In a technical company with dozens of maintenance contracts at once, nobody can keep track of which client has gone silent.