Ad Revenue Driven Websites - Step 4 - Plan Your Execution

In the last article of the series, I discussed steps to help you choose your idea for an ad revenue driven website. If you’re new to the series entirely, you can have a look at the entire section devoted to developing your ad revenue driven website.

This week, we’re going to talk about planning the execution now that you’ve narrowed down and chosen your idea for your website.

Set Milestones

Milestones are a wonderful thing. They help motivate but also allow you to manage your time correctly. I found that a work-until-it-gets-done attitude usually ends up with my mind running astray and I begin to work on different or more interesting projects. Give yourself general guidelines that you can follow, example:

September 4th - Logo Design
September 8th - Site Design
September 18th - Content Management System Development
September 24th - Web Development
September 30th - Implementation
November 10th - Marketing

If this is something you’re having trouble with. Think to yourself: What is standing between me and success? Work backwards from your due date as well as forwards from the present.

Plan The Details

This is an extension to the milestones, it goes into a little more detail. This helps you identify problems or delays before they occur. This will end up saving more time then this process takes. Your details may end up looking something like this:

September 24th - Web Development
- Need MySQL server
- Need Hosting
- James, our programmer, doesn’t work on weekends

Gather Your Resources

These are the preliminary things you can take of. Take care of them, It definitely helps to get the ball rolling knowing you’ve already started to take care of things. Examples include:

• Buying the domain name
• Calling up your programmer to see if he’s up for the task
• Buying hosting or appending your existing hosting account
• Buying the required software, eg. Adobe Photoshop and/or Adobe Dreamweaver

Draft an Information Architecture

What is an Information Architecture? When speaking in web development terms, an information architecture is a diagram illustrating the structure of your website and all its components (such as pages or password protected areas). This helps you realize the work that’s ahead of you and helps you better plan your execution. Here’s an example of an Information Architecture that I did for a client:

It doesn’t need to be pretty, or digital for that matter. The best thing about it, is anyone can do it, and it will save you from some long-term problems you can run into.

Draft a Wireframe

What is a Wireframe? When speaking in web development terms, a Wireframe is a diagram representing a specific page and generally lays out how it’s going to work and where things will generally be placed. Like Information Architectures, you don’t need to be good in design or good at computers. These can work just as well on computer or a whiteboard. Here’s an example of a Wireframe that I did for a client:

That’s all for now, if you’re new to the series entirely, you can have a look at the entire section devoted to developing your ad revenue driven website.
Good luck, hope that helps.

All information over Golfshops Pieper-Golf and other German Golfshops

Related Posts

• Ad Revenue Driven Websites Series Wrap-up
• Ad Revenue Driven Websites - Step 2 - Develop Ideas
• Ad Revenue Driven Websites - Step 5 - Execute