Rails + Javascript (inc. AJAX) App: Pre-launch code and security review + advice for future maintenance

I've spent the last few months building a Rails app that helps students preparing for job interviews to practise with each other. I hope to launch it in the next week or so, and have a promotional strategy in place that should guarantee a lot of users almost immediately. As this is the first time i've launched a site of this scale, I'm now looking for an experienced Rails developer to take the code the final 5% to get it ready for launch, but also meet me in person in London for a couple of hours to advise me on what I need to know about maintaining the site (and it's database) once its online. Ideally you would also have a strong competence in javascript and how it sits in the Rails asset pipeline, as the site is javascript heavy inc. pure javascript, jquery, jquery-ui, google maps, AJAX, and the chart library AMCharts. The app itself is not that large, with 4 models and controllers containing the bulk, with the majority of functions being the usual RESTFUL actions that you would expect on a user driven app. One of these is a notification system that sends emails to users for various events. - Meeting me in London in the next few days so I can take you through everything in person. - Predicting and patching security holes: could be e.g. checking model validations are sufficient, or preventing against double submission of AJAX forms. - Predicting and overcoming any issues that might arise from scale - Predicting and overcoming anything else to ensure the site functions successfully once launched - ...and then a final meeting in London to advise me on what I need to know to maintain the site once its launched on Heroku going forward. The work may also involve: - Refactoring the Ruby (although hopefully this has already been done sufficiently) - Organising the javascript in the asset pipeline (i've had a few problems with this) - Tweaking the capybara test suite Outsourcing this work has been planned and budgeted for from the start of the project - I've written the code with it in mind, being careful to make it self documenting, commenting where necessary, and strictly maintaining correct MVC organisation. You will not be ploughing through a total mess.