We understand your needs before preparing a scoped quote. Future proposals are in USD; scope, deliverables, timing and terms are agreed separately. An enquiry is non-binding, not a purchase or booking.
Forward-deployed engineering
Embedded engineering around an agreed workflow.
AI isn't a coat of paint you apply from outside. It works when engineers learn the process from the people doing it, build alongside them, and stay through the messy weeks of real use. That's what we deploy.
Scoped quote · Embedded responsibilities and staffing agreed separately
Illustrative 30-day sprint plan
Build it, harden it, measure it, defend it.
Days 1–7
Build
- · Agent loop on one real workflow
- · Tools wired to your systems
- · Guardrails and step limits
- · Trace scope and redaction agreed
Days 8–14
Harden
- · Structured outputs with schema checks
- · Checkpoints so runs resume after failure
- · Explicit behaviour for bad data and dead APIs
- · Escalation to a person when unsure
Days 15–21
Measure
- · A golden set of real cases, hand-labelled
- · Evals for correctness and escalation
- · Cost per run tracked and reduced
- · Known failure modes written down
Days 22–30
Defend
- · Results against the audit baseline
- · What it does, what it must not do
- · Runbook and owner on your side
- · Decision: scale, change or stop
What you keep
Deliverables agreed at the start of each sprint.
A running workflow
A validated prototype or release increment, depending on scope, access readiness and safety gates. Production use requires separate acceptance.
An eval suite
Agreed test cases and results, where included in scope, to support retesting after a change.
An audit trail
Purpose-limited audit events for agreed actions, with sensitive-data minimization or redaction and defined access and retention. Raw prompts, inputs and outputs are not logged by default; implemented controls require evidence.
A trained owner
Someone on your team who can run it and knows when to call us.
How we work with people
The hard part is trust, not code.
The people whose work changes are the ones who know where the exceptions hide. We treat them as co-designers: they see the map first, they decide what stays human, and they get the time back — not a surprise.
What each person receives
User
Department head / COO
Needs: A system that matches how the team actually works, not how the vendor imagined it.
Doubt: Custom software sounds slow, risky and hard to maintain.
Proposed deliverables · agreed in scope
- • A mapped real-vs-documented process
- • A running system for one department
- • Runbooks the team can follow
Buyer
CFO / finance lead
Needs: A cost case that holds against current seat spend and manual hours.
Doubt: The return will be asserted, not measured.
Proposed deliverables · agreed in scope
- • A baseline agreed before work starts
- • A 3-year rent-vs-own comparison
- • A measured result against that baseline
Approver
IT / security lead
Needs: Something supportable that does not add shadow IT.
Doubt: Another system the IT team will be left holding.
Proposed deliverables · agreed in scope
- • Architecture and data model documentation
- • Access control and audit design
- • A named handover plan
Affected
The team doing the work
Needs: Less re-keying and fewer workarounds.
Doubt: Automation will be imposed without asking them.
Proposed deliverables · agreed in scope
- • Shadowing time where their workarounds are recorded
- • Clear lines on what stays human
Access we ask for — and how you take it back
- • Read access to the department's tools and exports
- • Shadowing time with named team members
- • No production write access during the audit
Access is limited to the department in scope and logged.
Initial inquiry: non-sensitive summary only. Later assessment: authorised redacted samples or read-only access. Sandbox and production write access require separate approval, minimisation, access expiry and retention agreement.
Agree revocation, working-copy handling, retention exceptions and confirmation responsibilities before access.
Next step
An audit can help select a sprint.
If you already know the workflow, we can scope a sprint directly. If not, the audit picks it for you.