Apps & ERPs
Inventory, orders, scheduling, approvals, client portals — the tools your team works in every day. We build light, focused apps and ERPs that fit how you actually operate, not the other way round.
- Timeline
- 4–8 weeks
- Team
- Lead + 2 developers + designer
- Model
- Phased, fixed price per phase
- Teams running operations on spreadsheets and WhatsApp
- Businesses paying for a heavy ERP they use 10% of
- Processes that need roles, approvals and an audit trail
- 01Process mapping with the people who do the work
- 02Data model and permissions designed up front
- 03Web app that works on desktop and phone
- 04Dashboards and exports for decision-makers
- 05Integrations with accounting, payments or messaging
- 06Data migration from your existing sheets
- 07Training, documentation and ongoing support
Four steps.One wall.
The same four steps as every Human Works project, tuned for apps & erps.
- 01Before we start
Understand
We sit with your team and map the process as it really happens — every hand-off, exception and spreadsheet.
- 02Agree it
Scope
We pick the one workflow that hurts most and scope a first version that replaces it end to end.
- 03Make it
Build
Weekly releases to a staging app your team can click through. Feedback goes straight into the next week.
- 04Hand it over
Ship
Data migrated, people trained, old process switched off. Then the next phase, if you want one.
Apps & ERPswe've built.
Goodquestions.
01What does 'light' mean?
It does the jobs you need and nothing else. Fewer screens, fewer settings, faster to learn. It can grow phase by phase as you need more.
02Who owns the code and data?
You do. Code lives in your repository, data in your cloud account. No lock-in, and full documentation at handover.
03Can it connect to Tally, Zoho or our accounting tool?
Usually, yes. We check the integration options during scoping and build sync or export as part of the first phase where it's needed.