Need help?Jamie

Microsites

Exclusive Contractor Leads From Microsites in Your Name

You're done splitting leads with competitors, and you'd like homeowners to see your company's name before they ever pick up the phone.

Branded exclusive organic leads are calls and forms homeowners in eligible US markets send from Garrison microsites that show your company's name. Garrison is the microsite software from Trojan Digital Marketing, and we don't sell those inquiries to competing contractors. It's for the owner who asks, "Why does every lead I buy already have two other quotes?" In July and August 2026, our 204 Indiana water restoration sites brought in 17 inquiries.

Tell us the trade you sell and who on your team answers new calls. The first strategy call is free, and during business hours we aim to reply within five minutes.

  • Your name and number on every microsite
  • Inquiries never sold to a competing contractor
  • A written rule for what counts as qualified

We've been owner-run since Jeff Clerisier founded the company in March 2018, and Jeff confirms custom network terms himself. For a contractor weighing branded leads, the promise that your inquiries won't be sold to a competitor comes from the founder, and you can ask him about it on the first call.

Creative planning materials for a brand review
IllustrationHow microsites flowsThis page’s three priorities drawn as a path from the first contact to the next step. It’s an illustration with no platform or client data.HOW IT FLOWSMicrositesYour brand01Your name and number on every microsite02Inquiries never sold to a competingcontractor03A written rule for what counts asqualifiedNEXT STEP

See how I'd approach this

Choose a question
to look at with me.

Your brand connected to direct inquiriesDiscoveryYour pagesInquiriesFollow upYOUR BRAND
  1. Discovery through your branded pages
  2. Inquiries reach your business
  3. Your team follows up
Your brand connected to direct inquiries

Your company’s name, colors and logo go on every site in the towns you serve. Calls and forms from those sites go to your team, and before launch we check that route with a test call and a form fill. We don't sell a covered inquiry to a competing contractor.

Frequently asked questions

Does exclusive also cover our market?

Yes, for your trade. One contractor per trade holds each agreed market, so a competitor in your trade can't take the same towns on Garrison. We confirm a market is open before you join.

Is a descriptive domain still a branded microsite?

Yes, as long as your company's name shows clearly on every page and on the form. A domain that describes the service doesn't name your company by itself, so the page and form have to.

Are all microsite inquiries organic SEO leads?

No. A microsite can also get visitors from ads, referrals, people typing the address in and sources nobody can trace. We'd label each inquiry by the source the evidence shows and mark unclear ones as unknown.

Who decides whether an inquiry counts as qualified?

The written rule in your agreement, settled before launch. Inquiries past your year's included allowance get reviewed by hand against that rule before any invoice goes out.

What makes a lead branded?

The homeowner sees your company before they ever reach out. We put your company's name and logo on each Garrison microsite and route its phone number and form to your team, so the caller already knows who'll pick up. A lead form under a provider's own brand leaves that question open until somebody finally calls the homeowner back.

Does exclusive mean the homeowner won't call anyone else?

No, and nobody can promise that. Exclusive describes what happens to the inquiry itself: it goes to your team, and we don't sell it to a competing contractor. A homeowner is still free to look up other companies, so a quick callback wins jobs that a slow one tends to lose.

What counts as a qualified lead?

A call that runs over 60 seconds, or a form, from a homeowner or property owner inside your agreed service area who's asking for a service you sell. Your service area gets agreed before launch. A qualified inquiry still isn't a sale, and a wrong number or a 20 second hang-up doesn't qualify at all.

Which US markets can get branded Garrison microsites?

Eligible markets outside Indiana, and we confirm yours is available before you join, since one contractor per trade holds each agreed market. Tampa, Florida already has Garrison pages for roofers and water restoration companies. Houston, Texas has its own set, down to foundation repair and remodeling, which are scoped on request. Your own town list then decides where the sites go. After launch we watch each town's search data and rebuild or replace the towns that stay quiet.

What kinds of inquiries do branded microsites bring in?

Real service requests, going by our Indiana network. The water restoration inquiries from July and August 2026 included a burst sprinkler line and a basement holding seven inches of water, and 11 of the 17 came during the August floods. Missed calls aren't in those counts. Separately, our window network received five inquiries from 100 websites in their first five weeks live.

Do business owners vouch for Jeff?

Yes, on Google. Mike Bamosi wrote that the work "drove a noticeable uptick in leads within just a few weeks," and Heather Doan's review begins, "I had a great experience working with Jeff." Read those as reviews of how Jeff works with a business. The dated Indiana counts are the better guide to what branded microsites do.

Who owns the branded microsites?

We own and operate the Garrison membership network, and the microsites allocated to you carry your branding and send inquiries to your team. Account access and renewal scope are written into your agreement. If there's anything about ownership you'd want settled before signing, ask Jeff about it on the free strategy call.

“I had a great experience working with Jeff…”
Heather DoanGoogle review

We have more than 1,400 live websites.

Based in Indianapolis, we serve businesses across central Indiana, including Carmel, Fishers, Zionsville, Westfield, Noblesville, Greenwood, Avon and Plainfield.

We also work with clients across the United States.

Read our Google reviews

What gets checked before a branded microsite takes its first call?

Before the first call reaches you, each Garrison microsite in your US markets gets checked for your company's identity and a working route to your team.

  • Your company's name and logo match your other listings
  • The number on the site rings a phone someone answers
  • The services listed are ones you actually sell
  • The service area matches where your crews go
  • Test calls and form fills reach your team
  • The qualified lead rule is written into your agreement
  • No inquiry route points to another contractor
  • Each town's pages carry their own wording

How does a branded exclusive lead differ from a shared lead?

A Garrison lead in your US markets reaches one contractor from a site carrying that contractor's name, while a shared lead's handling depends on each provider's terms.

What you're comparingGarrison branded leadShared lead
Whose name the homeowner sees
Your company's name and logo
Depends on the provider
Who receives the inquiry
Your team and nobody else
Can go to more than one contractor
What counts as qualified
A call over 60 seconds or a form from your service area
Check each provider's own definition
Where it starts
Unpaid search landing on a microsite branded to you
Varies by provider

Choose a branded network for your business

Compare our 50, 100, 150, 200 and 300 Garrison microsite memberships. Year one includes the build, domains and the first year of hosting and upkeep. Annual renewal includes domain renewals, hosting, upkeep, a fresh batch of local articles, updated pricing guides and FAQs, and the same included qualified lead allowance again. The plans include 5, 10, 15, 20 or 30 qualified SEO organic leads respectively each membership year. The included allowance resets at renewal. Only additional qualified leads above that year’s allowance are manually reviewed and invoiced monthly at your plan’s additional lead rate. At the end of each membership year, each included qualified lead the network did not deliver becomes a credit toward your next renewal, valued at your locked additional lead rate. The credit is capped at the renewal price, applies to renewal only and has no cash value. Additional qualified leads are billed monthly, in arrears, at your tier rate after review against the agreed qualified lead definition and after the annual included allowance is used. Your additional qualified lead rate is fixed at signup and stays fixed while your membership renews without a gap. Published rates may change for new members.

Four words that need four clear definitions

Branded describes the business presented to the customer. Exclusive describes the agreed handling of the inquiry. Organic describes the supported source evidence. Qualified describes whether the request meets the business criteria. These are separate claims, and a request can satisfy one without satisfying all four.

How to inspect the offer behind the terminology
ClaimWhat to checkWhat it does not establish
Branded
The page and confirmation identify the real provider
The visitor already knew the brand
Exclusive
The provider routes the covered inquiry to your company under agreed terms
The customer will contact nobody else
Organic
The available source record supports organic discovery
Content and maintenance are free
Qualified
The inquiry meets the documented service criteria
A sale, appointment or completed job

Trojan plans microsite networks around those distinctions. The goal is a resource the customer can use and an inquiry process the owner can verify, with a defined role for each site in the broader brand.

Put the company identity at the decision point

A visitor should not need to search the footer to discover who will receive a form. Identify the company near the offer and before submission. Use the actual service name, approved business branding, relevant contact information, and a concise explanation of the next step.

Read more

A descriptive domain can support a focused resource while the page clearly states that it belongs to the named provider. Avoid presenting the site as an independent comparison service when it represents one company. A regional resource also should not imply an office or staffed location that does not exist.

The domain and customer trust guide provides a practical review from search result to confirmation. Brand consistency should continue after submission through the reply, appointment conversation, and proposal.

Specify what Trojan means by exclusive routing

Trojan routes inquiries from the covered branded microsites directly to your business. We do not sell those same inquiries to competing providers. The agreement should identify the covered properties, recipient business, delivery systems, and any authorized operational recipients needed to handle the request.

Read more

That describes our delivery arrangement. It does not control a customer's independent research or prevent the person from asking another contractor for a quote. It also does not imply that every other lead provider distributes the same lead. Providers use different models, and their current terms must be checked individually.

Keep geographic and trade rights explicit where they are part of an agreement. A phrase such as exclusive market can otherwise be confused with exclusive lead routing. The exclusive and shared lead comparison covers the broader purchasing distinction.

Make the lead definition reflect the work

A useful definition names the services offered, actual project coverage, information needed to respond, and any project characteristics that materially determine fit. For a window replacement business, a request for a product part may differ from a request for installation. For a restoration team, a general question may differ from an active incident inside the accepted response area.

Read more

Do not require customers to know technical specifications merely to count as a real inquiry. Some details belong in the next conversation. Use an awaiting information status when the office needs clarification, and identify who resolves it.

Keep duplicates, test submissions, spam, existing project updates, and new opportunities distinguishable. A second call about an open request is activity on that request; a later unrelated project may be a new opportunity under the agreed rules. The lead record reconciliation guide shows how to inspect those decisions.

Retain source evidence without inventing certainty

Record the entry page, available acquisition channel, submission destination, date, and an internal inquiry identifier. Customer reported discovery can be recorded separately. A person may see several sources before contacting the company, so the visible destination does not always reveal the entire journey.

Read more

Keep unknown source records in an unknown category. Do not relabel a direct visit as an organic lead merely because it reached a microsite built for SEO. If paid traffic reaches the same resource, keep that source distinguishable before evaluating unique customer outcomes.

Google Analytics documents separate lead lifecycle events. A useful implementation connects those stages with the business process. Personal customer details belong in the authorized lead system, and Google Analytics restricts personally identifiable information. Reporting should not expose contact details in public URLs or broad analytics labels.

Give the business usable control

Domain ownership, site access, content rights, tracking administration, and inquiry records need their own entries in the scope. A logo on a page does not establish ownership. A registrar login does not establish the rights to every photograph or software component used on that page.

Read more

Ask for an inventory identifying the responsible account, renewal obligation, permissions, and continuity process. Define whether each component is owned, licensed, or provided while the service remains active. This makes the owned lead claim practical and sets a clear handoff path if the engagement changes.

ICANN's registrant guidance explains the relationship between registration terms and registrant responsibilities. Use the account inventory guide to translate the actual arrangement into an operating checklist.

Review the whole customer path before expanding

Start with the decisionYour serviceFitTrustNext stepScopeEvidenceContact
Fit
Explain the service scope.
Trust
Show supporting evidence.
Next step
Give a clear contact route.
Start with the decisionOne service can lead to different questions about fit, evidence and the next step.

Test a labeled inquiry through the form and any call route. Confirm the right business receives it, the customer confirmation is accurate, the internal record preserves the intended source context, and a person owns the next action. Repeat after meaningful routing or platform changes.

Then assess organic discovery, relevant visits, qualified requests, response handling, and recorded outcomes separately. Branded exclusive routing can strengthen control over the customer relationship; it does not remove competition or establish a lead forecast. Bring Trojan your current lead journey to scope a branded organic lead channel with visible standards.

Sources & further reading

Talk with Trojan Digital Marketing

Compare local ownership and membership options.

Use the local guides to compare network ownership with membership before requesting a territory review.

Roofing and water restoration networks serve eligible markets outside Indiana. A guide does not confirm territory availability.

Treat a brand change as a change to the customer conversation

When a microsite receives new branding, preserve which business an earlier visitor expected to reach. The revised branding and the request handoff need an agreed connection to that original expectation.

  1. Name the receiving business before preparing the edit Have the business approve the company name used for the revised branding. We can inspect where the older name appears on the covered page. A logo file by itself may leave the receiving team unclear about what the new name means. The owner needs to explain the relationship that customers should understand.
  2. Keep the earlier wording available Save the actual name statement and contact prompt before changing them. Our task can attach those words to the page version being replaced. An open request may refer to that earlier wording after the new page is released. Retaining the starting point helps staff recognize the customer context without guessing which brand the person saw.
  3. Find the handoff that uses the old name Ask the receiving team to show a redacted example of the message label it currently gets. We can compare that label with the public page. If the message uses an older company name, the task may need another edit beyond the site artwork. Keep that receiving step visible before approving the public change.

A branding request often begins with a new logo or different colors. The practical issue is also how a person recognizes the company answering their request. We can discuss that change from our Indianapolis, Indiana base. Your business supplies the approved name relationship. Our proposed work can then identify where the public wording and receiving message need to carry it.

What if the new name has no approved explanation yet?
Keep the branding draft pending while the business settles that question. We can prepare layout options without publishing a guessed company relationship. An unresolved name change should not become a claim that another contractor now receives the requests. The business needs to supply the account that staff can use when a customer mentions the earlier page.
Should a historical request be renamed to match the new logo?
Keep the original page context attached to that request. We suggest adding the approved current business relationship where the receiving team needs it, while preserving what the person encountered. Replacing every earlier label can make the conversation harder to understand. The task should state which fields are current branding and which retain the original contact context.

Distinguish the customer-facing name from network ownership

Updating a microsite brand changes its public branding. The agreement still determines the underlying asset arrangement, so the revision should not imply that a logo change transfers a provider-owned site.

Westfield Roofer homepage and contact choices
Branded inquiry continuity checks: Westfield phone and contact choices. View the project
Branded inquiry continuity checks
change detailAnswer the business must supplyCheck proposed for the task
Company presentedThe current approved receiving business name.The released page identifies that business near the request action.
Earlier visitor contextWhich name appeared on the previous page version.The old reference remains available for an open request.
Receiving messageWhich label staff currently see when a request arrives.The approved current relationship can be understood from that message.
Network arrangementWhich rights and access the actual agreement provides.The branding edit makes no unsupported ownership statement.
Reply wordingHow staff should explain the current name to an earlier visitor.The business approves the account used in a response.
Unchanged referenceWhich older page or message is outside this revision.The remaining item has a named owner and a stated status.

The Garrison network remains under Trojan Digital Marketing ownership and operation. Covered microsites can present the member business while remaining within that provider-owned arrangement. We should describe a brand revision in terms the actual agreement supports. A new name on the page does not establish domain transfer, a registrar change or different rights to the underlying site.

The pictured Westfield Roofer page introduces its contractor brand. Its visible business content gives us a concrete reference for discussing how a page introduces its subject. The capture does not establish the terms of a Garrison membership. Your name-change task needs its own approved words and the actual agreement for the network property involved.

What does the name edit leave unchanged?
The new logo can leave the same page address and the same site owner in place. We suggest asking for those parts to be stated in the task. If the agreement has no change to rights, the public name should not imply one. Staff can then explain the brand customers see without calling the site an asset that the member now owns. A separate request for rights needs its own terms and the person who can approve them.
Could an old request mention the domain instead of the company?
Keep the actual domain reference supplied by the person. We can compare it with the page version the business retained. Staff may need that reference to find which public name appeared there at the time. A new logo does not change the words the customer used in the first request. Leave those words readable in the authorized record rather than assuming the customer knew the current company name.

Keep older request labels understandable to the receiving team

The new page may be ready while older request messages still carry a prior name. Decide how staff will recognize those requests and explain the current business relationship before closing the branding task.

Which older labels deserve an inspection?
Inspect the labels actually used in the receiving route covered by the agreement. We can work from a marked test or a redacted message that your team provides. A page heading and an inbox subject can change separately. Name the label involved instead of assuming the artwork edit reaches every system that passes the request onward.
What should staff retain about an open request?
Keep the page or business wording the customer encountered with the original request. Our suggested handoff also identifies the current approved receiving business. That lets the responder recognize the older reference without rewriting the customer history. Store personal details only in the business system authorized for that information. A public task note does not need the individual private contact details.
Can an old subject line simply remain in place?
The business can decide whether a retained label is clear enough for staff, provided its meaning is documented. We can price a message edit if the older wording creates confusion. A changed subject should still preserve the link to the earlier request. Decide what the responder needs to know before choosing which words to replace.
Does a label change establish a different recipient?
The displayed label needs to be distinguished from the underlying delivery destination. We can inspect each under the access agreed for the task. Rewording a subject does not prove that a call or form moved to another business. If the recipient changes, that is a separate routing task requiring its own authorization and check.
  • Ask a staff member to read the older message as if it had just arrived. We suggest checking whether they can tell which request it belongs to and which company should answer.
  • If the subject line uses a shortened name, ask the business what that name means. A neat abbreviation can still confuse a person who has only seen the full public brand.
  • Keep the original request date attached to its record. It helps staff tell a new request from a later reply about the same work, without relabeling the first contact to match new artwork.
Who should answer a reply about the older name?
The business needs to identify that role in its handoff. We can help make the page account readable, but staff need an approved answer when the customer asks directly. Keep the original words the person used with the request. The reply can explain the current name without changing those words or claiming the customer saw the revised site. If the staff role has not been settled, leave that part of the task open for the business to resolve.
What if the office uses an internal short name?
Ask the business whether that name is clear to staff and how it relates to the public brand. We can keep the earlier customer reference separate from the internal shorthand. A responder needs both meanings when a person uses the words from the old page.

Preserve the original request while planning the revised branding

A branding revision should leave the earlier customer context readable. Use the approved current relationship to guide the handoff, while keeping the old public version attached to requests that began there.

Hypothetical example A fictional provider-owned microsite receives an approved brand update

Before

  • In this hypothetical exercise, a member business wants the public site to use revised company branding. The network provider retains the site under its existing arrangement. An open request refers to the older name on the page. Nothing in this example identifies a real member, service market or completed brand change.
  • The proposed edit replaces the logo and page heading. Its task note does not address the older name in the receiving message. Staff plan to relabel every earlier request with the new name. That would remove a reference the customer may use when asking about the request. We would pause that part of the proposed handoff.

After

  • The revised plan asks the business to approve how the two names relate. The public page can state the current receiving business without promising site ownership. Our handoff retains the earlier page wording for the open request. The receiving team can recognize that wording and use the approved explanation when responding.
  • The planned check compares the named public page with the receiving message under agreed access. Any unchanged older label remains visible in the task record. The example asserts no actual test, completed transfer or customer outcome. It shows how a provider-owned property can receive a branding edit while the earlier conversation retains its context.
  1. Keep the customer reference tied to the request Retain the original request identifier with the earlier business wording where your authorized system allows. We suggest avoiding a wholesale rewrite of those historical details. The responder needs to understand why the customer names an earlier page, even when the current site has a different heading.
  2. Approve the explanation used in the response Have the business settle the wording staff should use. We can help draft a concise explanation from that approved account. The message should not invent a merger, new location or another contractor relationship merely to make the names sound connected.
  3. Record any part outside the edit If another message or page keeps the earlier label, name it separately. Our completion note can identify the public material changed without claiming every reference is now revised. The remaining owner can then inspect that item against the same approved explanation.

Inspect the choices a visitor sees before sending a request

The revised name should make sense at the action a visitor can take. Use the actual page choices to inspect that context, then check the receiving message separately when the task includes access.

Texas Journeyman Prep homepage with two choices
Branded inquiry continuity checks: Texas homepage with task choices. View the project

The captured Texas Journeyman Prep opening gives visitors an exam-date button and a separate application-check button. Those visible paths let us discuss whether a person can recognize the action that fits their purpose. It is a reference from another project. The image does not show the microsite being rebranded or establish how its requests are delivered.

  1. Read the name beside each covered action Open the actual revised page and inspect the action named in the task. We can assess whether the approved receiving business is clear there. A new logo at the top may leave an older contact label farther down. The check should follow the customer choice, with the exact passage being inspected recorded.
  2. Inspect each distinct message included Where a form test is authorized, use clearly marked sample details. Our note should state which action was taken and which receiving message was inspected. If two page choices create different messages, their labels need separate observations. A visible success screen for one action does not establish the behavior of the other.
  3. Compare the reply language with the approved account Ask the business to read the response wording against its explanation of the name change. We can inspect that meaning alongside the current page. The response should help an earlier visitor recognize the receiving company without adding a new service promise or a claim about who owns the site.
What if a call route is also part of the microsite?
Name its separate check in the agreed task. We can discuss whether the business greeting recognizes the public name customers saw. A successful form message does not establish a call destination. The receiving team needs its own account of how that route presents the company, with any untested portion of the task left clearly pending.
Can the image replace the actual route check?
The project screen provides a visual reference for planning. Your revised microsite needs its own inspection under the access approved for that property. We can discuss the action labels while arranging that check. Treat the photograph as visible branding, and record the actual page and receiving observations when they are available.

Price a bounded brand change with named acceptance points

The quote should identify the public versions and receiving labels covered by the change. Agree on the approved name relationship and the checks that will show whether that specific change is complete.

  • Name the covered property and the business branding approved for it. We can then distinguish the public edit from any separately requested network term change.
  • Identify the earlier versions needed to understand open requests. Our proposed handoff should preserve that context without exposing personal customer details in the public task record.
  • List the receiving labels to inspect and who controls each one. A business inbox may have an owner distinct from the person approving the page artwork.
  • State whether the quote includes marked message tests, a call-route check or visible-page inspection only. We should report the part actually checked under the agreed access.
  • Keep any outside reference or unresolved explanation identifiable at acceptance. An edited logo should not close a named dependency that still lacks the responsible owner.
What would support acceptance of this branding change?
Compare the approved company account with the released public passage and the receiving labels named in the task. We can leave the inspected versions in the handoff. That supports a conclusion about the branding edit itself. It does not establish a change in search source, request volume or the rights to the site.
Should the task include a forecast for the revised brand?
The proposed name change has a practical completion point without a lead forecast. We can inspect whether the business is clearly represented and the earlier request context remains readable. A later performance question requires its own dated records. The buyer should be able to accept the branding work without accepting an unsupported prediction about future requests.
What should the first conversation settle?
Bring the current microsite reference and the company name your business now approves. We can ask which earlier request labels need to remain understandable. The conversation should also establish who can release each edit and which actual network terms apply. Those answers make the proposed change concrete enough to price.

Our branded-lead service can be discussed alongside a specific branding change. Start with the property and the name relationship you want customers to understand. We can inspect the material within the agreed task, while your business approves its public account. The result should leave the next responder able to recognize an earlier visitor without treating new artwork as a different asset arrangement.

Sources