Buying process

Frequently asked questions

last reviewed

The questions that come up before anyone talks about Azure, data or automation specifically — cost, contracts, access, and who we are not the right fit for. Silo-specific technical questions live on their own hub pages, not here.

Questions buyers actually ask

What does the assessment cost, and how is it priced?

Every assessment is fixed scope, fixed price and fixed end date, agreed in writing before it starts — never open-ended, and never billed by the hour without your prior agreement.

We have not yet published a number or a price band on this site. See how we work for the current state of that answer, and why we would rather leave it visibly blank than publish a range we have not committed to.

What do we actually sign?

Two separate documents, not one.

A short engagement letter scopes and prices the assessment itself. Only if you decide to proceed does a second, separate statement of work price the delivery work — built from what the assessment actually found. Signing the first never commits you to the second.

Full detail on both stages is on how we work.

What access do you need, and is it the same on every engagement?

Yes — one access policy, not a different one per silo.

  • Named individual accounts for every engineer who touches your environment. No shared credentials, ever.
  • Least privilege by default, with elevation that is requested, approved, time-boxed and logged.
  • Multi-factor authentication enforced on our accounts as well as yours.
  • A documented offboarding step, executed at the end of the engagement and evidenced to you.

During an assessment specifically, access is read-only — we inspect, we do not change configuration. The full policy, including subprocessors and data handling, is on the trust page.

Who actually takes the call, and how quickly do we hear back?

An engineer takes the call — the person who would actually scope the work, not a salesperson.

We have not yet confirmed and published a response-time commitment for new enquiries, or a turnaround for the written summary that follows the call. See how we work for the current state of that answer — we would rather say it is pending than promise a number nobody has agreed to honour.

Where is your team, and which entity do we actually contract with?

Delivery is from Costa Rica, in US business hours, under a US entity and US contracts — stated plainly here rather than left for a vendor-risk reviewer to find out.

AS DataWorks is the trading name for the data and Azure practice of Automated Solutions LLC. The registered entity name, state of formation and registered address are being finalised alongside the AS DataWorks DBA filing and are not yet published on this site — an absent address beats an invented one. See about and trust for the current state of the entity details.

What happens if the relationship ends — on either side?

Everything we build is yours from day one: infrastructure and pipeline code in your repository, documentation and runbooks written for your team, and cloud subscriptions billed to you directly.

We do not build anything only we can operate — no undocumented scripts on somebody's laptop, no configuration that exists solely in a console. If you decide to leave, or if we ever had to stop, a competent engineer could pick up the repository and the runbook and keep going. That is a design requirement of how we work, not a promise made after the fact.

Who should not hire you?

Five kinds of caller, honestly:

  • You need a regulatory audit, an attestation, or a signed compliance opinion. We build and document environments that stand up to those reviews; we do not issue the opinion.
  • You run a global estate measured in thousands of servers. A systems integrator built for that scale is the right shape of firm, and we will say so.
  • You want a decision, or a cutover, by Friday with no assessment. That is how a cloud bill nobody can explain gets created.
  • Your only driver is "the board wants a cloud strategy" with no operational problem underneath it. The assessment will probably tell you to stay where you are — and we will still charge for it.
  • You need a model that makes or materially influences a regulated credit, lending, insurance-pricing or employment decision. That needs a specialist model-risk practice, not us.

We would rather tell you this on the first call than after you have paid for a discovery phase.

Start with the assessment, not the migration.

Book an assessment call

30 minuteswith the engineer who would scope the work[PLACEHOLDER: written-summary turnaround, not yet committed]