Spoonity Generation 3
  • Preamble
  • Company
    • Product Strategy
      • Sales and Marketing
      • Support
    • Onboarding
    • Development
    • Partnerships
    • Summary
  • Tools
    • Ingestion Services
      • Point of Sales
      • Importing Tool
    • OnScreen
    • Dashboard
    • Widgets
    • Summary
  • Product
    • Cache
    • Delphi
    • Drachmae
    • Lydia
    • Hermes
  • Architecture
    • Events
      • The Nexus
    • Cloud
    • Multi-Tenancy
    • Spoonity Apps
      • Technical Overview
  • Case Studies
    • Large Bubble Tea Chain
    • Sports Apparel Retail
    • Family-Owned Grocer
    • Neighbourhood Dentist Office
Powered by GitBook
On this page
  • Spoonity Partner Program
  • Entrypoints for Partners
  1. Company

Partnerships

PreviousDevelopmentNextSummary

Last updated 4 years ago

Spoonity Partner Program

Adopting a formal "Partner Program" is essential in order for us to adequately scale our services and features to meet the needs of all of our potential clients.

Migrating to a fully decouplied, microservices architecture and breaking up our product offerings will allow us to isolate and componentize specific blocks of functionality that we can then look to partners to build on our behalf for clients.

This has a tremendous impact, and is a core driving force behind the success of platforms like Shopify, Wordpress, and more.

Partners should be properly vetted and showcased as trusted teams that we have confidence in their ability to deliver an amazing product or addon to our services.

Offering first-party addon and partner services would not be out of the question, and would be dependent on market factors.

Entrypoints for Partners

Spoonity partners would be presented with a multitude of ways to integrate with our platform.

The most important way would be through a native "Spoonity Plugin" system that would allow them to build functionality directly into our model that sits on top of our .

We would also look to partners to build custom applications such as mobile application and/or web interfaces using our APIs or SDKs.

Point of Sale plugins and other should require much tighter controls and certification processes. In an ideal world, these components should be fully owned and managed by us, and built using a shared framework for standardizing their behaviour.

A new focus should be put on point of sale integrations, especially in the areas of configuration and management.

event-driven
Data Core
ingestion services
extensibility