Garrison Atlanta Foundation Repair Microsites for Inspection Calls

Where the roof water lands: the first page on every area site

Start each area site with a page about gutters, downspouts and grading. It meets owners weeks before a crack scares them, and it speaks in your inspector's words.

Ask your inspector how many visits end with a talk about downspouts. If the answer is a lot, the first page on each area site should be about roof water. Plenty of owners look up small things, like a gutter spilling over the front steps, well before anything makes them think about piers. A page that answers them puts your company's name on the house early, while the fix is still cheap and the owner still feels calm.

We'd write it with your inspector over one short phone call. What should an owner check after a hard rain? Where should a downspout empty? What does a damp crawlspace smell like on a July afternoon? Those answers go up beside pictures your crews took on real jobs, and the page closes with a plain line about when a visit from your team makes sense.

• Walk around the house during a heavy rain and watch where the water goes
• Check that each downspout empties as far from the wall as your inspector likes
• Pull back mulch or soil that's piled up against the brick or siding
• Clear the gutters after the leaves drop, since an overflowing run pours right beside the wall
• Notice puddles that are still sitting next to the house a day after the rain
• Call when a door starts sticking or a new crack appears after a wet stretch

Borrow page titles from the door that sticks in July

Homeowners rarely type pier or underpinning into a search bar. They type what they see and feel, so each page title should borrow their exact phrases.

Your office already hears these phrases every week. Leave a pad of paper beside the office phone for a month and write down how each caller opens. That list is your page plan. A phrase that turns up five times deserves its own page. One that turns up once can live as a question on a bigger page. Swap in only the jobs you actually do, and drop any row your crews don't touch.

Save the engineering words for further down each page. Once a reader trusts the page, they're glad to learn what a pier is. They just won't search for one first. We keep the title plain and let your inspector's explanation carry the technical part, the same way they'd explain it standing in the driveway.

Explaining red clay without scaring anybody

Every Atlanta foundation site needs a page about the ground under the house. Keep it calm, cite a real source and let your inspector draw the conclusions.

That's a fine fact for a page, and it's also where a lot of foundation copy goes off the rails. It leaps from red clay straight to a warning that the house is sinking. Nobody can say that about a house they haven't walked. The page's job is to explain what's under Atlanta yards, then hand the reader to someone who can come and look.

We draft the soil page from a short talk with your inspector. How does the clay behave on the jobs they've walked? What do they check first when they open a crawlspace door? When do they tell an owner to fix the gutters and wait a season? Their answers go in, in their words, and they read the draft before it goes live.

January 2026 changed the code edition, so the permit pages changed too

Facts on a foundation site go stale quietly. One shared fact list for the whole network lets a single correction reach every area site together.

A code edition matters because an owner planning pier work often reads the permit page twice, once when the worry starts and again right before signing. If the page names last year's edition, the sharp readers notice, and everyone else walks away with stale information. Either way, your company's name sits at the top of that page.

1. Keep one fact list for the network Every dated fact on every site, like a code edition or a rain figure, sits in one list with its source and the day someone last checked it.
2. Tag each page that uses a fact When a fact changes, the list shows every page it touches on every area site, so nothing hides on site number twelve.
3. Recheck when the rules move Code editions, fees and forms change. We look again now and then, and again whenever your office hears about a change on a job.
4. Run the new wording past your team Your inspector or office manager reads the corrected line first, since they're the ones answering the phone about it.
5. Ship the fix everywhere at once The corrected line goes out across the network together, so one area site never argues with another.

Who tells you when the city changes a form or a code edition?

Usually your own office hears first, from a permit tech or an inspector on a job. We also recheck the fact list now and then. Either way the change lands in one place, your team reads the new wording, and it goes out to every area site together.

What if a rule changes and nobody notices for a while?

Then the fact list is where the fix starts. Tell us what changed, and the corrected wording goes to every site together. Until it's checked, the page points readers to the Office of Buildings.

Should the permit page quote fees or wait times?

We'd keep both off. They change, and we couldn't confirm current figures. A line inviting owners to ask you, so you can check it for their job, ages far better than a stale number.

An inspection request that already knows your company's name

Someone who asks through your own area site knows exactly who's calling back. That changes the first minute of the call more than most owners expect.

Foundation work is a trust sale. People are letting a stranger crawl under their house and then tell them something expensive. When they've already read your inspector's page about sticking doors, a big share of that trust is in place before the callback. Your scheduler isn't cold-calling a name off a list. They're returning a call to someone who chose them.

We can't promise how many requests a site will bring, and nobody honest can. What we can promise is where they go. Every call and form from an area site reaches your office, tagged with the site it came from, and the site carries your company's name from top to bottom.

After someone presses send, the site tells them what comes next in your office's own words, like a call from your scheduler during business hours. It never names a visit time your team hasn't set, because a missed promise on day one is hard to win back.

Counting a slow trade: inspections booked, proposals sent, piers set

Foundation jobs move slowly from the first call to signed work. Judge each area site on the steps that lead to a job, and give it a fair stretch.

• Requests per site, split into phone calls and forms
• Inspections your team actually booked from those requests
• Visits that ended with a proposal from your office
• Proposals signed, with the size of each job
• Visits that ended with a drainage fix or a watch-and-wait note
• Requests you turned down, and the reason for each

The last two lines matter more than they look. A site that brings plenty of gutter questions and few pier jobs may be the one filling next year's calendar, once those owners come back. And a stack of turned-down requests from one area tells you that site is reaching past where your trucks like to go.

We tag every request with its site. Your office adds what happened next in whatever system it already uses. After a few months, the two lists side by side show which areas deserve more pages and which ones need a harder look from both of us.

One more habit helps. On the callback, ask how the owner found you. Tags catch most of it, but some people read a site on their phone, save your number and call weeks later from the car. Their answer fills the gaps a tag can't see, and it costs your scheduler five seconds.

The page that tells some owners they don't need you yet

Not every crack needs a crew. A page that helps owners sort worry from normal, in your inspector's words, builds trust long before any visit.

It sounds backward to publish a page that talks people out of calling. It tends to work the other way. An owner who reads your inspector's note on which cracks can wait, and which ones deserve a visit, remembers who was straight with them. When something does change, your number is the one they already trust.

Your inspector sets the rules, and we turn them into plain sentences. If they like the idea, we'd add a simple way to keep watch, like a pencil tick at each end of a crack with the date written beside it. If the crack creeps past a tick, the page asks the owner to send a photo. The page never diagnoses anything. It just gives a nervous owner something calm to do tonight.

• The kinds of cracks your inspector usually lets ride for a while
• How to mark and date a crack so any growth is easy to spot
• Photos to take today, so there's something to compare against later
• The changes that mean it's time to call, in your inspector's own words
• A short form for sending a new photo when something moves
• A friendly note that sending a photo costs nothing and commits them to nothing

What we'd ask a marketer if our own crew's name rode on the answer

You've probably sat through a few marketing pitches already. Here are straight answers to what we'd ask in your chair, including the ones with awkward answers.

How much of our inspector's time does this take?

Less than most owners fear. We send drafts for your inspector to correct, so it's mostly reading. There's one short call at the start, then a read-through before each new page goes live. After launch, they'll hear from us when a fact changes.

Who writes the parts about cracks and piers?

We draft, and your inspector corrects. Nothing technical goes live until someone on your team has read it. If they'd never say it in a driveway, it comes out.

Can we start with a few areas instead of a whole network?

Yes. Starting where your crews already spend most of their week is the sensible way in. More sites can follow once the first ones have a record you can look at.

If we part ways someday, who keeps the sites?

The Garrison sites belong to Trojan Digital Marketing, which runs them under your company's name while you're a member. The fate of those sites and the request records after a membership ends is written into your agreement. We settle that with you before launch, so nobody has to guess later.

If you send us only a few things, make them photos from your inspector's phone. A downspout emptying against the brick makes a strong first page, because every owner has seen one. A stair-step crack with a tape measure beside it comes next, since the tape gives the photo a sense of scale. After that we'd pick a wet crawlspace after a hard rain, lit by a flashlight.