Basics of web architecture : 101
This architecture was done circa 2005. It basically deals with intranet, contact data, bloggers (driving the organic SEO), prospecting and targeting, sales, and retention. Your architecture may have other toolsets like eDirect components, sales relays, social engineering components, dynamic SEO bots, CMS systems, but what’s important is that each part be theoretically isolated so that it can be constructed simply and then arranged in concert with the entire site – and by simply I mean in a way that your DB team isn’t frustrated.
Here’s some breakdown:
Public: At it’s most simplified and coherent, a public facing site should cover – who, what, when, where, why, how.
Culture/Bloggers:
Because the modern audience has the ability to investigate and cross reference, companies and products, they rely on it as their leading motivator to spend. What this means to your company or client is that empowering your entire staff with a blog will dramatically impact your standing within the world community. This impact is first realized in the area of organic SEO. 
Prospecting:
Another aspect of the cross referencing process of the audience can be addressed with a prospecting component. It’s essentially a comparison of corporations. A quick comparison will focus your ideal customers right away on you, while leaving the masses to continue their search.
Retention:
By using data-capture and then eDirect campaigns, you can foster retention. There can sometimes be a benefit by allowing clients or customers to cooperate with this data.
If you can capture the data in such a way that it’s available to the public as well as the targeted audiences and the client, then you’ve created as much gravity as the data can have on the web- this is when retention converts back to prospecting.
These components are generally the most sophisticated, require more resources, have the most longevity and are often overlooked by less sophisticated marketers. Which means you can probably have a dramatic effect at your organization should you be able to implement.
If you have any questions about this or your architecture, just email me at dennis@wakabayashi.us or IM me at risk18@mac.com. I’m happy to help.








































