Job - 100% remote - ThreeJS / ReactJs

For this project, we are offering 33% ownership.
We are currently a team of two developers, so we are offering equal shares.
This project will run alongside an existing project with thousands of members - UK-based.
Main site: kitchensexpert.co.uk

A contract and an NDA will be provided via Adobe Sign.
Our project description:

The ‘Planner’ is a web-based kitchen design application developed using a stack of modern technologies, including React.js for the frontend user interface, Bootstrap 5 for responsive design and styling, Three.js for rendering the 3D visualization component, and A-Frame for enhancing the 3D virtual reality experience. This application empowers users to create intricate kitchen layouts, defining dimensions, layout preferences, constraints, and fixtures. Users can select from a library of cabinet configurations and arrange them in a 2D top-down view. Additionally, it offers an immersive 3D visualization feature powered by A-Frame, allowing users to explore their designs in three dimensions and capture images for reference. Upon completion, the application generates a comprehensive PDF document containing an in-depth breakdown of selected cabinets and components, facilitating effective planning for kitchen renovation or design projects.

Here’s how this arrangement typically works:

  1. Voluntary Contribution: The developers are essentially working on the project as volunteers or without immediate financial compensation. They are dedicating their time, effort, and expertise to the project with the hope of eventually sharing in the project’s success.

  2. Profit-Dependent Compensation: The developers will only receive compensation when the project starts generating profits. Until that point, they may not receive any payments for their work.

  3. Profit Distribution: Once the project becomes profitable, the profits will be distributed among the developers based on the agreed-upon profit-sharing arrangement. This distribution can still be split equally (33% each) among the three developers if that’s what was initially agreed upon.

  4. Documentation: Even in this scenario, it’s essential to have a clear, written agreement in place that outlines the terms of the profit-sharing arrangement, roles and responsibilities, and any other relevant details. This agreement should specify when and how profits will be calculated and distributed.

  5. Risk Considerations: It’s important to recognize that this arrangement carries a higher level of risk for the developers, as they are investing their time and effort upfront without guaranteed compensation. They are essentially sharing in the project’s financial risks and rewards.

  6. Tax Implications: Developers should be aware of the tax implications of receiving profit-based compensation. Depending on their jurisdiction and tax regulations, they may need to report their income and pay taxes when profits are distributed.

  7. Timeline: It’s also essential to set clear expectations regarding when the developers can reasonably expect the project to become profitable. This can help manage their expectations and financial planning.

This type of profit-sharing arrangement is common in entrepreneurial ventures and startups where there may not be sufficient initial funding to pay salaries or fees. Developers who choose to participate in such projects should carefully evaluate the potential risks and rewards and have a well-documented agreement in place to protect their interests.

Contact:
Please, agencies do not contact me you will be ignored and blocked.
We are looking for a single developer with a personal interest in this project.
WhatsApp: +447533381767 (Initially: message only)

Hi,

There’s a few questions that come up on this…

  1. What are your companys financial projections over the next 5 years?
  2. If shareholder investors are taken on to gain traction to meet the financial projections, how would 3 developers share 100% of the company profit and how would the profit be distributed in this scenario?
  3. What is the companys current shares status? eg. how many, what’s the price of each share and how are they currently distributed?
  4. If the “reasonably expected timeframe” of the company / project becoming profitable is not part of the next 5 years financial projections, what is a reasonable timeframe and what are your companys 10 year financial projections?

Just a few things that may be best kept transparent when asking for profit share work on a project of this scale and complexity…

Asking for a mate :joy:

Thanks for the email.

The 33% split would be for this project “planner” but would share data from our main site. It’s not for the company as whole. As this is a new project, It wouldn’t be fair for me to make some figures up but as we have a member base, it’s not a startup project entirely.

Three developers, which comprises of myself, my business partner and the reactjs/three js dev. After costs for this part of the company are paid. It would be split 33% each.

We are not a public company so we don’t comprise of shares.

I would hope within 5 years would become profitable as in my previous answer, we are not a complete startup.

Hi Josh,
I think that you should probably have started with this post, outlining the situation, as opposed to your previously asking if any devs were available for work. It’s quite a different proposition when you are asking people to essentially work for nothing for an unspecified amount of time to share in some profits that may or may not ever materialise! In times of economic hardship, it’s a big ask for devs to offer their time for nothing. I wish you all the best with your project though.

For the attention of moderators on this forum, could you please ask prospective employers to place a [PAID] [UNPAID] tag in the title of the job posting, such that we can all be clear as to what specifically the job entails? That would be great.

Thanks,
Tony.

That’s why I flagged the previous post for deletion.
Thanks

This topic was automatically closed after 30 days. New replies are no longer allowed.