Contact person: SaaS Satisfaction Survey Platform Development

Phone:Show

Email:Show

Location: Madrid, Spain

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"1 General Information
A new survey solution platform will be developed.

A SaaS cloud platform must be developed, allowing multiple client companies (commercial accounts) to create, manage, and analyze satisfaction surveys about their products or services.
The system must be multi-company (each company with its own account) and multi-user (internal users defined as devices or stores).
________________________________________
2 System Objectives
• Provide companies with a simple and secure tool to collect customer opinions in physical stores or after an online purchase.
• Centralize survey management and results in a cloud environment.
• Allow the platform to be used by multiple client companies independently.
• Enable scalability and growth in the number of companies and users.
________________________________________
3 Functional Requirements
1. General Conceptual Areas
• General management and control area from our company.
• Management and control of client companies registered by our company.
• Campaign management and control area (from client companies).
• Interfaces for self-construction of surveys.
• Basic graphical interface for survey results.
• Export and download of results.
• Communication API to request the launch of a survey from other applications (e.g., after completing a web or physical purchase).
o The API must return a result and relational code to link the survey to a specific document or transaction.
2. Client Company Management (by our company)
• Creation, modification, and deletion of client companies.
• Definition of licenses and user control per company.
• Administration panel to monitor active companies.
• Interface to process requests for devices/stores from client accounts.
3. User Management (Devices/Stores) by Client Company
• Request creation, modification, and deletion of devices/stores, pending validation by our company.
• Control of active and inactive licenses.
• Assignment of surveys to specific devices/stores.
4. Survey Management
• Creation, modification, and visualization of surveys.
• Mandatory data: Title, Description, Application period, Status (draft, active, deactivated, canceled, obsolete), Assigned devices/stores.
• Support for one or multiple questions (open or closed).
• Visualization of all surveys created by a company.
• Visualization of aggregated results (count, values, averages).
5. Survey Structure
• Welcome screen with header image, background, and introduction text.
• Creation, modification, and deletion of questions in a survey.
• Supported rating types:
o Stars (0–5)
o Satisfaction faces (very unhappy to very happy)
o Numeric scale (0–10)
o Text answers or predefined multiple choice
6. Response Collection
• Display of surveys on assigned devices/stores.
• Response storage in the database.
• Control of active surveys according to application period.
7. Reports and Analysis
• Results panel per survey.
• Download results in Excel/CSV.
• Basic graphs (percentage, distribution, averages per question).
• Filters by dates, device/store, and survey.
________________________________________
4 Non-Functional Requirements
1. Security
• Secure authentication (ideally multi-factor).
• Strict data separation per client company.
• Encryption in transit (TLS) and at rest (AES-256).
2. Scalability
• Ability to grow in companies and users without degradation.
• Handling of 5,000 users answering surveys simultaneously and millions of annual responses.
3. Availability
• Minimum SLA: 99.9%.
4. Usability
• Responsive web interface (PC, tablet, mobile).
• Multi-language: auto-detection based on browser/OS, auto-translation, manual translation of questions by client company.
5. Maintenance & Support
• Periodic updates for technological changes.
• Capacity for continuous development and new features on demand.
• Support with response times defined in contract.
________________________________________
5 Suggested Technology Architecture
• Cloud web application (AWS/Azure/GCP).
• SQL database (PostgreSQL/MySQL).
• Scalable architecture based on microservices or serverless.
• REST APIs for external integrations.
• Responsive frontend (React, Angular, or similar).
________________________________________
6 Expected Deliverables
• Confidentiality and exclusivity agreement with economic penalty clause.
• Source code in Git repository.
• Technical and user documentation.
• Test and production environments in the cloud.
• Administration manual.
• Software testing and validation plan.
________________________________________
7 Timeline (Estimated)
• Design and architecture: 4–6 weeks.
• Pilot presentation in pre-production: 1–2 months.
• MVP development: 3–4 months.
• Testing and QA: 4 weeks.
• Production: 6 months from project start.
________________________________________
8 Acceptance Criteria
• All functionalities implemented as described.
• Cloud-accessible platform with high availability.
• Reporting and data export fully operational.
• Compliance with security and data separation requirements.
________________________________________
9 Administrative Conditions
• Software intellectual property belongs to the client.
• Full delivery of source code and infrastructure access.
• Payment by milestones (first payment after pilot approval).
• Confidentiality and exclusivity (NDA).
________________________________________
10 Annexes
1. Flow Diagrams and Mockups
• Process flow diagrams.
• Mockups or wireframes for approval.
2. Typical Use Cases
Use Case 1 – Post Online Purchase Survey
1. Customer completes e-commerce purchase.
2. System triggers API request with transaction ID.
3. Customer receives email or popup with survey.
4. Customer responds via web/mobile.
5. Response linked to the transaction.
6. Admin views results.
Use Case 2 – In-Store Survey
1. Customer pays at POS.
2. POS sends signal to API.
3. Survey appears on store device.
4. Customer responds.
5. Response stored in database.
6. Admin views results.
Use Case 3 – Survey Creation by Client Company
1. Admin logs into panel.
2. Creates survey: title, description, dates, assigned users.
3. Adds questions (NPS, open, multiple choice).
4. Activates survey → available on assigned devices." (client-provided description)