1. Home
  2. AI development
  3. Enterprise

Enterprise AI

Enterprise AI: a pilot on one team, built inside your cloud

We start enterprise work with a vendor onboarding package and a security review answered with the actual setup, then a pilot scoped to one team. The system is built in your own cloud tenant or on your servers, signs people in through your identity provider and writes logs that your IT team can read.

  • Prices published on the site
  • First working version in two weeks
  • Support month to month, cancel any time

A pilot on one team, with the paperwork done first

Security and procurement teams ask the same questions in the same order: who is this vendor, what will it touch, where does the data go and who can switch it off. We answer them in writing before any build starts, and we scope the first project to one team, one task and one set of data, so the review covers something real and small.

Because the system runs in your cloud tenant or on your servers, your own controls apply to it: your identity provider, your logging, your network rules and your key management. We work as a contractor inside your environment, so the system and its data live in your accounts.

Two phases, with your approval between them

Before we build

  1. Vendor onboarding

    A W-9, our certificate of insurance, and our state and federal registrations.

    Procurement
  2. Security questionnaire

    Answered with the actual setup, such as where the system runs, who can sign in and what is logged.

    Security
  3. Data-flow diagram

    One page showing which model sees which data, and where it is stored.

    Security
  4. Pilot scope

    One team, one task, one set of data, and the measure that decides whether the pilot worked.

    Scope

Build and hand over

  1. Built in your cloud

    In your own cloud tenant or on your servers, with accounts opened in your company's name.

    Build
  2. Your sign-in

    People sign in through your identity provider, so access is managed in your directory.

    Access
  3. Logs your IT can read

    Application and action logs go where your IT team already looks.

    Audit
  4. A runbook

    How to start, stop, back up and restore the system, written for your IT team.

    Handover
  5. Support under contract

    Care or Active, month to month.

    Support

The gate is your security and procurement sign-off. The build does not start before it.

Registrations and insurance your team can check

Each item is also on Government and public agencies and Trust and verification, so your team can compare it with the public record.

State certification

California Certified Small Business, DGS #2055405.

Federal registration

Registered in SAM.gov, UEI J5DBZNBAGMC5, CAGE 25RP4.

General liability insurance

General liability insured. The limits are listed on Government and public agencies, and a certificate of insurance is available on request.

When this way of working suits you

A good fit when

  • You can name one team and one task for a first pilot
  • Your policy lets a contractor build inside your cloud tenant
  • You want the system in your own accounts and repository
  • Your IT team will own it after handover

Another vendor suits better when

  • Your policy requires the vendor to host the system itself under the vendor's own audit report
  • The first project has to cover several departments at once, because we widen the scope after a pilot on one team
  • The work needs access to patient records, which we do not take

A pilot is connected systems, a rollout is a full build

Connected systems: $6,000 to $15,000, 4 to 8 weeks

Several systems made to work as one: integrations, roles, reports.

Full build: from $15,000, from 8 weeks

Custom software built from scratch, over a longer schedule.

A pilot on one team, built in your tenant with sign-in through your identity provider and logging, usually lands in connected systems. A rollout across several teams, roles and source systems is a full build.

Care $300 to $500 a month. Active $750 to $1,500 a month. AI model usage, GPU time and hardware are paid to the provider, on accounts in your name.

Questions from security and procurement teams

Can you complete our vendor security questionnaire?

Yes. We answer it with the actual setup of your pilot: where it runs, who signs in, what is logged and which model sees which data. Where a question has no plain yes, we write what we do instead.

Do you hold a SOC 2 report?

No. If your policy requires a SOC 2 report from every vendor, we do not meet it, and it is better to know that before the review starts. Where your policy allows a contractor to build inside your own cloud tenant under your access rules, that is how we work, and we put it in the pilot scope in writing.

What do you send for vendor onboarding?

A W-9, a certificate of insurance and our registrations: California Certified Small Business, DGS #2055405, and SAM.gov, UEI J5DBZNBAGMC5, CAGE 25RP4. If your portal asks for something not on this list, send us the form and we answer with what is true.

Which AI model sees our data?

We name it in the data-flow diagram before the build starts. It can be a model API called from your own cloud account, or an open-weight model such as Llama or Qwen on your servers when the data cannot leave. We build with Claude, Gemini and open-weight models, and with OpenAI if you already use it.

How long does a pilot take?

The first working version is ready two weeks after we have access to your environment. A one-team pilot with sign-in and logging usually takes 4 to 8 weeks. Your internal security review runs on your own schedule, and our clock starts when access is in hand.

Who supports the system after handover?

We do, month to month, under Care at $300 to $500 a month or Active at $750 to $1,500 a month. The runbook lets your own IT team run it without us, and the accounts and repository are in your name, so you can end support at any time.

Tell us what's slowing you down.

You get a free written review by email within two business days.

Only your email and the task are required. No passwords or client data needed.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.