"Just use whatever you think is best."
Six weeks ago, a Melbourne fintech founder said exactly that to her new developer. She wasn't being lazy. She was being trusting. He was the technical expert — surely he'd know what to pick.
He picked a cutting-edge framework he'd been wanting to try for months. Eighteen months later, she couldn't find a second developer who knew it. Her first developer left. Her MVP was stranded.
The real cost? $80K in development. $25K in sunk recruitment costs. And four months of runway chasing a rebuild.
This conversation happens twice a month in my world. And every single time, it was completely preventable.
Why Tech Stack Is a Business Decision (Not a Technical One)
Here's the thing most founders don't realise: your tech stack isn't just about what code you write. It determines who you can hire. How fast you can ship. What your infrastructure costs at scale. Whether investors will take you seriously.
Your developer knows the technical side. But they're not thinking about your hiring market in Brisbane. They're not thinking about your 12-month runway. They're not thinking about what happens when they leave.
That's the gap. And it's a dangerous one.
The real cost of a bad stack: Tech stack rewrites cost Australian startups between $40K and $120K on average — plus 3–6 months of lost momentum. Most happen because no one with business context was involved in the original decision.
Here's What Usually Happens
I've seen this play out three ways, and none of them end well.
Scenario 1: The shiny new framework trap. Your developer picks something they're personally excited about. It's modern, it's clever, and there are approximately 400 developers in Australia who know it. Good luck hiring your second engineer.
Scenario 2: The "Google does it this way" fallacy. Your developer recommends a Kubernetes cluster, microservices, and a distributed message queue. For a startup with 12 users. You're paying $8K/month in AWS costs before you've validated anything.
Scenario 3: The Frankenstein stack. You had three different developers over 18 months. One liked Python, one preferred Node, and your current one insisted on Go. Now nothing talks to anything else, your codebase is unmaintainable, and you need a full rewrite to add basic features.
Sound familiar? I see at least one of these every month. And every time, the founder says the same thing: "Nobody told me this was a risk."
Average cost of a tech stack rewrite for an Australian early-stage startup
Not Sure If Your Stack Is Right for Your Stage?
I do tech stack assessments for founders before they start building — and for founders who've already started but have a nagging feeling something's off. Let's look at what you've got.
Get a Stack Assessment →Here's What I Do Instead
When a founder comes to me before they start building, I run them through a structured tech stack decision process. It takes about two weeks. Here's how it works.
Step 1: Understand the business constraints first. What's your 18-month growth target? What does your ideal hiring profile look like? What's your infrastructure budget? What are your competitors using? I'm not asking these questions to be thorough — each answer eliminates entire categories of technology.
Step 2: Map to available talent. The best tech stack is one your team can actually build with and maintain. I look at the Australian developer market for your location, your salary band, and your timeline. If you can't hire for a stack in 8 weeks, it's not the right stack — no matter how technically elegant it is.
Step 3: Match complexity to stage. Pre-seed founders don't need infrastructure that can handle 10 million users. You need infrastructure that costs $200/month and can handle 10,000 users. I see founders over-engineer constantly. I see them under-engineer too — and then hit a wall at 5,000 users that costs $60K to fix.
Step 4: Lock in the decision and document it. The recommendation isn't just "use React and Rails." It's a documented decision record — why we chose it, what we ruled out, what the tradeoffs are. Your next hire reads that document and immediately understands the context. No repeat mistakes.
What This Looks Like in Practice
Last year, a Sydney-based health-tech founder came to me before signing with a development agency. The agency had already recommended a stack. It was technically sound — but it was built around the agency's preferred tooling, not the founder's hiring reality.
We spent two weeks doing the analysis. The agency's recommended stack would have cost $4,500/month in infrastructure and required senior engineers at $180K+/year to maintain. The alternative I recommended cost $900/month in infrastructure and could be maintained by mid-level engineers at $120K–$130K.
Real outcome: Over 24 months, the stack decision alone saved this founder approximately $85K in infrastructure and $120K in hiring costs. Total: $205K in savings from a two-week assessment. The agency stack wasn't wrong — it was just wrong for this founder's stage and constraints.
That's the difference a fractional CTO makes in this decision. Not picking the "best" technology. Picking the right technology for your specific situation.
Let's Talk About Your Stack Before You Build
If you're about to kick off development — or you've started and you're not confident in the choices that were made — let's have a conversation. I'll give you an honest read on where you stand.
Book a Discovery Call →30 minutes • No obligation • Honest feedback
The Questions a Fractional CTO Asks That Your Developer Won't
Your developer is hired to build. They're not hired to think about your business model, your funding runway, or your hiring plan. A fractional CTO bridges that gap — because I've been in both roles.
Here are the questions I ask every founder before touching a single line of tech stack discussion:
- What happens if your lead developer leaves in 6 months? Is your stack one that a replacement can pick up in two weeks?
- Where are you likely to hire your first 3 engineers? Sydney, Melbourne, offshore? Each market has a different talent pool.
- What's your 18-month infrastructure budget? Not just "affordable" — actual numbers. $500/month? $5K/month?
- Are you building for B2C or B2B? The performance and compliance requirements are completely different.
- What's your data privacy exposure? Health, finance, and legal data all change your stack options significantly.
Most developers don't ask these questions. They ask: "What are we building?" That's not enough information to make a good stack decision.
Ways We Can Work on This Together
Every founder's situation is different. Here's how I typically help:
Tech Stack Assessment ($2,500–$3,500): A focused two-week sprint. I review your current stack (or proposed stack), your business constraints, and your team. You get a written recommendation with full rationale. This is for founders who just need clarity on a single decision.
Build Oversight ($5,000/month, 3-month minimum): I stay involved as you build. Weekly reviews, architectural guidance, and a technical check on every major decision your team makes. This is for founders who are actively in development and need an experienced eye on the work.
Full Fractional CTO ($10,000–$15,000/month): I'm your head of technology. Tech stack decisions are just one part of what we tackle — I'm also working on your hiring, your processes, your vendor relationships, and your investor-facing technical strategy. This is for founders who need ongoing technical leadership, not just a one-off review.
Not sure which fits? Tell me where you're at and I'll point you in the right direction.
What You Get Out of This
When a founder works with me on their tech stack decision, here's what typically changes:
They stop second-guessing every technical suggestion from their developers. They have a documented decision they can explain to investors. They hire faster because they know exactly what skills to look for. And they avoid the $50K–$120K rewrite that trips up so many Australian startups at the 18-month mark.
The tech stack conversation isn't glamorous. But it's one of the highest-leverage decisions you'll make as a founder. Get it right early and it pays dividends for three years. Get it wrong and you're rebuilding from scratch right when you should be scaling.
Get Your Tech Stack Right the First Time
Whether you're pre-build, mid-build, or already wondering if you made the wrong call — let's talk. I'll give you a straight answer and a clear path forward.
Apply to Work Together →30 minutes • No obligation • Honest feedback on your situation