Skip to main content

PROJECT / PROBLEM / NEXT STEP

Tell me what you're trying to fix or build

You don't need a polished brief. Send the problem as you understand it, what's already been tried, and what a good outcome looks like. If the right answer is a repair instead of a rebuild, I'll tell you. If you don't need me at all, I'll tell you that too.

Direct reply within 24 hours, Monday to Friday.

01 / Start here

Send a message

Useful things to include: what you're working on, what's broken or missing, what's already been tried, and what a good outcome looks like. A paragraph is plenty.

Please don't send passwords, API keys, credentials, or personal data about your customers. If I need access to something, we'll sort that out securely once we're working together.

Your message is handled directly by William Lodge. It isn't added to a CRM or mailing list. A server-side copy is retained so an email delivery problem doesn't lose your inquiry.

02 / Useful starting points

Good reasons to contact me

  • Something is broken and nobody agrees where the problem is.
  • You need a technical audit before deciding whether to rebuild.
  • You need a website, web app, internal tool, crawler, or automation built.
  • Search visibility has a technical cause you can't find.
  • You need someone to take over an existing codebase.
  • You want a second technical opinion on work someone else has done.
  • You run a venue, festival, or promotion business and need specialized SEO.
03 / After you send

What happens next

  1. 01

    I read it.

    I look at the problem before trying to sell you anything.

  2. 02

    I tell you what I think the next step is.

    That might be a quick repair, an audit, a larger build, or occasionally “you don't need me for this.”

  3. 03

    We agree scope before work starts.

    We agree on the work before it starts. No surprise expansion and no production changes without your say-so.

04 / Direct contact

Or reach me directly

READ / REVIEW / RETURN

Not ready yet?