There is a considerable difference between setting up a company and building a business.
On paper, they look like the same thing.
You have a legal entity, a bank account, a website, clearly defined services, suppliers, tools, commercial proposals, contracts and probably a fairly long list of things still to do.
From the outside, that already looks like a company.
From the inside, you begin to discover that it is not necessarily a business.
You can have everything set up perfectly and still not have answered the most important question:
Is there a predictable way to find customers willing to pay for what you do?
That question changes your perspective considerably.
It is very easy to mistake activity for progress
I think this is one of the most dangerous traps when you start something, particularly if you come from a technical background.
There is always something to improve.
The website.
SEO.
A landing page.
The commercial proposal.
The CRM.
Internal processes.
An automation.
A new service.
The documentation.
The contracts.
The pricing.
An integration.
A dashboard.
The worst part is that many of those things are useful.
The problem begins when you use them as a substitute for what actually makes you uncomfortable.
Selling.
Talking to customers.
Hearing no.
Sending a proposal and receiving no reply.
Asking why an opportunity did not close.
Calling someone.
Putting yourself out there.
Accepting that the market may not understand your offer as well as you thought it did.
Building things gives you an immediate sense of progress.
Sales often does not.
You can spend ten hours working on a website and have something visible at the end of the day.
You can spend ten hours on business development and finish with exactly the same number of customers as when you started.
That makes it very easy to take refuge in the first kind of work.
A company can be incorporated relatively quickly. Trust cannot.
Setting up a company can take days or weeks.
Getting someone to trust it can take much longer.
This is particularly noticeable in professional services.
When you sell consulting, Cloud, DevOps, architecture or infrastructure services, the customer is not simply buying hours of work.
They are buying peace of mind.
They are allowing someone into a critical part of their company.
Production.
Cloud.
CI/CD.
Security.
Costs.
Availability.
Data.
Infrastructure that could directly affect their business if it fails.
That is where you encounter a reality you do not always consider when you start:
you can be technically very good and that may still not be enough for someone to buy from you.
Because the market does not know that yet.
It does not know your name.
It does not know how you work.
It does not know whether you will respond when something goes wrong.
It does not know whether you will still be there in six months.
It does not know whether it can trust you with something important.
You cannot deploy a reputation with Terraform.
I wish you could.
Your competition is often not another company
Something else I am beginning to understand is that, in B2B, your competition is not always another consultancy.
Often, it is simply:
“We can carry on as we are for now.”
The infrastructure may have problems.
The team may lose hours to deployments.
The cloud bill may be too high.
Observability may be missing.
There may be technical debt.
There may be operational risk.
And the company may still decide to do nothing.
Because it still works.
Because there are other priorities.
Because nobody wants to start another project.
Because the problem does not hurt enough yet.
This means that showing you can solve something is not enough.
You also have to show why it is worth solving now.
That has much less to do with technology than I imagined when I started.
Clearly defined services do not mean the market wants to buy them that way
Another thing that happens when you set up a company is that you design the offer from the inside.
It makes sense.
You know your experience.
You know what you can do.
You know where you add value.
So you define services, packages, prices and scope.
Then you take them to market.
That is where another phase begins.
Because the market comes back with questions.
“I don’t understand exactly what this includes.”
“Is this support?”
“Do you work on a project basis?”
“Can you manage this part as well?”
“Why do I need this now?”
“How long does it take?”
“What happens after the project?”
You start to realise that an offer that seemed perfectly clear internally may not be clear to someone who looks at it for thirty seconds.
That is also part of building a company.
Changing things.
Simplifying.
Removing services.
Renaming them.
Starting again.
Accepting that an idea you liked may not have worked as well as you thought.
A founder’s ego can be expensive
This is probably one of the lessons I am finding hardest to learn.
When it is your company, you have a fairly natural tendency to think you need to do everything.
Strategy.
Sales.
Marketing.
Operations.
Technology.
Finance.
Partners.
Customers.
Content.
Product.
For a while, you may even manage it.
The problem is that being able to do something does not necessarily mean you should do it.
There are areas where someone with ten or fifteen years of experience can make decisions in an afternoon that would take you months to learn how to make.
But delegating is difficult.
Because it means recognising that you are not the best person for everything.
It also means allowing someone to do things differently.
And perhaps even better than you.
I think professionalising a company begins precisely there.
Not when you rent an office.
Not when you have twenty employees.
But when you begin to distinguish clearly between the things that need your involvement and the things that need someone better prepared than you to solve them.
Invoicing does not mean you have built a business either
Winning a customer matters.
A great deal.
But then another question appears:
can I win another one?
And then another.
And another?
Where do they come from?
How much does it cost to acquire them?
How long does it take for an opportunity to become a project?
Why do some buy and others not?
Which customer profile works best?
Which problem creates genuine urgency?
Which service makes the most sense?
How much can we charge?
Which part of the process is repeatable?
That is where a business begins to emerge.
Not simply when money comes in, but when you begin to understand why it comes in.
Because one sale could be chance.
Two could be a coincidence.
When you begin to repeat the process, you have something much more interesting.
There is something particularly uncomfortable about all this
You can be working incredibly hard without the company moving forward at the same pace.
That gap feels strange.
We are used to thinking that effort and results have a more or less direct relationship.
In a company, it does not always work that way.
You can have an incredibly productive week and not generate a single euro.
You can spend months preparing something only for a twenty-minute conversation to become far more important.
The opposite can happen too.
Something you spent weeks on may end up being of virtually no use at all.
That forces you to change how you measure work.
I am trying to ask myself less often:
How many things have we done this week?
And more often:
What have we done this week that genuinely brings Nubyron closer to the business we want to build?
The difference looks small.
It is not.
Building a company means learning what to discard
More services are not always better.
Neither are more tools.
More automation does not always help.
More people do not necessarily solve the problem.
More content does not guarantee distribution.
More contacts do not mean better opportunities.
I think growth also means beginning to say no.
To projects.
To ideas.
To tools.
To services.
To customers who are not a good fit.
To things that seem interesting but do not move you towards any real objective.
That is probably much harder than starting new things.
I still do not have a perfect conclusion
I could end this article by saying that I now understand how to build a business.
It would not be true.
I am still learning.
I am still changing things.
I am still making decisions that I may consider mistakes six months from now.
I am still trying to find where Nubyron creates the most value, how to explain it better and how to turn that value into a sustainable company.
But there is one thing I understand much more clearly than when I started:
setting up a company is relatively easy.
Building a business is something else.
A business needs customers.
It needs trust.
It needs distribution.
It needs positioning.
It needs cash.
It needs repeatability.
It needs uncomfortable decisions.
Above all, it needs someone outside your own company to consider what you do valuable enough to pay for it.
Everything else helps.
But it does not replace that.
Perhaps this is one of the biggest shifts in perspective I am experiencing while building Nubyron.
To stop asking myself only what kind of company I want to build.
And to start asking:
what business deserves to exist?