Multi-Tenant SaaS Learning & Training Platform
A continuously evolving SaaS learning and training management product built around a multi-tenant architecture and serving organizations with different operational needs.
Beyond conventional learning management, the platform brings together training operations, assessments, certifications, financial processes, reporting, integrations, and other administrative capabilities within one product.
My contribution has evolved alongside the platform, from gathering and translating client needs into requirements, to defining functionality, supporting development teams, analyzing APIs, preparing compliance requirements, presenting the product, and supporting users after delivery.
The Challenge
Supporting one product while its requirements continue to grow.
Working on a SaaS product is different from delivering a system for a single fixed scope.
The platform needs to serve different organizations, accommodate evolving client needs, maintain a coherent product structure, support integrations with external systems, and continue expanding without turning every new request into an isolated customization.
For Business Analysis, this means looking beyond the requirement in front of you and asking how it fits within the existing product, roles, workflows, business rules, integrations, and future growth of the platform.
My Role Across the Product
Working across the layers that keep a growing product connected.
- 01Business Need
- 02Product Requirement
- 03Functional Behavior
- 04Prototype
- 05Implementation
- 06API
- 07Compliance
- 08Adoption
My Contribution
Analysis beyond the requirements document.
Translated Client Needs into Product Requirements
Collected and analyzed requirements from different client contexts, working to understand the business need behind each request rather than documenting requested functionality at face value.
A key part of this work was considering how new requirements fit within the broader product and identifying how they could be represented consistently within the existing platform structure.
Turned Business Needs into Functional Definitions
Prepared different levels of requirements documentation to support both business and technical audiences.
At a high level, I contributed to Business Requirements Documentation that communicated business needs and direction.
At a more detailed level, I documented system functionality by role and supported those requirements with interactive prototypes that helped clarify expected workflows, behaviors, and outcomes for development teams.
- Business Need
- Requirement
- Business Rule
- User Flow
- Expected System Behavior
Kept Business Intent Connected to Implementation
Collaborated with multiple development teams throughout implementation, clarifying requirements and resolving questions around intended business behavior.
Because the product continued to evolve, analysis was not limited to producing a document and handing it over. Requirements often needed to be revisited, clarified, connected to existing functionality, or adjusted as implementation details became clearer.
This made analysis an ongoing bridge between business intent and technical implementation.
Extended the Analysis to APIs
My contribution also moved beyond interface and workflow requirements into API analysis.
I analyzed APIs needed to connect frontend and backend functionality and documented their specifications in GitBook.
This helped connect the functional view of the product with the technical contracts supporting it.
- API purpose
- Request fields
- Parameter types
- Expected responses
- API mapping to platform pages and functions
Translated Accreditation Requirements into Product Requirements
Analyzed and prepared the platform requirements needed to support accreditation by the National Center for eLearning.
This involved translating external requirements into actionable platform considerations and identifying what needed to be available or adjusted within the product.
The platform subsequently received the required official approval.
The important part of my contribution was not simply documenting a compliance checklist, but helping connect those requirements to the actual product.
Made Proposed Experiences Easier to Discuss Before Implementation
Created conceptual wireframes and interactive prototypes for different product areas, including functional platform experiences and informational or marketing-facing pages.
These artifacts helped turn requirements into something stakeholders and development teams could inspect visually, reducing ambiguity around intended workflows and page behavior.
Presented the Product Through the Client's Context
Participated in client meetings to present the platform and deliver live product demonstrations.
This required understanding not only individual features, but how to explain the product through the client's needs, workflows, and expected outcomes.
These conversations also provided an additional source of insight into how organizations understood and expected to use the platform.
Turned Product Knowledge into Practical Guidance
Delivered orientation and knowledge-transfer sessions and prepared comprehensive user documentation to help different audiences understand and use the platform.
The documentation was structured around actual system responsibilities and workflows rather than simply describing screens individually.
This created references that could continue supporting users after the sessions themselves ended.
Key Deliverables
Different artifacts, one connected product understanding.
Business Requirements Documentation
Captured higher-level business needs and product direction for relevant initiatives.
Functional Requirements Documentation
Defined functionality, business rules, and expected behavior across system roles and workflows.
Interactive Prototypes
Made proposed functionality easier to review, discuss, and implement.
API Documentation
Connected frontend functionality with backend services through structured API specifications and page-level mappings.
Compliance Requirements
Translated NELC requirements into actionable product considerations that supported the accreditation process.
Wireframes
Visualized proposed informational and marketing experiences before detailed implementation.
Product Demonstrations
Supported client understanding through live walkthroughs and contextual explanation of platform capabilities.
Role-Based User Documentation
Created practical guidance to support onboarding, knowledge transfer, and continued platform use.
The Breadth of the Role
Business analysis across business, product, technical, and adoption layers.
Business
- Requirements
- Business needs
- Client conversations
- Compliance
Product
- Functional behavior
- Business rules
- Roles & workflows
- Prototypes
Technical
- API analysis
- API documentation
- Frontend/backend mapping
- Development clarification
Adoption
- Product demos
- Knowledge transfer
- User onboarding
- Role-based guides
Skills in Practice
Capabilities applied across an evolving product.
- Requirements Elicitation
- Requirements Analysis
- Product Analysis
- Business Rules
- Functional Specification
- Interactive Prototyping
- API Analysis
- API Documentation
- Systems Integration
- Compliance Analysis
- Stakeholder Communication
- Product Demonstration
- User Documentation
- Knowledge Transfer
Takeaway
Product analysis is as much about maintaining coherence as it is about defining new requirements.
Working on the same SaaS product over time has given me a different perspective on Business Analysis.
A requirement rarely exists alone. A new feature can affect roles, permissions, existing processes, APIs, reporting, documentation, integrations, and even requirements that were defined much earlier.
The challenge therefore becomes not only: What does the client need?
But also: How should this need become part of the product without breaking the logic that already holds it together?
That continuous context has been one of the most valuable parts of working on this platform.