Our approach
Clear scope.
Careful execution.
One recurring process. Four considered stages. A working relationship built on written clarity, not a calendar full of sales calls.
Describe the work.
A short written brief is enough to begin. Tell us the recurring trigger, current steps, systems, frequency and where things go wrong. Keep it non-confidential: do not send customer, payroll or financial records in the initial enquiry.
A shared understanding of the problem—not a sales call.
Agree the boundaries.
We assess fit, access and the quality of the inputs. If a narrow workflow makes sense, you receive the proposed outcome, checks, exclusions, responsibilities and price in writing. If it does not fit, we say so. Work begins only after the scope and price are agreed.
Fixed scope. Quoted in writing.
Build with controls.
Map the normal path and the exceptions. Confirm who reviews uncertain items and who approves financial actions. Build and test against agreed acceptance checks, including missing inputs, duplicate requests and recovery. We agree any live access separately and do not assume permission from an enquiry.
A tested process, a manual fallback and visible failures.
Hand over properly.
Provide documentation and a walkthrough. Identify the owner, monitoring responsibilities and what to do when an export or connected system changes. Verify the workflow against the agreed checks with your team, and define any ongoing support separately rather than implying an unlimited commitment.
Your team can understand, operate and maintain the work.
What belongs in the first brief?
The trigger, the steps, the systems, the approximate frequency and the outcome you want. Describe the problem in general terms. A fictional example is fine; actual confidential records are not needed.
Submitting the form records an enquiry privately. It does not send an automated confirmation email, book a call or authorize access to your systems.
From reading to doing