This content is incomplete and may be inaccurate, feel free to look around & please check back later for updates.

  • No currencies. The platform would not handle any money, currency conversions, or payments directly. This would all be passed off to a third party as they have the scaled infrastructure and security already. It would also be a monthly subscription service – not a pay-per-service. This further removes the platform from needing to know anything currency – all it needs to know is whether a subscription is paid/valid or not.
  • No translations (but maybe layer). Translations can be handled a few ways, either with a third party translating the page, or more controlled by having consistent labelling and storing the translations in the product itself. The third party method is the easiest, and can be added on later. In-product translations can happen further down the track if a customer requires more accurate results.
  • Globalisation. The entire system would have globalisation baked in, as the influx of customers about to be onboarded used multiple languages, currencies, timezones, and data laws.
  • Easy & Flexible UI. The ordering system for the customers in the original MVP was a massive code nightmare – we needed to avoid this by splitting it in to logical steps, using methods that severely reduced development time and technical debt.
  • Recurring Tree Structure. Brands could set up their assets, and customers could belong to many brands, with customers also belonging to other customers. The best part was each branch or node on the tree work identically, so complex businesses can be created with very minimal upfront development, also minimising training for staff and customers.
  • Simple Customer Onboarding. This was a tie-in to the existing sales strategy discovered from the years of MVP’s. The sales strategy was to develop a working prototype before visiting the customer, to show the customer it’s already there and done so no complicated onboarding in theory. So a customer (demo) needed to be easy to create on the system rapidly.
  • No-Code. Remove the man-hours and incredibly high costs of custom work, by making the entire process a customer requires doable from within a web based interface without ongoing technical help or development. If a developer is required to do something, then that needs to be accessible within the UI by non-developers.
  • 3rd party authentication. Shifting the authentication to a 3rd party (AWS Cognito) removes all of the trickery and functions for auth away, leaving us with just a flag saying whether the user is authenticated or not. Much simpler, moves the encryption and security of logins & passwords away, and also shifts all the “sign in with google” auth workload off of our plate later.