Logging
Errors are written to logs or databases which notify the developer so swift action can be taken.
← What we build
Example solution
Employee Onboarding
Before
- Take employee details.
- Put them into your spreadsheet
- Put them into your CRM
- Email them to payroll.
After
- A form in an app or email is filled out.
- Employee details are seamlessly entered into your CRM, spreadsheet and sent to payroll.
- Appropriate permissions and access rules are administered.
Example
API gateway
Automation
Check details
Map fields
Spreadsheet
| Employee name | Email address | Team |
|---|---|---|
| — | — | — |
CRM
- First name
- —
- Last name
- —
- Contact email
- —
- Department
- —
Built for the real world
Reliability and safeguards
A straightforward automation like this requires standard software concepts to ensure reliability.
Validation
Strict processes ensure input and output data is acceptable and correct. Without this, incoming information may be the wrong shape for the system and prevent the workflow from running properly/
Duplicate prevention
Before sending details to each platform, a check is carried out to ensure the details aren't already there - this is a rare case but it can happen if a successful write to said platform never returns confirmation - this is the kind of edge case BFdev systems are built with in mind of.
Built around your process
Customisation
This automation is highly adaptible to your business needs
Fit to your needs
While this automation specifically deals with the employee onboarding process, it's really an example of how many data input can be automated. For example even if you have a low turnover and employee onboarding takes little of your time, you may spend lots of time filling out candidate details - as in the case of a hiring manager or recruiter.
System variability
The main variability in this app comes with what systems your business uses - whether its CRMs, spreadsheets, an in house app, or even whatsapp for more informal setups.
Security concerns
As this automation handles employee information, stringent security measures may be required. Stronger checks on incoming information may be utilised, as well as stricter rules on who can access employee information once its in the system.
Suitable businesses
The same approach works wherever information needs to move between systems.
Recruitment
Capture candidate and employer details once and populate the relevant systems.
Property management
Transfer maintenance requests into the property system, linking the tenant, property and issue without retyping.
Legal services
Take information from client intake forms and populate case records and standard documents.
Marketing agencies
Take client briefs submitted through forms and create project records, tasks and campaign documentation.