Start With The Space Before The Software: A Coworking Tech Stack Lesson From Manifold

Buying software can feel like the professional thing to do when opening a coworking space. It gives the business structure, polish, and the promise that every booking, invoice, access event, and member touchpoint will be handled properly. But if the space has not yet learned how people actually use it, software can also lock in assumptions too early.

TL;DR

• Manifold Coworking started by learning from the space before buying too much software. In a regional New Zealand market, simple manual processes helped the team understand member behavior before committing to a more mature setup.
• Manual workflows can be research. Manifold's early paper sign-in process for a flex pass revealed usage patterns, admin friction, and what the team needed to automate later.
• Growth changed the technology needs. Moving from one location toward a scalable setup created more need for systems around memberships, bookings, access, documentation, and team responsibilities.
• Onboarding is where disconnected tools become visible to members. Access, bookings, billing, communication, and member information need to feel clear from the user's side.
• Documentation is part of the tech stack. Checklists and procedures move knowledge out of the founder's head and make the business easier to operate across a team.

This article is based on the Coworking Tech Week replay, Before the Tech Stack: How to Design What Your Space Actually Needs, featuring Graham Nelson, Founder of Manifold Coworking in New Plymouth, New Zealand. The full session is especially useful for founders deciding when to buy coworking management software, how to reduce member onboarding friction, and how to build operations around real behavior rather than assumptions.

The pressure to look ready

New coworking founders often feel pressure to appear fully formed on day one. That pressure can lead to early software decisions made for presentation rather than evidence. The space wants to look professional, cover every member touchpoint, and avoid messy manual work.

Graham Nelson’s Manifold story offers a more grounded path. Manifold did not begin with a finished coworking tech stack. It started with a small budget, a regional market where coworking was still unfamiliar, and a need to understand how people in New Plymouth would actually use the space.

That early constraint became useful. Instead of choosing tools first, the team put the space into the community, watched what happened, and let real behavior guide the next decisions.

What a regional market teaches you

New Plymouth is not a large global flex office market. In a regional city, coworking may have to be explained through lived experience, not category language. People need to understand when they would use the space, how it fits around their lifestyle, and why it is worth leaving home or the office for.

That context shaped Manifold’s technology decisions. The team could not simply copy the stack of a larger city operator. Members were working around school drop-offs, family schedules, lunch breaks, client meetings, and flexible days. The product had to match that rhythm.

For operators trying to build a coworking tech stack, this is an important warning. A stack that works for a dense urban location with heavy corporate demand may not work for a smaller market where education, habit-building, community trust, and flexible use are more important.

Manual processes can be research

One of the strongest examples in the replay is Manifold’s early flex pass. A member challenged the original plan because it did not match the way many people in the region wanted to work. Manifold responded with an hourly option.

At first, members signed in and out on paper. That may sound inefficient, but it gave the team direct evidence. They could see when people arrived, how long they stayed, how they used the space, and where the admin pain appeared. The manual process was not the destination. It was research.

Over time, the same workflow evolved into a more automated setup where members could tap in and out, time could be calculated properly, and invoicing could happen through the right tools. The important point is sequence. Manifold learned the workflow before automating it.

When growth makes structure necessary

The lesson is not that small operators should avoid software. Manifold eventually built a more mature stack around OfficeRnD, Google Workspace, Xero, E-Lock, custom API work, and operational checklists.

The timing changed because the business changed. A single-location, founder-led space can often run on direct oversight and informal knowledge. Once a team grows or a second location enters the picture, that model starts to break. Memberships, bookings, access, documentation, daily procedures, billing, and responsibilities need more structure.

This is where a coworking tech stack audit becomes useful. Operators should not ask only, “Which tool is best?” They should ask which workflow is now too important, too repetitive, or too risky to keep in someone’s head.

Onboarding is where members feel the stack

Members do not experience a tech stack as a diagram. They experience it as a first day in the space.

Can they enter the building? Do they know how to book a room? Can they understand billing? Do they need a separate tool for access, another for bookings, another for member communication, and another for invoices? Are they told everything at once, or do they receive the right information at the right time?

Graham’s discussion of onboarding is useful because it brings the stack back to the member experience. Too many disconnected tools create friction even when each tool is good on its own. A smoother onboarding flow gives members confidence and reduces the amount of support the team has to provide later.

Documentation belongs in the stack

One of the most practical parts of the session is not about software at all. It is about moving knowledge out of the founder’s head.

For years, much of Manifold’s operating knowledge lived with Graham. That worked while the business was smaller, but it became a constraint as the team and locations grew. The business needed procedures, checklists, and documentation so recurring work could be trained, repeated, and improved.

This is easy to underestimate because documentation does not feel like a product feature. But for a coworking space, checklists can be as important as an app. They define what happens every morning, how onboarding is handled, which tasks matter, how issues are escalated, and how the space can run without the founder being involved in every detail.

Test before you commit

Coworking software choices become expensive to undo once data, billing, member records, workflows, and team habits are built around them. That is why demos alone are not enough.

Before choosing a platform or adding a new tool, operators should test the real workflow:

1. What member behavior are we trying to support?
2. Can we test this manually before automating it?
3. Which team member will own the process every week?
4. What data will need to move between tools?
5. What will members see, click, receive, or have to remember?
6. How hard would this be to change later?
7. Does the tool reduce complexity, or move it somewhere less visible?

Manifold’s story is useful because it does not romanticize manual work. It shows how simple processes can reveal what deserves investment. The goal is not to stay manual forever. The goal is to let the business teach you what to automate.

Watch the full Coworking Tech Week replay with Graham Nelson for the complete Manifold story, including the early flex pass, current stack, documentation lessons, data use, and software evaluation advice.