Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Best way to monetise a web based application

Options
  • 27-11-2021 2:56pm
    #1
    Registered Users Posts: 388 ✭✭


    So we've developed a website that allows organisations to create trails on a map anywhere in the world with locations and points of interest, then publish the trail online instantly. When a location is saved a QR code is created that can be printed and displayed at the location, and points to the published trail.

    The app is in two parts, a front end where the public can view trails created by registered users and a back end where users can create the trails and publish them on the site. The front end is done in Angular and the back end is an API created in Node and Mongo hosted on AWS.

    The target market would initially be heritage organisations, county councils, bodies like the Office of Public Works in Ireland that maintain historical and cultural sites, etc.

    We're at a point now where we have a beta version that works pretty well but still needs a fair bit of tweaking. Apart from this tweaking we're struggling on the best way to charge for and sell or monetise the application "going forward" as they say. There are several options that come to mind:

     - charge organisations a monthly fee to create and publish trails

     - charge a one off fee per trail

     - open it to the public and charge a monthly / yearly fee

    One thing we envisage is organisations wanting to have the trails / content on their own site and not ours. Currently all the trails are published to oursite.com/trails but some customers would probably want e.g opw.ie/trails or dublincoco.ie/trails. This would involve creating an entire installation package and being able to deploy on the organisation's own web environment which could be tricky. So with this in mind other options could be:

     - white label the whole thing and sell it to organisations to use as part of their own website / web platform, like a CMS

     - open source the front end and give it away which would allow customisation of the front end by users, then charge for hosting and access to the API

    So many options 😅 If anyone has any thoughts on this we'd really appreciate any feedback or ideas.



Advertisement