Published on

Why I Started Bedenker Labs

Authors

For years I was the person who kept one organization's systems running. Internal ERP, tickets, hardware, the works. It's a good way to learn a lot fast, because when something breaks at 11pm, there's no one else to call — you figure it out or nothing gets fixed.

At some point I noticed I kept solving the same category of problem for different people who weren't even asking me to: a club here, a small business there, someone's side project. I was doing it on weekends because I liked it, not because anyone was paying me to.

The decision

The actual decision to start Bedenker Labs wasn't dramatic. It was closer to admitting something that was already true: I was already running a small software practice, I just hadn't given it a name, a bank account, or any of the boring-but-necessary scaffolding around it.

So I gave it those things.

What changed, practically

  • I stopped thinking in terms of "my job" and started thinking in terms of "my clients" — plural, with different needs, different risk tolerances, different definitions of "done."
  • I had to get serious about things I used to wing: backups, access control, who gets notified when something breaks at 3am (still me, but now it's a decision instead of a default).
  • I started building infrastructure meant to be reused across projects instead of bolted onto one system — the first real example of this was a centralized payment gateway (more on that in a future post) instead of wiring card payments into every project from scratch.

What didn't change

I still write the code myself, for most of it. I still get paged when something breaks. The scope just got wider — from one system to a portfolio of them, each with its own quirks and its own people depending on it being up.

If you're doing something similar — moving from "the person who fixes things" to "the person who runs the thing that fixes things" — I'd genuinely like to hear how you handled the transition. It's less about the tech and more about learning to say "not yet" to work that doesn't fit, which I'm still bad at.