5
13 Comments

This project takes 12 hours to build and I'm looking for a dev to work with

Hi devs of IH,

I'm currently working on a widget project. Similar to @DannyPostma's ParityBar.com (not copying you Danny but remotely the same concept).

There are two reasons I have taken this project. One is it's easy to build as the example I just shared was built in 12 hours. Two is I have found people asking for it. So I think it's worth a shot.

This will be a paid project but I'm thinking of paying as the project starts making money. For this reason, I'm willing to work with inexperienced devs and starters. In particular, I'm looking for basic-mid experience in PHP, HTML and CSS.

If you're thinking "Oh, unpaid work", let me be clear. While working with a starter dev last week, I showed him a working prototype and spent significant time teaching what a Save button does. And this is just an example, there's risk on my end while offering mentorship, allowing experiments, and working with someone starting to code. So trying to cancel that out by paying as the product matures.

Edit: To experienced devs: Two years back one had to pay for schools. Now that's changing in a way that one can pay them later in their career, no risks or debt whatsoever. Think the same. If you don't like the concept I'd recommend leaving at it, instead of trying to correct me by saying my way of working is wrong. I'm trying to work with starters, who share the same interest and risk:reward ratio as me.

Please comment if you're interested in working with me 🙏🙌

p.s if you'd like to check out the waitlist signup page - https://beta.bartono.com/

  1. 2

    I started my journey with php only. Though I moved to python, django and vue. I really miss the vibe. Let's connect.

    Introducting myself, I am a full stack developer with experience over multiple technologies and have helped a couple of startups over the years. You can call me jack of all trade master of a few. I believe in first principles thinking and deduce the analogy from there.

    1. 1

      Awesome background. I'll shoot you an email in some time.

      In the mean time, feel free to dm me on Twitter (https://twitter.com/iamdinakar) or via email [email protected]

  2. 2

    I hope you are able to find someone to work with you.

    Since you don't mention anything about the downside of this proposal, I'll bring up a couple of points you (or an interested dev) might consider.

    Based on the statements as written, it's a revenue sharing project. Probably capped, but still nothing is paid unless there is revenue. There is nothing wrong with the approach, just be forthright about the possible outcomes. As a dev, I would insist on a contract with the details in writing. As the product owner, I would also insist on a contract with the details in writing.

    Best of luck.

    1. 1

      Thanks much for your input 🤝

      I have thought this through and will generate revenue for sure. If all else fails I can still sell the project itself for a nice profit (given its potential) and pay 100% of the proceeds to the dev working on it.

      I'm ready to take all steps required to make it a success and safe guard the dev working on it if it fails.

  3. 2

    Similar to what @wparad said. What you are asking is more than you think.

    "One is it's easy to build as the example I just shared was built in 12 hours"

    Just because the project you mention allegedly took 12 hours to build, does not necessarily mean that is how long it takes. As a developer, I know how devilishly trick estimates like that are.

    There are non-trivial apps that I can create in a few hours, but that is because I would either already have created so many other similar apps and can easily copy/paste most the code. If I was to ask someone who has never created something similar, what might take me a day could take them weeks if not months to achieve.

    "If you're thinking "Oh, unpaid work", let me be clear ..."

    From that statement alone, it looks like you already know that people do freak out when they see proposals like yours. So you must already know that they are many people out there that seek free labor by claiming that it is for experience, mentorship, portfolio, e.t.c.

    1. 0

      This is probably going to be downvoted like my other response. Let's see.

      You clearly needn't say "take them ... months to achieve". But you said that as an example, so did I by mentioning it took 12 hours to build for someone.

      The statement is for experienced devs who I know will be picking on me in the comments.

      Now, I don't know about you. There are people who like helping others, making experiments and trying out things for free.

      For me personally, in the coming weeks, I'll designing and developing free for other people and release them as open source templates for even more people. In this particular project, I'm kinda into working with people who are willing to take risks and try new things without money as a goal. Hope you can understand.

  4. 2

    In order to sell revenue sharing project, you are putting a high burden on the developer to validate that you actually have a business idea.

    There are tons of paid internships in the world. With that you are asking for two leaps of faith, it just doesn't seam reasonable.

    Also a stack like php, html, css, is pretty antiquated. We're talking about ~20 years old at this point.

    1. 3

      I stopped using CSS in 2001 too.

      1. 1

        This comment was deleted a year ago.

    2. -3

      This comment has been voted down. Click to show.

      1. 3

        I agree 100% with @wparad.

        • Your risk equals unlimited rewards.
        • Dev risk equals capped (i.e. salary) reward.

        The word 'hiring' means: "I will pay you a salary so there is no risk to you, however I reap ALL the rewards"

        If they are sharing the risks, they are a 'co-founder' and revenue should be split accordingly.

        From my point of view, we share equal burden.

        Equal burden, equal rewards.

        1. 0

          I stay with my point. And I'm pretty much having to repeat myself here.

          Like I said, last week I spent more than half an hour teaching what a Save button does in a fully working prototype.

          They get to learn, mentored, portfolio, someone who allows experiments and connections, and a paying salary when it all works together. I get to work with starters, share my knowledge and get the job done, and reward when it all works together.

          "Hiring" also means join on 1st of Feb and I'll pay you at the end of the month. Which is pretty much the timeline I have. Also, the same way the jobs in the world works.

          Yeah, they can build the software one time and get rewarded each time I work hard in getting sales. Just a dev building a project will get me nothing, there is so much more to it, which I can simply hope you're aware of.

    3. 2

      This comment was deleted a year ago.

  5. 1

    lets do it! I am a full stack RoR dev.

    1. 1

      Great! I'm not able to reach you. Can you dm on Twitter (https://twitter.com/iamdinakar)?

      Or shoot me an email [email protected] ?

Trending on Indie Hackers
I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments How I Sourced 60% of Customers From Linkedin, Organically 12 comments Hero Section Copywriting Framework that Converts 3x 12 comments Promptzone - first-of-its-kind social media platform dedicated to all things AI. 8 comments How to create a rating system with Tailwind CSS and Alpinejs 7 comments