Four disciplines that ship together.
Most engagements pull from more than one. Start where the problem is sharpest (integrations, custom builds, strategy, or a readiness check) and we compose the rest around it.
Book a Ship Audit →Start where the problem is sharpest.#
Six situations that walk in the door most often, each pointing at one service and one first step. Pick the row closest to what you are dealing with today.
A prototype that will not reach production
The model works in a notebook, but nobody has wired it into your production stack.
Retrieval keeps giving weak or wrong answers
Your retrieval pipeline returns confident answers that are incomplete or off-target too often to trust.
InfoSec is blocking the launch
Security or compliance flagged the AI feature, and nobody can answer their questions with evidence yet.
Diligence before an acquisition
You are buying or being bought, and someone needs a written, defensible read on the AI claims.
Inference spend is over budget
The monthly bill keeps climbing, and nobody can say which surface is actually spending it.
A pilot will not spread past one team
One team's pilot works, but nobody has a plan to build it out for the rest of the company.
AI Integrations
We connect models and agents to the systems you already run. We also build the retrieval layer under them.
Custom Development
We build applications and agents for the way your operation works. You own the code when we finish.
Strategy & Architecture
We tell you what is worth building, and where a bought product beats a custom one. Your engineers can check every step of the roadmap.
Readiness & Diligence
We check your data and infrastructure, then the process that must carry them. You get a written plan that your board and your CTO can act on.
How the four disciplines compose.#
The order most engagements actually run in, start to finish. Not every engagement starts at step one; a team that already has a roadmap can walk in at Build.
- Diagnose
-
A Readiness & Diligence assessment scores your data and infrastructure, in writing.
Hands off: A go/no-go call, with every real risk named.
- Decide
-
Strategy & Architecture turns the assessment into a phased roadmap and a cost model.
Hands off: A sequenced plan your board can act on.
- Build
-
Custom Development builds the system the roadmap named.
Hands off: A working system, tested against real cases.
- Ship
-
AI Integrations wires it into your stack, with evals and monitoring in place.
Hands off: A production feature, fully instrumented and owned by you.
What every engagement includes.#
Whichever discipline you start in, this is what transfers at handover. None of it is held back for a retainer or a support contract.
- An eval suite that catches regressions before your users do.
- Infrastructure-as-code for everything we build or configure.
- A runbook your team can run without us.
- Full source code, yours from day one.
- A clean handover: every credential and account transfers.
You own every line.#
Explicit handover terms — this is what transfers to you when we're done.
- All source code transfers to you at handover.
- Infrastructure-as-code for the whole system transfers to you.
- The eval suite and tests transfer to you.
- Credentials and accounts we provision transfer to you.
- Documentation and runbooks transfer to you.
- No retainer required to keep it running.
- You can operate and extend the system without us.
What it costs, and how it starts.#
Every engagement is scoped and priced after a short call or a diagnostic. A single-discipline engagement runs weeks. A combined one runs longer, priced the same way, one discipline at a time. You see the scope and the price before you sign anything.
See Pricing for how we structure a quote. Not sure where to start? Book a Ship Audit and get a written scope before you commit budget. Or talk to us directly.
Choosing and combining.#
What buyers ask us before they pick a service.
01 Which service should we start with?
Start with the discipline nearest the problem you can name today. Most engagements grow into more than one service.
Link to this answer: Which service should we start with?02 Can we combine more than one service in a single engagement?
Yes. Most engagements pull from at least two disciplines, and a few use all four inside one build.
Link to this answer: Can we combine more than one service in a single engagement?03 How do you size and price a combined engagement?
We scope it after a Ship Audit or a short call. Then we price it the same way the four services price on their own. See Pricing for the exact model.
Link to this answer: How do you size and price a combined engagement?04 What if we're not sure which situation fits our case?
Book a Ship Audit. It is the fastest way to get a written scope, whichever service ends up running it.
Link to this answer: What if we're not sure which situation fits our case?