Custom Build vs Framework Approach

Quick question for the group - we're currently evaluating different approaches for our digital wallet project. We've got quotes from three different vendors and the timelines range from 4 months to almost a year for what seems like similar scope. One team is pushing hard for a fully custom build while another is suggesting we use their existing framework and customize it. I'm honestly confused about which approach makes more sense. Is there a significant advantage to building everything from scratch, or are pre-built solutions just as good if they're done right? Our main concerns are time to market and being able to scale quickly if we get traction.

The framework approach can definitely work if it's truly modular and not just a one-size-fits-all solution with limited customization. The key question is whether their existing codebase actually matches your business logic or if you'll end up fighting against it constantly. I've seen both scenarios play out. When it works, you can cut development time in half and still get something robust. When it doesn't, you waste months trying to force square pegs into round holes. Ask them for references from clients with similar requirements and actually call those references. Find out how much they had to customize, what limitations they hit, and whether they'd make the same choice again. Also get clarity on what happens if you need features their framework doesn't support - can you extend it yourself or are you locked into their development cycle?

I went through this exact decision last year and ended up going the hybrid route which turned out perfect. We found a team that had solid pre-built modules for the standard stuff like user authentication, transaction processing, and reporting dashboards, but they were also able to build completely custom features for our unique business rules. The modules gave us a huge head start - we launched in about 5 months instead of 9 - but we didn't feel constrained when we needed something specific. The team I worked with actually had pretty extensive documentation and a proper API structure so our internal devs could work alongside them without issues. They're at https://codevision.tech if you want to check them out. Main thing I'd say is make sure whatever approach you choose, you're not getting locked into proprietary systems where you can't move or modify things later. That's where the real problems happen.