How we work
Everything a buyer needs to know before the first call: what is in scope, how the work runs, who does what, what it costs, what controls ship with it and what you receive at each step.
An engagement covers one business workflow from trigger to completed outcome. Not a department, not a platform, not a roadmap.
In scope
Out of scope
Three phases. Each is priced before it starts, each ends in a decision you make with evidence in hand, and you can stop after any of them.
Phase 1 · Weeks 1 to 3
Fixed fee, quoted before we start and credited toward the build. We inventory current AI use, map one to three workflows, baseline cost and quality, and compare non-AI alternatives.
Phase 2 · Weeks 4 to 12
Scoped and priced from the assessment. We build the smallest production-relevant version, connect it, instrument every step and run it on real work with the people who own it.
Phase 3 · Monthly
A monthly retainer sized to run cost and review load. We track outcomes, exceptions, human review and spend against the baseline, then expand, improve or stop.
Most stalled projects stall on the client side, for want of a decision or an access request. We say up front what we need and when.
xGold Tech
You
You know the price of each phase before it starts, and you can stop after any of them.
Assessment
Quoted before we start. Credited in full toward the build if you continue within 60 days. If the assessment shows there is no case, you keep the map and the baseline.
Build and pilot
A fixed price for a defined workflow, acceptance scorecard and go-live date. Scope changes are priced as changes, in writing, before the work.
Operate
A retainer based on run cost, review volume and support terms. No minimum term. Model and infrastructure costs are passed through at cost, visible on the dashboard.
What drives cost: the number of systems touched, the volume and variety of documents or cases, the approval steps you require, and how much of the work is already structured data versus free text.
We do not replace systems, migrate data or stand up a parallel stack. We connect to what is there, under the rules you already have.
Your systems
ERP, CRM, HR, ticketing and document stores stay the systems of record. We read from them and write back through their supported interfaces.
Typical targets SAP, Oracle, NetSuite, Salesforce, ServiceNow, Workday, Microsoft 365, Google Workspace.
Your identity and access
Every assistant and agent gets its own identity under your single sign-on, with least-privilege access scoped to the workflow and approval gates where you already require them.
Permissions are inherited from the source system. Nothing runs under a shared or personal login.
Your data and security policy
Processing runs in your cloud tenant or your approved providers. Your classification, retention and logging rules apply. Your data is not used to train anyone's model.
Logs ship to your monitoring and audit tools.
It will, occasionally. The question is whether anyone notices, how fast, and what it costs. Every build ships with these in place.
Before the build starts we agree one primary metric with the process owner and baseline it. Everything below is tracked against that baseline, by your finance team, not ours.
The scorecard
The value rule
Nobody honestly can. We guarantee the baseline, the measurement and the stop rule, and we report before and after in units: hours, days and dollars per item, never a percentage without its denominator.
Hours saved are capacity, not savings. The business case counts spending avoided, capacity redeployed and margin created, minus build, license, model, review and run costs.
A 30-minute call. You leave with a one-page map of the workflow you picked, what it costs you today and whether it is worth a fixed-fee assessment.