Playbook IT Services

The Trust Funnel

Most buyers at the firms we work with cannot tell two IT services shops apart. This playbook fixes the credibility gap with three kinds of proof, one publishing rhythm, and the exact support system that keeps it running when the calendar fills.

Where IT services deals actually die

On a 5 to 50 person IT services or health-tech firm, the buyer cannot tell one shop from another by reading pricing. Nobody posts pricing, everyone claims quality, most sites look interchangeable. What decides deals is trust, and trust is built on one thing: visible prior work. The pie does not go to the best shop. It goes to the one whose work is easiest to verify.

Meanwhile referral motion stalls the first month a big contract ends. The pipeline is one relationship wide and the founder is the only one who can extend it.

The trust stack, as content

Three layers of trust. Each converts into one content pillar, and each pillar has a draft below.

Layer 1 visible operator

Full draft, credential proofFourth project in a row we shipped without changing the quoted timeline. Not a flex. The mechanism is a two-day design gate before the build starts, and we will not start without it. Most shops skip it because it is unpaid. It is the cheapest two days in the whole cycle.

Layer 2 visible prior volume

Full draft, failure storyA project we refused last year. Health data, two-year build, the buyer could not name the compliance owner on his side. We told him come back after naming one. He hired an entrant who said yes. Six months later we rebuilt the audit layer from scratch. Saying no is a trust signal most shops cannot afford. It is also the cheapest marketing there is.

Layer 3 visible work in progress

Full draft, process shotOn Thursday we finished a migration for a mid-size clinic group. Patient records moved to a single schema across nine locations. Zero downtime, one rollback drill passed. What most teams fail to publish is that same work happened in week two, not week six. That is where buyers form opinions about whether shops like ours can be trusted with a live system.

The first 30 days

Week 0: write the three drafts above, hold them. Week 1: publish the credential-proof post. Week 2: publish the failure story. Week 3: publish the process post. Week 4: pick the one that pulled the most engagement and write a second piece in that lane.

One cadence rule: every completed client engagement becomes a post within 7 days. Call it trust bookkeeping. The work already happened. It only needs to become visible.

What actually kills it

Week 2. Real work is at full speed, no one is assigned to write, and the drafts stay in a doc nobody opens. The system dies not from lack of proof but from lack of an operator who harvests proof while the founder is busy.

The weekly engine

The full DFY weekly cadence, priced in the open. It exists because the week-2 collapse above is predictable and fixable:

3 posts per week in your voice, harvested from your delivery notes and client emails.
Alert on every completed win: if the engagement closed this week, the post ships next week, no exceptions.
Monthly audit of what pulled buyer attention and what got silence, with the angle plan adjusted accordingly.
$500/month. Cancel whenever.

Book a 15-minute pipeline call, or reply "run it".

Back matter: the 5-question pre-pitch checklist

Run this on your own profile today, in 10 minutes:

Would a stranger know what you build, for whom, in 20 seconds?
Is there one named win visible on your profile from the last 90 days?
Is there one post from the last month that proves process, not opinion?
Could a buyer see who actually does the work, from the profile alone?
Is there one live page a stalled buyer can be sent back to, when they re-engage in a month?