skip to content

contact — the direct line

No forms. No funnels.

One address, read by the person who does the work. Write from your own mail client — or compose below: it runs entirely in your browser and opens as a draft in your mail app. Nothing is submitted, stored, or scored.

to: jamie@jamiemckaye.com · replies from the same address

the brief compiler

runs in your browser — nothing submits anywhere

01 — what is this about

02 — in your words

03 — your site (optional)

transmission preview

line: open


to      jamie@jamiemckaye.com

subject Brief


(the compiled brief appears here)

0/1400

opens as a draft — you press send

scope sheet — what a reader can already find in this draft

term detection only · plain prose always sends

shapes — how engagements usually run

01

the audit

a deep technical read of how machines see your site — finished as shipped fixes and a plain-english account of what moved, not a backlog document.

02

fractional head of search

your senior search function, part-time: strategy, prioritisation, and the hands that implement it — without the full-time seat.

03

embedded technical lead

inside your team and your codebase for the duration of a hard problem — migrations, rebuilds, recoveries — until it's boring again.

04

the build

the thing engineered end to end and shipped to production — a site, an instrument, a machine surface — with the reasoning on the record.

after you write — what actually happens

  1. 01

    Your brief lands in my inbox — not a CRM, not a triage queue. I read it myself.

  2. 02

    I reply with an honest read: whether the problem is one I'm the right person for, what shape the engagement would take, and what I'd want to see first. If we're not a fit, I'll say so and point you somewhere better.

  3. 03

    Scoping happens in one call or one email thread — whichever you prefer. Pricing and availability live there too, not on a rate card page.

  4. 04

    Work opens on the record: a frozen inventory of where things stand, so every claim about progress has a baseline.

read by me · answered by me

hersham, uk · london · remote (uk & us)

straight answers — including “don't hire me”

protocol — what this page refuses to be

01

no crm

replies come from the same address you wrote to — the person who does the work reads the mail.

02

nothing stored

the compiler above runs client-side. This page has no backend to leak, lose, or resell your brief.

03

agents welcome

machine-readable engagement is live: request_engagement on this site's mcp server. Or email like a human.