SlashFlow: built from our own work

The work we needed to coordinate

Our own operations needed a way to coordinate engagements, documents, delivery and billing. These are connected parts of a project: the agreement, the work being delivered, its records and the commercial details around it.

A workspace built inside SlashTech

We built an internal workspace around that need. It became the system behind our Client Hub: the Hub provides the client-facing view, while the Workspace coordinates our work behind it.

The interface shown here is that internal tool, using demonstration data. It gives this story a concrete starting point; it is not a preview of a finished SlashFlow product.

Learning through use

We used the workspace in our own operations and kept improving it. That puts the people building the system close to the work it needs to support, with opportunities to learn from use rather than treating delivery as the end of development.

Our approach to client work follows the same principle: understand the environment, build a useful system, test it in practice and keep learning. Internal use is a starting point for that learning, not evidence that every other team needs the same thing.

From our operation to other teams

The next step is to develop the internal workspace into a product for teams beyond SlashTech. That product is SlashFlow, being developed as a Slash Group venture.

This is a change in the audience we are building for. The product is still taking shape, and our own workflows provide a foundation to build from. The early-access waitlist is a way for other teams to register interest as that work continues.

Work should move. Not wait.

SlashFlow is becoming software for coordinating client work and operations. This public reveal opens its early-access waitlist; it is not general availability or an offer of immediate access.

Register your interest on the SlashFlow website using the waitlist link below. Access will be offered progressively.