Skip to main content
teamspace

Cloud ERP software for professional services firms: the depth of an ERP, without the ERP project.

teamspace runs in the browser, without your own server and without your own IT team. You roll it out in stages, each productive at once, and extend later without a migration.

Bright scene in the teamspace style: a browser window shows the cloud software, in which the rollout activates one stage after another along a timeline in three steps, start and stage 1 productive, stage 2 just going live. Top right a cloud with a tick for browser operation without your own server. Beside it, greyed out, the classic rollout ERP as a heavy server stack with a long monthly timeline.

Rollout in stages

The depth of an ERP, without fearing the ERP project.

Whoever hears ERP thinks of months of rollout, your own IT and cost long before impact. With teamspace the system grows out of the base setup, stage by stage, and each one is productive at once.

Start Produktiv

Grundeinrichtung

Stammdaten, Nutzer, erste Vorlagen

Etappe 1 Produktiv

Zeit und Projekte

Stunden buchen, Projekte führen

Etappe 2 Gerade live

Rechnung und CRM

Aus Stunden wird der Rechnungsvorschlag

Etappe 3 Folgt

Service Desk

Tickets und Wartung dazu, wenn so weit

Ein Datenstamm trägt über alle Etappen, ohne Migration dazwischen.

Jede Etappe ist sofort nutzbar. Kein Big Bang, kein Stillstand, bis alles steht.

The operating model

Runs in the browser, always on the current version.

Cloud here means above all one thing: you operate nothing yourself. teamspace runs in the browser, can be installed as an app on smartphone and tablet and is always up to date. Operation, updates and backup sit in the data centre.

  • No own server and no operations team to maintain it.
  • Updates without a rollout: new features are there at once, without installation.
  • On every device: in the browser or as an installed web app, at the desk or on the move.

Scope of functions

What makes good cloud ERP software.

Three properties separate it from a classic ERP and from a bunch of single tools.

One basis for everything

Client, project, hour and invoice live in the same system. The quote becomes the project, the hours become the invoice, without an export between four tools.

Modular and growing with you

You activate what you need today and add more later without a data move. light, office and enterprise are configuration, not a migration.

In the browser, no server

teamspace runs in the browser and as an installable app. Operation, updates and backup sit in the data centre, no IT team of your own is needed.

One system

All areas, the same data basis.

What becomes ready to go here is not a bunch of tools in the browser, but a system: projects, time, invoicing, CRM and service work on the same data. Client, project, hour and invoice exist only once.

Projekte

Struktur, Plan-Ist, Forecast

Zeiterfassung

Stunden im Browser und in der App

Rechnung

Aus Stunden wird der Beleg

CRM

Kontakte, Pipeline, Historie

Ein Datenstamm

Kunde, Projekt, Stunde und Rechnung, einmal angelegt

Service Desk

Tickets mit SLA und Portal

Teamwork

Wiki, Dateien, Kalender

HR

Personalakte, Urlaub, Abwesenheit

Arbeitsplatz

Plätze, Ressourcen, Buchung

Ein Login, ein Datenstamm, kein Export zwischen acht Werkzeugen.

Where it sits

Why not a classic ERP project?

Classic rollout ERP

  • Your own server and an IT team that looks after it
  • One big rollout over many months, cost before impact
  • New modules via a migration project
  • Customising by external consultants
Recommended

teamspace cloud ERP

  • In the browser, operation and updates in the data centre
  • Rolled out in stages, productive in weeks
  • Activate a module, without a data move
  • Configuration by the department

What you gain with cloud ERP

One system, ready sooner, growing with you.

The full depth of an ERP, without its weight: all areas on one basis, productive in weeks rather than months, and extendable without migrating again.

One system

One system, no export in between.

Lead, project, hour and invoice run in one logic, on one basis, with one login.

  • No export, no reconciliation scripts
  • One interface for the whole team
  • One contractual partner, one hosting

Pace

Live in weeks rather than months.

Base setup first, then module by module. Each stage is productive at once, no standstill until everything is in place.

  • Start with the areas that have the biggest lever
  • Data and configuration grow with you
  • No big migration in one step

Growing with you

Extend, without migrating again.

From the five-person team to the group with several offices. An edition change is a setting, not a move.

  • light, office and enterprise as configuration
  • New modules without a data move
  • You pay for what is active

Projects and time

Hours land on the project, not on a slip of paper.

The project arises from the confirmed order: order items become subprojects and work packages, hourly rates and billing type are set from the start. Staff log their time directly on it, in the browser or in the app.

  • Log on project, phase or work package, every hour billable or internal with its category.
  • Plan-actual per phase arises from the logs, not from a second list.
  • The structure becomes the billing: the same logs carry the invoice, the record and the margin.
To time tracking

“Staff in both support and project planning can see orders and invoices. That was not possible before.”

A+W Software GmbH was looking for an all-in-one solution instead of dated island tools. Today support and project planning see the same orders and invoices, on one data basis.
A+W Software GmbH

The path of a service

From lead to paid invoice.

One continuous path, without an export between CRM, project tool and accounting: the quote becomes a project, the hours become the invoice.

  1. 1

    Lead and quote

    Contacts, opportunities and quotes sit in the CRM. The accepted quote becomes an order in one click.

  2. 2

    Order and project

    The project arises from the order with structure, hourly rates and billing type, without re-entering it.

  3. 3

    Work and log

    The team logs hours on project, task or ticket, in the browser and in the app, each with its category.

  4. 4

    Approval and invoice

    Approved hours, flat rates and expenses flow into the invoice, the activity record is created automatically alongside.

  5. 5

    Analyse

    Plan-actual, margin and utilisation arise from the same transactions, current to the day, not from parallel spreadsheets.

Seen in the system

How you steer a project in teamspace.

Target, actual and forecast sit on every project, the contribution margin arises from the logged hours. The full project control is ready on its own module page.

Plan vs actual Forecast Margin
May 2026 · current to the day
3 projects

Customer portal · Relaunch

PRJ-014 · 240 h plan

Actual 176 h Forecast 109 %

CRM rollout

PRJ-021 · 180 h plan

Actual 121 h Forecast 96 %

Data migration

PRJ-009 · 90 h plan

Actual 86 h Forecast 98 %
Actual Forecast
1 over plan

Activated by module

What is active is what is needed.

You start with the areas that have the biggest lever today, often time tracking and billing. You switch on further modules later, without migrating data. Configuration and data store grow with you.

  • light, office and enterprise build on each other, an edition change is a setting.
  • From the five-person team to the group with several offices, the same logic.
  • You pay for what is active, per activated user per month.
See pricing

From the hour to the invoice

The invoice arises from approved hours.

At the end of the period the project lead approves the hours. The invoice arises from the approved, billable hours, the flat rates and the expenses, without an intermediate export.

  • Approval per project or period: first checked, then locked, then billable.
  • Activity record automatically as an annex to every invoice that bills time.
  • ZUGFeRD and XRechnung without an extra tool, the handover to DATEV runs over the certified interface.
To invoicing software

First call

Let us look at your processes.

Bring a typical flow, from quote to invoice. In the first call you see which modules have a lever first and what the path through teamspace looks like.

Book a call

Service desk

Tickets with a promised response time.

Many professional services firms run the ongoing service alongside the project: maintenance, support, small changes. Whoever has promised a response time for it needs it in view, not in the contract folder.

  • SLA per client, held in the CRM, attaches itself to new tickets automatically.
  • Remaining time as a traffic light, coloured by urgency; the warning comes before the deadline, not after.
  • Service time logged on the ticket, billable with its category, billed at the end of the period.
To the service desk

CRM

The customer history in one place.

Emails, calls, appointments, quotes and logged hours land on the same contact. Whoever opens a customer sees the whole story, without searching in five tools.

  • Organisation, contact and transaction as the base structure, and from it the complete customer file.
  • Sales pipeline and ABC classification, the quote becomes the project in one click.
  • Microsoft Teams and Outlook can be connected, appointments and calls attach themselves to the contact.
To the CRM

Seen in the system

From quote to paid, one document chain.

Quote, order, invoice, open item and payment hang together as one chain, on the same data rail from CRM, time and project. No document starts from zero.

  1. Angebot 01

    AN-2026-0042

    offen
  2. Auftrag 02

    AB-2026-0031

    beauftragt
  3. jetzt fällig
    Rechnung 03

    RE-2026-0051

    gestellt · fällig
  4. Offener Posten 04

    Mahnstufe 1

    erinnert
  5. Bezahlt 05

    Zahlungseingang

    ausgeglichen

Aus denselben Daten

CRM-KontaktGebuchte ZeitProjekt

Eine Kette: jeder Beleg kennt seinen Vorgänger und seinen Nachfolger.

Who benefits

Which teams gain the most.

One system on one data basis pays off differently for each role. Three views we hear especially often.

Management

  • No own server and no IT team to run it
  • Ready in stages, the cost grows with the benefit
  • One contractual partner, one hosting, one login

Project and team leads

  • Plan-actual per project from the logged hours
  • Utilisation and forecast in one place
  • Less coordination, more overview

Staff

  • One interface instead of constant tool switching
  • Log in the browser or in the app
  • Clearly structured processes, less searching

Comparison

Classic ERP versus cloud ERP from teamspace.

Both bring depth. The difference lies in rollout, operation and extension.

Feature

Classic ERP

teamspace cloud ERP

Recommended
Operation in the browser, no own server
Productive in weeks rather than months
Activate a module without a migration project
Projects, time, CRM and invoicing on one data basis
partly
Configuration by the department
consultant
ZUGFeRD, XRechnung and certified DATEV interface
varies
Hosting in an ISO 27001 data centre in Frankfurt
varies

What matters

Three things that make the difference.

Highlight 1

Log where the work happens.

Staff log in the browser, in the app or on the tablet, on project, task or ticket. Every hour carries its category, billable or internal.

Highlight 2

One data store, no export.

Client, project, hour and invoice exist only once. What begins in sales carries through to the analysis, without a CSV in between.

Highlight 3

Grow without migration.

The department switches on new modules, the edition change is configuration. The system grows with the firm.

First call

See teamspace on your own processes.

Show us a typical flow. We show which modules have a lever first, what the stages look like and where your current setup is already enough.

Why teamspace

What stands behind the software.

From Darmstadt since 1999

We have been developing teamspace in Darmstadt for over 25 years, self-financed and without outside capital. More than 20,000 users in around 400 companies work with it every day.

Hosting in Frankfurt

Operation in two geo-redundant, ISO 27001 certified data centres in Frankfurt am Main, data processing exclusively in the EU. The data centre is certified, not teamspace itself.

One system instead of island tools

Project, time, CRM, service and invoicing work on the same data basis. No export between tools, and one contact who knows your processes.

Case Study

From the tool zoo to one system.

Hypothetical practical example to illustrate how it works. Concrete values depend on the starting point, industry and implementation and are not guaranteed. A typical switching scenario: a project-based professional services firm with 60 staff that runs CRM, projects, time tracking and invoicing in separate tools.

Starting point

Leads lived in the CRM tool, projects in a second, hours in a time-tracking app, invoices in accounting. Between every step lay an export. Analyses arose from spreadsheets that someone merged at the end of the month, and were two weeks old by the time they were read.

Solution

Today sales, projects, time and billing run in one system. The quote becomes the project, the hours become the invoice, the activity record is created automatically. The rollout ran in stages: first time and projects, then invoicing and CRM, without a standstill and without a migration in between.

1

system instead of four separate tools

0

exports between the steps

current to the day

numbers, not only at month end

Security

Customer data stays in Frankfurt.

Projects, quotes and customer files hold sensitive things: terms, strategies, internal numbers. teamspace processes this data exclusively in the EU.

  • Hosting in an ISO 27001 certified data centre in Frankfurt am Main. The data centre is certified, not teamspace itself.
  • GDPR compliant with a data processing agreement; encryption via TLS, storage encrypted in the data centre.
  • In GoBD mode approved invoices and documents stay audit-proof for over ten years.
  • The contractual partner is 5 POINT AG, a German public limited company based in Darmstadt.

What cloud ERP software has to do

The depth of an ERP on one data basis, in the browser.

Cloud ERP software is an integrated business software that runs in the browser and carries the core processes of a company on one data store: sales, projects, time, billing and service. The word cloud stands for the operating model, no own server, no own operation, always on the current version. It is activated by module, what is needed.

teamspace is the ERP for professional services firms whose value creation arises from the work of their people. Materials management, warehousing and production stay deliberately out of scope; posting data goes to DATEV over the certified interface, the accounting stays with the tax adviser. This is how the depth of an ERP arises, without the weight of a classic ERP project from production and trade.

Module overview

The modules that form the ERP.

Nine areas mesh together on one data basis. Each has its own page with all the details.

Project management

Structure, plan-actual, forecast and capacity planning across all projects.

Learn more

Time tracking

Working and project time in the browser, in the app or on the tablet terminal.

Learn more

Invoicing software

From hours and flat rates to the document, with ZUGFeRD, XRechnung and DATEV.

Learn more

CRM software

Contacts, pipeline and customer history, the quote becomes the project in one click.

Learn more

Service desk software

Tickets with an SLA traffic light, customer portal and escalation, service time billed directly.

Learn more

Teamwork

Team calendar, company wiki, file and document store, Teams and Outlook integration.

Learn more

HR software

Digital personnel file, leave, sickness and cover in one team calendar.

Learn more

Workplace management

Book desks, rooms and resources, for hybrid teams and desk sharing.

Learn more

Quality management

Document control, approvals and audit-proof versions for your QM.

Learn more

Scope of functions

Functions at a glance.

Activatable by edition, all on one data basis.

Operational

  • Project structure with phases, tasks and work packages
  • Time tracking in the browser, in the app and on the tablet terminal
  • CRM with pipeline, contact history and ABC classification
  • Service desk with an SLA traffic light, customer portal and escalation
  • Teamwork with wiki, files and calendar

Billing and finance

  • Fixed price, time and material and flat rate on one order
  • Activity record automatically with the invoice
  • ZUGFeRD and XRechnung without an extra tool
  • Recurring contracts for recurring invoices
  • Handover to DATEV Unternehmen online

Cloud and operation

  • Web interface in the browser and installable PWA
  • Activatable by module: light, office, enterprise
  • Extend without data migration
  • Hosting in an ISO 27001 data centre in Frankfurt
  • GoBD mode with audit-proof retention

Terms

Six terms around cloud ERP.

Words that come up again and again when comparing cloud ERP and classic ERP.

Cloud ERP
An integrated business software that runs in the browser and carries the core processes on one data store. Cloud means the operating model: no own server, always up to date.
One data store
Client, project, hour and invoice exist only once. Each area works on the same data basis, instead of reconciling data via export.
Modular activation
Functions are switched on via the edition, from light through office to enterprise. An extension is configuration, not a data migration.
PWA
Progressive web app. teamspace can be installed on smartphone and tablet like an app, but runs in the browser, without an entry in an app store.
Time to value
The time to first productive use. Rolled out in stages, most teams work productively after a few weeks, not only after months.
ERP for professional services firms
An ERP for companies whose value creation arises from work: projects, hours, service. Without materials management, warehousing and production, and easier to roll out for it.

Who the cloud fits

Which professional services firms teamspace is tailored to.

teamspace is built for project-based professional services firms with 5 to 250 staff. Each industry has its own page with fitting examples.

Management consultancies

Engagement structure, fee models, consulting days and utilisation across practices and offices.

Industry page

IT service providers

Sprint deliveries, maintenance contracts, recurring invoices and service desk with SLA.

Industry page

Systems house

Projects, managed services, tickets, maintenance contracts and licence resale on one platform.

Industry page

Agencies

Budget management, media budgets, freelancer steering and creative shops with mixed billing.

Industry page

Architecture and engineering offices

HOAI phases, hour accounts, fixed-fee contracts with amendments and travel expenses.

Industry page

Who it is built for

Which companies teamspace fits, and which not.

Fits less well

  • Production and manufacturing with bills of materials and material scheduling.
  • Merchandise management and trade with warehouse and stock.
  • Very large groups with their own ERP operation.
  • Pure financial accounting without a project and services business.
Recommended

Fits well

  • Project-based professional services firms whose value creation arises from work.
  • Growing firms that roll out modules step by step rather than in a big bang.
  • Mid-market without a large IT team, from the small team to several hundred staff.
  • Companies that want lead, project, time and invoice on one basis.

Frequently asked questions about cloud ERP

How is teamspace different from a classic ERP?
Classic ERP systems are designed for large enterprises, high standardisation and long rollout projects. teamspace is cloud ERP for project-based professional services firms: faster to get going, activatable by module, operable in the browser, without your own IT team. We cover the core processes a company between 5 and 250 staff needs, without ending up in the complexity of classic ERP.
Do we have to roll out all modules at once?
No. You start with the areas that have the biggest lever today, often time tracking and billing. You activate further modules step by step, without data migration. Configuration and data grow with you. Extending later is not a migration.
How safe is our data in cloud software?
teamspace is operated in two geo-redundant data centres in Frankfurt am Main, data processing happens exclusively in the EU. Operation runs in an ISO 27001 certified data centre, GDPR compliant, with an activatable GoBD mode. The data centre is certified, not teamspace itself. The contractual partner is the German 5 POINT AG.
Can teamspace be connected to our accounting?
Yes. There is a DATEV-certified interface to DATEV Unternehmen online as well as REST APIs for custom connections. Incoming invoices can also be captured digitally and handed over via DATEV. You keep your financial accounting system and automate the bridge.
Do we need our own IT to run teamspace?
No. teamspace runs in the browser and as an installable web app, the operation sits in the data centre. There is no own server to maintain and no installation to roll out, updates are available at once. An IT team of your own is not needed.
What does cloud ERP from teamspace cost?
The prices given are annual prices per activated user per month, depending on the chosen module package. A shorter term carries a surcharge: plus 10 percent half-yearly, plus 15 percent quarterly, plus 20 percent monthly. No setup fee. Notice period: 3 months on an annual term, 1 month on a monthly term. We discuss the fitting edition in the 15-minute call.
How long does the rollout really take?
From experience the base setup is in place within a few days. After that the modules come step by step, each stage is usable at once. Most teams work productively after a few weeks, not only after months as with a classic ERP rollout. Our team handles the data migration from existing systems on request.
Is teamspace a classic ERP or industry-specific?
It is the ERP for project-based professional services firms. Leaner than a classic ERP from production and warehousing, but with project, time, CRM, service and billing in one logic. Materials management, warehousing and manufacturing are deliberately not the focus, which makes the rollout easier.
Can we use teamspace on mobile?
Yes. teamspace runs in the browser and can be installed as a web app (PWA) on smartphone and tablet, with its own app icon. There is no entry in the app store, and no native app either; the web app covers mobile use.

First call

Cloud ERP reviewed in 15 minutes.

In 15 to 30 minutes we discuss your processes and suggest an order for the rollout. You hear a clear assessment of whether teamspace fits. Free and non-binding.