At agileBase we see our mission as helping companies in their journeys of growth and change. Some examples are growth by acquisition, setting up new ventures or simply organic growth over a number of years.
Our longest-standing customer has tripled turnover to £80m over the past ten years, grown in staff to five hundred employees and along the way set up new businesses to expand into areas related to their core competency (food distribution).
Our newest customer is a very profitable group of companies, which has seen recent growth by acquiring other operators in their market, improving and standardising their processes to form a best practice.
The fundamental principles that lets us serve these businesses well are: to be
- fast – agileBase can keep up with business demands, building systems in days not months
- flexible – building to meet current needs but able to adapt to future requirements too
- usable – engaging, beautiful software means that users adopt enthusiastically and quickly
- affordable – the above mean much less up front costly build and training time is necessary
When customers get larger, we need to support a new set of requirements, whilst maintaining these principles and that’s what today’s news is about.
To support more complex organisational structures, we’re introducing a number of new options that will make life easier for larger organisations, without complicating anything for companies at the earlier stages of their journeys.
1) Data filters per group
agileBase already allows an automated filter per user. For example when a salesperson logs in, they might only see sales enquiries belonging to them by default. Data filters can now be applied in the same way to groups, and a user may be a member of a number of different groups, so this allows access to be controlled very flexibly. For example, many organisations may share a central list of customers, with someone at the centre seeing everything, but with employees of each only seeing their own.
2) User selection
When choosing users to assign to a record e.g. a salesperson to an opportunity, these groups can also be used to narrow down the list.
3) Pre-setting data intelligently
When creating a new data record, data can be initialised from calculations or lookups from elsewhere in the system. For example, when adding a new purchase order, the system may look up the most recent order for the same product and pre-set the price and quantity.
4) Notification visibility
The data filters in 1 above also apply to notifications. i.e. data that appears in a user’s comment stream (agileBase’s internal messaging system), will be only relevant to them.
What’s to come?
We’re only part of the way through our own journey but the next steps are taking shape rapidly, led by our development team, customers and collaborators. What we’re working on at the moment are features largely to do with improving notifications, to make sure that they’re
Users may want to opt in or out of particular types of message. Some people may like to get emails, others may prefer ‘in-product’ notifications. When using the comments stream, people may want to see who’s going to receive a comment and add or remove recipients. Some may like to be prompted automatically when certain criteria are matched, e.g. a key account hasn’t had a call in two months.
Stay tuned for releases of these and more in the near future.