TalonInsights Book a Groundwork Visit

Method, not magic.

Every job runs on the same spine — on-site discovery, a written fixed-price scope, milestone delivery, full handover. This page is the detail behind that: how each kind of work actually gets done, and the standards it's held to. If you like knowing how the sausage is made, this is your page.

Every job

The spine: four steps, in writing.

  1. Groundwork

    I come to your premises and map how the work actually flows — as observed, not as assumed. The Groundwork Visit has its own page.

  2. Fixed quote

    A written scope: what's being built, what it costs, what's deliberately excluded, and milestone dates. Changes go through a written variation with its own price.

  3. Build

    Delivered against the milestone dates, with working software or pages to look at along the way — not a progress report, the actual thing.

  4. Launch & handover

    Domain, code and content transfer on full payment, with documentation and a bug-warranty period. You are never locked in to me.

Custom software

Watch the job before writing the tool.

Internal tools fail when they encode how a manager thinks the work happens. So the method starts on the floor: watching the real process, finding the one workflow where software genuinely pays, and building only that.

  • Scope one workflow at a time. A small tool that gets used beats a platform that doesn't.
  • Real infrastructure from day one. A Supabase database, authentication with roles, and a GitHub-to-Vercel pipeline — so every change is reviewable and reversible.
  • Handover documentation as standard, written so another developer could take over.

Worked example — David Jackson & Son

  • Eight-stage drag-and-drop production scheduler with automatic breach detection on stage deadlines.
  • Started life on localStorage to prove the workflow, then migrated to a Supabase backend once it earned the infrastructure — spend follows evidence, not hope.
  • Two-factor authentication, and autosave with backup and restore — a planning tool is only trusted if it never loses work.
  • In daily use planning real factory jobs.
Full case study

Websites

Words first, design second, speed always.

A website is an argument for hiring you. The argument gets written before anything gets designed — then the build's job is to deliver it fast, to everyone, on anything.

  • Message before mockups. What you do, who it's for, why you — agreed in writing before design starts.
  • Performance budgets, not promises: LCP under 2.5s, INP under 200ms, CLS under 0.1 — measured, not claimed.
  • WCAG 2.2 AA accessibility as standard. A site some customers can't use is a site that doesn't work.
  • Schema markup and SEO foundations wired in at build time, not bolted on later at extra cost.

Worked example — WulfTek Tuning

  • A Three.js engine-bay renderer where an interactive moment genuinely earns its place — the rest of the site stays fast and plain.
  • Registration lookup with a graceful fallback chain: live data, then cached, then a generic model. The page works even when the data doesn't.
Full case study

Local SEO

Deliverables you can audit.

SEO has a snake-oil problem, so the method is built to be checkable. Each tier is a list of named deliverables done every month, and the monthly report shows each one happened — alongside the numbers that matter: rankings, calls, enquiries.

  • Google Business Profile first — the single biggest local-pack lever, and the cheapest.
  • Citations with identical name, address and phone across the directories that actually count.
  • Content aimed at what buyers type, not vanity keywords nobody searches.
  • If it isn't working, the report says so. Three-month minimum, then monthly rolling — no lock-in.
Tiers and pricing

What a monthly report contains

  • Rankings for the terms we agreed to chase, with movement.
  • Google Business Profile: calls, direction requests, website clicks.
  • The deliverables list, ticked off — or flagged, with the reason.
  • Plain-English commentary: what happened, what's next.

Research & strategy

A question, a model, a decision.

Research engagements start by pinning down the decision you actually need to make — then build just enough evidence to make it confidently. The output is never a data dump; it's a recommendation with the reasoning shown.

  • Define the question first. "Should we open the second unit?" is answerable; "do some market research" isn't.
  • Model when it pays. Where a decision hangs on uncertainty, I build a real statistical model rather than guessing politely.
  • Show the sensitivity. You see which assumptions actually move the answer — so you know what to watch.

Worked example — Alive Network

  • A Monte Carlo turnaround model run over ten million iterations, so the recommendation ships with a probability distribution, not a single hopeful number.
  • Sensitivity analysis identifying the assumptions that move the outcome.
  • Delivered as a twenty-two slide decision document: what to do, what it costs, what could go wrong.
Full case study
  1. 01

    Everything in writing

    Scope, price, dates, exclusions, variations. If it isn't written down, it isn't agreed — which protects you as much as me.

  2. 02

    Fixed means fixed

    The price in the scope is the price on the invoice. New scope gets its own written price before the work happens.

  3. 03

    You own everything

    Domain, code, content — transferred on full payment, with documentation. No hostages, ever.

  4. 04

    Plain English

    If I can't explain a technical choice in one sentence you'd repeat to a mate, I don't get to make it.

  5. 05

    One working day

    That's the longest you'll wait for a reply, from first enquiry to long after launch.

Get started

Book a Groundwork Visit — I'll come to you.

No jargon, no pressure, and a written scope you keep whether or not you go ahead. I reply within one working day.

Book a Groundwork Visit Call __PHONE__