The problem. What we found. What we built. What happened.

Problem

The firm needed a large website where every sentence could be traced back to an attorney's approval, reviewed line by line, and changed without disturbing anything else.

What we discovered

• The firm's email runs on Microsoft 365 with strict settings, and the domain sat with the previous agency, so launch had to be staged without any risk to mail.
• Copy review, not design, was the real work: hundreds of individual edits across several rounds by two attorneys.
• Visitors needed tools they could actually use: fee calculators and a consultation request that reaches both partners.

What we built

• A 24-page site generated from one set of approved content, so a change in one place updates everywhere it appears.
• A record of every edit: the original sentence, the replacement, and who asked for it, so any change can be reversed on its own.
• Fee calculators and a consultation form routed to both partners.
• Campaign landing pages for the firm's advertising, built from the same approved sentences so nothing on them says anything the attorneys have not signed off.

Result

• Live and public at fortressfamilylawco.com since September 2026. The firm's email was untouched through the switch.
• Every approved edit traceable. Nothing waiting on us.
• Campaign landing pages shipped October 2026.

Problem

A new restaurant has one chance at a first impression, and most of those first impressions now happen on a phone before anyone walks in. The owners needed to be findable, readable, and bookable from day one, without paying a third-party app a cut of every order just to host a menu.

What we discovered

• When someone nearby searches for breakfast, Google decides what to show them, and it reads the restaurant's own website to do it: hours, menu, address, photos. A restaurant with no site, or a site Google cannot read, is invisible at the exact moment a hungry person is choosing.
• Diners decide in seconds. If the menu is a blurry photo, the hours are wrong, or the page takes five seconds to load on a cell connection, they pick the place next door.
• Third-party menu and ordering apps are convenient, but they own the customer, charge a fee on every order, and put a competitor one tap away.
• The menu was going to change often, so updating it could not require a developer.

What we built

• A fast, phone-first website with the menu, hours, location, and photos written in a form Google reads directly, so search results and the map listing stay accurate.
• Online ordering and reservations on the restaurant's own site, where the customer relationship stays with the restaurant.
• A menu the owners update themselves, by text or from their point-of-sale system, with no developer in the loop.
• The business details and map listing set up together so the website and Google agree on everything.

Result

• Open with a website Google could read on the first day of business, instead of months of being invisible.
• Menu and hours changed many times since launch without a single developer ticket.
• Orders and reservations come through the restaurant's own site, with no per-order fee to a third party.

Problem

The company could not get its own domain back, so the new site had to launch on a new address, win back its place in Google from zero, and give customers a dependable way to reach the business.

What we discovered

• With the old domain out of reach, the new one would start from scratch with Google, and any mailbox on the old domain could be cut off at any time.
• The old site's words had been written by the prior agency, so everything had to be written fresh.
• The strongest asset the owner did control was his Google Business Profile, which drives most local search.

What we built

• A 21-page site plus fourteen city pages, each written with real local detail (housing, weather, permits) instead of the same paragraph with the city name swapped.
• Fresh copy written from scratch, not lifted from the old site.
• Forms that deliver to an inbox the owner controls, a service-area map Google can read, and a check that fails the build if any link is dead.

Result

• Live on a new domain the client owns since September 2026, with forms delivering and the site open to Google.
• An evidence file for the domain dispute, gathered alongside the build.