network design

That is a pretty vague set of requirements to base a design on. You can pull any number of "sample" designs off of Cisco's web site.

A network needs to meet the business objectives of the company. To do this you need to know the supporting business requirements. This is a functional, not technical, definition. With this, you can then define your technical objectives that directly support the business requirements. The technical objectives drive the technical requirements of the design - logical, physical, and component.

Are you remotes accessing the Internet, or simply internal resources? If it is all internal, a firewall and IDS may be overkill. Do you want an NMS to handle down to workstations, or simply the communications network? Will the remotes talk with each other, or simply the central site? Static routes work fine for point to point type of networks.

Why not specify your needs and call Cisco? They're so happy to sell you a solution that I'm quite sure that they'll be happy to design it for you. Since you've already decided that Cisco is your vendor of choice, why not take advantage of the excellent resources they have to offer? Cisco, like any other vendor of networking products, maintains a staff of experts for just this purpose. Use them!

I'm really not being facetious here - good vendors have been a godsend in my career. The good ones really do believe that their job is to make the customer completely satisfied, and their help can be invaluable. Take advantage of that, then take credit for the result at review time. Cisco won't mind, so long as they make the sale.