Org and permissions
Departments, jobs and roles are configurable. Who can see payroll, who can approve a contract—by rule, not by memory.
Custom software · App Customization
Write goals, current state, and constraints for App Customization. Ship in phases. Guides below stand alone.
01 / Method
If OA is slow, tickets go missing, and permissions are a mess, people retreat to WeChat groups. DaXi Technology starts with org structure and roles, then turns leave, expenses, contracts and seals into tickets you can chase and track.
When you need to connect a business system, finance or HR, the management back office is the entry—not a second copy of master data.
Get leave, expenses and seals running, then add contracts and ERP modules. Easier to land than boiling the ocean.
Who can see payroll, who can approve a contract—by rule. When someone changes jobs, access changes with them.
Overdue reminders by email or WeCom, so a flow does not die in unread.
02 / Deliverables
Scope notes, phased plan, and acceptance checklist for App Customization — not a one-line total price.
Departments, jobs and roles are configurable. Who can see payroll, who can approve a contract—by rule, not by memory.
Leave, expenses, purchasing and seals route by conditions. Overdue items can be chased; people can check status themselves.
Contract ledger, versions and expiry reminders live in one place, instead of on personal laptops.
Connect inventory, orders or basic finance when you need them. You do not have to buy a full suite on day one.
Policies, how-tos and FAQs are searchable, so new hires ask the same question one fewer time.
To-dos, email or WeCom reminders, so an approval does not sleep in a manager’s unread.
03 / Process
Clarify → scope & phases → design/build → integration & acceptance → launch and support.
List the approvals that must go live and who decides. Phase one stays at three to five.
Draw departments, jobs, roles and data scope before any form design.
Split by amount and department. Write overdue and reassignment rules into the system.
Which HR, finance and business APIs to use, and how old tickets become read-only archive.
Run real tickets for two weeks, then shut the parallel WeChat approvals.
04 / Scenarios
Scale and org shape change which flows go first. Match the scenario before you debate a full suite.
Select
Read this App Customization guide to align goals and phase-one scope.
Should You Build a Field-Service App? Dispatch, Trails, and Parts Closed Loops MatterScope
Read this App Customization guide to align goals and phase-one scope.
Designing Offline Sync for Industrial Apps: Conflict Policy Beats Works OfflinePhases
Read this App Customization guide to align goals and phase-one scope.
Should You Build a Field-Service App? Dispatch, Trails, and Parts Closed Loops MatterLand
Read this App Customization guide to align goals and phase-one scope.
Designing Offline Sync for Industrial Apps: Conflict Policy Beats Works OfflineAccept
Read this App Customization guide to align goals and phase-one scope.
Should You Build a Field-Service App? Dispatch, Trails, and Parts Closed Loops Matter05 / Guides
Guides on selecting, scoping, and landing App Customization. Each article stands alone.
Before you start
Many projects start with three to five high-frequency flows, then add modules once those run. Easier to land than boiling the ocean.
Inquiry
Start with headcount, the tools you already use, and the flows you want live first. Faster than “we want an OA.”