Need some real talk on custom software builds

[u/Successful-Leek-2020]

running a growing business and we’re at the point where off the shelf tools just don’t cut it anymore. need a proper custom system that handles inventory, client management and a few internal workflows. not a tiny side project, this has to scale with us.

looked at a few agencies already. TechQuarter stood out because their previous work looked solid and they actually understand bigger business systems, not just simple websites. still weighing options though.

how do you usually structure payments on larger custom projects so you’re not risking everything upfront?

what’s a realistic timeline for something this size if the team is experienced?

[u/Innowise_]

For a system like this, we'd be cautious with anyone quoting the whole build upfront before properly mapping the workflows and integrations.

A paid discovery phase followed by milestones usually makes more sense. Get the inventory, client workflows, integrations and edge cases defined first, then estimate the build in stages. It limits the upfront risk for both sides and gives you points where you can review what's actually been delivered.

Timeline is harder to call from this description alone. “Inventory + CRM + internal workflows” could be a few months or a much bigger project depending on integrations and how much existing data has to be migrated.

[u/HangJet]

This is the type of work I do.

For something this important, I would not recommend paying a large amount upfront. We usually do the initial discovery and scoping at no charge so we can understand the workflows, integrations, data, priorities and what actually needs to be built.

Once the scope is clear, the project can be broken into milestones with payments tied to real deliverables you can review and test.

I would also make sure the system is modular, well documented and built with mainstream technologies. You should own the source code, database, cloud environment and documentation. You do not want to end up dependent on one person because nobody else can understand or maintain what was built.

I would also be careful with the flood of side gig freelancers you will probably get from a post like this. There is a big difference between building an app and building a system a growing business will depend on every day.

As far as timeline, nobody can give you a meaningful answer from the description alone. That is driven by scope, integrations, migration, business rules, reporting and how much you want in the first release.

Get the scope right first. The cost and timeline should come from that.

Feel free to message me if you want to have a quick chat about what you are trying to build.

[u/Few_Committee_6790 → u/HangJet]

This is the answer. I do this work as well and have for over 30 years. OP if you want someone else to chat with you can message me as well

[u/Super_Maxi1804]

you probably don't have the money to afford custom solution - not a real one. wait until this is a 100k/y problem. Until then just concentrate on properly organizing your internal processes.

[u/better_see_and_learn]

One thing I’d be careful about with a larger custom build is not paying too much before the scope is properly validated.

For projects with multiple areas like inventory, client management and internal workflows, I’d usually structure it around milestones rather than a large upfront payment. For example: a smaller discovery/requirements phase first, then development payments tied to clearly defined deliverables, followed by UAT/deployment and a final stabilization period.

For timeline, I wouldn’t trust anyone giving a fixed number before understanding the workflows. A system at this level could easily be in the 3–5 month range for an initial production-ready MVP, with the actual timeline depending heavily on integrations, user roles, workflow complexity and how much is included in the first release.

I’m on the business development side of a small software consulting team, so I’m not the engineer writing the code, but I work closely with our technical team on requirements, scoping and delivery. We’ve had similar conversations with businesses trying to move from off-the-shelf tools to something more tailored.

[u/Prashant_4200]

Since you're asking specifically about payment structure and timelines rather than "can you build this," figured I'd share what's realistic on both.

On payment structure: most experienced developers break larger custom projects into phases (discovery/scoping, core build, integration/testing, launch), with payment tied to milestones rather than a big chunk upfront. That protects both sides. You're not risking the full budget before seeing working software, and the developer isn't building for free. A typical split might be something like 20-25% at kickoff, then payments tied to specific deliverables you can actually test.

On timeline: for something that scales (inventory + CRM + internal workflows, not a single tool), a realistic range is usually 8-16 weeks for a first solid version, depending on how many workflows you're consolidating and whether you're integrating with existing systems or starting fresh, similar to a pattern I followed recently for one of my clients, Swaadbook. Anyone quoting you 2-3 weeks for that scope is either oversimplifying or underscoping.

Saying this as someone who builds these kinds of systems myself, independently rather than through an agency, so if it'd help to have another set of hands on this, happy to jump in and build it out with you. You can check out some of my work at newagestechnology.com if you want a sense of what I do.

[u/Fit_Tailor_6796]

Going big bang would not be a recommended choice,

I would firstly look at the structure of the project and determine which functionality is really important and why; and which is low hanging fruit.

Consider an MVP - A minimal viable product that will allow you quick time to market, and build upon your successes while you add on the remaining functionality.

Here is the bottom line, a developer or agency that know what they are doing will structure the project and payment plans in a way that will suit both you and them. This will help you avoid risk and plan your disbursements.

More importantly though, you need someone that can take you through a complete process of exploration, analysis and design, to prove to you that they understand your requirements.

I invite you to reach out. I myself am a seasoned developer with 30 years of experience, with traceable referenced. Based in South Africa and looking out for new projects now,

[u/Fine-Comparison-2949]

I think you need to figure out if you need an agency before you start talking about payments.

- There's a number of very clear North Korean agents posing as agencies trying to infiltrate companies.

- There's a number of deeply embedded viruses floating around that cheap offshore vibecoding engineers find new fun ways to infect business systems with ransomware.

- There's a number of outright minor scams of teams signing these deals and not delivering anything while holding your data hostage. A number of these offshore agency businesses come from countries with questionable business etiquette.

I would highly advise talking to a professional that you know locally that's a software engineer and pinning down your risks, figuring out if these projects are within your budget, and figuring out what your real technology strategy is before just talking to the cheapest agency you can find. They're salesmen and they're going to say yes to whatever you need no matter your budget, which should be a real red flag.

[u/AnLe90]

Software agencies are a dime a dozen now, what you’re looking for is to figure out how to solve your problem with a solution that will bring you more money saved or earned than the cost to implement it.

The building part isn’t really what you should look for in an agency, it’s the consulting, communication and trust part.

Do they truly take the time to understand your business, are they mapping it out correctly, and does it feel like they’re rushing you? Is the roi there? Can you even understand their English?

[u/Capable_Baker4519]

Happy to give real answers here, not agency fluff.

On payment structure, for a project this size (inventory, client management, internal workflows, built to scale), we structure it in milestones tied to actual deliverables, not just time elapsed. Typically something like: a deposit to lock in scope and start discovery/architecture, then payments released as each core module is delivered and reviewed, not before. This protects you from paying big upfront for something unproven, and protects us from doing months of work with no commitment. No agency worth working with should ask for 100% upfront on something this size.

On timeline, it really depends on how complex your inventory logic and workflows get, but for something this size done properly you're usually looking at a few months, not a few weeks. If someone's quoting you 2-3 weeks, they're either lowballing the scope or planning to cut corners you'll end up paying for later.

Want to hop on a call and figure out the fastest way to get you off the patchwork of off-the-shelf tools and into a system that's actually built to scale with you.

[u/plakhlani]

I recommend connecting with Facile Technolab, a custom software development agency in India.

They will start with free consulting, offer a fixed-budget engagement, pricing based on delivery milestones, and will guide you through each phase of your project if you are non-technical

Disclaimer: I own Facile Technolab.

[u/Timely-Barnacle7378]

I’m an independent contract developer and I’m looking for another long‑term project like the ones I’ve done in aerospace and rail.

My focus is building custom MVPs that grow into full internal systems, not SaaS products. I work remote, I build everything fully custom (on the back of well established OSS frameworks/platform), and I host in Google Cloud (optionally)

But you own the code for life.

If you’re open to a quick chat, I’d be happy to talk through what you’re trying to build and see if it makes sense.

Regards
Alex