---
title: "IGF IT Consulting Case Study: Referral context carried to the call | The Quiet Protocol"
description: "IGF IT Consulting, independent it consulting in Ohio. A referral would open the door. The website was quietly closing it again."
url: "https://www.thequietprotocol.com/proof/igf-it-consulting"
---

[The casebook](https://www.thequietprotocol.com/proof#transformations) Case 05 of 06

# IGF IT Consulting

A referral would open the door. The website was quietly closing it again.

- **Business**: Independent IT consulting
- **Location**: Ohio
- **Size**: Solo practice
- **Before**: A one-page bio site with a single generic "contact me" form

![A handwritten letter of introduction beside a closed laptop on a consultant's desk.](https://www.thequietprotocol.com/images/proof/consulting-referral-note-800.webp)

## As we found it

IGF's practice runs almost entirely on referrals from a small circle of former colleagues and client contacts. A referral already carries trust before the first email goes out.

A referred prospect would visit the site before the intro call and find a thin, generic bio page. It undersold the exact expertise the referral had just vouched for. There was no way to tell a one-time IT assessment from an ongoing advisory retainer. Some prospects went cold and never booked at all. On calls that did happen, IGF had no idea who referred the person or what the referrer had already told them. Every call started from zero.

- **Structure**: IT strategy assessments and ongoing advisory retainers for small and mid-sized businesses, sourced almost entirely by referral
- **Seasonality**: Referral flow is steady but unpredictable, arriving in small warm batches rather than a pipeline

A prettier site would not have helped.

A prettier website wouldn't have fixed this. The real problem wasn't how the site looked. It had no way to route a prospect to the right offer, and no way to capture what the referrer already knew. A nicer-looking version of the same page would have walked into the exact same cold calls.

## Referral context carried to the call.

The same operation, drawn twice. Switch sheets or slide the overlay to see what changed, and what stayed the same.

- **As found**: Trust lost at the website
- **As built**: Referral context carried to the call

Overlay

**As found.** The referral arrives warm, meets a thin bio page, and the intro call starts from zero.

**As built.** Intake records who referred the prospect and why, matches the offer, and briefs the call.

## What we installed

Product families involved: Client Intake Systems, Follow-Up and Automation.

| Item | System |
| --- | --- |
| 01 | Authority Website with a clear, differentiated service architecture: IT Assessment, Advisory Retainer, and Fractional CTO engagements |
| 02 | A referral-aware intake path capturing who referred the prospect and what the referrer flagged as the need |
| 03 | Booking tied to offer type, so a prospect self-selects the right conversation |
| 04 | An automated pre-call brief compiled from intake answers, delivered before every call |

## How one change led to the next.

Read it left to right. Each step depends on the one before it, from the system itself to what the business felt. Take one out and the chain breaks.

### System change

1. Step 1 Referral context is captured at intake instead of living only in a text thread with the referrer
2. Step 2 The site's service architecture matches the level of trust the referral already built

### Behavior change

1. Step 3 Fewer referred prospects go cold after visiting the site

### Operational effect

1. Step 4 An automated brief means IGF walks into every call with context, not from zero
2. Step 5 Proposals fit the actual need instead of a generic pitch

### Business effect

1. Step 6 A higher share of referrals convert to a paid engagement

## What the numbers did.

Referred prospects per quarter, counted at every stage. Each percentage is worked out from the counts beside it.

Before: 17.9%

First 90 Days: 45.2%

Of referred prospects became a paid engagement. Before: Quarterly cohort, pre-implementation. First 90 Days: Quarterly cohort, post-implementation.

### Before

Quarterly cohort, pre-implementation. One mark per referred prospect.

**5** converted to a paid engagement **23** did not reach an engagement

### First 90 Days

Quarterly cohort, post-implementation. One mark per referred prospect.

**14** converted to a paid engagement **17** did not reach an engagement

| Stage | Before Quarterly cohort, pre-implementation | First 90 Days Quarterly cohort, post-implementation |
| --- | --- | --- |
| Referred prospects | 28 Starting count | 31 Starting count |
| Visited the site | 24 85.7% of prior stage | 30 96.8% of prior stage |
| Booked an intro call | 14 58.3% of prior stage | 27 90% of prior stage |
| Intro call held | 12 85.7% of prior stage | 26 96.3% of prior stage |
| Converted to a paid engagement | 5 41.7% of prior stage. Weakest stage | 14 53.8% of prior stage. Weakest stage now |
| Reached the last stage | 17.9% | 45.2% |

## Other measures in the case.

### Pre-call preparation time per referred prospect

Before: Roughly 35 minutes reconstructing context from email threads and texting the referrer directly

After: Roughly 6 minutes reviewing the automated pre-call brief

Measured per referred prospect: time back for the work clients actually pay for.

## Who felt the change.

### For the team

There's no staff. That's the point. The system does the context-gathering a growing team would otherwise have to absorb.

### For customers

A referred prospect gets a website and an intro call that both match the credibility the referral already promised, instead of a letdown.

### Twelve months on

The referral-to-engagement rate nearly tripled, with no change in referral volume. For a solo practice, new-business capacity is the real constraint, not demand. That's exactly the constraint this fixed.

### How customers see them now

Referred prospects now meet a practice that looks and responds as capably as the referral promised.

## What this case proves.

For a referral-driven practice, the website's job is to protect the trust the referral already built. Looking better isn't the same as working better.

If your business runs on warm introductions, treat the first digital touch after that introduction as part of the referral itself, not a separate marketing job. Get it wrong and you can undo the trust in one click.

The lesson any business can take from IGF IT Consulting.

[BGM Insurance Agency They already paid for a CRM. It just wasn't built to match how the agency actually worked. Read the next case ![A broker's policy binder open to a renewal schedule with a few dates highlighted.](https://www.thequietprotocol.com/images/proof/insurance-renewal-binder-800.webp)](https://www.thequietprotocol.com/proof/bgm-insurance-agency)

## You've read the record. Now let's draw yours.

Every case here started the same way: the business as it runs today, drawn honestly. A call with us does that for yours, then tells you whether the first move is a website, call coverage, connected follow-up, or something custom.

[Book a call](https://www.thequietprotocol.com/book/intro)

- **Record**: Your business
- **Sheet**: As found
- **Survey**: Not yet started