The expensive website mistakes Boston businesses keep making

We work with clients in Boston from Dubai, which means we see their sites the way a stranger does: cold, on a phone, with no goodwill and no context. The same mistakes come up again and again, and almost none of them are about taste. They are about Massachusetts law, about who actually buys in this city, and about how people here get online. Here are the ones that cost real money, and what we would do instead.

1. Publishing prices as if the fee rules did not change

The Massachusetts Attorney General's fee and subscription regulations, 940 CMR 38.00, took effect on 2 September 2025. They apply to anything advertised to, or sold to, consumers in Massachusetts. The practical effect on a website is blunt: the total price, including every fee that is not a government charge, has to be disclosed clearly and before you start collecting the visitor's information.

That kills a pattern designers have used for a decade. A booking flow that shows a headline rate, collects a name, email and phone across two steps, then reveals a service fee at payment is exactly what the regulation targets. So is a trial offer that never states the calendar date by which the customer must cancel, and a subscription you start in two clicks but can only cancel by phone.

This matters more in Massachusetts than elsewhere because of Chapter 93A. A violation is treated as an unfair or deceptive act, a consumer can send a thirty day demand letter, and damages can be doubled or trebled with attorney fees.

Instead: put the all in price on the page where the decision is made. Name each fee and say what it is for. If you sell a subscription, build the cancel path in the same place the signup lives, and write the cancellation date into the confirmation screen and the confirmation email.

2. Building a site that cannot survive a procurement review

If you sell anything to a hospital in the Longwood Medical Area, to Mass General Brigham, to a lab in Kendall Square, or to Harvard, MIT, BU, Northeastern or Tufts, your website is not the pitch. It is the first artefact their procurement office inspects. Universities here ask for a VPAT or an accessibility conformance report. Health systems ask for evidence of a written information security program, because 201 CMR 17.00 obliges anyone holding personal information about Massachusetts residents to maintain one.

Boston institutions also take digital accessibility more seriously than most buyers, for a specific local reason. The National Association of the Deaf sued both Harvard and MIT over captioning of public online content, and both ended in consent decrees, Harvard's in 2019 and MIT's in 2020. Institutions that have been through that do not sign off on a vendor whose site has unlabelled form fields and uncaptioned video.

Instead: treat WCAG 2.2 AA as a build requirement, not a remediation project. Caption every video before it goes on the site. Keep a short, honest security page you can hand to a reviewer. For research and clinical buyers, having those ready shortens the sales cycle more than a new homepage will.

3. Choosing the wrong languages, or the right ones badly

Roughly a third of Boston residents speak a language other than English at home. The languages that matter are not the ones an international template ships with. The City of Boston's own language and communications access work centres on Spanish, Haitian Creole, Cape Verdean Creole, Chinese, Vietnamese and Portuguese, and the Boston Planning agency has required translation into Spanish, Vietnamese, Haitian Creole and Cape Verdean Creole for Dorchester meetings.

Businesses serving East Boston, Dorchester, Roxbury or Chelsea publish a French version because a plugin offered it, and skip Haitian Creole and Cape Verdean Creole, the languages their customers actually use. Then they run what little they do translate through machine translation, and Cape Verdean Creole comes back as something no speaker recognises.

Instead: pick the two or three languages your customer base genuinely uses, pay a human speaker, and translate the pages that carry money and risk: pricing, intake forms, consent text, hours, directions. A fully translated blog archive is worth less than one correctly translated booking form.

4. Designing for the office network and not the Red Line

Boston is a transit city with old infrastructure. A large share of your visitors are on an iPhone, underground on the Red or Orange Line, or on commuter rail between Framingham and South Station where the signal drops for minutes. A site that feels quick on fibre in the Seaport can be unusable on the same phone eight stops later.

Instead: server render the page so text and the primary call to action appear without waiting on JavaScript, set explicit dimensions on images, and test on a throttled connection rather than your laptop. And publish the things people check while standing on a platform: today's hours, the nearest T stop, whether there is parking, and a phone number that dials on tap.

5. Writing the location page as if Boston were one place

People here do not search by city. They search by neighbourhood and by landmark: Back Bay, the North End, JP, Southie, Allston, Assembly Row, near South Station. They also cross municipal lines without thinking, which is where a lot of local SEO work goes wrong. Cambridge, Somerville, Brookline, Quincy and Newton are separate cities, and a single page optimised for "Boston" competes badly for every one of them.

The worse version is faking presence. A virtual office address on a Google Business Profile is a suspension risk, and in a city this small, a Financial District address on a company everyone knows works out of Waltham reads as dishonest.

Instead: one page per place you genuinely serve, with real detail on each: the T stop, where to park, which neighbourhoods you cover. If you are remote, say so plainly.

6. Ignoring the calendar this city actually runs on

Boston's year is shaped by the universities and the weather, and both are predictable. Late August and the first of September bring the annual lease turnover and a wave of students and new arrivals searching for everything at once. January brings a quieter stretch and snow emergencies that move demand online overnight.

Instead: plan the launch and the content around that calendar rather than your internal deadline. Make sure the site can carry a weather or closure notice without a developer, because the day you need one is the day nobody is at a desk.

7. Bolting tracking pixels onto pages about medical conditions

In October 2024 the Supreme Judicial Court decided Vita v. New England Baptist Hospital, holding that the Massachusetts Wiretap Act does not reach ordinary website tracking. That closed one route for plaintiffs. It did not make third party pixels on health related pages safe. HIPAA still applies where it applies, Chapter 93A is unaffected, and a comprehensive Massachusetts consumer data privacy bill has passed both chambers and sits in a conference committee.

Instead: know which pages describe symptoms, conditions, providers or appointments, and keep advertising pixels off them. Keep an inventory of every tag and who asked for it. A site with a consent layer and a documented tag list adapts to a new statute in a week. A site with five years of accumulated scripts does not.

The short version

1. 01Show the total price, with every fee named, before you ask for contact details.
2. 02Build to WCAG 2.2 AA and caption your video, because your biggest local buyers check.
3. 03Translate the money pages into the languages your customers actually speak, using humans.
4. 04Test on a throttled mobile connection, not on office wifi.
5. 05Write one real page per place you serve, and do not fake an address.
6. 06Keep a tag inventory and keep advertising pixels away from health content.

None of these are design problems in the way agencies usually mean it. They are compliance, content and engineering decisions that happen to show up on a screen.

We are a Dubai studio and we work with Boston clients remotely, not from an office here. That shapes the work: we read the Massachusetts rules properly rather than assume a generic United States build passes. If you are planning a rebuild and want an honest read on which of these apply to you, send us the brief.