Choosing coworking software: 7 workflows to test in a demo

1. A membership change that preserves its history

Start with an example that resembles your agreements: a company with several people, an agreed fee that differs from the list price and a change starting on a future date.

Try it in the demo: Add the company and its people. Show the plan and fee that apply now. Propose a change and follow what happens when it is confirmed, takes effect or is withdrawn.

You should understand: Who holds the membership, which company they belong to, which fee applies and what changed. A new list price should not make an existing agreement unclear.

Ask how previous terms and upcoming changes are displayed. Read how Cohuba connects members, companies and plans.

2. A room booking with a price you can explain

Availability is only part of a booking. You also need to understand the price, discount and what happens after a change or cancellation.

Try it in the demo: Book the same room as a member and as a guest. Show the price before confirmation, attempt an overlapping booking and cancel with a reason. Then change the room's price and check how the earlier booking is displayed.

You should understand: Which time is booked, which pricing rules were used and which fee was agreed. Hourly rates, day rates, member discounts and extras should be distinguishable. Also confirm whether displayed prices include VAT.

Ask how cancellation history and later price-list changes are handled. See Cohuba's approach to room bookings and prices.

3. A visit pass that counts the right thing

Visit days, room-booking allowances and payments represent different things. A visit-pass balance does not by itself establish how many meeting-room hours a member can book or whether an invoice has been paid.

Try it in the demo: Give an example member a balance of visit days. Register a visit, attempt a duplicate registration and correct a mistake with an explanation. Then open a room booking and show how any booking terms are handled separately.

You should understand: What unit the balance uses, how it changed and whether the member can understand a correction. Ask to see what happens when the balance runs out.

Write down your visit-day rules separately from your room-booking rules. That makes it easier to compare the same requirements across providers.

4. A member completing a task on their phone

Staff administration and a member's everyday tasks have different needs. Try a real member login, rather than only a smaller image of an administrator's screen.

Try it in the demo: Have a member sign in on a phone, find their membership information and practical information about the space, and book a room. Change the language and follow the route back to the booking.

You should understand: Can the member complete the task without staff assistance? Can they access only the information and actions appropriate for their role?

Also ask to see how staff and an external issue recipient differ from a member. The different ways into the system should have clear access boundaries.

5. An issue with a person responsible for the next step

A broken piece of meeting-room equipment can easily become an email thread someone has to coordinate. Test how an issue moves between the reporter, staff and the person responsible for resolving it.

Try it in the demo: Report an illustrative issue with a photo. Assign responsibility, write a shared comment and add an internal note. Then open the issue as a member or external recipient and check what that person can see.

You should understand: Who owns the next step, what can be shared and how you know the work is complete. Ask what happens when an assigned person loses access.

If you need recurring checklists or automatic reminders, ask the provider to demonstrate the actual workflow and explain what is available today.

6. AI and MCP that respect operational permissions

MCP can connect compatible AI tools to functions and data in an operational system. Assess that support together with the connection, available tools and the user's permissions.

Try it in the demo: Start with a read request, such as “Show our current membership plans.” Then walk through an action staff would like to perform with AI assistance. Show which information is required and how the change appears in the normal system.

You should understand: Which user is the AI tool acting for? What can that user read and change? Revoke access as well and check what happens to the connection.

Ask which AI tool the connection supports, what configuration it requires and how you decide when changes may be made. Cohuba's current MCP setup requires configuration and an authorized staff login. Read more about AI and MCP in Cohuba.

7. A setup with agreed responsibilities and financial workflows

A successful setup starts with your existing records and agreements. Walk through how they enter the system and which tasks remain with your team or other tools.

Try it in the demo: Follow a member, an agreed fee and a room through setup. Ask to see the information used for invoicing and the steps required to handle a payment.

You should understand: Who helps with the import, who checks the result and which integrations exist today? A calculated fee is not the same as a created invoice or a recorded payment.

Clarify support, access to your records and how you can obtain the information you need if you move systems later. Write down who owns each manual step.

Bring a simple checklist to every demo

Use the same examples with each provider. Mark each area as demonstrated in a working flow, requires manual work or missing today. Add the person responsible for the next step.

Memberships

Current terms, a future change and history

Room bookings

Price before confirmation, conflict and cancellation

Visit passes

Balance unit, registration, correction and an empty balance

Member portal

A completed mobile task with the right permissions

Issues

Responsibility, shared comments and internal notes

AI/MCP

A working connection, permitted actions and revoked access

Setup and finances

Import, invoicing information, integrations and manual ownership

Choose the workflows that matter most to your space. A useful decision record makes it clear both how the system helps and which work remains.

What does this mean for Cohuba?

Cohuba brings membership administration, room bookings and daily operations together with a member portal in Swedish and English. We offer assisted setup and walk through the approach with you.

Cohuba's current first release has defined boundaries. Automatic subscription payments, a Fortnox integration, recurring checklists and a general OAuth connection for AI clients are not included in the published offering. Walk through your requirements and financial workflows with us before deciding.

Book a personal Cohuba demo and bring the situations you want to try.