Why I stay in the room after the sale
There is a moment in most software projects that nobody puts in the contract. It is the moment right after the deal closes. The proposal is signed, the kickoff call is warm, everyone is optimistic. And then, at a lot of agencies, something quietly changes. The senior person who sold you the work moves on to sell the next deal. The team you were promised turns out to be busy on three other accounts. Your questions take a little longer to answer each week. Nobody says anything is wrong, because nothing dramatic has happened. You are just, slowly, on your own with the hard part.
I spent the first years of my career watching that moment happen from the inside, at agencies and firms before I started my own. It bothered me more than any technical problem ever did. A client had trusted us with something that mattered to their business, and the attention they got was highest before we had earned it and lowest when they needed it most. That is backwards. So when I started ScalaCode in 2012, I built the whole company around fixing that one moment.
Staying is a business decision, not a favour
People sometimes hear "we stay close after the sale" as a soft promise, the kind of line every vendor puts on a website. For me it is the opposite of soft. It is the most practical decision I have made as an operator, because of what it does to the numbers.
When you stay in the room, three things happen. Problems get caught early, while they are cheap to fix, instead of surfacing near a deadline when they are expensive. The client stops managing you and starts trusting you, which means they hand you bigger and harder problems over time. And when the project ends, they do not go shopping for the next one, because leaving a team that actually shows up feels like a downgrade. Close to 90% of ScalaCode's clients come back to us for their next project. That number is not a marketing achievement. It is the direct result of not disappearing.
The cheap version of running a services business is to win a deal, deliver the minimum, and move on. It looks efficient on a spreadsheet for about a year. Then you notice you are spending everything you have on winning new clients to replace the ones who quietly left. Staying close is the more expensive habit up front and the far cheaper business in the end.
What "in the room" actually means
It is easy to say and harder to do, so here is what it looks like week to week, not in theory.
It means a real cadence. You know when you will hear from us, and you hear from us then, whether the news is good or not. Silence is a choice, and we choose against it. It means clear ownership. When something breaks, you are not passed between three people who each think it belongs to someone else. One person owns the answer and gets back to you. It means we tell you the uncomfortable thing early. If a timeline is slipping or an approach is wrong, you hear it from us before it becomes a surprise, because a surprise late is far worse than bad news on time.
None of this is clever. That is the point. Staying in the room is not a technique, it is a temperament, and it is the thing most teams stop doing the moment they get busy. We treat it as the work, not as something extra we do when we have spare time, because we never have spare time and neither does anyone else.
Why the number is the only marketing I trust
I have seen every kind of claim a software company can make. Awards, badges, ratings, long lists of technologies. Most of it is noise, and buyers know it is noise, which is why they discount it. The one signal that is hard to fake is whether the people who already paid you would pay you again.
That is why I keep coming back to the repeat rate. A client who returns has no reason to be generous. They have already seen how we work when things go wrong, not just how we pitch when things are easy. When close to nine out of ten of them come back, it is because staying in the room did something for them that was worth paying for a second time. I would rather show you that one number than a wall of logos.
The same habit, in every company I build
This is not only a ScalaCode idea. It is the rule I carry into everything. iWebServices, which helps small local shops and retailers get online and win customers, runs on the same principle at a different scale. A small business owner is even more likely to be abandoned after they buy a website, and even more hurt by it, because they do not have a team to chase the vendor. Staying in the room matters more there, not less.
If you are deciding who to trust with something that matters to your business, that is the question I would tell you to ask, of me or of anyone else. Not what can you build, but will you still be here when I need you. My answer, and the way I have built every company I run, is yes.
If you want a team that works this way, that is what my companies do. See how ScalaCode works, or get in touch.