SaaS Procurement Full-Stack Build
Budget: ₹100 – ₹400 INR
I’m spinning up a focused, 4–6-week sprint to deliver the first production-ready slice of a SaaS procurement platform and I need a full-stack developer who can carry the work end-to-end. The immediate milestone is a robust Reporting & Analytics module: real-time data updates, fully custom report generation, and smooth hand-offs to common visualisation tools (think embedded BI dashboards).
The core application is already framed conceptually; what’s missing is the hands-on build—database design through to responsive UI—using the languages I work with daily: Python, Java and PHP. If you’re equally at home moving between these stacks and the web front end, you’ll slot straight in.
I’m based in Chennai and onsite collaboration is a bonus, but I can accommodate remote work provided daily stand-ups overlap with IST. Continuous delivery is important to me, so expect short review cycles and rapid feedback. A clean Git history, sensible unit tests and concise documentation will be part of the acceptance criteria alongside the working code.
By the end of week six I want:
• A live multitenant module deployed to my staging server
• Real-time reporting endpoints wired to sample procurement data
• A UI that lets users define, save and export custom reports
• At least one plug-in or API hook that feeds a visualisation tool of your choice
If that scope, the tech mix, and the timeline feel comfortable, let’s talk specifics and get the repository set up.
The core application is already framed conceptually; what’s missing is the hands-on build—database design through to responsive UI—using the languages I work with daily: Python, Java and PHP. If you’re equally at home moving between these stacks and the web front end, you’ll slot straight in.
I’m based in Chennai and onsite collaboration is a bonus, but I can accommodate remote work provided daily stand-ups overlap with IST. Continuous delivery is important to me, so expect short review cycles and rapid feedback. A clean Git history, sensible unit tests and concise documentation will be part of the acceptance criteria alongside the working code.
By the end of week six I want:
• A live multitenant module deployed to my staging server
• Real-time reporting endpoints wired to sample procurement data
• A UI that lets users define, save and export custom reports
• At least one plug-in or API hook that feeds a visualisation tool of your choice
If that scope, the tech mix, and the timeline feel comfortable, let’s talk specifics and get the repository set up.