Thinking in more details about the site - how it will work and what information you will need to make it work

The website you want will basically consist of two sites. The main, primary site that all website visitors will see (i.e. www.jamesescortssite.co.uk), then a second, password protected website. Also known as the backend this site acts as an admin interface for both yourself and if you want, for the escorts that you have on your books.

1. Primary Website

Think about what pages you want – these will be the links on your website, list them all, along with an outline of what content you want on that page, if you want, you can sub-divide this list further into things you definitely want on the page and things you think could be useful (we can advise you on this after we go through your specification);

i.e.

Homepage
The homepage of the website will include a general introduction, escort search and a small selection of featured escorts – could be good idea to have a random selection of escorts featured on the homepage showing picture, age, location and per hour price

About Us
Talk about the agency, where you are based, how long you’ve been going, owners experience in industry, what makes your escorts different etc

How to Join
Information on how a prospective escort can get in touch with you as well as any criteria you have for escorts on your books, what they should think about before joining, costing and how to pay information could also go here

FAQ’s
List of frequently asked questions such as ‘how do I join?’, ‘How do I make a booking?’, ‘What if my client fails to show up?’ – Could be a good idea to split this up into faq’s for clients and faq’s for escorts

…and so on.

After you have thought about the sort of content you want on each of the pages, you then need to recognise which areas of content are dynamic (things that will need programming and/or to be linked to your database) and as such will need further thought.

For example, the escort search on the homepage will be linked to the database and results will change based on a number of flexible criteria the website user chooses. Before you can decide what the search criteria on the homepage are, you need to consider the type of information you will be requiring for each escort that you sign up, for example, the information you need to hold in the database for each escort might be;

Fig.1

Working Name
Gender
Age
Height
Hair Colour
Eye Colour
Weight or Body build
Sexuality - Bi, Straight etc
Smoker
Nationality/Ethnicity
Location
Rates, 1st hour, 2nd hour, 3rd hour and so on
Description/Profile
Contact Details for Website
Full Contact Details (including real name for billing purposes)
Date Signed up/paid
Username
Password
Picture(s)

Once you have decided on what information your database needs to hold, you can then decide which bits of information will form that basis of your search, for example;

ESCORT SEARCH
Choose hair colour…
V

Choose age range…
V

Choose build…
V

Choose sexuality…
V

Choose Location…
V
1 Hr Rate…
V

FIND

Be aware that the more criteria you have, the more complicated the coding will be, keep it as simple as possible whilst ensuring you have all the key information you need. Also think about how you want this information displayed on the search results page.

If you do the above search and it finds say, 30 matches, what information do you want to show to provide the user with enough to make a decision on which escorts they would like to click on to see more information? Typically the search results would consist of a page showing a list of small thumbnail images for each escort along with a small amount of information and a ‘click here to see full profile’ link.

You will also need to think about how clients will contact the escorts, via phone, email and/or online contact form, also how many pictures you will allow each escort to have (the more pictures, the higher the bandwidth required from your server and this will add on additional costs).

2. Admin Website

The admin site is hidden from website users and will be password protected, you might want each escort to be able to edit their profiles, add more pictures and so on whenever they choose, or, much simpler, would be if the admin website is primarily for yourself, giving you control over what escorts are shown on the website at any time (for example, you will be able to ‘hide’ an escort on the live site so she can’t be found, this could be useful if you’ve not received payment from them yet for example).

The admin site would also allow you to put certain escorts on the homepage as featured or popular escorts and any other similar functionality you might want.

Payment Handling

On the escorts signup page you can choose how you would like to handle payment processing and there are a number of methods available, each with differing cost implications.

Probably, in the first few months of a site going live, and certainly if budget is an issue, it might be worth going with a simple manual method. Prospective escorts would fill in the online application form (which would contain all the information shown in figure 1) and submit it to you. You would receive an email containing the application, the information from this form would be automatically stored in the database.

You could then check the application and if happy to include the escort on your site you could then quickly and easily generate a Pay Pal invoice that would be emailed straight to the escort. Once the payment has been received, you could then login to the Admin website and put the new listing live.

If you would prefer to have your own secure server that accepts credit card transactions which go straight into your bank account, then this can also be arranged, although this will add substantial cost to the project and is something that could easily be added at a later date once your site gets more popular and starts generating you a revenue.

...Just some of the things you need to think of and let your designers / developers know.