
A Full-Stack Developer for AI-Powered Review Management tool
- or -
Post a project like this- Posted:
- Proposals: 40
- Remote
- #4497285
- Open for Proposals







Description
Current stack:
Next.js
NestJS
PostgreSQL
Prisma
OpenAI API
Main responsibilities:
Build AI-powered review analysis features
Create clean mobile-first dashboards
Implement review damage detection systems
Build recovery tracking and analytics
Improve frontend UX/UI
Work with Google Business Profile APIs
Requirements:
Strong Next.js + NestJS experience
SaaS dashboard experience
AI/OpenAI integration experience
Clean UI/UX skills
Strong backend architecture knowledge. Task sheet attached so please quote after viewing the task sheet, thanks
Sandy S.
100% (4)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

Do you want the AI-powered review analysis to process all reviews in real-time, or is batch processing acceptable?
Should the smart priority queue automatically reorder reviews as new data comes in, or require manual refresh? -

Hi Sandy,
Thanks for the invite.
Questions before final quote:
1. Is Phase 1 already production deployed?
2. Is there an existing authentication/organization system?
3. Are queues/background workers already implemented?
4. Is there an existing design system/component library?
5. Will OpenAI costs need optimization constraints?
6. Do you already have Google Business Profile sync implemented?
7. Will multiple staff users per organization exist in Phase 2?
Looking forward to your answers. -

Hi Sandy, is this budget a placeholder or an actual budget?
-

* Is Phase 1 already live in production with stable Google Business Profile syncing/authentication, or are parts of the ingestion/sync layer still evolving?
* How are you currently handling Google review polling/syncing — scheduled jobs, webhooks, queues, or direct request-based syncing?
* Do you expect AI analysis/reprocessing to happen synchronously during requests, or through background workers/queues for scalability?
* Roughly how many organizations/locations/reviews do you expect the system to handle initially, and what scale are you targeting longer term?
* For the Smart Priority Queue, should prioritization be primarily AI-driven, rules-driven, or a hybrid with adjustable weighting per organization?
* Are businesses expected to collaborate internally within the platform (multiple staff/users per organization with assignments/roles), or mainly single-owner workflows initially?
* How much flexibility should organizations have in overriding AI classifications, recommendations, and workflows?
* Do you already have the review categorization/risk-scoring logic partially defined from Phase 1, or is that part of the Phase 2 engineering/product work?
* Should the “Impact & Recovery Insights” focus mainly on operational metrics (response speed, recovery success, aging, resolution rates) or deeper business/reputation analytics too?
* Is the current frontend architecture already structured cleanly for modular Phase 2 expansion, or would part of the work involve refactoring/reorganizing existing dashboard architecture first?
* Are notifications planned only in-app initially, or also email/SMS/push-based escalation flows later?
* Since auditability is important in the scope, are there any compliance/security requirements around AI-generated actions, user tracking, or organization-level activity history?
-

A few quick questions:
1. Is Phase 1 already live in production or still under development?
2. Do you already have Google Business Profile syncing working from Phase 1?
3. Will AI processing run synchronously or through background jobs/queues?

