How a problem becomes a company.
A Slash company is not started because we can. It is built when a problem deserves sustained responsibility, and it has done its job when it can carry that responsibility without us.
Between those two points, this is the sequence.
Structure enables judgement.
One operating formula does not fit every company, so what stays consistent is how change gets approached. The eight steps that follow are this same loop, asked of one specific question: does this problem deserve a company?
Encounter reality. Not a brief about it.
Find the problem beneath the problem.
Decide what responsibility is ours to carry.
Build deliberately, without waiting for certainty.
Did it work, did it help, can it survive?
Change our thinking when the evidence demands it.
Return with better questions.
Start where reality happens.
We spend time inside the work before deciding anything — the site, the floor, the operation, the people carrying it. What an organisation describes and what is actually happening are rarely the same thing, and only one of them can be built for.
In practice this means the site visit happens before the proposal, and the conversation is with the people doing the work rather than only the person signing. SlashTech has talked itself out of projects at this stage, because what the technology was meant to fix turned out not to be a technology problem.
The stated problem is rarely the whole problem.
A missed deadline is a symptom. Underneath it sits a process nobody owns, a system that stopped fitting years ago, or a decision no one is positioned to make. We keep going until we find the thing that, if it changed, would change everything above it.
The pattern repeats often enough to be predictable: unclear ownership, a process nobody holds, knowledge trapped in one person, an inherited system, and a gap between what management believes happens and what happens. Most of it is organisational before it is technical.
A problem must earn a company.
Not every worthwhile problem is ours to carry. It has to matter enough to still deserve years of attention, be able to stand as a company in its own right, and have someone genuinely able to commit to it. Most ideas stop here, and they should.
A belief is not yet a business.
Before a company exists, the belief behind it is put in front of reality: real customers, real money, real operating conditions. We would rather find out we were wrong while being wrong is still cheap.
Give responsibility somewhere durable to live.
A company is what turns intent into something that survives a bad quarter and a change of staff. It gets its own name, its own leadership, its own customers and its own accountability — along with the foundations the group has already built.
Supported does not mean dependent.
Support is leverage while a company is finding its feet and a liability if it never leaves. So judgement is handed over as fast as it can be carried: the decisions, the numbers, the standards, the relationships.
A company succeeds when it can carry itself.
The measure is not how much the group is doing for a venture. It is how little the venture needs. A company standing on its own leadership, customers, judgement and economics has done the thing it was built to do.
SlashTech's own version of this is the line that decides whether a project is finished: we do not consider it done until someone can reliably run it. Documentation is built alongside the system rather than after it, and the people who will operate it are trained to. Support stays available — the point is that it stops being required.
The next venture should not start from zero.
What one company learns becomes the starting position for the next: the standards, the systems, the mistakes worth remembering, and the people who can now do more than they could before. That is what makes taking on something harder possible at all.
Leave things stronger than you found them.
Six questions, asked of finished work rather than of a plan. They are how we tell useful from merely delivered — and a project can pass every milestone and still fail most of them.
Build the hard parts once.
Each company stays accountable for its own customers and outcomes. What the group provides is the foundation underneath — so a new venture never starts from nothing, and nobody argues their way to a standard that already exists.