01How to work with us

Have it built, or build with it.

The same three agents, reached two different ways. Either they deliver a working system to you, or you call them from your own environment and stay in the driving seat. Most teams start with the first and move to the second.

02Side by side

Same agents. Different amount of you in the loop.

Delivered
We build it and hand it over running

You describe the problem. We deliver the system.

The three agents take your requirement all the way to a running system on your infrastructure: scoped, priced, contracted, built, deployed and supported. You never assemble a team, brief one, or wait on one.

What you get
  • A fixed-scope statement of work before any money moves
  • Working software deployed to your cloud, VPC, on-premise or edge
  • The source, the infrastructure-as-code and the acceptance results
  • Full ownership of everything produced for you
  • Ongoing support from ChiefRelations after go-live
What you do
  • Describe the problem in chat
  • Approve the scope and the price
  • Provide access to the systems it has to touch
Embedded
Call the agents from your own stack

Your team, with three more specialists in it.

Invoke ChiefManager, ChiefArchitect and ChiefRelations from your own environment over an API. Scope and price work, generate contracts, provision infrastructure, run delivery. Your engineers stay in control and stop reaching for a general-purpose chatbot for every task.

What you get
  • API access to all three agents and the pricing engine
  • Schema-validated, versioned output with a confidence score on every call
  • Webhooks for signature, payment and deployment events
  • Self-hosting for air-gapped environments
  • Your data never used for training, by us or any model provider
What you do
  • Authenticate and call the endpoints you need
  • Build your own surface on top, or use ours
  • Keep your own review and approval gates
03Delivered

Seven steps from a sentence to a running system.

Every step names the agent accountable for it. You appear at three of them: describe, approve, provide access.

  1. 01you
    Intake
    ChiefManager

    Describe the problem in chat. No form to guess your way through, no discovery call to schedule.

  2. 02
    Classification
    ChiefManager

    The request is typed as Computer Vision, LLM, or Hybrid, and the prerequisites for that path open up.

  3. 03you
    Scope & price
    ChiefManager

    Requirements become a fixed scope, a timeline, and a price with the complexity drivers shown in the open.

  4. 04
    Contract
    ChiefManager

    A Statement of Work is generated with acceptance criteria and change-order terms, ready for signature.

  5. 05
    Payment
    ChiefManager

    Card, ACH, wire or purchase order. Delivery does not start until payment is confirmed.

  6. 06you
    Build & deploy
    ChiefArchitect

    Repositories, infrastructure and pipelines are generated and deployed to the target you specified.

  7. 07
    Run & support
    ChiefRelations

    ChiefRelations takes over at handover with the full project history, and stays the line your users talk to.

04Embedded

Three specialists your engineers can call.

Rather than reaching for a general-purpose assistant on every task and hoping the answer holds, your team calls agents that are accountable for a specific stage and return validated, versioned output with a confidence score.

ChiefManager

Runs the deal and the plan, from first message to signed contract.

ChiefArchitect

Takes the approved scope and ships the whole thing.

ChiefRelations

Knows the whole history, and answers for it after go-live.

What a call looks like
POST /projects/:id/estimate
{
  "billing": "YEARLY",
  "addOns": ["PRIORITY_SUPPORT"]
}

// -> 201
{
  "estimate": {
    "complexity": { "tier": "HIGH", "multiplier": 1.5,
      "drivers": ["HIPAA compliance constraints detected", ...] },
    "deliveryDays": 11,
    "baselineWeeks": 31,
    "timeReductionPct": 95,
    "lineItems": [ ... ]
  }
}
No amount field in the request. The price is computed server-side from stored requirements, so a caller cannot set it, and every driver behind it is returned with the figure.