Extend your workflows
Build additional steps, rules and interfaces for processes that standard configuration cannot support. Keep that work connected to the records and responsibilities already in 390.
390 LABS · ENTERPRISE SOLUTIONS
390 Work, extended for your organisation.
Your organisation may need specialised workflows, integrations or applications beyond the standard setup. 390 Labs works with your team to design and build those capabilities on 390 Work.
Specialised workflows
Connected systems
Custom applications
390 Work
Business records · People and access · Daily operations
Build on what your organisation already runs on.
We begin with the capabilities in 390 Work, then identify what needs to be added or connected to support your requirements.
Connect your existing systems
Connect 390 Work with other software your organisation uses, so relevant records can move between systems without repeated entry.
Build applications on 390 Work
Create dedicated interfaces for your staff, customers or partners, using Work as the foundation for the business records and processes behind them.
What this could look like in your organisation.
ILLUSTRATIVE EXAMPLE
A distributor with a more demanding fulfilment process.
The business uses 390 Work for customers, sales and stock. It also needs specific rules for allocating stock across branches, a connection to a supplier’s ordering system and a dispatch interface for its warehouse team.
Labs would scope and build the additional capabilities around the business’s existing work on 390.
- 390 Work
- Customers, sales and stock.
- Additional requirements
- Allocation rules
- Supplier connection
- Dispatch interface
From an operational requirement to software your team can use.
Understand the work
We review the process, the people involved and the systems in use. Together, we identify what Work already supports and where additional engineering is needed.
Agree the scope
We define what will be built, how it should work and how delivery will be assessed. Responsibilities, milestones and costs are agreed before development starts.
Build and test with your team
We develop the agreed capabilities in stages and test them against the work your people need to complete.
Roll out and maintain
We agree the rollout, training, documentation and ongoing maintenance needed to support the solution.
An engagement scoped around your requirements.
Your proposal sets out the 390 Work subscription, engineering work, delivery milestones and ongoing support. Any third-party costs are identified clearly.
Labs is a separately scoped engineering engagement and can work alongside Guided or Advisory.
A few questions, answered.
Do we need to be using 390 Work already?
No. You can extend an existing Work setup or introduce Work as part of the agreed project. In either case, Work is the foundation of the solution.
How is Labs different from Guided and Advisory?
Guided helps you implement existing 390 capabilities. Advisory helps you structure operations and put them into practice on 390. Labs builds additional software when the requirements call for it.
Can we keep other software we use?
We assess how 390 Work can connect with those systems. Integration feasibility depends on the access and interfaces available.
What happens when 390 Work is updated?
Compatibility with Work updates and responsibility for maintaining the extensions are addressed in the solution design and support agreement.
What does your organisation need 390 to do?
Tell us about the work, the people involved and the requirements your current setup cannot meet. You do not need a technical specification to start the conversation.