Top of the Rim has never used a template. Every site has been written as custom code for that site, not assembled from a theme with the name swapped in. A template pretends the next organization needs the same pages, the same buttons, and the same sentences as the last one. It does not. The people are different. The job the site has to do is different. The words have to be true for that organization, or the site is a costume.
Chuck designs the site and Chuck builds it. There is no handoff from a designer who will never see the form fail, and no handoff to a builder who was not in the room when the scope was named. The person who hears what the site has to do is the person who writes the pages and makes them work.
This is the same rule as the rest of the practice. A narrow job stays narrow. A wide job is priced and built as a wide job. A one-page explanation is not quietly turned into a membership system. A membership system is not delivered as a one-page explanation and then described as if the system had been built. The shape is named first. The site follows that shape.
What gets named before anything is built
The first question is what a visitor is supposed to be able to do when they leave. Join a club. Find the next show. Watch a trail ride. Read the weather before they go. Send a note to the engineer. Those are different jobs. A site that tries to do all of them for every client is not a service. It is a menu.
The second question is who the site is speaking to, and what it must not pretend. A car club is not a shop. A trail site is not a consulting firm. A consulting firm does not need a ride calendar. The pages, the pictures, and the sentences have to survive a reader who already knows the organization. If a sentence would embarrass the person who does the work, it does not go on the site.
The third question is what finished means. Which pages exist on the day it goes live. Which forms send, and to whom. What the visitor can do on a phone. What is deliberately left out. A site without that edge keeps growing in the middle of the build, and the thing that goes live is not the thing that was described.
You talk to Chuck for that conversation. There is no sales layer turning a package into a site that does not match the organization.
What the build includes
What you get is the site in the scope, built by the person who scoped it. That is the pages, the words, and the way those pages behave. It includes the path a visitor actually takes, from the first screen, to the next click, and to the place they write to you if the site is supposed to receive a message. It includes a layout that can be read on a phone without a separate "mobile version" that was never finished.
If the site has to send mail, the mail is part of the job. A form that looks finished and does not arrive is not finished. If the site has to take a membership, show an event, publish a video, or send a note on a schedule, those parts are in the scope only when they were named. They are not sprinkled on because another site had them.
Changes are tried before they replace the live site. The address people already use stays the live site. You have access to a separate address while the work is in progress. That address is a full preview of what production will look like after you sign off. It shows the changes, and it shows the current look of the development site you are being asked to approve. The live site does not change until that sign-off.
What you do not get is work that was never named. A new section, a second language, a store, a members-only area, or a rebuild of the words six months later is a new scope unless that work was in the original job. The other way is just as firm. If the job was the membership path and the show calendar, the delivery is not a single page with a phone number and a promise to add the rest later.
Sites that are live
These are production sites. Each one is live at its own address. Each one was built for the work that organization does. None of them is a draft, and none of them is a copy of the others.
- Mopars Unlimited of Tacoma A 501(c)(3) Mopar club in Pierce County, Washington, at moparsunlimited.org. The site carries the club. That includes the annual Sunbust car show, the meetings, the cruises, the family events, and the way someone joins. A visitor who wants the next show should be able to find it. A visitor who wants to become a member should not have to guess who to call. That is a club site. It is not a trail log, and it is not a consulting practice.
- Roxy The Polaris A trail site at roxythepolaris.com, based in Overgaard, Arizona. The rides are on the Mogollon Rim and in the Phoenix desert. The site has the videos, the weather, and a way to follow along. Someone planning a ride should be able to see where the trails are and what the last runs looked like. That is not a club roster. It does not need a car-show calendar. The pages follow the rides.
- Top of the Rim IT Consulting This practice, at totrconsulting.com. The site has to say what the engineering work is, who does it, and how to book that person. The notes, the capabilities, and Meet Chuck are there because those are parts of the practice. It does not pretend to be a club, and it does not pretend to be a trail diary. The sentences are the ones the engineer will stand behind on a call.
Read those three next to each other and the difference is the point. The club site spends its pages on the show and the membership. The trail site spends its pages on the rides. The consulting site spends its pages on the work and the person who does it. Swapping the pictures would not make them interchangeable. The structure would still be wrong.
What this work is not
It is not a package every organization is asked to buy. There is no standard page count, no standard add-on list, and no monthly plan that turns a small site and a large site into the same invoice. The price follows the scope, the same way the rest of the practice prices an engagement. A simple site and a site with membership, mail, and a calendar are not the same job, and they are not the same price. That explanation lives on the pricing page.
It is not a coat of paint on someone else's theme. The code is written for that site. The pages are written for the organization. If a sentence is there because a template had a hole to fill, the sentence comes out.
It is not a promise about search rankings, ad spend, or a rewrite of the business. The site can say what the organization does. It cannot invent a service, a location, or a result. If you already have a site, and you are not comfortable with where the design is going, or you are not happy with the people who have it now, that is a reason to call. The new work starts from the site you have. The scope names what changes.
If the site needs a place to live, Top of the Rim can host it. For a new site, that includes registering the domain. The name is registered and locked so someone else cannot transfer it to another provider and hold it hostage. Hosting can also include the company email addresses that belong with the domain, and the security certificate that serves the site over HTTPS. Those pieces are part of the scope when you need them. They are not assumed, and they are not quietly added after the site is live. Later edits are a new conversation unless they were in the original job.
The site follows the rules that actually apply to it. A private site is built so people can use it. Text that can be read against its background, forms that can be completed, and pages that work without a mouse are part of the build. There is no law that requires a private site to add a contrast page, a text-size switch, or an overlay, and those controls are not sold as if a new rule required them.
How a first conversation goes
Bring the organization as it is. If you already know the pages, say so. If you only know that the current site does not match the work, that is enough to start. Chuck will ask what a visitor must be able to do, what must not be on the site, and what finished looks like. A club calendar and a one-page practice site do not leave that conversation as the same build.
If the first description was incomplete, the job is not silently stretched. A members area, a second show, or a move from a few pages into a site people update every week is a new scope. It gets its own conversation. The smaller site is not punished for having been the right size. The larger site is not forced into a plan that was never meant for it.
If you want the engineering work and a site, those are still two scopes unless you bring them as one. Identity, Windows Server, patching, and a public website are not the same afternoon. They can be the same client. They are named separately, and each one is built as the job it is.