8 {{ upvoteCount | shortNum }}
8 {{ upvoteCount | shortNum }}

Front-end or Back-end

by Jessica barton
7 replies
Hi fellow warriors,

I'm about to create my product but rather stuck on this issues.

I know that frontend and backend products must be relevant and backend are usually a bigger and more-packed value relevant product than the front-end.

1.)What I want to know is that, should I start by creating my frontend or backend product first?

2.)How should I plan my project? Please list them accordingly : 1st,2nd and 3rd
-Get all the graphics done
-Brainstorm and register a domain name
-create and complete my product, then add in twists according to the domain name and graphics


Really hope I can get some help on this as I have been thinking over and over again for the past week.

Thanks in advance guys!
#backend #frontend
  • Profile picture of the author giveusallfreedom
    Let's see definitely create your product 1st and go from there. As you're creating it, things might change and everything should be based of the product.

    Second (and I realize this is in reverse order) create one product and test it out. Then create a second product and test it out. If they do well than choose one and make it your backend and one your front end. Or better yet, create a third product and use your first to for backend to that product.

    My point is worry about creating and promoting one product at a time. Otherwise you spend all your time creating products and have nothing to show for it. You can always go back and sell previous customers your backend product, but why spend all the time to create two products and when you don't even know if the first one will sell.
    {{ DiscussionBoard.errors[56730].message }}
    • Profile picture of the author Brian Edmondson
      If you create your backend product first, or your "complete package", you can then extract parts of that to make the front end....

      Example: I may make a training course which is video based around screen capture.

      That could be my backend product. From that I could have the audios transcribed into a pdf, and make a front end "special report" out of that.

      Just and idea, hope that helps.

      Brian
      {{ DiscussionBoard.errors[56735].message }}
      • Profile picture of the author Jessica barton
        Thanks for the suggestions guys!

        Brian,
        Your suggestion open up my mind. Seems like creating backend first is the way to go.

        Anymore suggestions? Especially my 2nd question.

        Thanks!
        {{ DiscussionBoard.errors[56752].message }}
      • Profile picture of the author sknollii
        I agree with Brian.

        It is much easier to create the full (larger) backend product first and draw off of it for your front end.

        As for the order in which you do things, it is a little tough to say.

        If you come up with a good domain name for a concept and it is available, I say go ahead and grab it. The cost is nominal and good names can be hard to come by.

        Next create your product. You can always test out a product's marketability or at least get reviews prior to having graphics and sales copy.

        Next you'll want Sales copy and then I usually do graphics last.

        My reason for this is that I find it easier to tell a designer what I want when the product is complete and the sales copy is crystallized. In order to write good sales copy, one must have an understanding of the kernel of a concept as well as the root, emotional motivating factor driving people to want that product.

        Once you have that precise understanding of the message to be conveyed it is much easier to ask a designer to build off of it.

        Don't forget Sales emails as well as post sales emails to help folks consume your product as well as upsell and even promote your product for you.

        Hope that helps some.

        Sam
        {{ DiscussionBoard.errors[56755].message }}
        • Profile picture of the author martinkeens
          Personally, I would spend more time on the front end. If the front doesn't draw people in, they're never going to see the back.

          Come up with the product first, then think of a name. It is far easier to build a brand around a product, than to build a product around a brand.
          Signature
          Blogging Syndicate Bonus
          Martin Keens Internet Marketing
          Membership Guru Free Report
          Instant List Building Kits
          {{ DiscussionBoard.errors[56785].message }}
          • Profile picture of the author Arindam Chakraborty
            I believe in starting small. Let's say that I am already selling a product. I create (or outsource) another product which is related to the first product in some way. I promote the first product on the download page of the second product (I am not a big fan of OTOs, btw) and vice versa. I also promote it in the download emails I send out, etc. Works for me

            Arindam
            Signature
            DO NOT Click here! It SUCKS!

            The WORST Internet Marketing Newsletter, Ever!
            {{ DiscussionBoard.errors[56897].message }}
            • Profile picture of the author Frank Bruno
              Actually that's the same thing Russell Brunson was teaching at his affiliate incubator last year is to create your back end product first and extract parts of that for your Front end.

              Now I don't agree or disagree with this it depends in how larger backend product is or what it is actually.

              But you should definitely have a front in product then an OTO product then your backend product.

              Now how large these products are is left up to determination by you, but if you have a least all three these elements to start with, rest assured you can compound your sales very quickly and start building your customer base.

              If you start out with these three elements you can always grow on each aspect of it such as your backend offer.

              Frank Bruno
              {{ DiscussionBoard.errors[56922].message }}

Trending Topics