Project, service and ticket on one platform
Client projects, maintenance contracts and service tickets share one data foundation. Hours on project, flat-rate contract or ticket, margin and SLA status live. No isolated silos.
With teamspace, IT systems houses run their project, service and support business on a single cloud platform. Maintenance contracts, flat rates, time and materials, SLAs and hardware orders in one logic. Made in Germany, hosted in an ISO-27001-certified data centre in Frankfurt am Main, GDPR compliant.
Three properties that distinguish teamspace from a tool mix of helpdesk, Excel timesheets and accounting.
Client projects, maintenance contracts and service tickets share one data foundation. Hours on project, flat-rate contract or ticket, margin and SLA status live. No isolated silos.
Recurring maintenance flat rates, licence subscriptions and hosting fees run automatically. Hours consumed beyond the flat-rate quota slip into time-and-materials billing without anyone keeping lists.
Margin per service customer, project and maintenance contract in real time. Threshold alerts surface risks early. Leadership sees aggregated views, service management sees the detail.
Seven steps, one continuous systems house process. The quote becomes a project, the project hands over to service, service produces tickets, every hour lands on the right contract.
Packages for hardware, licences, implementation and maintenance in one quote, with rates per role and flat rates per period. Templates from past orders, no typos, no stale price list.
When the deal is won, the quote turns into a project with phases, tasks, milestones, rates, hardware delivery items and licence subscriptions. No double entry.
Engineers log hours on tasks or phases, on mobile or desktop. Material costs, travel and subcontractor hours land directly on the project. Plan-vs-actual live.
After go-live the project becomes a service contract with flat-rate quota or time-and-materials billing, SLA, response and resolution times. Contracts run with clear renewal dates.
Service requests land in the service desk with SLA monitoring and escalation. Hours booked on tickets, flat-rate quota or time-and-materials billing detected automatically. The customer portal with knowledge base reduces first-level load.
Monthly or quarterly the invoice is generated from maintenance flat rate, time-and-materials hours, licence subscriptions and any hardware add-ons. ZUGFeRD or XRechnung for public-sector buyers.
The service customer remains active in CRM, contract durations, renewal dates and cross-sell potential (e.g. additional module, new location) are transparent. Renewals are not missed.
Systems house software does not fit every constellation. teamspace is a particularly good fit if you recognise several of these points:
From 10 to 150 employees, with a mixed model of implementation projects, managed services and licence reselling.
Recurring-revenue business with maintenance contracts, cloud operations, 24/7 support, SLA-bound response times and on-call duty.
Licence subscriptions, implementation engagements, maintenance and customisation tickets in parallel, engagement structure across group customers.
Pen-test and audit projects, security operations centres with 24/7 monitoring, incident response under SLA pressure, compliance reports as deliverables.
Server and network roll-outs with hardware procurement, implementation and maintenance, reselling business with distributor connections.
From an Excel setup to a structured steering system, without having to swap systems again at 50 or 100 employees.
A comparison for systems houses running today on a helpdesk tool, Excel timesheets, Lexware invoicing and a separate CRM, considering whether consolidating onto one platform pays off.
| Feature | Helpdesk + Excel + tools | teamspace |
|---|---|---|
| Project and ticket on one data foundation | - | ✓ |
| Maintenance flat rate and time-and-materials in parallel | hard | ✓ |
| Recurring invoices | add-on | ✓ |
| SLA monitoring with escalation | limited | ✓ |
| Margin per service customer live | - | ✓ |
| Licence subscriptions automated | manual | ✓ |
| On-call and stand-by | external | ✓ |
| Renewal reminders and contract terms | manual | ✓ |
| ZUGFeRD and XRechnung | - | ✓ |
| Audit trail and compliance | weak | ✓ |
| Hosting in Frankfurt am Main | varies | ✓ |
| ISO 27001 data centre | varies | ✓ |
The most relevant capabilities, grouped by business area. Fully included in every edition, no module surcharge.
Case Study
Hypothetical practice example for illustration. Concrete values depend on starting point, industry and execution and are not guaranteed. A migration scenario from the customer base: a Microsoft partner systems house with 60 employees, two locations in southern Germany, mixed business of cloud migrations, managed services and licence reselling.
Tickets ran in Zammad, hours in Excel per employee, CRM in HubSpot, invoicing in Lexware, licence subscriptions in a separate Excel sheet. Reconciliation at month-end took 2.5 days. SLA reports for customers were assembled manually from Zammad. Service margin became visible only at quarter close, often with unpleasant surprises. Renewal dates were missed repeatedly, costing recurring revenue.
With teamspace, CRM, projects, service desk, time tracking, maintenance contracts, licence subscriptions and invoicing were brought together on one platform. Migration from HubSpot, Zammad and Lexware delivered at fixed price by the 5 POINT AG customer success team. SLA reports are generated from service data, renewal reminders are built into the system. Service margin is now visible daily-fresh.
5 → 1
tools running operations
+11 pts
service margin after 12 months
2.5 → 0.2
days reconciliation at month-end
An IT systems house is neither a pure project deliverer nor a pure service provider but both at the same time. That makes steering complex: the business mixes implementation projects (roll-out, migration, integration) with managed services (cloud operations, monitoring, patch management), service tickets (incidents, change requests), licence reselling (Microsoft 365, Adobe, Atlassian, security) and hardware orders.
Real systems house software has to bring these five worlds onto one data foundation. Classic tool mixes break down precisely there: tickets in one tool, hours in a second, invoices in a third, licence subscriptions in an Excel sheet. Data is merged manually, reconciliation costs days, margin gaps are detected too late. teamspace solves this with a cloud platform on which project, service, ticket, contract and invoice live in the same system.
In the systems house business, service typically follows the project. A cloud roll-out hands over after go-live into a managed service contract. A SAP implementation transitions into a maintenance phase with patches, customisations and user support. teamspace models this transition natively:
That is a meaningful difference from setups in which project and service live in separate systems and the handover has to be reconstructed manually.
Maintenance contracts are the recurring-revenue backbone of a systems house. teamspace runs them with the flexibility the business requires:
Hours are booked on the right contract type, the period invoice combines flat rate, time-and-materials, licence and hardware in one document. ZUGFeRD and XRechnung are standard. More on Invoicing software and E-invoicing.
Service Level Agreements are contractual in the systems house business, often with penalties on breach. teamspace ships the service desk with:
More on Service desk software and Ticket system.
Microsoft 365, Adobe, Atlassian, security and backup subscriptions form a substantial part of recurring revenue in many systems houses. Manually they are a renewal trap: dates get missed, volume changes forgotten, margin uplifts applied inconsistently. teamspace manages subscriptions as recurring invoice items with:
This replaces the Excel workbook in which a single person centrally maintains subscriptions today.
The biggest leverage of integrated systems house software is daily-fresh customer economics. Classic setup: margin appears at quarter close, often with unpleasant surprises. teamspace shifts the picture to:
That makes steering possible before the margin issue lands in the quarter close. More on Project controlling software.
Systems houses often serve sectors with high compliance requirements: financial services, public sector, healthcare, energy. The own systems are in scope of audits. teamspace is:
The contracting party is 5 POINT AG, a German stock corporation, German contract law, no US CLOUD Act exposure, an argument for compliance-sensitive end customers of a systems house.
Moving from the established tool mix to an integrated platform is a migration project. The 5 POINT AG customer success team delivers this migration at fixed price on request:
The fixed-price migration is the alternative to monolithic ERP rollouts with open-ended consulting days.
Wondering whether teamspace is the right systems house software? Instead of an unguided 30-day trial we offer a 15 to 30-minute requirements check with the customer success team. Together we evaluate whether teamspace fits your mixed business of project, service, maintenance and licence, and you see the relevant modules live on a sample customer.
More about the platform on SME business software, Solutions and Features.
Modules systems houses use most.
Tickets, SLAs, maintenance contracts and customer portal in one logic.
WBS, plan-vs-actual, forecast, hardware delivery items on the project.
Recurring invoices for maintenance and licence subscriptions.
Hours on project, maintenance contract or ticket, mobile or desktop.
In the requirements check we discuss your service and project logic, maintenance contracts, licence reselling and billing. You receive a clear first opinion whether teamspace fits, free of charge and without obligation.