Choosing coworking software: 12 workflows to test

A useful software demo starts with a normal day in your space. A member changes a booking. A company adds a teammate. An invoice needs attention. Your next system should make those jobs understandable to the person who actually handles them.

Bring a short list of your own situations to every supplier. Ask to see the steps, then try the important ones yourself. A feature name on a pricing page cannot tell you how much work a task will take.

This guide includes a downloadable demo scorecard. Use it to record what you saw, what still needs checking and what each option would cost your space. It is designed for evaluating any supplier, including Kommonz.

Start with your space

Write down your locations, membership types, meeting rooms, desks and team structure. Include the less frequent situations that matter: a company paying for several members, a guest booking a room, or an event running outside normal hours.

Next, list the systems you use for bookings, invoices, payments, access, accounting and member communication. For each one, note who maintains it and where information gets copied by hand. This becomes your integration checklist.

Choose three requirements that would rule out a supplier if they failed. For one space that might be a particular access system; for another, company billing or support in the language staff use. Keep these separate from conveniences you could live without.

Test the everyday workflows

1. A member books a room

Use a member account to find availability, make a reservation and check its confirmation. Then look at the operator calendar. Can staff identify the member, room, time and booking status? Check the experience on the device members are likely to use.

2. That booking changes

Move or cancel the reservation. Check who can change it, what the member sees, and whether any charge or refund needs a separate action. Try a time that conflicts with another reservation. Have the supplier explain the actual behavior rather than simply saying conflicts are handled.

3. A guest books something

If your space sells to non-members, test that path too. Check account requirements, payment steps, confirmation and how the booking reaches the calendar. Write down transaction charges and who answers the guest if something goes wrong.

4. A member joins and later leaves

Create a membership with the start date and billing arrangement you use. Then ask what happens when it ends. Check future bookings, account access and any remaining balance. A polished signup flow is only half of this job.

5. A company changes its team

Add a person to a company account, then remove them. Inspect who receives invoices, who can make bookings and who can see company information. If team administrators matter to your space, test their permissions using a separate login.

6. A recurring charge is due

Follow one membership through invoice creation, payment and reporting. Ask which steps run automatically and which need staff approval. Use the exact billing timing and payment methods your space supports; a demonstration of another setup may miss the difficult part of yours.

7. A payment needs attention

In a test environment, inspect an unpaid or failed payment. Can staff tell an unpaid invoice from a payment still processing? Check where reminders, corrections and refunds are handled, who can make them and how the history is recorded.

8. An event reaches capacity

For spaces running events, test a member RSVP or ticket purchase and then a cancellation. Ask how capacity, guest information and any payment are tracked. Check whether staff need a separate event tool for requirements that matter to you.

Check the edges of the system

9. A booking reaches another tool

Choose an integration you actually need and follow a change through it. Ask what information is sent, in which direction, how quickly, and what happens when the connection fails. A logo in an integration directory does not establish that your exact workflow is covered.

10. A staff member needs help

Give a colleague a normal task and let them attempt it without the salesperson narrating each click. Note where they hesitate. Ask the supplier to show the relevant help article and explain support channels, staffed hours, implementation help and any additional charges.

11. You move in, or eventually move out

Ask what can be imported, what requires manual setup and who checks the result. Include future bookings, company relationships and outstanding balances in the discussion. Ask for an example export too: which data can you take away, in what format, and with what help? Use the migration checklist to structure this part.

12. Your space grows

Ask for a written monthly total based on your current space and another based on plausible growth. Define the billable unit: active members, all contacts, locations, resources or something else. Record setup, payment, app, integration, support and optional-service charges separately, including which taxes are excluded.

Kommonz’s pricing section explains its own member-based calculation. Apply the same total-cost questions to every option.

Compare evidence, not feature counts

The scorecard uses four simple states: not tested, does not fit, fits with extra work, and fits the task. Beside each result, record a screenshot reference, a short observation or the supplier’s written answer.

Do not turn unknowns into passes. If an essential workflow has not been demonstrated, keep it open. A supplier with more checked feature boxes may still create more work in the three jobs your team performs all day.

Before deciding, have the people who run billing, bookings and member support review the same evidence. Agree who owns each unresolved question and what would count as an answer. Keep the final choice tied to your space’s requirements, not the smoothest presentation.

Why these questions matter

Operator discussions repeatedly return to booking, billing, fragmented tools and help when setup gets complicated. An operator software-selection discussion begins with memberships, payments and room bookings as core needs. A later tech-stack discussion describes the practical work of maintaining separate systems.

These are self-selected public accounts, not a representative survey or a ranking of suppliers. They informed this checklist’s questions. Your own workflow tests should decide which answers are good enough for your space.