Skip to content

The founders

Two CTOs. One engagement.

Most fractional CTOs are one person and a calendar. Signal CTO is two senior technical operators on every engagement — coverage, and a second opinion on every big call.

Ben Wallace, Co-founder of Signal CTO

Ben Wallace

Co-founder

Ben is CEO and President of QStart Labs, the Columbus, Ohio software studio he's run for over a decade, shipping web, mobile, and AI products for startups, SMBs, and enterprise teams. He also founded Made By Velocity, a web studio focused on getting founders from idea to launched product fast. Across those engagements he's played every role a young company needs from its first technical leader — architect, hiring manager, vendor wrangler, and the person in the room who says "not yet" to the rewrite. He's built and led engineering teams from the first hire, stood up delivery process that fits the size of the company rather than fighting it, and shipped production systems on the same modern stack he still writes in today. Ben studied at The Ohio State University and works with founders who need CTO-level judgment before they can justify a CTO-level salary.

What I believe

  • Most rewrites are procrastination with a budget.
  • Your first engineering hire matters more than your framework choice.
  • If you can't explain what your team shipped this week, that's the problem to fix first.
  • Ship the boring version, learn, then earn the right to build the interesting one.
LinkedIn
Ryan Powers, Co-founder of Signal CTO

Ryan Powers

Co-founder

Ryan is a software systems engineer and technical leader who has spent his career close to the code that keeps companies running. He studied software systems at The Ohio State University and has partnered with Ben at QStart Labs, where he's designed architectures, led delivery, and cleaned up the kind of inherited codebases that keep founders awake at night. His strength is diagnosis: reading an unfamiliar system quickly, finding the two or three things that actually matter, and turning a vague sense of "something's wrong" into a concrete, ordered plan. He's led engineers, managed contractors and agencies, and made the pragmatic build-versus-buy calls that keep small teams shipping instead of stalling. Ryan is the second senior opinion on every Signal CTO engagement — the one who pressure-tests the big technical decisions before they reach the founder.

What I believe

  • Complexity is a cost you pay every day, not just the day you write it.
  • Read the system before you judge it — most "bad code" was a reasonable decision under pressure.
  • A roadmap without an order is just a wish list.
  • The right architecture is the simplest one that survives your next 18 months — not your dream scale.
LinkedIn

Put two CTOs on your problem.

Book a Signal Call