Why I keep WayTech small

WayTech started in 2026, and today it is me: one software engineer. I want to be upfront about that, because it shapes how I work and who I am the right fit for. It is also a choice I made on purpose, not a stage I am hurrying to leave.

What being small gets you

The biggest benefit is that the person you talk to is the person doing the work. There is no account manager translating your goals for a developer, and no chain of handoffs where the details get lost. If something is unclear, you ask me, and you get an answer the same day.

• Speed of decisions. Small questions get answered in a message, not a meeting.
• Accountability. Nobody else is responsible for the quality of the result, so I take it personally.
• Full context. I hold the whole system in my head, which makes design decisions more coherent and bugs easier to find.
• Fair pricing. You pay for engineering, not for layers of overhead.

What being small costs

It would be dishonest to pretend there are no downsides. One person has a limited amount of time, so I take on a small number of projects and I will tell you plainly if I cannot start when you need me to. One person can also be a single point of failure: if I am sick or unavailable, the project slows down.

I take those risks seriously, and most of what I do about them is the same set of habits I would recommend to any team.

• A mainstream stack that any competent engineer can pick up, not clever tools only I understand.
• Documentation written as I go, including how to run, deploy and change the system.
• Everything in accounts that belong to you: your repository, your hosting, your domain.
• Automated tests and checks, so the system protects itself when someone new touches it.

The goal is that you are never dependent on me. If you decide to bring the work in-house or to another team, the handover should be dull.

What I will not do

I will not pretend to be a larger company than I am. I will not take on more work than I can do well just because the pipeline looks good. And I will not hand your project to someone you have not met without telling you first.

When I would bring in help

Some projects are bigger than one person, or need a skill I do not have, such as brand design or specialised security work. In those cases I would rather say so and involve trusted collaborators openly, with you knowing who they are and what they are doing, than stretch myself thin.

Is this right for you?

A small studio suits you if you value direct communication, careful work and a partner who cares about the long-term health of what gets built. It may not suit you if you need a team of fifteen starting on Monday, or round-the-clock support. I would rather tell you that in the first conversation than in the third month.

If it sounds like a fit, I would like to hear about your project.