What Led Me to Build NeuraByte?

I was in a meeting with my colleagues, getting ready for a client call. We weren't preparing the work — that part was fine. We were preparing what we wouldn't tell the client. There were two things we'd missed; one was technical, one was a mistake on our side. Everyone in the room agreed neither needed to come up. We had a script for the questions we expected. We had a script for the questions we didn't want.

That was the meeting where I realised I was uncomfortable with my job in a way I couldn't fix from the inside.

It wasn't even unusual. It was a normal Wednesday. The kind of meeting that's normal in every company I've worked at. You sit there and notice that what you're being trained on isn't engineering — it's how to handle the client, in a direction that asks you to be slightly less honest than you'd want to be.

That's the moment that started NeuraByte, although I didn't quit the next day. It stayed with me.

What I was actually tired of

A few things had been adding up for a while.

Ideas would die in committee. I'd bring something to a leadership meeting that I thought solved a real problem we kept hitting, and the answer would be a polite "let's revisit next quarter," which everyone in the room knew meant no. The work culture rewarded looking busy more than actually shipping. We had stand-ups where everyone reported updates that would have fit in a Slack message. We were told we had to be back in the office on Mondays — for what, exactly, was never explained, because the work hadn't changed and the meetings were still on Zoom.

And the client meetings. Slowly, project by project, the gap between what we knew and what we were saying out loud got wider. I never agreed to it. I just stopped pushing back, because pushing back wasn't part of my job description either.

I wasn't bitter about any of it. I just couldn't see myself doing this for the next ten years and being proud of what I'd built.

The decision

It wasn't dramatic. There was no "I quit" moment. The accumulated weight of small wrongnesses became enough one quiet evening, and I told my wife, and then I started looking at what it would actually take.

The plan I made wasn't ambitious. Get a project. Then get another. Don't pretend I'm something I'm not. Don't take work I don't believe in. See what happens.

How NeuraByte actually started

I didn't do cold outreach. I didn't write a business plan. I didn't have a pitch deck.

What I had was two relationships.

A friend reached out about a problem he was hitting in his business — a tool that didn't exist, that he wanted built. I took it on, focused on solving the actual problem rather than maximising what I could charge. That was the first paying project. He's still a client.

Around the same time, an old colleague from my previous job brought me an automotive project. He'd worked with me before, knew how I operated, and trusted me enough to bring me into something that really mattered to his team. That was the second.

Two clients, both from people I'd already earned trust with, both grounded in real problems. No sales funnel. No paid ads. Just trust plus work plus showing up.

What I was right about

Two things turned out exactly how I'd hoped.

Telling clients the truth is the strategy, not the exception. This was the bet I quit on, and it's the one that's paid off the most. When something goes wrong on a project, I tell the client the same day, in plain language, without a script. They don't lose trust — they gain it. They tell their colleagues about us. The hours we used to spend at big companies on managing the relationship now go into doing the work, because the relationship doesn't need managing when you're being straight with people.

Working without a manager is even better than I thought it would be. I knew I'd like the freedom. I didn't realise how much energy was being eaten up by the small stuff of being in a chain of command — the politicking, the going-along-with-things, the careful wording of every email. With that load gone, I get better engineering work done in less time. That alone has been worth it.

What I was wrong about

The hardest part isn't anything you read about in founder books. It's jumping between completely different jobs all day.

In a normal week, I'm doing sales pitches before lunch, debugging a tricky issue mid-afternoon, writing a proposal in the evening, interviewing a potential collaborator the next morning, and supporting a live client somewhere in between. None of those are hard on their own. They're hard because they're all in the same head. You can't be in deep-engineering mode and sales-pitch mode and hiring-judgement mode in the same day without it costing you something.

I've gotten better at it — grouping similar work into the same day, putting deep engineering into specific blocks, keeping a written list so jumping between things doesn't lose information. But the underlying cost doesn't go away. It's the price of being free of a chain of command. You become every layer of the org chart, and they all want a piece of your attention.

If you're thinking about starting something — assume you'll like the freedom. Plan for the cost of doing every job yourself. That's the bigger surprise.

What NeuraByte is now

A small core, a network of specialists I've worked with for years, and three deliberate service areas — automotive software, mobile and web apps, and privacy-first home automation. We pick projects we believe in. We say no to the ones we don't. We tell clients the truth even when it's awkward, because that turned out to be the whole product.

The values aren't on a wall poster. They're the things I left a job to be able to do.

Closing

This is the company I wanted to work at, and I couldn't find one that operated this way, so we built it. Not as a marketing line — as the literal answer to the question in the title.

If you're an engineer who recognises any of the meetings I described — the spec we couldn't question, the truth we couldn't tell, the day we couldn't justify being in the office — then maybe what you want isn't to find the right company. Maybe it's to build a corner of the industry that operates the way you'd want to be treated. That's what NeuraByte is. The door's open, both for clients and for the kind of engineers who'd rather work this way too.