There's a moment that every technology leader hits.
It doesn't look like a crisis. There's no server outage, no mass resignation, no angry board call. It's quieter than that.
It's the Monday morning where you open Slack, scan the updates, and realize you have no idea whether things are actually on track or whether everyone is just busy.
It's asking for a timeline and feeling like you're nailing jello to the wall. It's hearing "we're almost there" for the fourth month in a row and not knowing whether that's true or whether you just don't have the technical depth to challenge it.
It's watching the budget climb and the product stay stuck and thinking: I should be able to figure this out. Why can't I figure this out?
If you've felt that, you're in the right place.
We're Dom DeStasio and Josh Gretz, the partners behind ForceBuilders.
Between us, we carry 40+ years of engineering and operational leadership. Dom has spent 15 years as a strategic operator, the person in the room when things aren't working and someone needs to tell the truth about why. Josh has spent 20+ years as a hands-on-keyboard CTO and software architect, the person who can look at a codebase, a team, and a process and tell you what's actually happening versus what you're being told is happening.
We also work alongside Jim Stout, a Licensed Professional Counselor and executive coach who has spent over two decades helping organizations navigate rapid scaling and complex transitions. Jim combines strategic insight with a deep understanding of how people actually behave under pressure, using validated assessments to turn team friction into sustainable results.
That combination (a coach-counselor, an operator, and an architect) isn't accidental. It exists because of something we've learned the hard way, across dozens of engagements with founders, CEOs, CTOs, and investors:
The technology is almost never the root problem.
Here's the pattern we keep seeing.
A founder is racing to ship a product. The market window is closing. They hire developers, pick a framework, build a roadmap. Six months later, the roadmap is in shambles and nobody can explain where the time went. So they try a different dev shop. Or a different framework. Or a different project manager. The technology changes. The result doesn't.
An investor puts $7M into a company over three years. The operator keeps saying the product is almost ready. The investor can feel something is wrong but can't prove it, because they don't have the technical depth to look under the hood, and everyone around them has a reason to keep the story positive.
A VP at a services company tries to build a software product three separate times. Each attempt fails. The company is a quarter-billion dollars in revenue with brilliant people. They're smart enough. They just can't organize themselves to build something new while running the existing business.
A CEO inherits a technology platform with an offshore team he can't evaluate. The only person who understands the codebase is the same person who keeps telling him everything is fine. He doesn't know if the code is solid or falling apart. And every time he asks for a straight answer, it feels like nailing jello to the wall.
Different companies. Different industries. Different stages. Same underlying problem.
In every case, the instinct is to treat it as a technology problem. Get better developers. Rewrite the code. Change the vendor. Hire a CTO.
But the code was never the root issue. The organization around the code was.
That's what this newsletter is about.
We might talk about technology trends when they matter to how you lead, when understanding what's happening in AI or cloud infrastructure or development tooling helps you ask better questions of your team. But every conversation here will be grounded in something bigger than the technology itself.
Ignite is about the stuff that actually determines whether your technology succeeds or fails. And almost none of it is technical.
It's about why your dev team can't give you a straight timeline, and what that reveals about how work flows through your organization.
It's about why you've changed developers three times and the problem didn't get better. Because you keep replacing the people instead of fixing the structure.
It's about the gap between what leadership thinks is happening and what's actually happening, and why that gap is the most expensive problem in your company.
We think about it through three lenses: People, Process, and Product. Not just the code. Not just the team. Not just the workflow. All three, because they're connected, and you can't fix one without understanding the other two.
This is the perspective we bring into every engagement.
We've used it to tell an investor the truth about a $7M problem inside of 30 days, and then developed the strategy to get them back on track and led them through the evaluation process to determine if continued investment was the right thing for them.
We've used it to help a first-time software founder go from zero internal team to a functioning development organization in under a year.
We've used it to help a technology leader build an internal dev org that ships predictably, after years of falling behind on someone else's platform.
Now we're putting it on the page.
Everything we write here comes from the work. Not theory, not generic advice.
Real situations where the presenting problem was technical and the actual problem was organizational. The diagnostic questions we ask when we walk into a company and need to understand what's actually happening. The patterns we've seen repeat across industries, stages, and team sizes.
The perspective shifts where what you thought was the issue turns out to be a symptom of something deeper, and seeing that changes everything.
The goal is simple: whether you ever work with us or not, you walk away seeing your organization more clearly than you did before.
If you're a founder trying to figure out why your team can't ship, a CEO who inherited a codebase you can't evaluate, an investor wondering whether the operator is telling you the whole story, or a leader who's tried to build something new and keeps hitting the same wall, this is for you.
Welcome to Ignite. The start of real transformation.
- Dom & Josh
Ignite is the newsletter from ForceBuilders. Subscribe to get frameworks, stories, and perspective shifts delivered to your inbox.
