Staff operations
Employee records, attendance and leave sit alongside payroll workflows. Overnight shifts require records to follow the shift's start day rather than splitting at midnight.
Internal Async platform / Async Management CRM
Internal software shaped around how our team works.
We built Async Management for our own company. The platform brings staff operations and a sales workflow into one internal system, with access rules and records that reflect the way the team works.
Discuss a similar projectTHE BRIEF
The work behind Async Management CRM.
An internal platform has to account for the exceptions in daily work. A shift can cross midnight. An imported lead may already exist. A quote can be accepted or rejected, and each decision changes what the team needs to do next.
We combined these workflows in a shared application rather than describing them as separate dashboards. This is internal Async software. The scope below explains the work involved without exposing staff records or financial data.
PRODUCT SCOPE
What we built.
Sales workflow
Lead imports feed customer records, quotes and loads. Duplicate handling and explicit quote decisions help keep the workflow consistent as records move between stages.
Finance and review
The system brings expenses, salary records and invoice workflows into the same platform. Financial calculations and review states belong to the data model as well as the interface.
Access and integrations
Role-based permissions restrict sensitive actions. Call-record integration and an audit trail support review across the teams using the platform.
WORKFLOW
A connected sequence of tasks.
- 01Import
Bring lead records into the system.
- 02Qualify
Maintain the prospect and customer record.
- 03Quote
Record the offer and its decision.
- 04Operate
Manage accepted work and review the figures.
DESIGN & ENGINEERING
Decisions that shaped the build.
Model the exceptions before building the screens.
Overnight attendance, duplicate imports and cancelled records each affect reporting. Those rules need definitions and tests, even when the interface looks straightforward.
Treat permissions as part of the workflow.
Staff records, financial actions and administrative changes need different access. A shared platform should not imply that every user can see or change everything.
Use scope to explain a software estimate.
The cost of a system like this depends on its rules, integrations and operating requirements. Our software-cost guide uses this project's workflows to explain what needs to be defined before estimating a similar build.
Read the custom software cost guide for the scope decisions behind an estimate.
RELATED SERVICES
Bring this experience to your project.
Next.jsReactTypeScriptPostgreSQL
YOUR PROJECT
Tell us what you need to build.
Share the users, the current workflow and the part you want to improve. We can discuss a useful first release.
Discuss your project