Enterprise
Workflow
Optimizer

The price is based on module complexity, number of distinct user roles, depth of analytics required, and third-party integrations needed. A single-module CRM with two roles and basic reporting is at the lower end. A full LMS with instructor dashboards, automated certificates, payment integration, and a student-facing portal is at the upper end. After the discovery call, a fixed price within this range is confirmed in writing before work begins — no ambiguity, no post-project surprises.

50% upfront before work begins, 50% on delivery of the staging environment — before production deployment and source code handover. For a ₹50,000 project: ₹25,000 upfront, ₹25,000 on delivery. For a ₹70,000 project: ₹35,000 upfront, ₹35,000 on delivery. The exact split is confirmed in the scope document.

Three complete rounds of consolidated feedback — submitted in writing as a single batch per round, not individual ad-hoc requests. Each round is addressed within 48–72 hours. Revisions cover adjustments to the agreed scope: changing how a workflow works, adjusting dashboard layouts, modifying role permissions, correcting data logic. They do not cover new modules, new features, or direction changes that weren't in the original brief. Three rounds is more than enough for a well-briefed engagement.

Bugs and performance issues in the delivered scope — things that break or behave incorrectly in production that weren't caught in QA. Security patches for vulnerabilities in our code. Role permission issues from the original implementation. Deployment problems tied to the original infrastructure setup. It does not cover new features, new user roles not in the original brief, or issues caused by changes your team makes to the codebase after handover.

Yes. Client-facing portals with restricted views (e.g. a client sees only their project status, invoices, and documents) are a common addition to CRM builds. This is scoped as part of the discovery process — the role-based access control architecture supports any combination of internal and external user types. Mention client portal requirements clearly in the brief.

Data migration from legacy systems (Excel, old software, another database) is available as an add-on scoped at kickoff. It is not included in the base package. If you have existing data that needs to carry over, disclose the volume and format in your initial brief — we'll assess the complexity and include the migration cost in the scope document before work begins.

Next.js 16+ frontend with TypeScript and Tailwind CSS. Node.js backend with REST API architecture. Supabase / PostgreSQL database. Deployed on Vercel or AWS depending on scale requirements. CI/CD pipeline configured for automated deployments. The stack is chosen for longevity and developer accessibility — any competent full-stack developer can read, extend, and maintain it after handover.

Yes — that's the point of an admin dashboard. User management (adding, deactivating, role assignment) is handled directly through the admin interface without touching code. For configuration changes that are deeper (new workflow stages, new analytics metrics), those are either in the admin UI already or quoted as new scope. The documentation explains what can be self-managed versus what requires a developer.

Email automation (triggered notifications, reminders, reports) via Resend or SendGrid is commonly included in the scope. SMS via Twilio or similar is available as an integration — the cost of the SMS service itself (per-message rates) is on your account, not ours. Mention notification requirements in the brief and they'll be scoped explicitly.

The codebase is fully yours. You can hire a developer to extend it using the provided documentation. For continued support or feature development from AdnanBuilds, that becomes a new engagement quoted at a transparent rate. Many enterprise clients opt for a quarterly feature sprint — a fixed-scope block of new features quoted per sprint. That conversation happens after delivery, not during.