I am running an ICM knowledge base for my engineering company using GitHub, VS Code, and Claude Code. The efficiency gains in our workflows have been massive, and I see a clear opportunity to offer this to other regional companies as a new business unit. ​However, this dev-centric stack creates too much friction to be presented directly as a product to non-technical clients. ​The model I envision starts with heavy consulting to align the client's processes and culture. Once maturity is reached, it transitions into a managed service: issue tracking, periodic context pruning, and ad-hoc consulting for new agentic features. ​Has anyone here successfully commercialized this philosophy? I am particularly interested in how you package the delivery and abstract the technical friction (like the IDE and repo management) for the end user. Are there platforms already solving this?

Let's consider a five-person firm. Maybe a consulting firm (as was the build by @Eytan Levy ). Each consultant has a workspace of markdown files, client context, working notes, output logs, and Claude Code runs on top of it. The whole thing lives in one company repo. Everyone clones it, pulls in the morning, pushes at the end of the day. It works. I'd build it the same way. Now ask what's stopping consultant three from opening client seven's folder. The honest answer is nothing. She just doesn't. There's a contract, there's training, she's a professional, and you know her. That's a real control and I'm not going to pretend otherwise. But it's worth being precise about what's actually holding the system together, because it isn't the architecture. Git permissions stop at the repo boundary. Inside the repo, everything is readable by everyone who cloned it. The thing keeping client seven private is not a permission. It's a person. That costs you nothing while it's true. The problem is that nothing in the system tells you the day it stops being true. And it stops for ordinary reasons. You hire past the point where you personally know everyone. You bring a contractor in for one engagement. Someone leaves for a competitor. You sign a client whose contract says their data can't sit on personal devices. You take on a client who competes with a client you already have, and the gap between two folders suddenly needs to be an actual wall. On the day one of those lands, you reach for the lever and find out what you really have. You remove the person from the repo. That stops their next pull. The clone they made three weeks ago is on their laptop, complete, and it stays there. Repo permissions govern who can get it. They don't govern who has it. That is distribution control, and most people think they bought access control. The part I keep my eye on is calling this a big-company problem. It isn't a headcount thing. A fifty-person firm of salaried employees under proper contracts might be perfectly fine. A three-person shop with one contractor who also works for your competitor is not. The trigger isn't scale. It's the first time there's someone inside the system you wouldn't personally vouch for. That usually shows up with growth. It doesn't have to.