Skip to content
MambaTech
How we work

Small firms cannot afford a failed programme

So engagements are structured to fail cheaply and early if they are going to fail at all: fixed boundaries, an acceptance test written before the build, and a measure agreed in advance.

Delivery method

Five stages, in order, every time

The sequence does not change with the size of the engagement. Only the time spent in each stage does.

  1. 01

    Diagnostic

    A written map

    We sit with the people doing the work and trace one operational cycle end to end, recording where information is re-entered, where it stalls and where it is lost. The output is a written map with the friction points ranked by what they cost.

  2. 02

    Scope and estimate

    A fixed proposal

    We propose the smallest change that resolves the most expensive problem, with a fixed boundary, a fixed price, and the acceptance test written down before either side commits.

  3. 03

    Build and pilot

    A system run in parallel

    The system is built against a copy of your real data and run alongside the existing process, so the two can be compared before anything is switched off.

  4. 04

    Handover

    Credentials and documentation

    Credentials transferred, documentation written for the staff who will run it, and training recorded so a new joiner can be brought up without calling us.

  5. 05

    Review

    A measurement against scope

    We measure against the acceptance test agreed at scoping. If it did not land, we say so and fix it. This is also where the next candidate workflow is identified.

The stage that saves the most money is the one where we recommend doing nothing. It happens more often than a technology firm is supposed to admit.

Engagement models

Three ways to work with us

There is no rate card. Each model is scoped to the bottleneck, the systems already in place, and the size of the team that has to run it afterwards.

Focused execution

Implementation sprint

For a firm with one pressing operational problem that does not warrant a multi-month programme.

  • Deliverable boundaries agreed in writing before work starts
  • A delivery date fixed in the engagement letter, not estimated afterwards
  • Written handover and recorded training for the staff who will use it
  • Defect support for an agreed period after go-live
Scope a sprint
Most engagements begin here Ongoing operations

Managed systems and helpdesk

Your IT function, run remotely. We keep the systems standing and improve one workflow each month.

  • Defined response commitment for staff laptops, email and network faults
  • Daily backup verification and endpoint patching
  • One workflow improvement delivered per month, agreed in advance
  • Monthly arrangement sized to seat count, reviewed quarterly
Discuss a partnership
Executive counsel

Fractional technology advisory

Senior guidance for founders and managing partners about to commit capital to software or infrastructure.

  • Independent vendor evaluation and contract review
  • Fortnightly technology steering session with the leadership team
  • Data Protection Act compliance and digital risk governance
  • Direct access to the engagement principal, not an account manager
Request a briefing
Operating principles

Four commitments, held to in writing

These appear in the engagement letter, not only on the website. If we break one, you are entitled to say so and to hold us to it.

01
Plain language
Technical decisions are explained in terms of operational impact, cost and accountability. If a recommendation cannot be justified in a sentence a director would repeat, it is not ready.
02
You own everything
Domain records, credentials, automation logic and source code are registered to you from day one. There is no proprietary layer holding your operations hostage, and no exit fee.
03
Measured against work
Every system we build must remove hours of repeated effort or protect revenue that is currently at risk. We agree the measure before the build, and report against it after.
04
We will say no
Where a spreadsheet, a written procedure or an off-the-shelf product already solves the problem, we will tell you and decline the work. Selling unnecessary systems is how firms end up here.
Commercial basics

Three commitments we will put in writing

These are the ones prospective clients ask about first. The full terms sit on a page of their own and are issued with every engagement letter.

You own it

Source code, automation logic, domain records and credentials are registered to your organisation from the outset. There is no proprietary runtime holding your operations, and no fee for leaving.

No vendor commission

We take no commission, rebate or referral fee from any software or hardware vendor. Where a product is right for you, you buy it directly at the price you negotiate.

Scope fixed before work starts

The deliverable, the price and the acceptance test are written down before either side commits. Work outside that scope is quoted and approved in writing, never invoiced as a surprise.

Full terms Privacy notice

Questions about either, write to mambatech@zohomail.com.

Start with the diagnostic

Fixed scope, written output, no obligation to proceed. It is the only sensible first step for both of us.

Request a diagnostic Review the service lines