Total Engineering Reset

He’s sharing his screen with me the day before we sign our contract.

He’s pointing at an easy dev task.

Look at this one. Sixteen hours, my client says. Just a simple piece of dev. Sixteen hours. It ended up taking twenty-one.

Then comes the whisper, the one you hear in the deep, dark hours of the morning when you’re staring at the ceiling and thinking about every mistake you’ve ever made. My client had it, too. A nagging feeling.

It should take forty-five minutes.

And the cold, greasy dread that slides down your spine is the certainty that he was right. He was right. But he can’t prove it. No, sir. Can’t prove a thing.

You look at the payroll. You look at the output, the number of tasks they’re supposedly working on, and it’s like staring into a deep well.

You know there’s water down there, but you can’t see it, and you’re starting to think maybe it’s poisoned. 

The math doesn’t lie, clients are dropping like flies. And your gut… your gut is screaming bloody murder.

So you ask. You join the stand-up, a digital seance on your screen. It’s a graveyard of black boxes, each one a hiding place. Every camera is off.

You’re speaking to ghosts. Their voices float out of the void, disembodied and complacent. They could be anywhere, doing anything.

You ask for a straight answer, just once, and wait for the darkness to speak back.

What you get is fog. A thick, rolling bank of it, made of words like Source Code and Bugs and Refactor. It’s a language designed to keep you out, a high fence of jargon built to make you feel stupid.

Obfuscation.

It’s a tactic. A weapon. And it’s working.

Because the good ones, the ones who still have the light in their eyes, the ones who remember the simple joy of building something that delights the client? They’re frustrated. You see them in the slack channels, their virtual shoulders slumped. You’ll see their profiles getting updated on those job-hunting websites. They’re quietly, desperately, looking for a way out. They can smell the rot.

And the worst ones? The comfortable ones? The ones who speak the fog-language as their native tongue? They’re thriving. They’re building little fiefdoms of complexity where only they hold the keys.

This is the spiral. The slow, grinding descent into darkness. It never happens with a thunderclap. It happens in the small white lie increments. It happens in every jargon-filled answer to a simple question. You’re in the passenger seat of a car heading for a cliff, and the people in the driver’s seat are telling you, with a perfectly straight face, that this is the scenic route.

And the real horror, the thing that will keep you awake tonight and every night after, is that you’re not crazy. You’re right.

10x your engineering team's output.

Let’s face reality.

If your devs aren’t your favorite (and most profitable) part of your team, something is massively fucked.

We are in the golden age of technology.  

With the right tools, the right resources, the right training, development has the potential to be the most impactful, highly leveraged part of your business.

And I’m not just talking about “using AI”.  Yes, use fucking copilot, cursor or whatever else they want to use. 

If you are reading this, chances are extremely high that your engineers are not building mission critical enterprise technology that is backend heavy, that requires weeks and weeks of planning to get one feature built.

We’ve implemented these systems with our own team, working in high risk, mission critical environments where things typically take months, and we’ve reduced that to weeks and sometimes days or hours.

Your devs are likely doing most of their development on the front end.

What does that mean? 

In short – they are not coding logic.  

Their job is to take the design brief and code it.

“Test it” and deploy it.

That’s it.

After having a call with your devs, you probably hear the word “bug”.  

Here’s what your devs are not telling you. 

In the UI – there are no “bugs”, a bug is purely when a functional (logic/backend) part of a piece of software does not work.

What they really should say instead is… 

“I did not follow the fucking design brief.”

Which in case you’re wondering, should not take hours on end to “test”.

They are likely going from Figma -> front end code. 

The good news is this is the easiest, fastest and lowest complexity part of coding.

And likely – that’s what your team is developing 99% of the time. 

When our clients go through the Total Engineering Reset, heads roll. 

We remove the parasites on your team, and we train the rest in the best methods, the best strategies to develop with 10x velocity, and better quality output.

We do that by bringing the spotlight of truth to the development process and people.

We question why certain parts of the process need to happen in a certain way and in a certain sequence.

What are the assumptions around your pipeline and backlog?

How are tasks assigned?

How long is it realistically supposed to take to get a task delivered?

How do you process client feedback when things slip past QA? 

How do you handle ad-hoc tasks that come up? 

Do you structure your team is squads/pod or is it just one large unit?

How modular is your team – if one person were to leave, does that mean you’d lose a client or struggle where they left off? 

Does it feel like it’s every dev for himself, or does it feel like you have an active team that is cohesive that actively support and help each other? 

Cut your opex in half.

The symptoms you’re dealing with is probably due to a few factors.

Bloated processes, opaque accountability, confusing communication channels, intra-team or team-client relationships, misaligned or vague incentives.

And as a result of this, you’re stuck in a cycle of putting out dumpster fires, and apologizing to clients… so much so, that you don’t have your eyes on the core KPIs.

FUBAR means you can’t focus on your KPIs.

Percentage of tasks that fail QA?

Billing ratio per dev?

Average turn around time?

How many tasks you deliver for every 1K you spend on dev payroll?

Cost per task completed?

And maybe you’ve never looked at the actual cost of completing one average task.

Or maybe you have – and you think it must be normal. 

After all – that’s what the experts on your team are telling you.

We are able to cut our clients cost per task in half easily.

Typically we cut over 90%.

If you have a “head of dev”, “technical lead” or other similar role that is currently filled, he is going to hate this process.

It’s been a paradise of zero technical accountability. 

How do the dev estimates get built (ie – you said 10 hours for this task, show me exactly how you came up with that)?

Why are things actually taking so long?

Why are you not using code snippets from similar projects?

How long does it actually take to test your code? 

Do you have a repo and is every dev pushing (at least) daily?

It’s been a free for all when it comes to team communication.

Devs have been able to hide in the shadows and show up to “stand ups” with no camera on, say nothing material and get back to playing Raid: Shadow Legends.

We are going to end the grotesque cash bleed that is happening today under their purview.

We are going to identify and eliminate the barriers, risks, attack vectors and enemies in your house.

And… you are probably overstaffed. 

You are probably overpaying for engineering resources. 

And no – we’re not going to recommend that you offshore your devs and hire Indian devs who are 6,000 miles of open ocean away from you. 

That’s a recipe for disaster. 

We will cut the fat, optimize the team that remains – and/or help you bring in better resources who are properly vetted and who are zero bullshit.

In 6 weeks.

Your dev team is getting away with what they can.

When you talk with them – they look at you and say indirectly or directly…

“Well, do it yourself then.” 

The problem is you’re not an engineer.  You’re an entrepreneur.

You built a well oiled machine.

Every other part of the enterprise is greased.  

You’ve built the reputation (that their white lies and bullshit are destroying). 

Your company culture is the embodiment of “You can just do things.” 

But your dev team doesn’t match that energy. 

You hear excuses about “sprints”, “that’s not easy”, “we need more time”.  

You know that’s bull.

But you can’t back it up.  You can’t pinpoint why.  

You wonder if you’re being taken for a ride.

You wonder if you’re the fool at the table.

That ends today.

We will conduct a technical review covering people and process.

No stone will be left unturned.

You will get the cold hard truth.  

You will be vindicated.

Your team will get behind you or the fuck out of your way.

We will give you a plan or execute it for you that will reset your engineering and make your devs profitable and productive.

Here is your logical next step.

If you’ve read this far, you are in the right place. 

You’ve got the right instincts. 

Let us be the bad guys. 

Keep your hands clean.

Let us come in and do what needs to be done.

Let us throw the losers out the windows and unlock and unleash your winners.

Apply here to get started.

Jonathan De Collibus