Case Study

A Portal to turn Ideas into Products with Co-Revenue Model

The main goal of the project is to enhance the existing platform by introducing a dynamic marketplace that supports both finished projects and early-stage product ideas.
Objective

The main goal of the project is to enhance the existing platform by introducing a dynamic marketplace that supports both finished projects and early-stage product ideas. This new feature will allow users to submit concepts with just a title and description, connecting them with global collaborators for 2D drafting, 3D modeling, Analysis and Documentation. By streamlining the product development process and implementing a revenue-sharing model, the platform aims to foster innovation, ensure fair compensation for contributors, and create a seamless ecosystem that transforms ideas into market-ready products.

Project Details

  • Provide a platform by introducing a dynamic marketplace supporting finished projects and early-stage product ideas. Allowing users to submit their concepts and ideas with just a title and description, connecting them with global collaborators for 2D drafting, 3D modeling, Analysis and Documentation.
  • Provide a platform by introducing a dynamic marketplace supporting finished projects and early-stage product ideas. Allowing users to submit their concepts and ideas with just a title and description, connecting them with global collaborators for 2D drafting, 3D modeling, Analysis and Documentation.
  • Provide a platform by introducing a dynamic marketplace supporting finished projects and early-stage product ideas. Allowing users to submit their concepts and ideas with just a title and description, connecting them with global collaborators for 2D drafting, 3D modeling, Analysis and Documentation.
Key Features of the Application:

Revenue Share Model:

  • Fixed Sales Share: Fixed percentage of sales for the entire product lifecycle.
  • Dynamic Sales Share: Tiered percentage based on sales volume (e.g., 10% for the first 100 units, 8% for the next 200, and 5% thereafter).
  • Instant Payment (Challenge): One-time payment instead of a revenue share.

Public Marketplace Access: Unauthorized users can browse the marketplace to view listed projects but must register to participate in collaborations.

Counter Offer System: Collaborators can submit counter offers in response to initial offers made by project owners, with the option to prepopulate initial offers for easier negotiation.

Communication & Collaboration: Once an offer is accepted, project owners and collaborators can communicate through an integrated chat model, share files, and discuss project details in real-time.

Multiple Projects Collaboration: Project owners can also serve as collaborators on other projects, enabling flexible participation in multiple collaborations.

Challenges

  • Revenue Share Model: Design and implement a system where project owners can choose from multiple revenue-sharing models, including a fixed sales share, a dynamic sales share based on volume, and a one-time instant payment option (Challenge). Each model must allow customization of percentages or amounts.
  • Public Marketplace Access: Ensure unauthorized users can browse the marketplace and view listed projects, but require registration to participate in collaborations, maintaining a seamless user experience between public access and registered participation.
  • Counter Offer System: Develop a feature where collaborators can submit counter offers to initial offers made by project owners. Additionally, prepopulate initial offers for collaborators to streamline negotiations and make the process more efficient.
  • Communication & Collaboration: Build a communication system where, once an offer is accepted, project owners and collaborators can chat, share files, and collaborate on project discussions in real-time, ensuring effective teamwork and document sharing.

Technologies

  • Frontend: ReactJs, Next.js, HTML, Tailwind CSS, TypeScript, JavaScript, CSS
  • Backend: C#, PostgreSQL, .Net framework, Entity framework, Azure.
  • Repositories & Data Store: GitHub, Azure services.

Solutions

Revenue Share Model

Providing the project owners the flexibility in revenue distribution, the platform implemented a customizable revenue-sharing system with three primary models:

• Fixed Revenue Share: A predefined percentage of revenue is allocated to collaborators for each sale of the product on individual level.

• Dynamic Revenue Share: Revenue distribution adjusts based on sales volume, rewarding collaborators based on performance and product success.

• Fixed Cash Challenge: Project owners can choose to pay collaborators a fixed upfront amount instead of sharing a long-term sales revenue.

Each model includes customization options where project owners can set percentages or fixed amounts. A smart contract or automated distribution system will ensure seamless and transparent payment processing.

Public Marketplace Access

The platform offers a publicly accessible marketplace where unauthorized users can browse and explore listed projects. However, to maintain platform security and encourage meaningful participation, registration will be required for users to engage in collaborations, submit offers, and contribute to projects. A progressive access model will ensure a smooth transition from public browsing to registered participation, enhancing the overall user experience.

Counter Offer System

To facilitate seamless negotiations, the Counter Offer System allows collaborators to propose modifications to the initial offers made by project owners. This feature includes

  • A structured negotiation flow where users can submit counter offers with changes in revenue share.
  • Prepopulated initial offers based on industry standards and past successful agreements, streamlining the negotiation process.

Communication & Collaboration

Once an offer is accepted, a dedicated collaboration workspace is created for the project owner and collaborators. This includes:

  • A chat feature is implemented for Interval of updates presenting challenges in performance, efficiency, and user experience. Frequent API polling can lead to excessive network requests, which can be optimized using longer intervals with conditional fetching (e.g., fetch only when the user is active).
  • Large attachments are handled efficiently by chunking the uploads and optimizing storage (e.g. using AWS S3 or Firebase Storage).
  • To improve performance for searching messages with large datasets, indexing has been done in the database and with debounced search queries help improve performance.
  • Downloading attachments must ensure secure file access and proper MIME types. Overall, balancing real-time updates, data efficiency, and smooth UX is key.
Contact us

Partner with us for Comprehensive IT

We’re happy to answer any questions you may have and help you determine which of our services best fit your needs.

Your benefits:
What happens next?
1

We Schedule a call at your convenience 

2

We do a discovery and consulting meeting 

3

We prepare a proposal 

Schedule Consultation