Building a Large-Scale Football Manager Simulation on Replit – Looking for Advice and Feedbac

Deployments
1

Hi everyone,

I wanted to introduce a project I’ve been working on for quite some time.

I’m currently building a football management simulation game entirely on Replit. What started as a small idea has grown into a much larger platform than I originally expected.

Some of the features already implemented or currently in development include:

  • Match simulation engine

  • Tactical management system

  • Club and squad management

  • Transfer market

  • Financial management

  • League and competition systems

  • Youth development

  • Historical statistics and records

  • AI-powered coach and scouting assistants

  • Advanced analytics and recommendation systems

The long-term goal is to create a modern football manager experience that combines traditional management gameplay with AI-assisted decision making.

As the project continues to grow, I’m beginning to face challenges regarding scalability, infrastructure, development workflow, and especially Replit usage costs. The AI tools have been incredibly helpful, but the project is reaching a size where I need to think carefully about long-term sustainability.

I’m curious whether anyone here has experience building larger applications or games on Replit.

Some questions I would love feedback on:

  • How large are the biggest projects you’ve successfully run on Replit?

  • At what point did you start separating services or moving parts of the application elsewhere?

  • Are there any programs, partnerships, grants, or creator opportunities that support larger long-term projects?

  • What would you do differently if you were starting a project of this scale today?

I’d also be happy to share screenshots, architecture details, and development progress if people are interested.

Thanks for reading and I appreciate any advice.

*The Manager is acutally in german.

2
21920×995 402 KB

2

Hi — I went through almost exactly what you’re describing while building my own app (NEXIA, an AI app now heading to launch).

I started with a simple spec too. But as it grew, I kept adding features to turn it into a real, professional product. That evolution is exciting — but it comes with a cost nobody really warns you about. In my case, “going bigger” brought:

More bugs. More features = more surface area = more things that break, often in combination.

Technical debt to manage. Early shortcuts that were fine at small scale start slowing you down, and eventually you have to pay them back.

Higher resource usage — RAM, bandwidth, compute. The bill grows with the ambition.

More auditing and real control protocols. Once it’s serious, you can’t just “hope it works” — you need testing, reviews, and checks before every change.

Designing for real users. You start having to think about how many people might use it at once, and build systems that can scale, not just run.

Honestly, the unforeseen build costs ended up roughly 3x what I first imagined.

But here’s the other side: now that I have an app that genuinely works well, I’m really proud of it — and I tell myself it was worth it. In the end, it was.

So for your scaling questions: expect that “small idea → large platform” multiplies both cost and complexity, plan for it early (debt, audits, scaling), and don’t be discouraged when the bill and the bugs grow — that’s the normal price of building something real.

I hope this helps, and I’m happy to answer specific questions if you have any.

1 Like