The Most Expensive Thing a Software Partner Can Do

When you hire a dedicated engineering team, you're buying something you can't really inspect.

Not a fixed deliverable you can hold up against a spec — people's time and judgment, applied to your problem day after day, most of which you will never see. You're trusting that the hours are real, that the hard parts are being handled and not quietly hidden, and above all that when something goes wrong, someone will tell you while there's still time to act.

The whole arrangement rests on one thing. Not talent — talent is everywhere. It rests on whether the team tells you the truth, especially the truth you'd rather not hear.

So let me say something about honesty, because I've come to think it's both rarer and far more practical than it sounds.

The economics of a lie

Honesty is hard. Genuinely hard. I've come to believe that a person who is completely honest — with others, and with themselves — has almost nothing left in the world that can defeat them, because they never spend a single day defending a version of reality that isn't true. Everyone else is carrying that weight without noticing it.

Lying, by contrast, is easy. But the first person a lie deceives is the one telling it. You don't actually believe the lie. What you believe is that the lie will make the problem go away. It won't. The problem is sitting exactly where it was. You've simply convinced yourself you've handled it, in the easiest, least effortful way available — which means you've quietly stopped working on the only thing that mattered.

Now put that in the context of building software.

The status update that says "we're on track" when you're not doesn't make the schedule un-slip. It just moves the moment you find out — from now, when the problem is small and cheap, to later, when it's large and expensive. A risk raised in week three costs a conversation. The same risk raised in month six costs a release. The kindest-sounding update is almost always the most expensive one, because what it actually takes from you is the time you'd have used to respond.

A conviction, not a strategy

Here is where I part ways with how this usually gets framed.

Most of the industry treats honesty as a strategy: be transparent, because transparency retains clients. It sounds like the same thing. It isn't. Honesty held as a strategy has a breaking point, and the breaking point is always the same place — the moment the truth threatens the relationship. And bad news always threatens the relationship. That is precisely what makes it bad news. A team that is honest because it pays will filter out exactly the messages that matter most, at exactly the moment they matter.

So we hold it the other way around. At Core70, honesty is a conviction — something closer to a faith than a policy. We tell you the truth whether the consequence is good or bad for us, even when the truth itself puts the relationship at risk. Not because it always works out in our favor. Because that is the only version of honesty that reliably lets bad news reach you.

Take the simplest test — the one you could never catch us on: hours. You will never really know how many hours were worked on your product. An engineer who drifts for an afternoon and bills it anyway would get away with it, every single time. If honesty is a tactic, there is always a reason why this once is fine. And once there is a first time, there will be a second, and a third — the erosion of your trust isn't a risk at that point, it's a certainty, just a delayed one.

What a team believes about lying determines what it does when no one is watching. And almost all of a dedicated engagement happens when no one is watching.

I won't pretend that every engineer who works with us holds this belief exactly the way I do. A conviction can't be installed in a person; it can only be chosen. What we can do is build a company where telling the truth is the natural way to work — where nothing in how people are paid, measured, or kept rewards them for hiding anything — and then keep the people who choose it.

What eighteen years is evidence of

Everyone will promise you honesty, of course. Every vendor on earth says they believe in transparency. Words are free. So the only thing worth weighing is evidence — relationships that have survived the truth, over and over, for years.

One of our core teams has worked with the same UK company for eighteen years — the same people, deepening the same relationship, year after year. You don't reach year eighteen by carefully managing what the client knows. You reach it by being the team that told them the truth early, every time — including the times it was uncomfortable — until honesty was simply the thing they'd come to expect from us.

We didn't stay for eighteen years and therefore become honest. It runs the other way. We were honest — and that is why, in year eighteen, we were still there.

A smaller promise, and a more honest one

So here is what I'd actually promise you — which is smaller, and more honest, than what you're usually promised. Not that we'll never hit a problem. Every real project hits problems, and any partner who implies otherwise is already managing your perception rather than your project. What I'd promise is that you'll hear about it from us first — while it's still small, while you can still do something about it.