How to build your own ERP in 2026 (when SAP, NetSuite, and Odoo are overkill)

SAP and NetSuite quote six figures with year-long implementations. Odoo and Microsoft Dynamics are cheaper but still painful. For a $5M to $50M SMB, the new option in 2026 is building your own ERP for a few hundred dollars a month. Here's the playbook.

The word "ERP" used to mean one of three things, all bad for an SMB owner:

1. SAP, Oracle, or Microsoft Dynamics implementation. Six-figure license. Year-long deployment. Consultant army. Designed for $500M+ enterprises.
2. Odoo or NetSuite mid-market. Cheaper but still six figures over three years once you factor in implementation, customization, and the consultant retainer.
3. Excel and a sigh. What most $5M to $50M SMBs actually use because the above options were impossible.

In 2026 there's a fourth option that nobody warned you about: building your own ERP, in a custom-built native app, for a few hundred dollars a month all-in.

This is the playbook for that fourth option.

What an SMB ERP Actually Is

Enterprise ERP (SAP-grade) is a multi-thousand-feature monster designed for multinationals. Your SMB doesn't need that. Your SMB needs:

• Clients and leads, with a kanban pipeline matching your real sales process.
• Projects or jobs, attached to clients, with statuses, budgets, and timeline.
• Field operations (if you have field teams): mobile check-in, voice notes, photos, AI reports.
• Documents: quotes, contracts (with e-sign), invoices.
• Inventory (if you have inventory): SKUs, stock levels, supplier orders.
• Time tracking and timesheets (or integration with a payroll provider).
• Cash flow visibility: invoiced vs paid, payables aging.
• Role-based access: owner sees everything, dispatcher sees jobs, tech sees their own.
• Reporting: basic dashboards on revenue, project profitability, team utilization.

That's it. About 9 modules. Each one is a couple of weeks of evening work in Rork. Compounded, it's a complete SMB ERP that fits your business better than anything you could buy.

The Stack You Build On

Custom doesn't mean from scratch. The right SMB ERP stack in 2026:

• Rork for the application layer. Generates Expo / React Native + web from one project.
• A managed backend (Postgres database, auth, storage, row-level security) that Rork runs for you, no separate database account to buy or operate.
• Your existing accounting tool (QuickBooks, Xero, Sage, Holded, FacturaDirecta) for books, via API.
• Your existing payroll provider (Gusto, Rippling, ADP, Sage Payroll) for payroll, via API.
• An e-sign provider (Dropbox Sign, SignNow, DocuSign) for contracts.
• An email service (Resend or Postmark) for transactional emails.
• OpenAI or Anthropic API for AI features (voice transcription, structured reports, document analysis).

Monthly cost for a 50-person business:

• Rork: from $20/month (Rork Pro); Rork Max at $200/month if you need native iOS Swift. Rork's managed backend (Postgres, auth, storage) is included, not a separate database bill.
• E-sign provider: $25 to $50/month
• AI APIs: $50 to $200/month
• Email service: $20/month

Total: roughly $100 to $500/month all-in for a custom SMB ERP, depending on your Rork plan and usage.

Compare to a Microsoft Dynamics SMB implementation at $50k+ upfront and $2k+/month ongoing. Compare to NetSuite at six figures upfront and $10k+/month. The custom path is dramatically cheaper for what most SMBs actually need.

The 90-Day Build Plan

You don't build the whole ERP at once. You build modules in order of pain.

Days 1 to 7: Foundation

• Managed Postgres backend. Six core tables (Client, Lead, Job, Interaction, Document, User).
• Auth (Apple Sign In, Google Sign In). See the auth guide.
• A skeleton mobile app and web target in Rork.

Days 8 to 30: Client + Project Module

• Client list, client detail screen, lead pipeline kanban.
• Project list, project detail screen, project status workflow.
• Interaction logging (calls, notes, emails).
• Push notifications when a new lead lands.
• Roll out to office staff. They use it as the new source of truth.

Days 31 to 60: Field Operations Module (If Relevant)

• Mobile field crew app: GPS check-in, voice notes, photos.
• AI-powered site report generation. See field service guide.
• Offline-first sync.
• Role-based access (technician sees only their jobs).
• Roll out to field team.

Days 61 to 90: Documents + Finance Module

• Quote generation from project data.
• Contract auto-generation with e-signature. See contract guide.
• Invoice generation tied to project milestones.
• Integration with accounting (QuickBooks/Xero/Sage API).
• Cash flow dashboard.

Days 91+: Iteration

By day 90 you have a working ERP your whole team uses. Subsequent work is incremental:

• Inventory module (if needed).
• Payroll integration.
• Time tracking.
• Reports your accountant wants.
• Specific automations as you discover them.

What You Get That SAP Can't Give You

The custom ERP has three advantages SAP, NetSuite, and Microsoft Dynamics structurally can't:

1. Workflow Fits Your Business

When your subcontractor model is non-standard, when your invoicing requirements are Spanish or German or Brazilian, when your sales cycle has a step the SaaS doesn't model: the custom ERP just does it. SAP can't be told to change.

2. Cost Doesn't Scale With Headcount

SAP, NetSuite, Dynamics, all charge per user. Your 50-person team costs 5x what your 10-person team did. Rork is credit-based, not per-seat, so your subscription doesn't multiply every time you add a teammate to the app. Hire 100 more people and your team's seats don't drive the bill the way per-user enterprise licenses do. The math gets better as you grow, not worse.

3. You Own the Roadmap

Want a new field on the client record? Add it tonight. Want a new report your tax accountant requested? SQL query. Want to integrate with the local government's e-invoicing portal that launched last month? Edge Function. With SAP, every change is a consultant ticket. With custom, every change is yours.

What You Lose

Honest tradeoffs:

• No "out of the box" features for things you didn't think about. SAP has 47 reports you'd never have built. Most you'll never miss. A few you'll have to build when you realize you want them.
• No vendor support hotline. Discord and the Rork support team replace this. Different model.
• No third-party integrations marketplace. SAP has thousands of pre-built connectors. With custom, you build the connector (usually a couple of hours per integration). Slower upfront, but you only build what you need.
• No on-paper compliance certifications. SOC 2, ISO 27001, HIPAA, are claims SAP makes on its infrastructure. A certification held by an underlying infrastructure provider does not automatically transfer to your application, your data handling, or your business processes, so don't assume your custom ERP inherits a compliance posture. For most SMBs the managed backend's security is fine as-is. For regulated industries (healthcare with HIPAA, finance with SOC 2 requirements), plan to do your own compliance work on top.

What Operators Are Actually Doing

A $20M Spanish construction company runs its custom ERP on this stack. Client intake, project tracking, field operations, contracts, invoicing, all in Rork. Spanish SII e-invoicing integration via Edge Function. Apple Business Manager internal distribution. The owner pays $200/month for Rork Max plus another $200 for infra. Total: about $5,000/year. SAP would have quoted $80k for licenses alone. NetSuite was $40k for the same SMB tier.

A B2B wholesale operator built a custom distribution ERP for $4,600 of Rork spend across 30 projects of iteration. Order management, customer pricing tiers, multi-location inventory.

A cannabis dispensary chain built a compliance-focused ERP across 24 Rork projects: POS, age verification, inventory by category, compliance reporting, multi-location aggregation.

A healthcare practice manager built rehabilitation patient tracking across multiple iterations. Patient progress, treatment plans, billing integration.

All in 2026. All in Rork. None of them needed SAP.

What to Do This Week

If you've been carrying an ERP project in your head and the vendor quotes have made you give up: stop comparing them to each other. Open Rork. Build the first module (clients + leads). Ship to TestFlight by Friday. Hand it to your office team.

In 90 days you have your own ERP. In a year you have a system that fits your business better than anything anyone could sell you, at 5% of the price.

Frequently asked questions

Can a non-technical owner really build a working ERP?+

Yes, for an SMB definition of ERP (clients, projects, inventory, invoicing, payroll integration, basic reporting). What you can't build alone is a Fortune-500-grade ERP with deep multi-currency, multi-entity consolidations, regulatory compliance for dozens of countries simultaneously, and 10,000-user concurrency. For a $5M to $50M business, what you actually need is in reach of a non-technical operator using Rork plus Supabase in 60 to 120 days.

What does a custom ERP actually replace?+

For a typical SMB it replaces some combination of: a CRM ($24k/yr SaaS), a field service tool ($18k/yr), an e-sign tool ($3k/yr), a scheduling tool ($7k/yr), a project management tool ($5k/yr), document storage ($9k/yr), plus the manual workflows people do because nothing fits (a part-time admin role at $30k+). Total savings: $50k to $100k/year.

Why don't more SMBs do this?+

Two reasons. (1) Until 2024 the tooling wasn't good enough. AI builders produced toys. (2) The category awareness lag, most SMB owners still think 'ERP = SAP = $500k.' They haven't updated their mental model. The early movers are eating their competitors' margins right now.

Does it integrate with my accounting (QuickBooks, Xero, Sage, Holded)?+

Yes via API. All major SMB accounting platforms have REST APIs. A Supabase Edge Function syncs invoices, payments, expenses both directions. Setup is typically half a day per integration. The custom ERP handles operations; the accounting tool handles books. Each does what it's actually good at.

What about payroll? Inventory? Compliance?+

Payroll usually stays in a specialized provider (Gusto, Rippling, Sage Payroll, ADP). Your custom ERP integrates with the API for time tracking and payment data. Inventory: build it custom inside the ERP if your inventory is operational (construction materials, retail SKUs). Compliance: country-specific e-invoicing (US, UK MTD, Spanish SII, German XRechnung, Brazilian NF-e) is doable as Edge Functions integrated into your ERP.

How long does it take to ship a usable custom ERP?+

v1 with client management, project tracking, and invoicing: 30 to 60 days. Full v2 with field service, contracts, e-sign, accounting integration: 60 to 120 days. The good news: you ship modules, not the whole thing at once. Module 1 (client CRM) is in production while you build module 2 (project tracking). Compounds fast.

What's the right team size to start?+

One non-technical owner with 30 to 60 days of evenings is sufficient for v1. Some operators bring in a freelance developer for 5 to 10 hours/week for tricky parts (Apple Sign In, complex SQL, native module customization). Optional, not required.