Development Web Audits

Problem
You are surfing online, reading an article, perhaps do some online shopping. Have you noticed how things are broken? Outdated links, grammatical errors, or even purchase buttons that do not work. Super annoying (and also very unprofessional). Whatever the error it is pretty much anything online that consists somewhere, somehow, somewhat problems that can be contributed to any of the 4 sections
- Grammar
- Technical
- Aesthetical
- Legal 

Not all problems are equally breaking but it is better for everybody, like yourself who owns (or is presented by) the page or any viewer.  Especially if this reflects in revenue loss (e.g. broken links to merchandise, local cloth sizes for an international operating webshop).

Solution
To build a piece of software, driven by AI that (with the incorporation of other pieces of existing software) retroactively and actively monitors your web presence and (if selected) automatically fixes those mistakes based upon suggestions from big data and algorithms (provided by the other pieces of software).

Who are those (other) pieces of software?
Grammar - Grammarly
Technical - Unknown (Probably there is something out there that can do already)
Aesthetical - Unknown (Probably there is something out there that can do already)
Legal - LegalRobot

The benefit:
Take Grammar for example. Grammarly is definitely not the only software out there fixing grammar issues. Web audits consult all grammar fixing software and this scaling benefit will yield more accurate results as it goes through all the algorithms, each with their own criteria to validate, verify and fix. 

How will this work?
Front-end:
The user will have its own account in which you can enter the URL's you want to be monitored. The software will ask the user also want to include all sub-pages and you click either yes or no. Then the user will be asked to log in to that account where the URL is from just to verify the user has actually access to it. This only needs to be done once. The user can select in its profile if the software only needs to monitor or also automatically fix the issues. If it is just monitoring it will present all the issues, categorized with a label for easy filtering presenting the solution to what has been found and can be fixed. A simple checkmark / red cross will be behind it allowing the user to decide which fixes actually go through. 

Back-end
Web audits AI (WAAI for short) will crawl through the top URL and all its sub-page URL's and utilize the strength of these other pieces of software to do the legwork. When something is found it will analyze the given solutions (provided there are more competitors) and based upon a ranking score the most likely solution will be chosen (or if multiple software gives the same answer it becomes crystal clear for the AI what to pick) and that will be pushed back to the user in case they want to control the fixes manually or it will be automatically fixed and the user will receive at the end of the day a report in their dashboard to see what the AI has done for them, like a worklog.

Why is this better (or different) from existing solutions?
Check 'why us' on this link. 

Where does the raised budget go to?
100% to the development of a working product to be created by a software development company due to its complexity and multi-disciplinary requirements. Which software development company that is going to be will be determined after the fundraising is completed. We want to find a software development company that can deliver what we want for 50k euros.

What will I get in return?
The software will be subscription-based but the ones that invest upfront will get access for as many months as they have contributed to the fundraising. For example. If the subscription price is 10 dollars per month and you invested 50 dollars during the fundraising you will get access for 5 months for free. 

Notes:
1. This is a piece of software yet to be built. What we fundraise is to turn this idea into a tangible piece of software that acts as proof of concept for investors and alpha-testers. Some of the other software we want to incorporate is so new that is actually in development itself too. 

2. The software is meant to be running in the background on anything that has to do with a digital presence. In other words, if you can access it via URL, the software will work.

3. Final prices, packages etc. are yet to be determined and can change until public release. 

Do you help us to make this come true?