Plenty of sites look fine and do nothing.
That usually happens because nobody decided what the site was for before the design started. The work begins with the one action you want a visitor to take — and then every page either supports it or gets cut.
- 01
Planning and content structureWhat the site is for, who it is for, and the single action it should support
- 02
Experience and visual designBuilt around your brand, not around a template that came with the theme
- 03
Copy and contentWritten, edited, or shaped from yours — scoped explicitly either way
- 04
Development and buildMobile-first, because most of your visitors already are
- 05
Testing and accessibilityAcross devices and assistive technology, before launch rather than after a complaint
- 06
Domain, hosting, and launchSet up in your name, with the cutover planned rather than improvised
- 07
IntegrationsForms, booking, payments, or your existing systems where that is in scope
- 08
Ongoing maintenancePlatform and plugin updates, backups, and content changes, if you want them
Page count, copywriting, photography, hosting, domain, accessibility targets, integrations, maintenance, revision rounds, and content ownership are defined in the applicable agreement.
Design & build
Most business sites fail at the same two points.
The first is the phone. A visitor on a small screen, one-handed, in a hurry — if they cannot find what you do and how to reach you within a few seconds, the quality of the desktop view is irrelevant. That is why the build starts at the narrow width and grows, rather than the reverse.
The second is the ask. A page carrying six competing calls to action has none. We decide the primary action first and let everything else support it — which usually means removing things, and usually meets some resistance.
There is a third benefit to writing plainly about what you do: AI assistants can only recommend an organization whose website actually says what it does.
Scoped in your agreement
Page count, who writes the copy, photography, integrations, accessibility targets, revision rounds, and the review and sign-off process.
Revision rounds are stated as a number. Open-ended revisions are how fixed-price website projects quietly become hourly ones.
Hosting, launch & maintenance
A site is software, and software rots.
Launch is the visible milestone, and the smaller half of the job. Domain and hosting get set up in your name, the cutover is planned so search engines and existing links follow you, and the analytics are in place before the first visitor arrives rather than three months later.
Then it ages. Platforms and plugins accumulate known vulnerabilities, contact details drift out of date, and the page about the service you stopped offering stays up for four years. An unmaintained website stops being a marketing asset and becomes a security liability on your own domain.
Scoped in your agreement
Hosting and domain arrangements, launch and redirect plan, analytics setup, update cadence, backup arrangements, and how content changes are requested and charged.
Maintenance is optional. It is worth deciding about at launch rather than in two years.
Website projects go wrong over four things. All four are agreeable in advance.
None of these are difficult. They are simply the ones most proposals leave vague, and vagueness is what turns a fixed price into a dispute.
You own all of it
The domain is registered to you, the hosting account is yours, and the site and its content are yours. Leaving us should cost you a transfer, not a rebuild. Any provider who resists this is telling you something.
A page count is not a scope
Who writes the copy, who supplies photography, how many revision rounds are included, and which integrations are in — those four answers are the actual scope. We name them, because assumptions about them are what blow projects up.
Accessibility is a target we test against
We build and test toward a stated accessibility standard and tell you what we checked. Nobody can promise permanent total conformance across content that keeps changing after handover — and a provider claiming to has not thought about it.
An unmaintained site is a liability
If nobody is updating the platform, the site becomes a known-vulnerable application on your own domain. We will say so at launch rather than selling maintenance back to you after an incident. Managed cybersecurity
Worth asking any web developer pitching you.
Particularly the first one, and particularly before you sign anything.
01Who owns the website and the domain?
You do. The domain is registered to you, the hosting account is in your name, and the site and its content are yours to take.
This matters more than it sounds. A depressing number of small organizations discover at the point of changing supplier that they cannot move their domain or take their site with them. Ask any provider this before signing, and get the answer in writing.
02Do you write the content?
Copywriting and photography are scoped explicitly, so you know what is included rather than assuming. Both can be ours, yours, or a mix.
The honest recommendation is usually a mix. You know what customers actually ask, which objections come up, and how you explain the work in a room. That raw material beats anything written from the outside — we shape it and make it work on a page.
03How long does a website take?
It depends on page count, how much content already exists, how many people need to approve it, and which integrations are involved. We scope and schedule it against your project rather than quoting an average that would not apply.
The most reliable predictor is not our capacity — it is how quickly content and approvals come back from your side. We will tell you what we need from you and when, so the timeline is something both parties can actually hold.
04Do we need a rebuild, or can our current site be improved?
Often it can be improved, and we will say so. If the structure is sound and the platform is current, better content, clearer calls to action, and a mobile pass can do most of the work for a fraction of a rebuild.
A rebuild is the right answer when the platform is out of support, the structure fights every change, or the site was built around a business you no longer run. We would rather tell you that you do not need one than sell you a project you will resent.
05What happens after launch?
Ongoing maintenance is optional and scoped separately — platform and plugin updates, backups, monitoring, and content changes with a stated way to request them.
If you would rather handle it internally, that is legitimate and we will hand over properly documented. What we will not do is launch a site and say nothing about the fact that it now needs looking after.
Tell us what you want a visitor to do.
A first conversation covers who you are trying to reach, what you want them to do when they arrive, what exists today, and whether the honest answer is a new site, a better one, or something else entirely.
Or call (734) 772-9499 · Mon–Fri, business hours