Skip to main content

Services

Six rungs.One ladder.

Start where you actually are. Most people begin with a Survey and end up on a Retainer, but nothing here requires you to buy the next thing.

The wholespec sheet.

Fixed scope means a fixed price, quoted as a number rather than a range. Never hourly. Model and third-party costs sit on your own accounts and stay yours.

  1. 01

    The Survey

    Find what is worth automating

    Over two weeks, we speak with the people doing the work and map the current workflow. You receive a ranked list of automation opportunities, estimated savings, and a fixed quote for the first build. If a simpler tool or spreadsheet formula is enough, we recommend that instead.

    • Ranked list, scored
    • A fixed price for build one
    • Fee credited in full
    Open The Survey→
    Time
    2 weeks
    Terms
    Fixed price, quoted up frontCredited in full against The Build
  2. 02

    The Blueprint

    Turn an idea into a spec

    Four weeks on a single initiative. We take an idea that lives in your head and turn it into documentation a development team can execute from, including the architecture, the integration map, the threat model and a budget that survives contact with a CFO.

    • Architecture and integrations
    • Threat model
    • A budget that survives a CFO
    Open The Blueprint→
    Time
    4 weeks
    Terms
    Fixed price, quoted up frontHalf credited against The Build
  3. 03

    The Build

    Live in 30 days, or free

    One workflow, live in your own cloud and your own accounts, inside 30 days. With an eval suite, a runbook, a rollback path, alerting, and your team trained on it. Then we do the next one. This is the whole business: a thing that runs on a Tuesday when nobody is watching.

    • Your cloud, your repo
    • Evals, runbook, rollback
    • 30 days hypercare
    Open The Build→
    Time
    30 days to the first workflow in production
    Terms
    Fixed price, fixed scopeIn production in 30 days, or you do not pay
  4. 04

    The Hardening

    Break it before someone else

    One to two weeks on an AI system that is already live, or on the AI coding tools your developers are already using. We red team it, scope the permissions properly, and hand you a severity-rated report with the config changes already made. Run by Atul, whose 15 years are mostly in the part of this that goes wrong.

    • Red team, scored before and after
    • Least-privilege tool calls
    • Incident playbook
    Open The Hardening→
    Time
    1 to 2 weeks
    Terms
    Fixed price, quoted up front
  5. 05

    The Retainer

    Keep it alive when models move

    Automation is not a project that finishes. Providers retire models, upstream APIs change their schema without telling you, and quality drifts quietly for weeks before anybody notices. The Retainer is the answer to the only question that matters six months after launch: is it still working, and who would know?

    • Migrations included
    • Drift watched on a schedule
    • One new workflow a quarter
    Open The Retainer→
    Time
    Month to month, 30 days notice either way
    Terms
    Monthly30 days notice. No lock-in, rate held
  6. 06

    The Pair

    Both of us, on your backlog

    Some companies do not need a discovery process. They need two people who can build, who have shipped in production before, and who can start on Monday. The Pair is us inside your team: your repo, your standup, your backlog, moving at the speed you actually work at.

    • Starts this week
    • Ships weekly
    • Documented as we go
    Open The Pair→
    Time
    Month to month, 30 days notice either way
    Terms
    MonthlyBoth of us. One of us part time, quoted lower

How it is built

Agents getcredentials.Act like it.

Most of what goes wrong is a default nobody changed. Atul has fifteen years of production engineering and owns this on every engagement.

We do not hold SOC 2 or ISO 42001 certification. If your procurement process requires a certified vendor, we will let you know on the first call so you can choose a suitable partner.

Runtime
Your cloud. Your keys. Your accounts
Tool calls
Least privilege. Destructive actions gated
Training
Provider tiers that exclude your data
Models
Version pinned. Never whatever is newest
Quality
Scheduled evaluations with visible results
Alerts
Failure, cost spikes, upstream schema drift
Before ship
Tests for prompt injection and data exposure
On exit
Code, prompts, evals, runbooks. All yours

Objections

The questionsthat kill deals.

Where does our data go, and will it be used to train a model?

Your system runs in your cloud, using your API accounts and keys. We choose business or enterprise tiers whose terms exclude training on your data and confirm this in writing. During a build, we see only what you share on screen. The Survey identifies any data that must stay within your environment so the system can be designed around that requirement.

Do you hold SOC 2 or ISO 42001?

No. We do not hold either certification. We can answer your security questionnaire, apply least-privilege access, and have Atul own the engineering decisions. If your procurement process requires a certified vendor, we will say so on the first call.

Who owns the code?

You own it from the first commit. Code, prompts, system instructions, evaluation sets, documentation, and runbooks live in your repository. You keep the system and its accounts if you stop working with us.

What happens when the model we built on is retired?

We pin model versions and use evaluation checks to assess a replacement before switching. Model migration is included in a retainer. Without a retainer, we will still let you know when a migration is needed.

How do we know it still works in six months?

Scheduled evaluations track quality over time so you can spot changes early. Alerts also cover failures, cost spikes, and changes to upstream APIs or data formats.

You are two people. What if one of you is unavailable?

Both of us stay involved in every engagement, and we document the work as we build. Either of us can step in. Your team also keeps the code, accounts, and documentation, so another builder can take over if needed.

Can our own developers build from your plan?

Yes. The Blueprint includes requirements, architecture, and acceptance criteria that your developers can work from. You can build it in-house or ask us to help with specific parts.

What does it cost to run once it is live?

Model and third-party software costs are charged to your own accounts. We estimate running costs before you commit and report the cost per run during the build. The final amount depends on the workflow and how often it runs.

What if the first project does not work?

The Build includes a shipping guarantee: one workflow in production in 30 days, or you do not pay for the build. This covers delivery, not business results, which also depend on your data and team.

Do you work with companies outside your listed industries?

Yes. Our listed industries are areas where we have already delivered work. We also work with other teams and will tell you during the first conversation if your domain requires expertise we cannot offer.

How fast can you start?

We take on no more than three active engagements at a time. A Survey can usually start within two weeks, depending on availability. We will confirm timing before you commit.

Is there a lock-in or a minimum term?

There is no platform lock-in. Fixed-scope work has an agreed scope and price. Retainers and embedded work run month to month, with 30 days notice from either side and the rate held for the engagement.

Not surewhich rung?

Book a thirty-minute conversation about your workflow and goals. We will help you decide whether we can make a useful difference.

Book 30 minutes

3 engagements at a time