Skip to content
TRDThe Research Desk, home

05 · Consulting

Technical consulting before you commit budget

Sometimes the right first step is not a build but a clear plan: what to automate, in what order, with which tools, and what it will cost to run. You get it in writing, and you are free to build it with anyone.

Free first conversation · No obligation · You own the code

§ 01Is this you?

You're likely in the right place if…

  • 01You know things are inefficient but not where to start.
  • 02You've been quoted very different prices and approaches for the same idea.
  • 03You inherited a system nobody can explain.

Sound familiar? Tell us which one on WhatsApp (opens in a new tab) and we'll suggest where to start.

§ 02Deliverables

What we build

  1. 01

    Process mapping

    A documented map of how work moves through your business today, with the bottlenecks marked.

  2. 02

    System and spreadsheet audit

    A review of existing scripts, sheets and tools: what's fragile, what's duplicated, what's at risk.

  3. 03

    Automation roadmap

    A prioritised plan with estimated effort, running costs and expected time saved per item.

  4. 04

    Build-vs-buy advice

    An honest recommendation, including when an existing product is the better choice.

§ 03Approach

How we build it

  1. Written deliverable

    Every engagement ends in a document you keep, not just a call.

§ 04FAQ

Questions about technical consulting

01What do we receive from a consulting engagement?

A written document you keep: the process map, findings, recommendations, priorities, estimated effort and running costs.

02Do we have to hire TRD to build what you recommend?

No. The roadmap is yours to use with any team. If we think an existing product is the better choice, we'll say so.

03Can you review a system someone else built?

Yes. We audit scripts, spreadsheets, databases and code, and explain in plain language what's fragile, what's at risk and what to fix first.

04How long does consulting take?

Most engagements take a few days to two weeks, depending on how many processes and systems are involved.

05How is the price decided?

After a short study of your process we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it; payment is typically 50% to start and 50% on delivery.

06Who owns the work when it's finished?

You do. Code, accounts and documentation are handed over in your name once the project is paid.

Next step

Ready to talk about technical consulting?

Not sure what to build yet? A short call to map the process and decide the first step, with no obligation to build with us.

Free first conversation · No obligation · NDA on request