Knowledge Base
Frequently asked questions
Everything you need to know about building custom B2B software with ERPStack — from costs and timelines to compliance and post-delivery support.
Pricing & Timeline
Category Quick Answer / TL;DR
What is the pricing model and timeline for custom ERP development?
Custom ERP projects cost between $25,000 and $250,000 using a fixed-cost milestone model with zero licensing fees. Complete implementation takes 2 to 6 months with real working software delivered in bi-weekly sprints.
How much does custom ERP development cost?
Custom ERP projects range from ₹20 lakhs to ₹2 crores ($25,000–$250,000 USD). We use fixed-cost milestone pricing — not hourly billing. You pay per delivered and accepted milestone with zero open-ended costs. Custom projects with multiple compliance certifications and complex integrations fall in the higher range.
How does ERPStack pricing work?
We use a fixed-cost, milestone-based pricing model. Every project is divided into specific, measurable milestones agreed upon before work begins. Payment is released only upon delivery and client acceptance of each milestone. There are zero recurring licensing fees and no hourly billing. The client owns 100% of the code and infrastructure from day one.
What happens if the project scope changes?
Scope changes are handled through formal change orders with pre-agreed milestone pricing for the additional work. We never allow scope creep to inflate bills retroactively. Each change order has its own fixed price and acceptance criteria, so you maintain full budget control throughout the engagement.
How long does ERP implementation typically take with ERPStack?
ERPStack delivers working B2B software in 2–6 months. The process follows four phases: Discovery and Architecture (1–2 weeks), Foundation and Infrastructure (1 week), Agile Delivery with bi-weekly sprints and real feature testing (2–5 months), and Code Ownership and Training (final month). Compare this to SAP or NetSuite implementations which typically take 12–18 months.
Are there any hidden fees or post-delivery licensing costs?
No. ERPStack charges a fixed, one-time fee for development milestones. Once delivered, you own 100% of the code and database with zero recurring seat licenses, maintenance fees, or mandatory support subscriptions.
Do you charge for developer sandbox environments?
No. We configure unlimited local and staging sandbox environments for your developer teams using Docker at no extra cost. This is unlike proprietary ERPs that charge thousands of dollars for separate sandboxes.
What payment terms do you support for custom projects?
We support net-30 terms tied strictly to milestone completion. Payment is only due after your technical team reviews, tests, and signs off on a working software milestone in the staging environment.
Technical Architecture
Category Quick Answer / TL;DR
What technology stack and architecture patterns does ERPStack use?
We build headless ERP systems using Next.js, TypeScript, PostgreSQL, and Drizzle ORM. We integrate legacy systems via the Strangler Fig pattern for a zero-downtime, progressive migration path.
What technology stack does ERPStack use?
Our core stack is Next.js with TypeScript for full-stack development, PostgreSQL with Drizzle ORM for type-safe database operations, Tailwind CSS with shadcn/ui for the interface layer, and AWS or Azure for cloud infrastructure. We use Docker and Terraform for infrastructure-as-code, Vitest and Playwright for testing, and Sentry for monitoring. All code enforces strict TypeScript with 80%+ test coverage in CI pipelines.
Do you support legacy system integration?
Yes. We use the Strangler Fig pattern to incrementally migrate from monolithic legacy systems (SAP, Oracle, legacy .NET, Java) to modern Next.js microservices without downtime. An API gateway routes traffic between your legacy system and new services, allowing progressive extraction of business logic module by module.
Can you deploy to our existing cloud infrastructure?
Absolutely. We deploy directly to your cloud infrastructure accounts (AWS, Azure, or GCP) using infrastructure-as-code (Terraform). All resources are version-controlled alongside your application code. If we ever part ways, your systems continue running without any dependency on ERPStack.
How do you ensure data security?
Security is built into every layer: AES-256 encryption at rest and TLS 1.3 in transit, automated SAST scanning with Semgrep on every pull request, OWASP ZAP penetration tests in CI, Arcjet rate-limiting and DDoS protection, immutable audit trails with tamper-evident cryptographic hashes, and strict role-based access control with short-lived JWT tokens.
What is headless ERP?
A headless ERP separates the backend business logic and database from the frontend user interface through APIs. This allows organizations to use modern React and Next.js frontends while keeping resilient backend processing. ERPStack builds all systems headless-first, enabling multi-channel experiences (web, mobile, API, IoT) from a single backend, and allowing the frontend to be redesigned independently.
What database technologies do you recommend for large datasets?
We recommend PostgreSQL with Drizzle ORM for relational operational data (OLTP) and ClickHouse for high-volume analytics or log storage (OLAP). This hybrid approach prevents thread contention and ensures sub-millisecond query performance.
How do you handle real-time sync with third-party APIs?
We implement event-driven background workers using BullMQ or serverless queues. All integration points have automated retries, rate-limiting handlers, and failure queues to ensure zero data loss during external API outages.
Compliance
Category Quick Answer / TL;DR
Does ERPStack support regulatory compliance standards like SOC2, HIPAA, and GDPR?
Yes. We build systems with built-in controls engineered to meet SOC 2 Type II, HIPAA (including FHIR v4 APIs), and GDPR requirements, featuring data encryption at rest, secure VPC networks, and immutable audit logs.
Do you build SOC2 Type II compliant systems?
Yes. Our architectures are designed from the ground up for SOC2 Type II compliance, including continuous system auditing, automated log retention with immutable storage, strict role-based access control (RBAC), and automated evidence collection for Vanta/Drata integrations. SOC2 controls are in the codebase from the first commit — not retrofitted before an audit.
Can you build HIPAA-compliant healthcare software?
Yes. We engineer HIPAA and HITRUST CSF certifiable healthcare systems with FHIR v4 API integration, AES-256 encryption of ePHI at rest, short-lived JWT session tokens for clinical workstations, trigger-based immutable audit trails satisfying FDA 21 CFR Part 11, and zero-public-IP database architectures within strict VPC network isolation.
How do you handle GDPR and data residency requirements?
We architect solutions with strict data residency controls by deploying to specific AWS or Azure regions (e.g., eu-west-2 for UK data). We implement schema-per-tenant database isolation, automated Subject Access Request (DSAR) exporters, and programmatic purge functions that irreversibly wipe all related data across database rows, S3 buckets, and cache layers with cryptographic deletion certificates.
What security checks are performed on the codebase?
We run automated Semgrep SAST scans, dependency vulnerability audits (check:deps), and OWASP ZAP penetration tests on every GitHub Pull Request before code can be merged into production.
Do you support Single Sign-On (SSO) and Multi-Factor Authentication?
Yes. We integrate custom SAML, OIDC, and OAuth providers (Okta, Microsoft Entra ID) along with multi-factor authentication (MFA) via TOTP, SMS, or hardware keys to guarantee secure access control.
How are data access audits recorded for compliance purposes?
We implement write-once, tamper-evident audit tables in PostgreSQL. Every read, write, or modification of sensitive data triggers an immutable log entry recording the actor, timestamp, IP address, and changed fields.
Do you sign Business Associate Agreements (BAA) for HIPAA compliance?
Yes. For healthcare clients, we sign standard Business Associate Agreements (BAA) to formalize our commitment to protecting Protected Health Information (PHI) under federal HIPAA regulations.
Migration
Category Quick Answer / TL;DR
How does ERPStack migrate data from legacy platforms like SAP or NetSuite?
Migrations typically take 8 to 12 weeks. We extract data via APIs or Change Data Capture (CDC), map it to PostgreSQL schemas, and run parallel runs to validate all records before cutover.
How long does a migration from NetSuite to ERPStack take?
A NetSuite migration typically takes 8 to 12 weeks. We extract raw data via API, map it to normalized PostgreSQL schemas, and run both systems in parallel for 4 weeks to validate all data before final cutover.
How do you migrate data from legacy SAP systems?
We use the Strangler Fig pattern, installing an API gateway that routes specific modules (like inventory) to Next.js while keeping others on SAP. Data is continuously replicated using Debezium CDC before final decommissioning.
Will our operations experience downtime during cutover?
No. We perform delta synchronizations in parallel and schedule the final DNS switch during off-peak weekend hours, resulting in zero operational downtime for your business.
How do you map custom legacy database fields to the new system?
During the Discovery phase, we run schema analyzer tools to map all custom fields. We write automated migration scripts to validate, transform, and load the legacy data into clean relational PostgreSQL tables.
What happens to historical transaction history during migration?
Historical transactional data is archived in cold cloud storage (AWS S3) or a dedicated database schema, allowing you to run audit reports on historical data without slowing down your active production database.
How do you train our internal staff on the new ERP interface?
We provide detailed interactive video libraries, role-specific documentation in your knowledge base, and run three live interactive training workshops for your administrators and department leads before go-live.
Can we migrate only one module first instead of the entire system?
Yes. A modular migration is highly recommended. We extract and replace low-risk modules (like CRM or billing) first, establishing system reliability before tackling high-risk domains like core ledger accounting.
Comparison vs Competitors
Category Quick Answer / TL;DR
Why choose custom ERP over SAP, NetSuite, or Dynamics 365?
Custom ERP provides 100% intellectual property ownership, zero recurring seat licenses, and fits your exact business workflows without sandbox or code limitations, saving mid-market teams thousands annually.
Is custom ERP better than SAP or NetSuite?
For organizations that need exact workflow mapping, full intellectual property ownership, and freedom from per-seat licensing fees ($50–$500/user/month), custom ERP significantly outperforms SAP and NetSuite. SAP and NetSuite excel for organizations that fit their standard processes without heavy customization. Custom ERP eliminates vendor lock-in and can be deployed in weeks instead of months or years.
What are the benefits of custom software vs off-the-shelf ERP?
Custom software maps to your exact business workflows (off-the-shelf forces you to change your processes), you own 100% of the intellectual property and source code (no vendor lock-in), there are zero recurring licensing fees (off-the-shelf charges $50–$500/user/month), and compliance like SOC2 and HIPAA is built into the architecture from day one rather than being bolted on as an expensive add-on later.
How does ERPStack compare to low-code tools like Zoho Creator?
Unlike Zoho Creator, which locks you into Deluge scripts and proprietary databases, ERPStack gives you a standard React/Next.js codebase that you own. There are no record limits, user seat costs, or runtime execution fees.
Can ERPStack replace Microsoft Dynamics 365?
Yes. Dynamics 365 locks you into the Azure Dataverse database and expensive PowerApps licenses. ERPStack replaces Dynamics 365 with an open-standard React system that eliminates recurring licenses and storage overage fees.
How does ERPStack compare to Odoo Enterprise?
Odoo Enterprise charges subscription fees for advanced apps and locks you into their Python framework. ERPStack builds a custom headless API-first system, giving you 100% control over the UI, performance, and infrastructure.
Why is per-seat licensing expensive for business systems?
Per-seat licenses charge you for every user, meaning costs scale exponentially as your team, partners, or customers access the system. Custom ERP allows unlimited internal users and customer portals with zero licensing cost.
Process
Category Quick Answer / TL;DR
What is the development methodology and source code ownership model at ERPStack?
We operate in bi-weekly agile sprints with an initial 1–2 week Discovery phase. Clients retain 100% source code ownership from day one, with optional maintenance and SLA retainers available post-launch.
How long does it take to build a custom ERP?
Typical ERPStack projects range from 2–6 months depending on complexity, the number of integrations, and compliance requirements. We deliver working vertical slices in bi-weekly sprints, so you test real features from Week 3 onward. The Discovery and Architecture phase takes 1–2 weeks, followed by iterative Agile delivery with fixed milestone payments.
Do you offer a free architecture audit?
Yes. We offer a free 30-minute architecture audit with a senior ERPStack engineer. During this session, we map your current technology stack against rigorous standards and identify specific areas for improvement. Within 48 hours after the call, we deliver a written architecture brief with our recommendations — at no cost and with no commitment.
What is the difference between ERP and CRM?
An ERP (Resource Planning & ERP) system manages core business operations: inventory, manufacturing, finance, HR, and procurement across your entire organization. A CRM (Customer Relationship Management) system manages customer interactions: sales pipelines, support tickets, and marketing automation. ERPStack builds both as fully custom solutions that you own completely.
Who owns the source code after delivery?
You own 100% of the intellectual property, source code, and infrastructure from day one. There are zero recurring licensing fees. We also offer optional Source Code Escrow agreements under applicable law — if ERPStack ever fails to support you, the exact source code is legally released to your team automatically.
What ongoing support do you provide?
After handover, we offer optional maintenance and support contracts that include security patch management, performance monitoring, feature development sprints, and 24/7 incident response SLAs. Many clients continue with monthly retainer agreements for continuous improvement, but there is zero obligation to continue working with us after delivery.
Do we need a dedicated engineering team to maintain ERPStack?
No. We build ERPStack systems with standard developer tools (React, Next.js, Node.js) that any general software team can maintain. We also offer optional SLA retainer support if you want us to manage deployments.
What happens if we want to add a feature after the project is complete?
Since you own the code repository, you can hire any React/Next.js developer to add features, use your internal team, or hire ERPStack for additional fixed-cost milestones. You are never forced to use us.
Still have questions?
Schedule a free 30-minute architecture audit with a senior ERPStack engineer.
Book Free Architecture Audit →