How do you know you've outgrown spreadsheets?
The symptoms are consistent across every company we've seen at this stage: the same number exists in three places and disagrees in two of them; month-end close takes a week of copy-paste forensics; one operational person has become a human API between systems; and leadership makes decisions on numbers that were true nine days ago. Each symptom is annoying alone — together they're a scaling ceiling, because every new customer, SKU or hire multiplies the reconciliation work.
The conventional prescription is an ERP suite: NetSuite, SAP Business One, Odoo with consultants. For some companies that's right. But mid-six-figure implementations, per-user pricing forever, and — the quiet killer — reshaping your operations to match the software's assumptions is a steep price for a company whose actual need is 'make our seven core workflows share one database.'
What does a right-sized custom ERP include?
Exactly the modules your operations need, and nothing you're forced to buy alongside them. We scope from your workflow map, not a vendor's feature matrix.
Every module reads and writes one shared database — that single fact eliminates the reconciliation industry your team has been running by hand.
- Order and inventory management shaped to how your products and fulfillment actually flow
- Finance operations: invoicing, payables, budget tracking, month-end reporting — synced to your accounting system, not replacing your accountant
- Project and resource management where services revenue needs it
- People operations: capacity, contractors, approvals and onboarding flows
- Dashboards with live numbers — the same number, everywhere, finally
- Role-based access and audit trails, because ERPs hold the crown jewels
Why is custom ERP suddenly affordable?
Because the economics of building software collapsed. The work that made ERP implementations seven-figure projects — armies of consultants configuring, integrating and customizing — is precisely the work AI-accelerated development compresses hardest. A senior engineer with modern tooling now ships in weeks what a consulting pod shipped in quarters, and Chalk Labs's whole delivery model is built on that arbitrage.
Our ERP builds run $15k–40k fixed against enterprise implementations that routinely land between $100k and $500k+ before annual licensing. The trade-off is honest: you get your workflows, not five thousand configurable features you'll never open. For a 20–200 person company, that trade is almost always correct — the feature you need is 'fits us', and it's the one feature no suite sells.
How does an ERP build avoid becoming the thing it replaces?
The failure mode of every operations system is drift: the business changes, the system doesn't, workarounds accumulate, and three years later someone is pitching a replacement. We design against drift from day one — modular architecture where workflows are cheap to modify, admin controls that let your team adjust fields, stages and rules without a developer, and documentation written for whoever maintains it after us.
Rollout is phased deliberately: one workflow goes live first with its real users, feedback reshapes it, then adjacent modules follow — because big-bang ERP cutovers are where adoption goes to die. Post-launch, clients choose an iteration retainer or in-house ownership of a standard-stack codebase. The system's job is to stop being a project and become plumbing: boring, trusted, and quietly saving your team its Priya.
Questions we hear about this
Suites win when your operations are standard for your industry and you want their ecosystem — accounting depth, compliance modules, marketplace apps. Custom wins when your workflows are non-standard, the suite quote exceeds six figures, or you'd be renting hundreds of features to use nine. We'll map your workflows against both paths honestly before you spend.
No, and it shouldn't — QuickBooks or Xero remain your ledger of record, keeping your accountant and auditors happy. The ERP handles operations (orders, inventory, projects, approvals) and syncs clean transactions into accounting automatically. That boundary is deliberate: operational flexibility where you need it, compliance-grade accounting where required.
We phase it precisely because your team is stretched: one workflow migrates at a time, running parallel with the old spreadsheet until trust is earned, with training built into weekly demos. The people who run the current system are design partners from week one — their workarounds are requirements, and their buy-in is the project.
They will — that's designed for. Admin controls cover routine changes (fields, stages, rules, users) without code; structural changes go through an iteration retainer or your own developers on the documented standard stack. Compare that with suite ERPs, where process changes mean consultant engagements at consulting rates, forever.