Multi-tenant cloud ERP SaaS platform
Since 2020, Netbase has worked as offshore development and managing partner on a multi-tenant cloud ERP that a US software company offers as SaaS to small and mid-sized businesses. This record covers phase-one scope for agency SMEs; the client and product are not named, and no usage or business result is claimed.
Submit a project See the related service
Record at a glance
- Evidence level
- Portfolio record: scope from the platform's 2023 company profile, attested by Netbase's CEO
- Client
- A US software company; client and product not named
- Netbase role
- Offshore development and managing partner since 2020
- Phase one
- 2020 to 2023, focused on agency SMEs
- Service
- Custom Product Engineering
- Published metrics
- None
Context
A US software company set out to offer small and mid-sized businesses a cloud ERP delivered as SaaS: one platform, many customer organizations, each with its own data, users and settings. The first target market was agencies, which needed to manage clients, work, people and internal knowledge in one place and connect it to the other tools they used.
Netbase role
Since 2020, Netbase has worked on the platform as offshore development and managing partner. Phase one ran from 2020 to 2023 and focused on agency SMEs.
Delivered phase-one scope
- a multi-tenant SaaS foundation serving many customer organizations from one platform;
- CRM for managing customers and contacts;
- real-time team messaging;
- HR management;
- a knowledge base;
- custom fields and configurable workflows;
- work and project management;
- API integrations with external services.
Technology
The recorded stack includes React and Next.js on the front end, Laravel and Strapi on the back end, PostgreSQL, MySQL, MariaDB and MongoDB for data, deployed on AWS. Using more than one database is common in a platform like this, where different modules have different data shapes, but it adds operating work that a buyer should plan for.
What is planned, not delivered
The source also describes a second phase aimed at retail SMEs, with point of sale, inventory, purchasing and vendor management, e-commerce integrations, loyalty and promotions, financial management, reporting, multi-store management and supply chain features. When the profile was written this was planned work. It is listed here to show the platform's direction, not as delivered scope, and no results are claimed for it.
Evidence level and limitations
- The record describes scope from the company profile. It does not report adoption, usage, performance or revenue.
- A usage figure in the source is unverified and is not published.
- The client, its city and size, and the product name are withheld.
- Interface screenshots in the source contain private data and are not used. The image on this page is illustrative and does not show the client's premises.
Lessons for a similar project
For a multi-tenant business platform, make these decisions before a module list becomes a committed scope:
-
Tenant isolation
How each customer's data is separated, and how that is tested.
-
Roles and data boundaries
Who can see and change what, inside a tenant and across the platform.
-
Configurability
Which fields and workflows customers can change themselves, and which need a release.
-
Migration
How new customers bring their existing data in.
-
Integration ownership
Who maintains each external connection when an API changes.
-
Operating responsibility
Who monitors, patches and supports the platform after each phase.
These are the kinds of questions a discovery milestone in Custom Product Engineering answers before build work is committed. The operating workflows this kind of platform serves are set out in ERP and back-office operations, and the configurable-workflow layer is the same machinery that document and approval workflows relies on.
Questions buyers ask
Was the retail phase delivered? No. Point of sale, inventory, purchasing, vendor management and the other retail features were planned work when the company profile was written. This record presents only phase one, from 2020 to 2023, as delivered scope.
Why are the client and product not named? The claim register approves this record in anonymised form only, so the client, its city and size, and the product stay withheld. The methodology page explains when a name may be published.
Can a similar multi-tenant platform be built for us? Yes, as a scoped engagement that starts with the tenant, role and configurability decisions listed above. This record shows the shape of that work; it is not a codebase or template offered for reuse.
Is any of this work AI? The recorded phase-one scope contains no AI feature, and none is claimed for it.
Building a multi-tenant product?
See the other portfolio records and how long-running work is governed on the project delivery page. When you are ready, submit a project brief. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.