The TechGuidr Method

Know what happens next and what you’ll have to show for it

Every engagement starts with the decision or outcome you need. Reviews and diagnoses end with a written answer. Anything we build follows the method: start small, prove the value against a baseline, then extend only where the numbers justify it.

Built for tomorrow. Delivering today.

Before the technology

Start with the work, then the system

Before choosing technology, we look at where time goes, which decisions are made and where the organisation gets stuck. Where technology is part of the answer, we then design the systems, data, AI and operating model the new way of working needs.

What a working system looks like

Sources, platform, AI layer, product

Where the answer includes a system, this is how we scope it and report on it: which sources we connect, what the platform has to do, where the AI layer sits and what people end up using.

  • SourcesCRM, ERP, documents, events, third-party data
  • PlatformIngest, govern, serve
  • AI layerRetrieval, reasoning, evaluation
  • ProductThe thing people use on a Monday morning

The method

How we break down and build the work

The method has three phases, Evaluate, Engineer and Evolve, with five steps inside them. Decide, Transform and Operate are what you can buy; the method is how we deliver any of it.

BaselineStart smallBuildProveExtend
  1. EvaluateUnderstand the work and agree what success looks likeBaseline, Start small
  2. EngineerBuild it, and prove it against the baselineBuild, Prove
  3. EvolveExtend what works and keep improving itExtend
Evaluate · Step 01 of 05

Baseline

Before anything changes, record how the work runs today: the time it takes, its quality, the rework and the cost. Agree the acceptance criteria the result must meet.

What you receive
A baseline of the work today and acceptance criteria agreed up front. Assumptions and missing evidence are recorded.
What we check
Task time, error rate, quality, rework or running cost: the numbers the result will be judged against.

Working agreement

The working agreement

Before work starts
A written scope covers deliverables, price, exclusions, dependencies, data handling and the people involved. A retainer also specifies capacity, availability, term and notice.
During delivery
The update cadence follows the engagement. Updates cover completed work, next steps, decisions and risks. Material risks are raised when identified through the agreed escalation route.
When something changes
Changes to scope, price or timing are recorded and agreed before additional work begins. Our own estimating errors within the agreed fixed scope are our responsibility.
Before acceptance
The plan identifies the delivery lead, review responsibility and the client's acceptance owner. Independent security or specialist assurance is separately identified when required.
At handover
You receive the outputs in the scope. For software this includes agreed source and configuration access, operating information and ownership or licence terms.
After the engagement
Follow-up, support, cover and incident response are defined in the agreement. A short review does not create an ongoing support commitment.

Engagement and ownership

What the method covers, and what stays yours

The method follows the work you buy

The method is how we deliver every engagement. Decide work, such as the AI Review, Discovery, an Independent Review or Technology Due Diligence, is the Evaluate phase on its own and ends with a written answer you own; senior leadership runs on a monthly remit. Transform work runs through all three phases, from baseline to proof; a rescue starts with a diagnosis, and any repair follows the method. Operate work is the Evolve phase on a monthly scope, with the measures agreed before it starts.

Compare the services

Decisions, ownership and interests

Our review outputs are yours to use without buying delivery from us. Ownership, licensing, handover and exit arrangements are agreed in writing before delivery, so you know what you can take forward, how your systems remain accessible and what happens if you move to another provider. Client-specific work, existing TechGuidr products, third-party components and source access are treated separately in that agreement, and any help with a move to another provider is scoped and priced at the time. We disclose relevant commercial interests, including a recommendation to use our own products or delivery services.

Meet the people who lead the work

Independence

How we stay independent and accountable

We take no vendor commissions and disclose any interest in our own products, so the advice does not change with what we could sell you.

  • Buy, build, improve what you already run or do nothing: each is a real answer, and a review stands alone
  • Vendors and platforms judged on what suits you, including the ones you already pay for
  • Our fees and the running cost of what we recommend set out before you commit
  • Handover and training so your own people can run, change or replace what we build
  • Agents work within agreed permissions, with a named person accountable for what they do
  • Before we build or change anything, we agree the baseline and measure the result against it

What needs to be different at the end?

Tell us the outcome or decision you need. We can then work out the smallest useful engagement and what evidence it should produce.