CUSTOMIZATION
Built to your process, not around it.
Standard ERP covers maybe eighty percent of how you work. The remaining twenty is where projects usually go wrong. We build that part as proper versioned code that survives the next upgrade.
WHAT WE BUILD
The work that actually gets requested.
Across both platforms, in sprints you can see and stop.
Doctypes and data models
New record types that fit your domain — with the validations, naming series, permissions and links to existing records already thought through.
- Custom doctypes & fields
- Naming series and numbering
- Role-based permissions
Workflows and approval chains
Multi-step approvals with the right people, the right thresholds and an audit trail that satisfies your auditor rather than annoying your staff.
- Conditional routing
- Delegation and escalation
- Full audit trail
Reports and dashboards
Query reports, print formats and dashboards built against your real data, in Arabic and English, with the numbers your management actually asks for.
- Bilingual print formats
- Scheduled email reports
- Role-scoped dashboards
Integrations
Banks, payment gateways, logistics providers, government portals, WhatsApp, your existing warehouse system. Retries, logging and alerting included.
- REST and webhook based
- Retry and dead-letter handling
- Integration monitoring
Upgrade-safe by construction
Everything ships as a versioned app in your repository with tests. When the platform moves, we know what breaks before you do.
- Versioned in Git
- Automated test coverage
- Regression run per upgrade
HOW WE WORK
Terms that keep both sides honest.
- Engagement
- Two-week sprints with a demo at the end of each
- Pricing
- Fixed scope, fixed price — or retainer for ongoing work
- Code ownership
- Yours. Delivered to your repository.
- Documentation
- Handover docs and a recorded walkthrough per feature
- Warranty
- 30 days on delivered work
- Platforms
- Frappe / ERPNext and Odoo
PROCESS
From request to production.
The same loop every sprint, so nobody is surprised at invoicing time.
- 01
Scope
We write down what the feature does, what it doesn’t, and what it costs.
- 02
Build
Development on a staging instance with your real data shape.
- 03
Review
You test on staging and sign off, or send it back with notes.
- 04
Ship
Deployed to production through the pipeline, with rollback available.
QUESTIONS
Before you ask us.
Yes, unconditionally. It lands in your repository as we build it, not at the end of the project. If you leave, the code leaves with you.
Usually. We start with a short audit to see what we’re dealing with — sometimes the honest answer is that a rewrite is cheaper than maintaining what’s there, and we’ll say so.
Small changes get absorbed. Anything larger becomes its own scoped item for the next sprint, priced before we start. We don’t do surprise change orders.
Yes, though it works better when we do both — we can test against the real environment and deploy through a pipeline we control.
Describe the process that doesn’t fit.
We’ll scope it and price it before you commit to anything.