The Shed Is Not A Metaphor
There is an actual shed. It sits at the back of the property, about twelve feet by sixteen, with a single window that faces north and a propane heater that takes four minutes to make the room tolerable in winter. The wifi reaches it on a good day. On a bad day tethering to a phone means watching the upload bar crawl during a screen share. The desk is a door blank on sawhorses. One good chair.
The reason for being clear about this is that a certain kind of writing about solo consultancy turns the small workspace into a symbol, of freedom, of intentionality, of having opted out of something soul crushing. This is not that. Working in the shed happens because it is the space available, and working there has consequences that are easy to underestimate at the start.
Running a small practice from a constrained physical setup differs from running one from a well resourced home office, and it differs from renting a desk somewhere. The constraints are real and they compound. Temperature affects how long you can stay focused. Noise from outside the building, a lawnmower, a delivery, a dog, lands differently when there is no buffer of hallway or floor between you and it. The space does not signal anything to a client on a video call except that you are somewhere small, and you learn quickly that you either own that or you spend energy managing around it.
What tends to happen over time is that the physical limits of the space force operational honesty that is easy to avoid when there is more room to spread out and pretend. That is not a silver lining. It is just what happens. The constraints are the conditions, and the work has to fit inside them.
What the Space Costs You
The first thing that goes is the buffer. In a conventional office you have hallways, a commute, a coffee machine, small rituals that create transition time between the person you are at home and the person a client is paying to think clearly. A shed eliminates that. You walk fifteen feet and you are supposed to be on. Some days that works. Other days you sit down still carrying whatever happened at breakfast, and the work shows it.
Client perception is a subtler cost, but it is real. Video calls from a small outbuilding require you to think carefully about what is behind you, what the acoustics sound like, whether the heating unit kicks on mid sentence. None of this is fatal, but it consumes attention that should be going toward the conversation. A restoration contractor once asked, during a call, whether the person on screen was in a storage unit. The background had not been managed well that day. That question cost something, not the engagement, but a few minutes of credibility that had to be rebuilt.
Focus is the cost that compounds. A solo consultancy lives or dies on the quality of thinking it produces, and a small space with poor insulation, limited light, or a door that does not fully separate you from the rest of the house will interrupt that thinking in ways you stop noticing because they become ambient. You adapt, which is not the same as solving it. The interruptions just become part of the texture of the day, and you start to assume a certain ceiling on your output without ever identifying why it is there.
Hours are the last thing. A shed that is cold in winter or airless in summer is not a place you stay in past a certain point. That is not weakness, it is just physics. But it means your working window is shaped by the building as much as by the work, and in independent consulting, that constraint is rarely visible to anyone except you.
The Systems You Build When You Cannot Fake Scale
When there is no office manager, no ops coordinator, and no shared drive maintained by someone whose job title includes the word "systems," you find out quickly which infrastructure was load bearing and which was just institutional furniture.
Running a solo consultancy out of a shed stripped that question down fast. There is no room, literally or financially, to maintain processes that exist because a larger practice needed them for headcount reasons. What survived was only what moved work forward.
A few things that turned out to matter more than expected:
- A single intake document that does the qualifying work. Not a CRM. Not a pipeline dashboard. One document that forces a prospective client to articulate what they need before getting on a call.
- Calendar blocking that is non negotiable, not aspirational. When your workspace has hard edges, a shed gets cold, a shed gets loud when the neighbor runs equipment, you stop pretending you can work in ambient chaos and start protecting the hours that are productive.
- A file structure that assumes you are the only person who will ever touch it, and that future you will be in a hurry. No elaborate taxonomy. Dated folders, plain language names, nothing nested more than two levels deep.
- One communication channel per client, agreed on at the start. Email or a shared workspace. Not both, not three.
What got dropped: weekly status reports nobody read, a project management tool maintained for the appearance of rigor, and a proposal template so long it was really a defense mechanism.
The constraint reveals which parts of the operation were small practice discipline and which parts were borrowed habits from organizations built around different problems entirely.
What Gets Wrong Before You Stop Fighting the Setup
For longer than is worth admitting, many solo practitioners run their consultancy as though it were a smaller version of a bigger practice. That distinction sounds minor. It is not.
The most expensive mistake is the proposal process. Templates built for teams include sections covering project governance, escalation paths, stakeholder communication protocols. Those sections tend to survive longer than they should because deleting them feels like admitting the practice is operating at a different scale. Clients ask questions about the governance section and the consultant spends twenty minutes on a call explaining why it does not really apply to the engagement. That burns the client's time and the consultant's time, defending infrastructure that existed to make the document look serious rather than to serve the work.
The second mistake is meeting cadence. Defaulting to weekly check ins is common because that is what larger organizations do. Some of those calls have nothing to report. They happen anyway because canceling feels unprofessional. What it often communicates is that the consultant has not thought carefully about what the engagement needs. Clients notice. A gently delivered observation that it was not clear what was being decided on the calls is feedback that lands hard and usefully.
The third is the way capacity gets discussed. Language like "we can look at resourcing that" creates confusion when the simple answer is that the consultant will be doing the work or will not take it on. The hedging obscures what practice the client is hiring. When that language gets dropped, conversations become shorter and cleaner, and work stops being lost to mismatched expectations rather than genuine competition.
None of these are catastrophic failures. They are slow credibility leaks. The shed does not cause them. Those habits come from somewhere else and get carried past the point they are useful.
What Holds Up About Small Practice Work
The shed does not teach anyone to love constraints. What it does is make certain self deceptions too expensive to maintain.
A solo consultancy runs best when the person running it stops measuring it against a version of itself that does not exist. Not against the agency it might become, not against the firm it used to be part of, not against whatever a competitor appears to be doing from the outside. The shed is a fixed variable. The client work is not. Spending energy trying to disguise the former is energy taken directly from the latter.
The physical reality of small practice work also shapes the thinking in ways that are genuinely useful, not just tolerable. When you cannot retreat into a conference room or hand something off down a hallway, you stay closer to the actual problem longer. That proximity is uncomfortable. It is also where most of the real value in independent consulting gets made.
A belief worth questioning is that the setup is temporary. Treating the shed, the stripped down systems, the absence of staff, as a phase on the way to something more legitimate is a framing that costs something. It keeps the practitioner half committed to the structure of the work, always optimizing for a transition rather than for the practice already running.
A small practice is a different thing from a large practice, with different failure modes and different pressure points. The sooner it gets taken seriously on its own terms, the less time gets spent apologizing for what it is not. That is where this thinking has settled. Not as a conclusion arrived at cleanly, but as something the work eventually makes obvious.